CyberKit

Event IDs

Security event 4742

A computer account was changed

Channel: Security. Category: Computer Account Management.

What it records

Generated on a domain controller every time an existing computer object's attributes are changed: one event per change, recording who made it (Subject), which computer account was changed, and a Changed Attributes block (SAM account name, delegation SPN list, UAC flags, DNS host name, SPNs, etc.). A change to an attribute not in that enumerated list, Microsoft's own documentation cites a DACL edit as the explicit example, still generates 4742, but with every listed attribute shown as '-'.

Why it matters

This is the trip-wire for delegation abuse. Traditional constrained-delegation abuse shows up directly: AllowedToDelegateTo going from '-' to a populated SPN list is the documented signal that a computer account's msDS-AllowedToDelegateTo attribute was set. Resource-Based Constrained Delegation abuse (writing msDS-AllowedToActOnBehalfOfOtherIdentity) still fires 4742 on the target computer object, but since that attribute isn't one of the event's enumerated fields, it lands in the same 'all attributes blank' bucket Microsoft's own docs describe for DACL changes; a 4742 against a high-value computer account with a fully blank Changed Attributes block is therefore still worth investigating even though the event doesn't name what changed.

What triggers it

Legitimately, a scheduled computer-account password rotation (roughly every 30 days by default, reflected in Password Last Set), an admin configuring Kerberos delegation on the account's Delegation tab, or routine SPN registration after a reboot following a domain join. Anomalously, an attacker with sufficient rights over a computer object writing delegation settings, flipping UAC flags such as 'Trusted For Delegation,' or making any other change to a high-value computer account (a domain controller, admin workstation, or critical server) outside a known change window.

Fields that carry the answer

Key fields
FieldWhat it tells you
Account Name (Computer Account That Was Changed)The machine account whose object was modified. Routine noise on most hosts, but a change on a domain controller or admin workstation account is high-value.
AllowedToDelegateToPopulated (rather than '-') means the account's constrained-delegation SPN list was set or changed: the direct signal for constrained-delegation abuse.
New UAC ValueAccount-control flags after the change. Compare against Old UAC Value for 'Trusted For Delegation' or 'Trusted To Authenticate For Delegation' flipping to enabled on an account that shouldn't have delegation rights.
Account Name (Subject)Who made the change: the operator to check against expected admin/deployment activity.
Password Last SetShould change roughly monthly for a normal computer account; more frequent changes can indicate an anomaly.

In practice

Logged when CORP\admin-jdoe changes computer account WEBSRV03$'s New UAC Value to include 'Trusted For Delegation' with AllowedToDelegateTo populated with an SPN list. Expected if a planned constrained-delegation configuration is underway, but worth escalating if WEBSRV03$ wasn't on the approved delegation list. A 4742 against a domain controller's own computer account with every Changed Attributes field showing '-' is consistent with a DACL-level edit such as writing msDS-AllowedToActOnBehalfOfOtherIdentity to configure Resource-Based Constrained Delegation.

Sample record

A computer account was changed.

Subject:
	Security ID:		CORP\admin-jdoe
	Account Name:		admin-jdoe
	Account Domain:		CORP
	Logon ID:		0x2E80C

Computer Account That Was Changed:
	Security ID:		CORP\WEBSRV03$
	Account Name:		WEBSRV03$
	Account Domain:		CORP

Changed Attributes:
	SAM Account Name:	-
	Display Name:		-
	AllowedToDelegateTo:	HOST/WEBSRV03.corp.local
	Old UAC Value:		0x1000
	New UAC Value:		0x81000
	DNS Host Name:		-
	Service Principal Names:	-

Additional Information:
	Privileges:		-

Sources

Paste a record into Event XML or open a log in EVTX Reader.