Home / Blog / Alert Triage
Spotting New Local Admin Accounts with Events 4720 and 4732
Learn what Windows events 4720 and 4732 show, why seeing both close together matters, and how to check them with a short Splunk search and a few simple questions.
A new account on a server is not unusual. A new account that is quickly made a local administrator is a pattern worth a second look. This guide explains the two Windows events behind that pattern, event 4720 and event 4732, and shows how a SOC (Security Operations Centre) analyst checks them without jumping to conclusions.
The two events to learn first
Windows writes both events to the Security log, but only if the matching audit setting is switched on.
- 4720: a user account was created. It belongs to the Audit User Account Management setting.
- 4732: a member was added to a security-enabled local group. It belongs to the Audit Security Group Management setting.
Both events can appear on domain controllers, member servers and workstations. On a domain controller, 4720 is about a domain account. On other machines it is usually about a local account on that machine.
The detail inside each event is split into blocks. These are the ones to read:
- Subject: the account that made the change. Read this first in both events.
- New Account (4720): the name of the account that was created.
- Member (4732): the account that was added to the group.
- Group (4732): the group that gained a member, such as Administrators.
Tip: In a 4732 event for a local group, the Member account name is often just a dash, even when the member is a domain account. Read the Member Security ID (SID, the unique number Windows gives every account and group) instead. The built-in local Administrators group always has the SID S-1-5-32-544, so you can recognise it on any Windows machine, whatever language it uses.
Why the pair matters more than either event alone
Someone who gains access to a machine often wants a way back in that does not depend on one stolen password or one piece of malware. A spare account with admin rights does that job.
MITRE ATT&CK is a public catalogue of attacker behaviours. It lists this as Create Account: Local Account, technique T1136.001, under the Persistence tactic. Adding the account to a group fits Account Manipulation, technique T1098.
Each event on its own is usually harmless:
- A 4720 alone is normal when IT builds a new account.
- A 4732 alone is normal when someone joins a support team.
- Both on the same host within a short time tell a story: an account was made and given admin rights.
That short time is your window. One hour on the same host is a sensible starting point. It is a choice you can tune, not a standard.
Two short Splunk searches
Start by listing both events for the last day. The index name is a placeholder, so use the one your team has.
index=wineventlog sourcetype="WinEventLog:Security" (EventCode=4720 OR EventCode=4732) earliest=-24h
| table _time host EventCode src_user user Group_Name
| sort _time
- Line 1 finds the two event codes in the Security log from the last 24 hours.
- Line 2 shows the time, host, event code, the names and the group. With the Splunk Add-on for Microsoft Windows, src_user is usually who made the change and user is usually the account created or added.
- Line 3 puts the oldest event first, so you read the story in order.
Field names depend on how your data is collected. Click the fields list beside your results to see what you actually have, then adjust.
Next, keep only hosts where both events fall in the same hour, and only count 4732 when the group is Administrators.
index=wineventlog sourcetype="WinEventLog:Security" earliest=-24h (EventCode=4720 OR (EventCode=4732 Group_Name="Administrators"))
| bin _time span=1h
| stats count values(EventCode) AS codes dc(EventCode) AS event_types by _time host
| where event_types=2
- Line 1 keeps every 4720, but only the 4732 events where the group name is Administrators.
- Line 2 drops each event into a one hour bucket.
- Line 3 counts events per host per hour, lists the codes seen, and counts how many different codes appeared.
- Line 4 keeps only the rows where both codes appeared.
Buckets have hard edges. A 4720 at 10:58 and a 4732 at 11:03 land in different hours and will be missed, so run the first search too when something looks close.
Questions to ask before you escalate
A hit from the search is a lead, not a verdict. Work through these in order:
- Who is in Subject? An IT admin or a build service account may be expected. An ordinary user who never does admin work is not.
- Is there a change ticket for that host and that time?
- Does the new name fit your naming standard, or does it imitate a system name?
- What did the account do next? Search for successful logons (event 4624) using that name, and note where they came from.
- Was it deleted soon after? Event 4726 records a deleted account, and a short life can hide temporary admin use.
On a machine you are allowed to check, these read-only PowerShell lines show the current state:
Get-LocalGroupMember -Group "Administrators"
Get-LocalUser | Select-Object Name, Enabled, PasswordLastSet, LastLogon
- Line 1 lists who is in the local Administrators group right now.
- Line 2 lists local accounts, whether each is enabled, when the password was last set and the last logon time.
Expect false positives. Imaging tools, software installers and helpdesk work all create accounts and change groups. The ticket and the Subject account settle most of them quickly.
Where this shows up and what to study next
On a shift you will usually meet this as a SIEM (Security Information and Event Management) alert with a name like "user added to local Administrators". Your job is to gather the facts above and pass them clearly to the host owner or to the next level.
As far as I could verify, CompTIA CySA+ CS0-003 objective 1.2 covers indicators of potentially malicious activity, and objective 1.3 includes log analysis and correlation, which is exactly what this exercise practises. Check CompTIA's official objectives page for the current exam version before you plan your study.
Try these next:
- On a test virtual machine only, create a test local user, add it to a test group, then find the 4720 and 4732 events in Event Viewer.
- Read the Microsoft Learn pages for events 4720 and 4732 and compare their field lists with what you saw.
- Read the mitigations on the ATT&CK page for T1136.001, such as limiting who can create accounts.
The habit to keep is simple: read the Subject first, look at the group second, and ask whether anyone expected the change.
Written by Ben, Cybersecurity Student