You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a handful of steps users must take to ensure they are able to successfully take action on Sentinel One hosts (for the initial tech preview release in 8.12, the only action is to isolate / release a host). We want to make sure we have a page that walks through the full configuration requirements.
Prerequesites:
Should have active running S1 agents
High level steps:
Ensure there is an agent policy created (Fleet) that will be responsible for pulling S1 data)
Add and configure the Sentinel One integration to policy
Create a security detection rule to get elastic alerts for Sentinel One alerts
logs-sentinel_one.alert*
Create a connector for Sentinel One
The text was updated successfully, but these errors were encountered:
#4312 already existed to track docs work on the SentinelOne integration, so I copied the info from this issue to that one, and will close this. Follow #4312 for further updates.
First release of our bidirectional integration work - https://github.com/elastic/security-team/issues/6200
There are a handful of steps users must take to ensure they are able to successfully take action on Sentinel One hosts (for the initial tech preview release in 8.12, the only action is to isolate / release a host). We want to make sure we have a page that walks through the full configuration requirements.
Prerequesites:
High level steps:
The text was updated successfully, but these errors were encountered: