Skip to content

Active Response

Active Response is a forensic tool that analysts control. It gives analysts direct access to endpoints, so that they can examine threats in more detail. With this access, analysts can fully investigate threats and respond to them. Active Response gives important information and helps analysts to make sure that a threat is real. It also lets analysts do manual remediation actions that stop threats and decrease their effect.

With Active Response, you can do these actions:

  • Get suspicious files for detailed analysis.
  • Deploy remediation scripts and files.
  • Stop processes.
  • Isolate networks.
  • Run cross-platform investigation scripts. A Python interpreter in the endpoint agent runs these scripts.

Active Response is available on Windows and Linux endpoints.

Full audit trails record all activity.

Benefits

Active Response lets you respond quickly to threats. Thus, you can resolve incidents faster, with less damage and downtime. This decreases the effect of a breach.

Active Response gives security teams direct, audited access to the systems that they must investigate. Thus, the teams can do forensic investigations, and Active Response helps to decrease the quantity of false positives. You can also give this access to your 24/7 MDR provider, so that the provider can take action for you.

How it works

Connectivity

Each endpoint that has the Universal Sensor installed and Active Response enabled makes a mutual TLS connection to the analysis platform. This connection uses a WebSocket. Active Response users do not connect directly to the Active Response endpoints. All connections go through the SenseOn analysis platform. Active Response uses the same connectivity as the analysis platform. Thus, new firewall rules are not necessary.

Permissions

To use Active Response, all of these conditions are necessary:

  • The user has Active Response access.
  • The user has an enrolled authenticator app (TOTP).
  • The endpoint is in a segment that has Active Response enabled.
  • Active Response is switched on for your organisation. SenseOn manages this setting.

User permissions

To give or remove Active Response access, go to the Team page at Settings -> Team. Use the Active Response item in the three-dot menu of the user. Only an Admin who already has Active Response access can give it. Thus, SenseOn gives it to your first user. The Team list shows an Active Response granted tag for each user who has access.

Active Response User Settings

⚠ Enforced MFA: If a user has Active Response access, that user must use MFA. The MFA setting of your organisation does not change this.

Segment settings

You must enable Active Response on a segment before users with Active Response access can use it on the endpoints in that segment. To create or change segments, go to Settings -> Device Configuration. You can also enable the feature there, in the segment configuration.

Active Response Segment Settings

Step-Up Authentication

Before you start an Active Response session, the platform makes you authenticate again. The platform also does this before you give Active Response access to another user. This procedure is step-up authentication.

When the platform starts step-up authentication, it asks you to enter:

  1. Your SenseOn account password
  2. Your current TOTP code from your authenticator app

Step-up authentication has a time limit. If the time limit expires before you act, the platform asks you again. The Audit Log records all step-up attempts, both successful and unsuccessful.


Action Groups

With Action Groups, you can schedule a script or a built-in action to run on one or more endpoints. You do not open an interactive session. Action Groups are useful for remediation or investigation tasks across a fleet.

Scheduling an action group

  1. Go to Active Response.
  2. Select one or more endpoints from the device list (use the checkboxes).
  3. Click Schedule Action.
  4. Select the script or built-in action to run.
  5. Enter the required parameters for the script. The platform does a check of the parameters before you can submit the action.
  6. (Optional) Link the action to a case.
  7. (Optional) Add a note that tells why you scheduled the action.
  8. Click Schedule.

💡 Offline endpoints: If a selected endpoint is offline when you schedule the action, the action waits in a queue. The action runs automatically when the endpoint is online again.

Supported operating systems

You can run Active Response actions on Windows and Linux endpoints. macOS endpoints do not support Action Groups. If you select an endpoint that does not support the selected action, the platform shows a warning.

Agent version requirements

Some scripts and actions work only with a minimum version of the Universal Sensor agent. If the agent on a selected endpoint is out of date, the platform excludes that endpoint from the action group. The platform also shows a compatibility warning. Upgrade the sensor on that endpoint. Then schedule the action again.

Viewing scheduled action groups

To see all scheduled and completed action groups, go to Active Response > Action Groups. The list shows:

  • The status of each action
  • The endpoint or endpoints for the action
  • The user who scheduled the action
  • The related case, if there is one

Audit logging

A full audit log is available for each Active Response activity that is related to a specific user. The log includes:

  • Authentication attempts against the service itself.
  • The start and stop of each Active Response session.
  • Each script that runs, with the full script payload.
  • Files that users upload and download.

The Active Response Audit Log is at Assets > Device Session History. It is available to Admins with Active Response access. Managers and Analysts cannot see it, even if they have Active Response access.

Active Response Audit Log

Quick Actions

Active Response has some quick actions. To use a quick action, select the hosts on the Active Response page. Then click the Actions buttons.

Active Response Quick Actions

Host isolation

You can use an Active Response action to block outbound network traffic on a Windows host. This action blocks all outbound traffic, except traffic to the SenseOn analysis platform. Inbound traffic continues, so that you can investigate the host and tools such as Remote Desktop can connect to it. To end the isolation of a host, use an Active Response action.

If a host is offline, the Active Response action waits in a queue. When the host is online again, the action runs. Active Response Isolation Pending

💡 Isolating non Windows devices: You can use Active Response to isolate a system that is not Windows, but you cannot use a Quick Action for this. To isolate the system, use Python to change the firewall on the host.

Python Scripts

The endpoint agent contains a Python interpreter. With it, you can run cross-platform scripts for remediation and investigation. The virtual environment on the hosts contains a Python module. This module gives access to more functions, which include: * File upload / download * Device isolation * Additional modules in development

💡 Script permissions: Scripts that you run with Active Response have the same privilege level as the endpoint sensor. This level is root or system.

You can use these example scripts with Active Response.

Active Response Script - Isolation Control

Active Response Script - Process Control

Active Response Script - Directory and File Access Control