SentinelOne bidirectional actions - response console & history (classic/ESS)

docs/index.asciidoc

@@ -36,6 +36,8 @@ include::cases/cases-index.asciidoc[]
 
 include::osquery/osquery-index.asciidoc[]
 
+include::management/admin/response-actions.asciidoc[]
+
 include::management/manage-intro.asciidoc[]
 
 include::siem-apis.asciidoc[]

docs/management/admin/host-isolation-ov.asciidoc

@@ -1,6 +1,6 @@
 [[host-isolation-ov]]
 [chapter, role="xpack"]
-= Host isolation
+= Isolate a host
 
 :frontmatter-description: Host isolation allows you to cut off a host's network access until you release it.
 :frontmatter-tags-products: [security, defend]
@@ -67,7 +67,7 @@ All actions executed on a host are tracked in the host’s response actions hist
 ====
 NOTE: The response console is an https://www.elastic.co/pricing[Enterprise subscription] feature.
 
-. Open the response console for the endpoint (*Manage* -> *Endpoints* -> *Actions* menu (*...*) -> *Respond*).
+. Open the response console for the host (select the **Respond** button or actions menu option on the host, endpoint, or alert details view).
 . Enter the `isolate` command and an optional comment in the input area, for example:
 +
 `isolate --comment "Isolate this host"`
@@ -124,7 +124,7 @@ image::images/host-isolated-notif.png[Host isolated notification message,350]
 ====
 NOTE: The response console is an https://www.elastic.co/pricing[Enterprise subscription] feature.
 
-. Open the response console for the endpoint (*Manage* -> *Endpoints* -> *Actions* menu (*...*) -> *Respond*).
+. Open the response console for the host (select the **Respond** button or actions menu option on the host, endpoint, or alert details view).
 . Enter the `release` command and an optional comment in the input area, for example:
 +
 `release --comment "Release this host"`

docs/management/admin/response-actions-config.asciidoc

@@ -1,5 +1,5 @@
 [[response-actions-config]]
-= Response actions configuration
+= Configure third-party response actions
 
 :frontmatter-description: Configure third-party systems to perform response actions on protected hosts.
 :frontmatter-tags-products: [security]
@@ -12,7 +12,7 @@ Endpoint response actions involving third-party systems require additional confi
 [[configure-sentinelone-response-actions]]
 == Configure SentinelOne response actions
 
-SentinelOne response actions allow you to perform bidirectional actions on protected hosts, such as directing SentinelOne to isolate a suspicious endpoint from your network, without needing to leave the {elastic-sec} UI.
+You can direct SentinelOne to perform response actions on protected hosts, such as isolating a suspicious endpoint from your network, without needing to leave the {elastic-sec} UI.
 
 preview::[]
 

docs/management/admin/response-actions-history.asciidoc

@@ -6,7 +6,7 @@
 :frontmatter-tags-content-type: [reference]
 :frontmatter-tags-user-goals: [manage]
 
-{elastic-defend} keeps a log of the <<response-actions,response actions>> performed on endpoints, such as isolating a host or terminating a process. The log displays when each command was performed, the host on which the action was performed, the {kib} user who requested the action, any comments added to the action, and the action's current status.
+{elastic-sec} keeps a log of the <<response-actions,response actions>> performed on endpoints, such as isolating a host or terminating a process. The log displays when each command was performed, the host on which the action was performed, the {kib} user who requested the action, any comments added to the action, and the action's current status.
 
 .Requirement
 [sidebar]
@@ -27,9 +27,10 @@ image::images/response-actions-history-page.png[Response actions history page UI
 To filter and expand the information in the response actions history:
 
 * Enter a user name or comma-separated list of user names in the search field to display actions requested by those users.
-* Use the *Hosts* menu to display actions performed on specific endpoints. (This menu is only available on the *Response actions history* page for all endpoints.)
-* Use the *Actions* menu to display specific actions types.
-* Use the *Statuses* menu to display actions with a specific status.
-* Use the *Type* menu to display actions manually run by a user (`Triggered manually`) or automatically run by a rule (`Triggered by rule`).
+* Use the various drop-down menus to filter the actions shown:
+** *Hosts*: Show actions performed on specific endpoints. (Only available on the *Response actions history* page for all endpoints.)
+** *Actions*: Show specific actions types.
+** *Statuses*: Show actions with a specific status.
+** *Types*: Show actions based on the endpoint protection agent type ({elastic-defend} or a third-party agent), and how the action was triggered (manually by a user or automatically by a detection rule).
 * Use the date and time picker to display actions within a specific time range.
 * Click the expand arrow on the right to display more details about an action.

docs/management/admin/response-actions.asciidoc

@@ -30,6 +30,7 @@ Launch the response console from any of the following places in {elastic-sec}:
 * *Endpoints* page -> *Actions* menu (*...*) -> *Respond*
 * Endpoint details flyout -> *Take action* -> *Respond*
 * Alert details flyout -> *Take action* -> *Respond*
+* Host details page → *Respond*
 
 To perform an action on the endpoint, enter a <<response-action-commands,response action command>> in the input area at the bottom of the console, then press *Return*. Output from the action is displayed in the console.
 
@@ -41,28 +42,33 @@ Activity in the response console is persistent, so you can navigate away from th
 
 IMPORTANT: Once you submit a response action, you can't cancel it, even if the action is pending for an offline host.
 
+[discrete]
 [[response-action-commands]]
 == Response action commands
 
 The following response action commands are available in the response console.
 
+[discrete]
 === `isolate`
 <<host-isolation-ov,Isolate the host>>, blocking communication with other hosts on the network. 
 
 Required privilege: *Host Isolation*
 
 Example: `isolate --comment "Isolate host related to detection alerts"`
 
+[discrete]
 === `release`
 Release an isolated host, allowing it to communicate with the network again.
 
 Required privilege: *Host Isolation*
 
 Example: `release --comment "Release host, everything looks OK"`
 
+[discrete]
 === `status`
 Show information about the host's status, including: {agent} status and version, the {elastic-defend} integration's policy status, and when the host was last active.
 
+[discrete]
 === `processes`
 Show a list of all processes running on the host. This action may take a minute or so to complete.
 
@@ -75,6 +81,7 @@ Use this command to get current PID or entity ID values, which are required for
 Entity IDs may be more reliable than PIDs, because entity IDs are unique values on the host, while PID values can be reused by the operating system.
 ====
 
+[discrete]
 === `kill-process`
 
 Terminate a process. You must include one of the following parameters to identify the process to terminate:
@@ -86,6 +93,7 @@ Required privilege: *Process Operations*
 
 Example: `kill-process --pid 123 --comment "Terminate suspicious process"`
 
+[discrete]
 === `suspend-process`
 
 Suspend a process. You must include one of the following parameters to identify the process to suspend:
@@ -97,6 +105,7 @@ Required privilege: *Process Operations*
 
 Example: `suspend-process --pid 123 --comment "Suspend suspicious process"`
 
+[discrete]
 === `get-file`
 
 Retrieve a file from a host. Files are downloaded in a password-protected `.zip` archive to prevent the file from running. Use password `elastic` to open the `.zip` in a safe environment.
@@ -116,6 +125,7 @@ TIP: You can use the <<use-osquery,Osquery manager integration>> to query a host
 When {elastic-defend} prevents file activity due to <<malware-protection,malware prevention>>, the file is quarantined on the host and a malware prevention alert is created. To retrieve this file with `get-file`, copy the path from the alert's *Quarantined file path* field (`file.Ext.quarantine_path`), which appears under *Highlighted fields* in the alert details flyout. Then paste the value into the `--path` parameter. 
 ====
 
+[discrete]
 === `execute`
 
 Run a shell command on the host. The command's output and any errors appear in the response console, up to 2000 characters. The complete output (stdout and stderr) are also saved to a downloadable `.zip` archive (password: `elastic`). Use these parameters:
@@ -139,6 +149,7 @@ Example: `execute --command "ls -al" --timeout 2s --comment "Get list of all fil
 
 WARNING: This response action runs commands on the host using the same user account running the {elastic-defend} integration, which normally has full control over the system. Be careful with any commands that could cause irrevocable changes.
 
+[discrete]
 === `upload`
 
 Upload a file to the host. The file is saved to the location on the host where {elastic-endpoint} is installed. After you run the command, the full path is returned in the console for reference. Use these parameters:
@@ -154,29 +165,35 @@ TIP: You can follow this with the `execute` response action to upload and run sc
 
 NOTE: The default file size maximum is 25 MB, configurable in `kibana.yml` with the `maxUploadResponseActionFileBytes` setting. You must enter the value in bytes (the maximum is `104857600` bytes, or 100 MB).
 
+[discrete]
 [[supporting-commands-parameters]]
 == Supporting commands and parameters
 
+[discrete]
 === `--comment`
 
 Add to a command to include a comment explaining or describing the action. Comments are included in the response actions history.
 
+[discrete]
 === `--help`
 
 Add to a command to get help for that command.
 
 Example: `isolate --help`
 
+[discrete]
 === `clear`
 
 Clear all output from the response console.
 
+[discrete]
 === `help`
 
 List supported commands in the console output area.
 
 TIP: You can also get a list of commands in the <<help-panel,Help panel>>, which stays on the screen independently of the output area.
 
+[discrete]
 [[help-panel]]
 == Help panel
 
@@ -194,11 +211,16 @@ If the endpoint is running an older version of {agent}, some response actions ma
 [role="screenshot"]
 image::images/response-console-unsupported-command.png[Unsupported response action with tooltip,350]
 
-
+[discrete]
 [[actions-log]]
 == Response actions history
 
 Click *Response actions history* to display a log of the response actions performed on the endpoint, such as isolating a host or terminating a process. You can filter the information displayed in this view. Refer to <<response-actions-history>> for more details.
 
 [role="screenshot"]
 image::images/response-actions-history-console.png[Response actions history with a few past actions,85%]
+
+include::host-isolation-ov.asciidoc[leveloffset=+1]
+include::response-actions-history.asciidoc[leveloffset=+1]
+include::third-party-actions.asciidoc[leveloffset=+1]
+include::response-actions-config.asciidoc[leveloffset=+1]

docs/management/admin/third-party-actions.asciidoc

@@ -0,0 +1,28 @@
+[[third-party-actions]]
+= Third-party response actions
+
+:frontmatter-description: Perform response actions on hosts protected by third-party endpoint security systems.
+:frontmatter-tags-products: [security]
+:frontmatter-tags-content-type: [reference]
+:frontmatter-tags-user-goals: [manage]
+
+preview::[]
+
+[discrete]
+[[sentinelone-response-actions]]
+== SentinelOne response actions
+
+You can direct SentinelOne to perform response actions on protected hosts without leaving the {elastic-sec} UI. Prior <<response-actions-config,configuration>> is required to connect {elastic-sec} with SentinelOne.
+
+The following response actions and related features are supported for SentinelOne-protected hosts:
+
+* **Isolate and release a host** using any of these methods:
++
+--
+** From a detection alert
+** From the response console
+--
++
+Refer to the instructions on <<isolate-a-host,isolating>> and <<release-a-host,releasing>> hosts for more details.
+
+* **View past response action activity** in the <<response-actions-history,response actions history>> log.

docs/management/manage-intro.asciidoc

@@ -1,14 +1,10 @@
 [[sec-manage-intro]]
 
-= Endpoint management
+= Manage endpoint protection
 
 The following section provides an overview of the management tools admins can use to manage endpoints, integration policies, trusted applications, event filters, host isolation exceptions, and blocked applications.
 
 include::{security-docs-root}/docs/management/admin/admin-pg-ov.asciidoc[leveloffset=+1]
-include::{security-docs-root}/docs/management/admin/response-actions.asciidoc[leveloffset=+2]
-include::{security-docs-root}/docs/management/admin/response-actions-history.asciidoc[leveloffset=+2]
-include::{security-docs-root}/docs/management/admin/host-isolation-ov.asciidoc[leveloffset=+2]
-include::{security-docs-root}/docs/management/admin/response-actions-config.asciidoc[leveloffset=+2]
 include::{security-docs-root}/docs/management/admin/policy-list.asciidoc[leveloffset=+1]
 include::{security-docs-root}/docs/management/admin/trusted-apps.asciidoc[leveloffset=+1]
 include::{security-docs-root}/docs/management/admin/event-filters.asciidoc[leveloffset=+1]