Detection rules for SentinelOne Data sources. Every rule contains its MITRE ATT&CK mapping, an impact rating, and details on what it identifies.
This category lists 19 detection rules.
| Rule | Category | Technique | Impact (C/I/A) |
|---|---|---|---|
| Custom Detection Rule Triggers | Execution | T1059 - Command and Scripting Interpreter | C:3 / I:3 / A:2 |
| Deep Visibility Threat Indicators | Defense Evasion | T1070 - Indicator Removal on Host | C:3 / I:3 / A:2 |
| Kernel-Level Threat Detection | Privilege Escalation | T1068 - Exploitation for Privilege Escalation | C:3 / I:3 / A:3 |
| Memory Injection Detection | Defense Evasion, Privilege Escalation | T1055 - Process Injection | C:3 / I:3 / A:2 |
| SentinelOne AI-Based Threat Hunting Alerts | Defense Evasion, Privilege Escalation | T1055 - Process Injection | C:3 / I:3 / A:2 |
| SentinelOne Agent Tampering Attempts | Defense Evasion | T1562.001 - Impair Defenses: Disable or Modify Tools | C:3 / I:3 / A:3 |
| SentinelOne Behavioral Threat Detection | Defense Evasion, Privilege Escalation | T1055 - Process Injection | C:3 / I:3 / A:2 |
| SentinelOne Cloud Workload Protection Alert | Defense Evasion, Persistence, Privilege Escalation, Initial Access | T1078.004 - Valid Accounts: Cloud Accounts | C:3 / I:3 / A:2 |
| SentinelOne Container Security Alert | Defense Evasion, Execution | T1610 - Deploy Container | C:3 / I:3 / A:2 |
| SentinelOne Endpoint Detection and Response (EDR) Alerts | Execution | T1059 - Command and Scripting Interpreter | C:3 / I:3 / A:2 |
| SentinelOne IoT Device Compromise Indicator | Execution | T1203 - Exploitation for Client Execution | C:3 / I:3 / A:2 |
| SentinelOne Policy Downgraded from Protect to Detect | Defense Evasion | T1562.001 - Impair Defenses: Disable or Modify Tools | C:3 / I:3 / A:3 |
| SentinelOne Rollback Operation Patterns Detection | Impact | T1490 - Inhibit System Recovery | C:2 / I:3 / A:3 |
| SentinelOne Suspicious Exclusion Addition | Defense Evasion | T1562.001 - Impair Defenses: Disable or Modify Tools | C:3 / I:3 / A:2 |
| SentinelOne Suspicious Script Execution Detected | Execution | T1059 - Command and Scripting Interpreter | C:3 / I:3 / A:2 |
| SentinelOne Threat Mitigation Failures | Defense Evasion | T1562.001 - Impair Defenses: Disable or Modify Tools | C:2 / I:3 / A:2 |
| Storyline Correlation Event | Attack Chain Detection | Attack Chain Analysis | C:3 / I:3 / A:2 |
| Suspicious Process Tree Analysis | Defense Evasion, Privilege Escalation | T1055 - Process Injection | C:3 / I:3 / A:1 |
| Threat Intelligence Matches | Execution | T1203 - Exploitation for Client Execution | C:2 / I:2 / A:2 |
Rule Example
Below is an example of a rule definition for Custom Detection Rule Triggers (view in repository):
# Rule version v1.0.0
dataTypes:
- antivirus-sentinel-one
name: Custom Detection Rule Triggers
impact:
confidentiality: 3
integrity: 3
availability: 2
category: Execution
technique: "T1059 - Command and Scripting Interpreter"
adversary: origin
references:
- https://docs.sentinelone.com/
- https://attack.mitre.org/techniques/T1059/
description: |
Detects when custom detection rules configured in SentinelOne trigger, indicating organization-specific threat patterns or policy violations have been identified. Custom rules are tailored to detect specific behaviors or patterns unique to the organization's security requirements.
Next Steps:
1. Review the specific custom rule that triggered and understand its purpose
2. Investigate the affected endpoint (log.syslogHost) for additional suspicious activity
3. Check if the same custom rule has triggered on other endpoints
4. Verify if the detection is a false positive based on the custom rule's logic
5. If legitimate threat activity, initiate incident response procedures
6. Consider updating the custom rule if false positives are frequent
where: |
(contains("log.eventDescription", ["custom rule", "custom detection", "Custom Rules"]) ||
equals("log.detectionSource", "CustomRule") ||
equals("log.ruleType", "Custom")) &&
exists("log.syslogHost")
groupBy:
- lastEvent.log.eventDescription
- lastEvent.log.syslogHost
Rule Details
Custom Detection Rule Triggers
Detects triggers from custom detection rules set up in SentinelOne, signaling that organization-specific threat patterns or policy violations have been found. These custom rules are designed to catch behaviors or patterns tailored to the organization's unique security needs.
Category: Execution
Technique: T1059 - Command and Scripting Interpreter
Impact: C:3 / I:3 / A:2
Rule file: custom_detection_rule_triggers.yml
Reference: https://docs.sentinelone.com/
Reference: https://attack.mitre.org/techniques/T1059/
Deep Visibility Threat Indicators
Detects advanced threat indicators via SentinelOne's deep visibility monitoring. This rule fires when specific threat-related events appear in the SentinelOne logs.
Category: Defense Evasion
Technique: T1070 - Indicator Removal on Host
Impact: C:3 / I:3 / A:2
Rule file: deep_visibility_threat_indicators.yml
Reference: https://www.sentinelone.com/blog/rapid-threat-hunting-with-deep-visibility-feature-spotlight/
Reference: https://attack.mitre.org/techniques/T1070/
Kernel-Level Threat Detection
Detects kernel-level threats such as rootkits, kernel exploits, driver manipulation, and other low-level system attacks aimed at compromising the operating system kernel.
Category: Privilege Escalation
Technique: T1068 - Exploitation for Privilege Escalation
Impact: C:3 / I:3 / A:3
Rule file: kernel_level_threat.yml
Reference: https://attack.mitre.org/techniques/T1068/
Reference: https://attack.mitre.org/techniques/T1014/
Memory Injection Detection
Detects memory injection attempts, including DLL injection, process hollowing, reflective DLL injection, and other in-memory attack techniques identified by SentinelOne.
Category: Defense Evasion, Privilege Escalation
Technique: T1055 - Process Injection
Impact: C:3 / I:3 / A:2
Rule file: memory_injection_detection.yml
Reference: https://attack.mitre.org/techniques/T1055/
SentinelOne AI-Based Threat Hunting Alerts
Detects threats uncovered by SentinelOne's AI and machine learning threat hunting, such as zero-day exploits, fileless attacks, and never-before-seen malware variants.
Category: Defense Evasion, Privilege Escalation
Technique: T1055 - Process Injection
Impact: C:3 / I:3 / A:2
Rule file: ai_based_threat_hunting_alerts.yml
Reference: https://www.sentinelone.com/platform/ai-powered-prevention/
Reference: https://attack.mitre.org/tactics/TA0043/
Reference: https://attack.mitre.org/techniques/T1055/
SentinelOne Agent Tampering Attempts
Identifies attempts to modify, deactivate, or interfere with the SentinelOne agent. Since threat actors often turn off security defenses before carrying out their primary attack, this is a critical security event. A prompt response is necessary.
Category: Defense Evasion
Technique: T1562.001 - Impair Defenses: Disable or Modify Tools
Impact: C:3 / I:3 / A:3
Rule file: agent_tampering_attempts.yml
Reference: https://support.sentinelone.com/hc/en-us/articles/360001089343-Protecting-the-SentinelOne-Agent
SentinelOne Behavioral Threat Detection
Detects behavioral threat patterns recognized by SentinelOne's AI engine, such as suspicious process behavior, anomalous system calls, and departures from normal endpoint activity patterns.
Category: Defense Evasion, Privilege Escalation
Technique: T1055 - Process Injection
Impact: C:3 / I:3 / A:2
Rule file: behavioral_threat_detection.yml
Reference: https://www.sentinelone.com/platform/behavioral-ai/
Reference: https://attack.mitre.org/techniques/T1055/
SentinelOne Cloud Workload Protection Alert
Detects cloud workload protection alerts, such as suspicious cloud API calls, unauthorized cloud resource access, cloud account compromise, or cloud-native threat detection.
Category: Defense Evasion, Persistence, Privilege Escalation, Initial Access
Technique: T1078.004 - Valid Accounts: Cloud Accounts
Impact: C:3 / I:3 / A:2
Rule file: cloud_workload_protection_alerts.yml
Reference: https://www.sentinelone.com/platform/singularity-cloud-workload-security/
SentinelOne Container Security Alert
Detects container-related security events, such as container drift, unauthorized container deployment, cryptominers in containers, or suspicious container behavior.
Category: Defense Evasion, Execution
Technique: T1610 - Deploy Container
Impact: C:3 / I:3 / A:2
Rule file: container_security_alerts.yml
Reference: https://www.sentinelone.com/platform/singularity-cloud-workload-security/
Reference: https://www.sentinelone.com/resources/cloud-workload-security-for-containers/
Reference: https://attack.mitre.org/techniques/T1610/
SentinelOne Endpoint Detection and Response (EDR) Alerts
Critical EDR alerts from SentinelOne, including suspicious endpoint activities, unauthorized system changes, malicious command execution, and advanced persistent threat (APT) indicators. These alerts point to potential security incidents that demand immediate investigation.
Category: Execution
Technique: T1059 - Command and Scripting Interpreter
Impact: C:3 / I:3 / A:2
Rule file: endpoint_detection_response_alerts.yml
Reference: https://www.sentinelone.com/platform/edr/
Reference: https://attack.mitre.org/techniques/T1059/
Reference: https://attack.mitre.org/techniques/T1547/
SentinelOne IoT Device Compromise Indicator
Detects signs of IoT device compromise, including unauthorized firmware modifications, suspicious network behavior from IoT devices, or anomalous IoT device activity patterns found by SentinelOne's Singularity Ranger. This rule fires when IoT-related threats are identified, including compromised embedded systems, firmware backdoors, industrial control system attacks, or SCADA system compromises.
Category: Execution
Technique: T1203 - Exploitation for Client Execution
Impact: C:3 / I:3 / A:2
Rule file: iot_device_compromise_indicators.yml
Reference: https://www.sentinelone.com/platform/singularity-ranger/
Reference: https://attack.mitre.org/techniques/T1203/
SentinelOne Policy Downgraded from Protect to Detect
Detects when a SentinelOne policy is downgraded from Protect mode to Detect-only mode, which halts automatic threat remediation. This is a critical defense evasion indicator because attackers with console access weaken protection before deploying malware.
Category: Defense Evasion
Technique: T1562.001 - Impair Defenses: Disable or Modify Tools
Impact: C:3 / I:3 / A:3
Rule file: s1_policy_downgrade.yml
Reference: https://support.sentinelone.com/
SentinelOne Rollback Operation Patterns Detection
Detects rollback operations in SentinelOne that may signal ransomware recovery attempts or suspicious rollback activity. Rollback operations are critical system recovery events that should be monitored for legitimate recovery as well as potential abuse.
Category: Impact
Technique: T1490 - Inhibit System Recovery
Impact: C:2 / I:3 / A:3
Rule file: rollback_operation_patterns.yml
Reference: https://www.cybervigilance.uk/insights/sentinelone-how-does-rollback-work
Reference: https://attack.mitre.org/techniques/T1490/
SentinelOne Suspicious Exclusion Addition
Detects suspicious additions to SentinelOne exclusion or allowlist entries, which attackers abuse to keep their malware or tools from being detected after gaining console access.
Category: Defense Evasion
Technique: T1562.001 - Impair Defenses: Disable or Modify Tools
Impact: C:3 / I:3 / A:2
Rule file: s1_exclusion_abuse.yml
Reference: https://support.sentinelone.com/
SentinelOne Suspicious Script Execution Detected
Detects suspicious script execution activities, including PowerShell, Python, Bash, or other scripting interpreters that may indicate malicious activity or fileless attacks. SentinelOne's behavioral detection engine flags these patterns as potential threats that could compromise system integrity.
Category: Execution
Technique: T1059 - Command and Scripting Interpreter
Impact: C:3 / I:3 / A:2
Rule file: suspicious_script_execution.yml
Reference: https://www.sentinelone.com/platform/singularity-cloud-workload-security/
Reference: https://attack.mitre.org/techniques/T1059/
SentinelOne Threat Mitigation Failures
Identifies unsuccessful threat mitigation actions in SentinelOne, potentially indicating sophisticated malware that avoids remediation, a compromised system that blocks cleanup, or configuration problems. Unsuccessful mitigations demand immediate investigation.
Category: Defense Evasion
Technique: T1562.001 - Impair Defenses: Disable or Modify Tools
Impact: C:2 / I:3 / A:2
Rule file: threat_mitigation_failures.yml
Reference: https://support.sentinelone.com/hc/en-us/articles/360004195934-Threat-Mitigation-Status
Reference: https://attack.mitre.org/techniques/T1562/
Storyline Correlation Event
Detects correlated attack patterns found by SentinelOne's Storyline feature, which links related events to expose complete attack chains and multi-stage threats.
Category: Attack Chain Detection
Technique: Attack Chain Analysis
Impact: C:3 / I:3 / A:2
Rule file: storyline_correlation.yml
Reference: https://www.sentinelone.com/platform/storyline-active-response/
Reference: https://attack.mitre.org/tactics/enterprise/
Suspicious Process Tree Analysis
Detects suspicious process tree patterns recognized by SentinelOne, such as unusual parent-child relationships, process hollowing, and malicious process chains commonly used in attacks.
Category: Defense Evasion, Privilege Escalation
Technique: T1055 - Process Injection
Impact: C:3 / I:3 / A:1
Rule file: suspicious_process_tree.yml
Reference: https://attack.mitre.org/techniques/T1055/
Reference: https://attack.mitre.org/techniques/T1057/
Threat Intelligence Matches
Detects matches against threat intelligence feeds, including known malicious hashes, IPs, domains, and behavioral patterns tied to APT groups and cybercrime campaigns. This indicates that SentinelOne has found a file, behavior, or network connection that matches known threat indicators.
Category: Execution
Technique: T1203 - Exploitation for Client Execution
Impact: C:2 / I:2 / A:2
Rule file: threat_intelligence_matches.yml
Reference: https://attack.mitre.org/techniques/T1203/