Event ID 4742 is a Windows security log event indicating that a computer account was changed. In Zerologon investigations, this event becomes especially important when the change is made by Anonymous Logon, because that pattern can signal suspicious or malicious password reset activity on a domain controller.
What Event ID 4742 Means in Windows Security Monitoring
Event ID 4742 is a change event for a computer account, so it belongs in the same investigative family as other directory and account-management telemetry rather than generic host noise. In practice, it helps answer who changed the account, when the change occurred, and whether the modification fits expected administration or looks like abuse.
That matters because computer-account changes can affect trust relationships, password state, delegation settings, and directory access paths. When the event appears in an investigation, the key question is not just whether a change happened, but whether the actor, timing and surrounding log context make the change legitimate.
Why It Matters in Zerologon Investigations
In Zerologon cases, Event ID 4742 becomes especially important when the computer account change is made by Anonymous Logon. That pattern can indicate suspicious password reset activity on a domain controller, which is why defenders treat it as a correlation point rather than a standalone alert.
The event is most useful when read alongside adjacent domain-controller telemetry. A single log record rarely proves compromise on its own, but a computer-account change from an unexpected security principal can strengthen the case that an attacker interacted with directory state, not just application data.
For broader Windows logging context, Windows Event Log Guide is the natural reference for how event IDs, audit policy and log sources fit together.
How Analysts Use the Event During Triage
Analysts typically use Event ID 4742 as a triage pivot. They compare the affected computer account with domain-controller activity, review the subject account and source fields, and look for nearby indicators such as other account changes, authentication anomalies, or directory-service events that show the change was part of a larger sequence.
The event is also valuable for baseline validation. Not every computer-account change is malicious, because administrators, provisioning systems and legitimate lifecycle tasks can update machine accounts. The practical task is to separate routine maintenance from changes that occur outside approved change windows or from principals that should not be performing the action.
For identity and access context around account manipulation, MITRE ATT&CK T1098 Account Manipulation Guide helps place computer-account changes in a broader abuse pattern.
Detection, Baselines and Response Follow-Up
Detection works best when Event ID 4742 is paired with directory-change telemetry, authentication logs and host coverage on domain controllers. If the event shows an unexpected caller, defenders should validate whether the account change aligns with known admin workflows, service operations or recovery activity.
When the event supports a suspected compromise, the follow-up is to review surrounding directory state, confirm whether any related passwords, sessions or trust-linked credentials need rotation, and determine whether additional changes were made to persist access. In other words, the event is a clue to possible compromise, not the end of the investigation.
For defenders building domain-controller coverage, Active Directory Security Monitoring and Event IDs Guide gives the surrounding event model, and Kerberos Security Guide is useful when the investigation expands into ticketing, resets and trust abuse.
Practical Interpretation for Security Teams
Event ID 4742 is best treated as a high-value change signal, not a generic log line. Its meaning depends on whether the computer account change was expected, who performed it, and whether the surrounding telemetry supports routine administration or suspicious reset activity.
A mature monitoring approach gives this event a clear place in the investigative workflow, because machine-account changes can be part of both normal operations and adversary action. Security teams get the most value when they use the event to narrow the question quickly: was this a sanctioned change, or a sign that the domain controller or its account state has been manipulated?
For response workflow and related event coverage, Endpoint Telemetry Guide helps show how Windows audit data should be collected and correlated across the environment.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1098 — Account Manipulation | Event 4742 can indicate account-state manipulation on a computer account. |
| T1078 — Valid Accounts | Suspicious computer-account changes can support valid-account abuse and persistence. | |
| Recommendation — Correlate 4742 with other account-change telemetry to confirm or rule out manipulation. Treat unexpected 4742 activity as a lead for valid-account abuse and persistence hunting. | ||
| NIST SP 800-53 Rev 5 | AU-6 — Audit Review, Analysis, and Reporting | Event 4742 is useful only when audit data is reviewed and correlated effectively. |
| IA-5 — Authenticator Management | Computer-account changes can affect passwords and other authenticating material. | |
| AC-2 — Account Management | The event records account lifecycle changes that fall under account governance. | |
| Recommendation — Review and correlate computer-account change events with adjacent logs for context. Validate and rotate affected authenticators when a suspicious computer-account change is confirmed. Track, approve, and investigate computer-account changes as account-management events. | ||
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org