ID | Technique | Tactic |
---|---|---|
T1110 | Brute Force | Credential Access |
Detection: Crowdstrike Admin Weak Password Policy
Description
The following analytic detects CrowdStrike alerts for admin weak password policy violations, identifying instances where administrative passwords do not meet security standards. These alerts highlight significant vulnerabilities that could be exploited by attackers to gain unauthorized access. Promptly addressing these alerts is crucial for maintaining robust security and protecting critical systems and data from potential threats.
Search
1`crowdstrike_identities` primaryDisplayName = "*admin*"
2| rename riskFactors{}.severity as severity, riskFactors{}.type as risk_type, roles{}.type as role_type, accounts{}.domain as domain, accounts{}.dn as dn, accounts{}.samAccountName as user
3| stats count min(_time) as firstTime max(_time) as lastTime by domain dn primaryDisplayName risk_type severity riskScore riskScoreSeverity user role_type
4| where risk_type = "WEAK_PASSWORD_POLICY"
5| `security_content_ctime(firstTime)`
6| `security_content_ctime(lastTime)`
7| `crowdstrike_admin_weak_password_policy_filter`
Data Source
No data sources specified for this detection.
Macros Used
Name | Value |
---|---|
crowdstrike_identities | sourcetype=crowdstrike:identities |
crowdstrike_admin_weak_password_policy_filter | search * |
crowdstrike_admin_weak_password_policy_filter
is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
Default Configuration
This detection is configured by default in Splunk Enterprise Security to run with the following settings:
Setting | Value |
---|---|
Disabled | true |
Cron Schedule | 0 * * * * |
Earliest Time | -70m@m |
Latest Time | -10m@m |
Schedule Window | auto |
Creates Notable | Yes |
Rule Title | %name% |
Rule Description | %description% |
Notable Event Fields | user, dest |
Creates Risk Event | True |
Implementation
To implement crowdstrike:identities logs, use the Falcon Streaming API. Set up an API client, authenticate with your CrowdStrike credentials, and subscribe to the "crowdstrike:identities" event stream. Process and store the logs as needed, integrating them into your logging or SIEM system for monitoring and analysis.
Known False Positives
unknown
Associated Analytic Story
Risk Based Analytics (RBA)
Risk Message | Risk Score | Impact | Confidence |
---|---|---|---|
Weak Password for Admin User found on $domain$ | 80 | 100 | 80 |
References
Detection Testing
Test Type | Status | Dataset | Source | Sourcetype |
---|---|---|---|---|
Validation | ✅ Passing | N/A | N/A | N/A |
Unit | ✅ Passing | Dataset | crowdstrike:identities |
crowdstrike:identities |
Integration | ✅ Passing | Dataset | crowdstrike:identities |
crowdstrike:identities |
Replay any dataset to Splunk Enterprise by using our replay.py
tool or the UI.
Alternatively you can replay a dataset into a Splunk Attack Range
Source: GitHub | Version: 2