Subscribe to the Taegis™ XDR Documentation RSS Feed at .

Learn more about RSS readers or RSS browser extensions.

Taegis™ Linux Agent Installation

integrations endpoints edr taegis agent secureworks


Prior to installation, review requirements and follow prerequisite steps on Taegis™ Endpoint Agent Information and Prerequisites.

Data Provided from Integration

  Alerts Auth DNS File Collection HTTP NIDS Netflow Process File Modification API Call Registry Scriptblock Management Persistence Thread Injection
Taegis™ Linux Endpoint Agent            

Secure Boot Enabled Instructions

If Secure Boot is enabled, follow these key enrollment with mokutil steps first; otherwise, proceed to Installation.

  1. Download and import the Secureworks driver signing key:
curl https://drivers.taegiscloud.com/scwx-falco-signing-cert.der -o /tmp/drivers.der && sudo mokutil --import /tmp/drivers.der

You will be prompted to create a password; record or remember this for Step 3.

  1. Reboot:
sudo reboot
  1. Enroll the Secureworks driver signing key:

Perform MOK Management

Perform MOK Management


  1. Install on Linux VM or physical CentOS, RHEL, or Ubuntu machine by running the following commands as root user:
sudo yum -y localinstall [filepath]/taegis-agent_[version].rpm


sudo rpm -i [filepath]/taegis-agent_[version].rpm
sudo apt-get -y install [filepath]/taegis-agent_[version].deb
  1. Register the agent:


  • taegisctl is the recommended controller to register, start, and stop the agent. Additionally, it can be used to view agent status and load the driver.
  • taegisctl should be run as sudo user.
  • In order to proceed further, you need the Registration Key and Registration Server URL from the Group Configuration tab of the Endpoint Agents page.

The following are the options for taegisctl:

Usage: /opt/secureworks/taegis-agent/bin/taegisctl [command] [--key <regkey>] [--server <servername>] [--allow_missing_driver] [--enforce_apparmor] [--enforce_selinux] [--without-selinux-policies] [--use_proxy]
insmod    Attempt to install driver
register  Attempt to register
start     Starts services if not already running.  Calls insmod, background registration
status    Lists status of components and configuration
stop      Stops services if running

Register the agent using the copied registration parameters:

sudo /opt/secureworks/taegis-agent/bin/taegisctl register --key REGISTRATIONKEY --server REGISTRATIONSERVER

In order to run taegisctl without entire file path in front, the directory must be added to $PATH. To do so, run the following command:

export PATH=/opt/secureworks/taegis-agent/bin:$PATH

Expect: registration success logged to console


Find additional information for registering the agent on CentOS-based systems using SELinux in the following SELinux/AppArmor section.

  1. Start the agent:
./taegisctl start

Proxy Support

Beginning with Taegis™ Endpoint Agent for Linux 1.1.28, the agent looks for http_proxy and https_proxy environment variables to identify and use a proxy to communicate with the Taegis™ backend. Credentials are obfuscated in the agent.log file.

To use this feature, issue the following commands:

taegisctl stop
taegisctl register --use_proxy --key xx --server yyy
taegisctl start

Validate Installation

Check services status after installation using the following command:

./taegisctl status

Examples of successful output:

Status Output Example

Status Output Example

Status Output Example

Status Output Example

SELinux/AppArmor and the Agent

CentOS-based systems use SELinux and Ubuntu-based systems use AppArmor. Secureworks provides SELinux policies and AppArmor profiles designed to protect the agent from tampering. Note that AppArmor and SELinux self-protection support is experimental.

To enable SELinux self-protection, use --enforce_selinux. To enable AppArmor self-protection, use --enforce_apparmor.


To change SELinux and AppArmor states from enforcing to permissive or back, you must stop and restart the agent via taegisctl stop and taegisctl start for SELinux and AppArmor enforcement changes to be picked up.


SELinux runs in two modes: enforcing and permissive. The permissive mode doesn't protect the system at all and can be ignored. To see which mode is active, run getenforce:

[user@centos ~]$ getenforce

If a system is in enforcing mode, you can enable self-protection with SELinux or AppArmor by passing --enforce_selinux or --enforce_apparmor, respectively. Alternatively, you can ignore SELinux enforcement by passing --without_selinux_policies. Please note --without_selinux_policies is required when running on systems in enforcing mode not running the targeted policy.


Currently SELinux and AppArmor support is experimental and you may receive some security-related log messages such as the following that can be ignored. As development of SELinux and AppArmor support continues, these log messages will begin to disappear and eventually cease.


Aug 26 15:55:10 localhost setroubleshoot: SELinux is preventing unix_chkpwd from write access on the file /usr/sbin/unix_chkpwd. For complete SELinux messages run: sealert -l da4bbcb0-b962-4627-89e8-d50541fd77d8


Aug 26 15:57:25 dw-ubuntu20-vm kernel: [ 8988.538364] audit: type=1400 audit(1661543845.962:11736): apparmor="ALLOWED" operation="chmod" profile="/opt/secureworks/taegis-agent/bin/taegis" name="/opt/secureworks/taegis-agent/var/status/" pid=9098 comm="taegis" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

Additional Info: SELinux Policy Types

If in enforcing mode, it's helpful to know which SELinux policy is being enforced. This is available in /etc/selinux/config, as SELINUXTYPE:

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
# SELINUXTYPE= can take one of three values:
#     targeted - Targeted processes are protected,
#     minimum - Modification of targeted policy. Only selected processes are protected.
#     mls - Multi Level Security protection.

The following table summarizes our supported and unsupported SELinux system configurations:

SELinux Status SELinux Policy Support Status
enforcing targeted Supported (use --enforce_selinux for self-protection)
enforcing Not targeted Best effort (use --without_selinux_policies)
permissive All policies Supported

Review Endpoint Agents Summary

Endpoint Agents Summary

Endpoint Agents Summary

As Taegis™ XDR processes endpoint telemetry, a list of endpoints is generated. Review these by navigating to Endpoint Agents → Summary from the left-hand side navigation in Taegis™ XDR. For more information, see Manage Endpoint Agents.


On this page: