Documentation

SenseLinks docs

Everything you need to deploy agents on Windows and Linux, connect them to your SenseLinks server and keep them running.

Overview

SenseLinks has three main parts:

  • Agents run on the machines you want to protect. They collect logs, file changes, software inventory and configuration data, and send them to the server.
  • The server (manager) analyses the data with detection rules, raises alerts and runs automated responses.
  • The dashboard is the web interface where you see alerts, investigate events, deploy new agents and track vulnerabilities and compliance.

Requirements

PlatformSupported versionsArchitectures
WindowsWindows 10, 11, Windows Server 2012 R2 and later32 and 64 bit
Linux (DEB)Ubuntu, Debian and derivatives64-bit Intel/AMD (x86_64)
Linux (RPM)Red Hat, CentOS, Rocky, AlmaLinux, Fedora, Amazon Linux, SUSE64-bit Intel/AMD (x86_64)
macOSNot available yet

The agent uses about 35 MB of RAM and very little CPU in normal operation. You need administrator (Windows) or root (Linux) rights to install it.

Network ports

Open these ports on the SenseLinks server and in any firewall between it and your agents:

PortProtocolUsed for
1514TCPAgent connection (events and status)
1515TCPAgent enrolment
8088TCPAgent package downloads
443TCPDashboard (administrators only)

Install from the dashboard

The easiest way to install an agent is from the dashboard. Open Agents → Deploy new agent, choose the operating system and architecture, enter your server address and copy the generated command. It does the same steps as the manual commands below.

In the commands below, replace SERVER with the address of your SenseLinks server and VERSION with the agent version shown in your dashboard.

Windows agent

Open PowerShell as Administrator and run:

Invoke-WebRequest -UseBasicParsing -Uri "http://SERVER:8088/packages/senselinks-agent-VERSION.exe" `
  -OutFile $env:TEMP\senselinks-agent.exe
Start-Process -Wait -FilePath $env:TEMP\senselinks-agent.exe -ArgumentList '/S','/SERVER=SERVER'

The installer sets the server address, enrols the computer and starts the agent. Options: /NAME=name (the name shown in the dashboard; default: the computer name), /GROUP=group1,group2 and /PASSWORD=x (when your server asks for an enrolment password).

One-file installer (no internet needed on the computer)

Your server also builds a full installer with the agent and all protections, already set up for that server. Download senselinks-agent-full-VERSION.exe or .msi from http://SERVER:8088/packages/installers/, from Deploy new agent in the dashboard, or with Get installer for other computers in Manage Agent on a Windows computer. Copy it to the computer and run it as Administrator:

senselinks-agent-full-VERSION.exe /S /SERVER=SERVER
msiexec /i senselinks-agent-full-VERSION.msi /qn SERVER=SERVER

/SERVER= (MSI: SERVER=) is only needed to change the server already stored in the installer. Other options: /GROUP=name and /PASSWORD=x (for the MSI: GROUP=, PASSWORD=). If the server cannot be reached during the install, the agent enrols itself later.

Deploy to many Windows computers (Active Directory)

In a Windows domain, a Group Policy can install the agent on every computer in chosen OUs. Each computer installs, enrols and starts the agent at boot, and upgrades it when your server has a newer version. Download the three scripts from http://SERVER:8088/packages/ad/ into one folder on a domain controller (or a machine with the Group Policy tools) and, as a domain admin, run:

# Create the policy and link it to an OU: computers install the agent at their next restart
.\New-SenseLinksAgentGpo.ps1 -Manager SERVER -TargetOU 'OU=Workstations,DC=corp,DC=local'

# Optional: install now on the computers that are running (uses WinRM)
.\Invoke-SenseLinksAgentInstall.ps1 -Manager SERVER -SearchBase 'OU=Workstations,DC=corp,DC=local'
  • -Group NAME enrols the computers into an agent group; -GroupFromOU uses each computer's OU name as its group. Create the groups in the dashboard first.
  • -RegistrationPassword is needed if your server requires an enrolment password.
  • The computers need ports 1514, 1515 and 8088 to the server. Each one logs to C:\Windows\Temp\senselinks-agent-install.log.

The README.md in the same folder lists all options.

Sign in with Active Directory and find unprotected machines

In the dashboard, open Management → Active Directory (administrators only):

  • Connection: the domain controllers, a service account (a plain domain user is enough) and the search base. Test connection shows how many users, groups and computers it found.
  • Permissions: choose which AD groups get full access and which get read-only access. Their members then sign in with their AD user name and password.
  • Machine discovery: where SenseLinks looks for computers that have no agent: the AD computer list, the domain's DNS records, DHCP leases, the agents' neighbour reports and, optionally, a scan of chosen subnets.

Management → Unprotected machines lists what was found, with coverage per subnet, and gives the install command for the selected computers. New unprotected machines also raise an alert. To use DHCP leases, add the agents of your Windows DHCP servers to the agent group senselinks-dhcp.

Detect attacks on Active Directory

Install the agent on every domain controller, then run this on each of them as a domain admin (it reports first; -Apply turns on the missing audit settings):

.\Enable-SenseLinksAdAuditing.ps1
.\Enable-SenseLinksAdAuditing.ps1 -Apply

SenseLinks then alerts on Kerberoasting, AS-REP roasting, DCSync, password spraying, waves of account lockouts, changes to admin groups, AdminSDHolder and Group Policy. The home page shows the AD alerts of the last 24 hours.

Linux agent

On the computer, as root or with sudo (Debian, Ubuntu, Red Hat, CentOS, Rocky, AlmaLinux, Amazon Linux, SUSE; 64-bit Intel/AMD):

curl -fsS http://SERVER:8088/packages/linux/senselinks-agent-install.sh | sudo SENSELINKS_SERVER='SERVER' bash

The script picks the right package (DEB or RPM) from your server, installs it, enrols the computer and starts the agent.

A few seconds after the agent starts, it shows up as Active in the dashboard.

macOS agent

Not available yet. The SenseLinks agent for macOS is in preparation. This section will hold the installation steps once it is released. If you need to protect Mac computers, contact us.

Manage the agent

WindowsLinux
StartNET START SenseLinksSvcsudo systemctl start senselinks-agent
StopNET STOP SenseLinksSvcsudo systemctl stop senselinks-agent
StatusGet-Service SenseLinksSvcsystemctl status senselinks-agent
ConfigurationC:\Program Files (x86)\ossec-agent\ossec.conf/var/ossec/etc/ossec.conf
LogC:\Program Files (x86)\ossec-agent\ossec.log/var/ossec/logs/ossec.log

To uninstall: on Windows, remove SenseLinks Agent in Settings → Apps. When the agent's self-protection is on, Windows refuses that: get an Uninstall token on the computer's page under Computers in the dashboard and run, in PowerShell as Administrator, & "C:\Program Files (x86)\ossec-agent\uninstall.exe" /S /TOKEN=TOKEN. On Debian/Ubuntu run sudo apt-get remove senselinks-agent; on RPM systems run sudo rpm -e senselinks-agent.

Troubleshooting

The agent doesn't appear in the dashboard

  • Check that the machine can reach the server on ports 1514 and 1515 (Windows: Test-NetConnection SERVER -Port 1514; Linux: nc -zv SERVER 1514).
  • Check the server address you gave: running the install command again with the right address corrects it.
  • Read the agent log (see the table above).

The agent shows as Disconnected

Make sure the agent service is running and that no firewall blocks port 1514 between the agent and the server. Then restart the agent.