Windows Create Local Account
Description
The following analytic detects the creation of a new local user account on a Windows system. It leverages Windows Security Audit logs, specifically event ID 4720, to identify this activity. Monitoring the creation of local accounts is crucial for a SOC as it can indicate unauthorized access or lateral movement within the network. If confirmed malicious, this activity could allow an attacker to establish persistence, escalate privileges, or gain unauthorized access to sensitive systems and data.
Query · spl
| tstats `security_content_summariesonly`
values(All_Changes.result_id) as result_id
count min(_time) as firstTime
max(_time) as lastTime
from datamodel=Change where
All_Changes.result_id=4720
by All_Changes.user All_Changes.dest All_Changes.result All_Changes.action
| `drop_dm_object_name("All_Changes")`
| `security_content_ctime(lastTime)`
| `security_content_ctime(firstTime)`
| `windows_create_local_account_filter`
Implementation guide
This search requires you to have enabled your Group Management Audit Logs in your Local Windows Security Policy and be ingesting those logs. More information on how to enable them can be found here: http://whatevernetworks.com/auditing-group-membership-changes-in-active-directory/
Known false positives
- It is possible that an administrator created the account. Verifying activity with an administrator is advised. Accounts created on Domain Controllers will trigger this too. Exclude if it becomes too noisy. This analytic is set to anomaly to allow for risk to be added. Filter and tune as needed. Restrict to critical infrastructure to reduce any volume.
Analyst notes
Known false positives: It is possible that an administrator created the account. Verifying activity with an administrator is advised. Accounts created on Domain Controllers will trigger this too. Exclude if it becomes too noisy. This analytic is set to anomaly to allow for risk to be added. Filter and tune as needed. Restrict to critical infrastructure to reduce any volume.