Windows Event ID 4674: An operation was attempted on a privileged object
Written when a privileged operation is attempted on an already-opened protected object. It is one of the events that captures the actual use of a strong right.
Overview
The subcategories are Audit Sensitive Privilege Use and Audit Non Sensitive Privilege Use. It is generated when a privileged operation is performed on an already-opened protected subsystem object. Typical cases are use of SeShutdownPrivilege (shutdown), SeRemoteShutdownPrivilege (remote shutdown), or SeSecurityPrivilege (manage auditing and the security log). A failed operation produces a Failure event.
How it is triggered
- A privileged operation on an opened object (shutdown, manipulating the security log, and so on).
- The privilege used appears in the
Privilegesfield.
Security review points
- Use of
SeSecurityPrivilegerelates to manipulating the security log (clearing it, and so on), so note it in the context of evidence concealment. Read it together with the log clear 1102. - Exercising remote-shutdown privilege can be disruption aimed at availability. Investigate use by an unexpected subject.
Notes for log review
- Like 4673, enabling it yields a high volume. Narrow by notable privilege and subject.
- It also appears in legitimate system operations (such as shutdown). Confirm who used which privilege in the expected context.
MITRE ATT&CK mapping
| Technique | Tactic | What this event shows |
|---|---|---|
| T1685.005 Clear Windows Event Logs | Defense Impairment | Use of SeSecurityPrivilege can precede a log clear |
| T1529 System Shutdown/Reboot | Impact | Use of the remote shutdown privilege by an unexpected subject |
Mapping as of ATT&CK v19.2. To search by technique, see the ATT&CK reverse lookup.
Detection rules
SigmaHQ has 1 public detection rule that uses this event ID as a condition.
| Rule | Type | Severity |
|---|---|---|
| SCM Database Privileged Operation | Sigma | Medium |
Rules are collected from SigmaHQ r2026-07-01 and from Azure-Sentinel as of 2026-10-09, limited to those whose conditions include this event ID. Sentinel rules are limited to those that query the SecurityEvent or WindowsEvent table. “Threat-specific” rules target a particular threat group or malware, and “needs setup” rules require values for your environment. Severity is the value each rule’s author assigned.
Key fields
| Field | Meaning |
|---|---|
Subject\Account Name | The account that performed the operation |
Privileges | The privilege used |
Process Name | The originating process |