[8.13] SentinelOne bidirectional actions - response console & history (classic/ESS) (backport #4885) #4933
+66
−17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributes to #4875 by documenting the latest functionality for SentinelOne actions (can be performed from response console and are now displayed in response action history).
Previews
Terms: "bidirectional"?
This PR leans more heavily on the name "bidirectional" as a category of response actions. Is this term meaningful to customers, or would a different term be better, such as "third-party" or something else?
TOC Reorg
This PR also does some reorg to improve the flow and navigation for response actions, which were previously buried two levels deep under a very broad "Endpoint management" section.
Serverless docs
No serverless docs PR open yet. I'll wait until the content is finalized in this classic/ESS PR, then open a serverless docs PR with the same content changes.
This is an automatic backport of pull request #4885 done by Mergify.