shashank-elastic
113 lines
4.5 KiB
TOML
113 lines
4.5 KiB
TOML
[metadata]
|
|
creation_date = "2025/07/31"
|
|
integration = ["crowdstrike"]
|
|
maturity = "production"
|
|
promotion = true
|
|
updated_date = "2025/10/17"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Generates a detection alert for each CrowdStrike alert written to the configured indices. Enabling this rule allows you
|
|
to immediately begin investigating CrowdStrike alerts in the app.
|
|
"""
|
|
from = "now-2m"
|
|
index = ["logs-crowdstrike.alert-*"]
|
|
interval = "1m"
|
|
language = "kuery"
|
|
license = "Elastic License v2"
|
|
max_signals = 1000
|
|
name = "CrowdStrike External Alerts"
|
|
note = """## Triage and analysis
|
|
|
|
### Investigating CrowdStrike External Alerts
|
|
|
|
CrowdStrike Falcon is a cloud-native endpoint protection platform that delivers real-time threat detection and response capabilities. The rule captures security alerts generated by Falcon and enables analysts to investigate threats rapidly based on behavioral indicators and threat intelligence.
|
|
|
|
### Possible investigation steps
|
|
|
|
- Review the associated process, file path, and command line to determine whether the activity is legitimate or suspicious.
|
|
- Investigate the user account and host involved in the alert to validate whether the activity was authorized.
|
|
- Cross-reference the alert with CrowdStrike Falcon console for additional context, including process tree, behavioral tags, and threat intelligence matches.
|
|
- Check for any related alerts from the same host, user, or file hash to identify whether this is part of a larger attack chain.
|
|
- Consult the Crowdstrike investigation guide and resources tagged in the alert for specific guidance on handling similar threats.
|
|
|
|
### False positive analysis
|
|
|
|
- Alerts involving known and trusted software tools (e.g., remote administration tools) may be false positives. Confirm intent before excluding.
|
|
- Security assessments or penetration testing activities might mimic real threats. Validate the activity with responsible teams.
|
|
- Scheduled jobs, IT scripts, or automation tools may trigger alerts if they behave similarly to malicious code.
|
|
- Review alerts based on detection confidence levels and behavioral scoring to filter out low-confidence or known-benign triggers.
|
|
|
|
### Response and remediation
|
|
|
|
- Isolate affected endpoints to prevent lateral movement if malicious behavior is confirmed.
|
|
- Quarantine any identified malicious files and block related hashes or domains.
|
|
- Investigate how the threat entered the environment and close any exploited vulnerabilities.
|
|
- Reset credentials for compromised user accounts or escalate to incident response.
|
|
- Review CrowdStrike Falcon policies and detections to fine-tune future alerting and response coverage.
|
|
- Document the findings and update detection logic or exceptions accordingly.
|
|
"""
|
|
references = ["https://docs.elastic.co/en/integrations/crowdstrike"]
|
|
risk_score = 47
|
|
rule_id = "aeebe561-c338-4118-9924-8cb4e478aa58"
|
|
rule_name_override = "crowdstrike.alert.name"
|
|
setup = """## Setup
|
|
|
|
### CrowdStrike Alert Integration
|
|
This rule is designed to capture alert events generated by the CrowdStrike integration and promote them as Elastic detection alerts.
|
|
|
|
To capture CrowdStrike alerts, install and configure the CrowdStrike integration to ingest alert events into the `logs-crowdstrike.alert-*` index pattern.
|
|
|
|
If this rule is enabled alongside the External Alerts promotion rule (UUID: eb079c62-4481-4d6e-9643-3ca499df7aaa), you may receive duplicate alerts for the same CrowdStrike events. Consider adding a rule exception for the External Alert rule to exclude data_stream.dataset:crowdstrike.alert to avoid receiving duplicate alerts.
|
|
|
|
### Additional notes
|
|
|
|
For 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).
|
|
"""
|
|
severity = "medium"
|
|
tags = [
|
|
"Data Source: Crowdstrike",
|
|
"Use Case: Threat Detection",
|
|
"Resources: Investigation Guide",
|
|
"Promotion: External Alerts",
|
|
]
|
|
timestamp_override = "event.ingested"
|
|
type = "query"
|
|
|
|
query = '''
|
|
event.kind: alert and data_stream.dataset: crowdstrike.alert
|
|
'''
|
|
|
|
|
|
[[rule.risk_score_mapping]]
|
|
field = "crowdstrike.alert.incident.score"
|
|
operator = "equals"
|
|
value = ""
|
|
|
|
[[rule.severity_mapping]]
|
|
field = "event.severity"
|
|
operator = "equals"
|
|
severity = "low"
|
|
value = "21"
|
|
|
|
[[rule.severity_mapping]]
|
|
field = "event.severity"
|
|
operator = "equals"
|
|
severity = "medium"
|
|
value = "47"
|
|
|
|
[[rule.severity_mapping]]
|
|
field = "event.severity"
|
|
operator = "equals"
|
|
severity = "high"
|
|
value = "73"
|
|
|
|
[[rule.severity_mapping]]
|
|
field = "event.severity"
|
|
operator = "equals"
|
|
severity = "critical"
|
|
value = "99"
|
|
|
|
|