SentinelOne Alert External Alerts

  1[metadata]
  2creation_date = "2025/07/31"
  3integration = ["sentinel_one"]
  4maturity = "production"
  5promotion = true
  6min_stack_version = "8.18.0"
  7min_stack_comments = "Introduced support for SentinelOne alert promotion"
  8updated_date = "2025/08/04"
  9
 10[rule]
 11author = ["Elastic"]
 12description = """
 13Generates a detection alert for each SentinelOne alert written to the configured indices. Enabling this rule allows you
 14to immediately begin investigating SentinelOne alerts in the app.
 15"""
 16from = "now-2m"
 17index = ["logs-sentinel_one.alert-*"]
 18interval = "1m"
 19language = "kuery"
 20license = "Elastic License v2"
 21max_signals = 1000
 22name = "SentinelOne Alert External Alerts"
 23note = """## Triage and analysis
 24
 25### Investigating SentinelOne Alert External Alerts
 26
 27SentinelOne is a cybersecurity platform that provides endpoint protection by detecting and responding to threats in real-time. The rule identifies such threats by monitoring specific alert events, enabling analysts to swiftly investigate and mitigate potential security incidents.
 28
 29### Possible investigation steps
 30
 31- Correlate the alert with recent activity on the affected endpoint to identify any unusual or suspicious behavior patterns.
 32- Check for any additional alerts or logs related to the same endpoint or user to determine if this is part of a broader attack or isolated incident.
 33- Investigate the source and destination IP addresses involved in the alert to assess if they are known to be malicious or associated with previous threats.
 34- Analyze any files or processes flagged in the alert to determine if they are legitimate or potentially malicious, using threat intelligence sources if necessary.
 35- Consult the SentinelOne investigation guide and resources tagged in the alert for specific guidance on handling similar threats.
 36
 37### False positive analysis
 38
 39- Alerts triggered by routine software updates or patches can be false positives. Review the context of the alert to determine if it aligns with scheduled maintenance activities.
 40- Legitimate administrative tools or scripts may trigger alerts. Identify and whitelist these tools if they are verified as non-threatening.
 41- Frequent alerts from known safe applications or processes can be excluded by creating exceptions for these specific behaviors in the SentinelOne configuration.
 42- Network scanning or monitoring tools used by IT teams might be flagged. Ensure these tools are documented and excluded from triggering alerts if they are part of regular operations.
 43- User behavior that is consistent with their role but triggers alerts should be reviewed. If deemed non-malicious, adjust the rule to exclude these specific user actions.
 44
 45### Response and remediation
 46
 47- Isolate the affected endpoint immediately to prevent lateral movement and further compromise within the network.
 48- Analyze the specific alert details to identify the nature of the threat and any associated indicators of compromise (IOCs).
 49- Remove or quarantine any malicious files or processes identified by the SentinelOne alert to neutralize the threat.
 50- Apply relevant security patches or updates to address any exploited vulnerabilities on the affected endpoint.
 51- Conduct a thorough scan of the network to identify any additional endpoints that may have been compromised or are exhibiting similar behavior.
 52- Document the incident and escalate to the appropriate security team or management if the threat is part of a larger attack campaign or if additional resources are needed for remediation.
 53- Review and update endpoint protection policies and configurations to enhance detection and prevention capabilities against similar threats in the future.
 54"""
 55references = ["https://docs.elastic.co/en/integrations/sentinel_one"]
 56risk_score = 47
 57rule_id = "9b35422b-9102-45a9-8610-2e0c22281c55"
 58rule_name_override = "rule.name"
 59setup = """## Setup
 60
 61### SentinelOne Alert Integration
 62This rule is designed to capture alert events generated by the SentinelOne integration and promote them as Elastic detection alerts.
 63
 64To capture SentinelOne alerts, install and configure the SentinelOne integration to ingest alert events into the `logs-sentinel_one.alert-*` index pattern.
 65
 66If this rule is enabled alongside the External Alerts promotion rule (UUID: eb079c62-4481-4d6e-9643-3ca499df7aaa), you may receive duplicate alerts for the same SentinelOne events. Consider adding a rule exception for the External Alert rule to exclude datastream.dataset: sentinel_one.alert to avoid receiving duplicate alerts.
 67
 68### Additional notes
 69
 70For information on troubleshooting the maximum alerts warning please refer to this [guide](https://www.elastic.co/guide/en/security/current/alerts-ui-monitor.html#troubleshoot-max-alerts).
 71"""
 72severity = "medium"
 73tags = ["Data Source: SentinelOne", "Use Case: Threat Detection", "Resources: Investigation Guide", "Promotion: External Alerts"]
 74timestamp_override = "event.ingested"
 75type = "query"
 76
 77query = '''
 78event.kind: event and data_stream.dataset: sentinel_one.alert
 79'''
 80
 81
 82[[rule.risk_score_mapping]]
 83field = "event.risk_score"
 84operator = "equals"
 85value = ""
 86
 87[[rule.severity_mapping]]
 88field = "event.severity"
 89operator = "equals"
 90severity = "low"
 91value = "21"
 92
 93[[rule.severity_mapping]]
 94field = "event.severity"
 95operator = "equals"
 96severity = "medium"
 97value = "47"
 98
 99[[rule.severity_mapping]]
100field = "event.severity"
101operator = "equals"
102severity = "high"
103value = "73"
104
105[[rule.severity_mapping]]
106field = "event.severity"
107operator = "equals"
108severity = "critical"
109value = "99"