CyberKit

Event IDs

Security event 4674

An operation was attempted on a privileged object

Channel: Security. Category: Privilege Use (Audit Sensitive Privilege Use / Audit Non Sensitive Privilege Use).

What it records

Generated when an attempt is made to perform a privileged operation on a protected subsystem object that is already open: e.g., using SeShutdownPrivilege, SeRemoteShutdownPrivilege, or SeSecurityPrivilege. A Failure event records unsuccessful attempts.

Why it matters

Captures privileged actions taken against an already-opened object/handle. Microsoft's own guidance specifically calls out monitoring Failure events here, since a failed attempt to exercise a sensitive privilege (e.g., SeSecurityPrivilege to tamper with the security log) is a strong signal of malicious intent.

What triggers it

Legitimate administrative operations such as remote shutdowns or security-log management, as well as attempts to manipulate protected objects (e.g., trying to clear/alter the security log), especially notable when the requesting account is not an expected administrator.

Fields that carry the answer

Key fields
FieldWhat it tells you
Object NameThe object the privileged operation targeted, when captured.
PrivilegesThe specific privilege exercised against the already-open object (e.g. SeSecurityPrivilege for security-log tampering, SeShutdownPrivilege/SeRemoteShutdownPrivilege). Microsoft specifically flags Failure events here as a strong signal of malicious intent.
Object ServerThe Windows subsystem the operation was performed against (e.g. LSA, Security Account Manager), which scopes what part of the system was targeted.
Process NameThe process performing the privileged operation.

In practice

A Failure 4674 shows account CORP\jsmith, Object Server Security Account Manager, and Privileges SeSecurityPrivilege on an already-open handle to the Security event log: a failed attempt to exercise the privilege needed to clear or tamper with the log, which Microsoft's own guidance flags as a strong signal of malicious intent even though the attempt didn't succeed.

Sample record

An operation was attempted on a privileged object.

Subject:
	Security ID:		S-1-5-19
	Account Name:		LOCAL SERVICE
	Account Domain:		NT AUTHORITY
	Logon ID:		0x3E5

Object:
	Object Server:		LSA
	Object Type:		-
	Object Name:		-
	Object Handle:		0x0

Process Information:
	Process ID:		0x1F0
	Process Name:		C:\Windows\System32\lsass.exe

Requested Operation:
	Desired Access:		16777216
	Privileges:		SeSecurityPrivilege

Sources

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