Windows Security log
4720 A user account was created.
A user account was created, in the domain (logged on a domain controller) or locally.
- SecurityLog
- Microsoft-Windows-Security-AuditingSource
- Audit User Account ManagementAudit policy
- 0Cases and alerts that use it
Fields to read
| Field | What it tells you |
|---|---|
SubjectUserName | Who created it. |
TargetUserName | The new account. |
Normal
- Onboarding new staff through the usual provisioning process and accounts.
Suspicious
- An account created outside that process, by an administrator account at night.
- A name that imitates a service account, followed by a 4728 or 4732 group addition.
Find it
Microsoft Sentinel (KQL)
SecurityEvent
| where EventID == 4720Splunk (SPL)
index=wineventlog source="XmlWinEventLog:Security" EventCode=4720Table, index and source names as CyberSim uses them; your workspace may name them differently.
Where you meet it in CyberSim
The L3 war room
- Macro to domain takeover
Other Security events
- 4624 An account was successfully logged on.
- 4625 An account failed to log on.
- 4634 An account was logged off.
- 4661 A handle to an object was requested.
- 4662 An operation was performed on an object.
- 4663 An attempt was made to access an object.
- 4672 Special privileges assigned to new logon.
- 4688 A new process has been created.
- 4698 A scheduled task was created.
- 4728 A member was added to a security-enabled global group.
- 4768 A Kerberos authentication ticket (TGT) was requested.
- 4769 A Kerberos service ticket was requested.
- 4886 Certificate Services received a certificate request.
- 4887 Certificate Services approved a certificate request and issued a certificate.
- 5136 A directory service object was modified.
- 5145 A network share object was checked to see whether client can be granted desired access.
- 6416 A new external device was recognized by the System.
Source: Microsoft Learn: event 4720