CyberKit

Event ID Reference

The Windows Security and Sysmon event IDs that matter for DFIR.

The Windows Security and Sysmon event IDs that matter for DFIR, each checked against Microsoft's own auditing and Sysinternals documentation.

Open an event for what triggers it, the fields that carry the answer, a sample record, related events and ATT&CK mappings.

Before you read the table

  • Many of these only exist if the audit policy turns them on. 4688 without command-line auditing has no command line.
  • Sysmon events need Sysmon installed and a configuration that keeps them.

125 rows.

Windows Security and Sysmon event IDs
IDSourceNameWhat it shows
1100securityThe event logging service has shut downGenerated by the Windows Eventlog service whenever the Event Log service itself shuts down: both during a normal system shutdown/restart and when the service is stopped independently of a shutdown. It does not generate during an emergency system reset.
1102securityThe audit log was clearedGenerated by the Windows Eventlog service itself (Provider Microsoft-Windows-Eventlog, not the Security-Auditing provider) every time the Security event log is cleared. The event's LogFileCleared payload records the SID, account name, domain, and logon ID of whoever performed the clear.
1104securityThe security log is now fullGenerated when the Security event log reaches its maximum configured size while the log's retention method is set to 'Do not overwrite events (clear logs manually)': new events stop being recorded until the log is archived or cleared.
4624securityAn account was successfully logged onRecords that a logon session was created on the computer being accessed. Captures the account (Subject and New Logon), the Logon Type (Interactive, Network, RemoteInteractive/RDP, Service, Batch, Unlock, NewCredentials, etc.), the process that requested the logon, and the source workstation/IP.
4625securityAn account failed to log onLogged for any failed logon attempt, regardless of the reason, on the computer where the attempt was made. Captures the target account, the Logon Type attempted, the source workstation/IP, and a Status/Sub Status code identifying the specific failure reason.
4626securityUser/Device claims informationGenerated together with 4624 for new account logons and lists the user and/or device claims (Dynamic Access Control attributes) associated with the new logon session. It does not fire if the account/device carries no claims; requires the Audit Logon subcategory (success) to also be enabled.
4627securityGroup membership informationGenerated together with 4624 and lists every group SID the logged-on account belongs to at logon time. Multiple 4627 events are generated (marked with an event-in-sequence counter) if the full membership list doesn't fit in one record.
4634securityAn account was logged offRecords that a logon session was terminated and no longer exists. Logged on the computer where the session existed, and includes the account and the Logon Type of the session that ended.
4647securityUser initiated logoffGenerated when a logoff is initiated by the account itself (via the logoff function), as opposed to the session simply ending. Typically appears alongside 4634 for the same Logon ID.
4648securityA logon was attempted using explicit credentialsLogged when a process explicitly specifies a different account's credentials to start a new logon, rather than using the current session's identity. Records both the originating account (Subject) and the account whose credentials were used, plus the target server and process.
4649securityA replay attack was detectedGenerated on a domain controller when the KDC returns KRB_AP_ERR_REPEAT. It received a Kerberos authenticator (server name, client name, timestamp, microseconds) that duplicates one it has already cached from a recent request.
4656securityA handle to an object was requestedLogged the first time a process requests a handle to a file, registry key, or other securable object that has a SACL configured for the requested access type, recording the requested access rights (Access List/Access Mask) and whether the request was granted (Success) or refused (Failure).
4658securityThe handle to an object was closedGenerated when a previously opened handle to an audited object (file, registry key, etc.) is closed, provided Success auditing is enabled for the Audit Handle Manipulation subcategory. Records only the Handle ID and process information, not the object's name.
4660securityAn object was deletedGenerated when an object that has 'Delete' auditing set in its SACL is actually deleted. Contains only the Handle ID (not the object's name): the name must be resolved by correlating back to the 4656 event that shares the same Handle ID.
4663securityAn attempt was made to access an objectRecords that specific access rights (read, write, delete, etc.) were actually exercised against an audited object, unlike 4656, which shows only that access was requested. Includes the Object Name directly, and has no Failure variant.
4672securitySpecial privileges assigned to new logonFires whenever a new logon session is granted one or more sensitive privileges from a fixed list (SeTcbPrivilege, SeBackupPrivilege, SeCreateTokenPrivilege, SeDebugPrivilege, SeEnableDelegationPrivilege, SeAuditPrivilege, SeImpersonatePrivilege, SeLoadDriverPrivilege, SeSecurityPrivilege, SeSystemEnvironmentPrivilege, SeAssignPrimaryTokenPrivilege, SeRestorePrivilege, and SeTakeOwnershipPrivilege), and lists exactly which were assigned.
4673securityA privileged service was calledGenerated when an attempt is made to perform a privileged system-service operation: e.g., using SeTcbPrivilege, SeSystemtimePrivilege, or SeCreateGlobalPrivilege. A Failure event is logged if the privileged service call fails.
4674securityAn operation was attempted on a privileged objectGenerated 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.
4675securitySIDs were filteredGenerated on a domain controller when one or more SIDs presented across an Active Directory trust are filtered (stripped) according to that trust's SID-filtering configuration. Records the target account, the trust direction/type, and the filtered SIDs.
4688securityA new process has been createdGenerates every time a new process starts. Records the new process's PID and full image path, the parent/creator process, the account under which it ran, the token elevation type, and, only if the 'Include command line in process creation events' Group Policy is enabled, the full command line (empty by default).
4689securityA process has exitedGenerates every time a process exits. Records the process name and PID, the account that requested termination, and the process's exit status code.
4697securityA service was installed in the systemGenerated (Windows Server 2016 / Windows 10 and later) when a new service is registered with the Service Control Manager, recording the service name, the Service File Name (binary path, including any command-line parameters), Service Type, Service Start Type, and the Service Account it runs as.
4698securityA scheduled task was createdGenerated every time a new scheduled task is registered with Task Scheduler, capturing the Task Name (path within the Task Scheduler Library tree) and the full Task Content XML: triggers, actions, run-as principal, and logon type.
4699securityA scheduled task was deletedGenerated every time an existing scheduled task is deleted, recording the Task Name and the XML content of the deleted task.
4700securityA scheduled task was enabledGenerated every time a scheduled task is enabled (a task must be enabled to run at its scheduled time), recording the Task Name and its XML content.
4701securityA scheduled task was disabledGenerated every time a scheduled task is disabled (the task definition remains, but it won't run until re-enabled) recording the Task Name and its XML content.
4702securityA scheduled task was updatedGenerated whenever an existing scheduled task's definition is changed (any modification other than enabling/disabling) recording the Task Name and the new Task Content XML.
4719securitySystem audit policy was changedGenerated whenever the local computer's audit policy changes, identifying which audit category and subcategory (e.g., Logon/Logoff, Object Access) was modified and whether Success and/or Failure auditing was added or removed for it. Per Microsoft's documentation, this event is always logged regardless of whether the 'Audit Policy Change' subcategory is itself set to be audited.
4720securityA user account was createdRecords the creation of a new local or domain user object, capturing the creator's identity and a snapshot of the new account's initial attributes (SAM account name, display name, UPN, primary group, UAC flags, password-last-set, etc.).
4722securityA user account was enabledRecords that a previously disabled user account (or, on a domain controller, computer account) was re-enabled, identifying who performed the operation and which account was affected.
4723securityAn attempt was made to change an account's passwordRecords a self-service password-change attempt (the account changing its own credentials) logging success or failure for both domain and local accounts.
4724securityAn attempt was made to reset an account's passwordRecords when one account (typically an administrator or help-desk operator) resets the password of a different account, rather than the account changing its own password.
4725securityA user account was disabledRecords that a user account (or, on a domain controller, computer account) was disabled, identifying who disabled it and which account was affected.
4726securityA user account was deletedRecords the deletion of a user object, identifying who requested the deletion and which account was removed.
4727securityA security-enabled global group was createdRecords the creation of a new security-enabled global group in Active Directory: the domain-wide group scope most commonly used for role- and department-based access (e.g. Domain Admins). Documented by Microsoft as field-identical to event 4731, generated for the global scope instead of local.
4728securityA member was added to a security-enabled global groupRecords that an account was added as a member of a security-enabled global group, capturing who performed the addition (Subject), which account was added (Member), and which group (Target) it was added to. Documented by Microsoft as field-identical to event 4732, generated for a global group instead of a local group.
4729securityA member was removed from a security-enabled global groupRecords that an account was removed from a security-enabled global group. Documented by Microsoft as field-identical to event 4733, generated for a global group instead of a local group.
4730securityA security-enabled global group was deletedRecords the deletion of a security-enabled global group. Documented by Microsoft as field-identical to event 4734, generated for a global group instead of a local group.
4731securityA security-enabled local group was createdRecords the creation of a new security-enabled local group. Scoped to a single machine's local SAM database (member server or workstation) or, for a domain-local group, scoped within a domain.
4732securityA member was added to a security-enabled local groupRecords that an account was added as a member of a security-enabled local group: most notably the built-in local Administrators group on a workstation or server. A separate event is logged per member added, and it typically follows a 4735 'group changed' event with no visible attribute changes.
4733securityA member was removed from a security-enabled local groupRecords that an account was removed from a security-enabled local group, most notably the local Administrators group. A separate event is logged per member removed.
4734securityA security-enabled local group was deletedRecords the deletion of a security-enabled local group on a domain controller, member server, or workstation.
4735securityA security-enabled local group was changedFires whenever a security-enabled local group's tracked attributes change (its SAM account name or SID History). If the change is to an attribute this event doesn't track (for example, a DACL edit) it still generates but every Changed Attribute field shows '-', giving no detail on what changed.
4737securityA security-enabled global group was changedFires whenever a security-enabled global group's tracked attributes change. Documented by Microsoft as field-identical to event 4735, generated for a global group instead of a local group.
4738securityA user account was changedFires on modifications to a user object's attributes (display name, UPN, home directory, delegation settings (AllowedToDelegateTo), primary group, or User Account Control flags) with a separate event per change. Some changes (e.g. a DACL edit) still generate the event but show every Changed Attribute as '-', giving no detail on what changed.
4740securityA user account was locked outRecords that a user account was locked out after exceeding the configured failed-logon threshold, including the account performing the lockout (almost always SYSTEM) and the Caller Computer Name the failed attempts originated from.
4749securityA security-disabled global group was createdRecords the creation of a new security-disabled global group. Microsoft's internal term for a distribution group (e.g. a mail distribution list), which cannot be used to grant permissions the way a security group can. Generated only on domain controllers.
4751securityA member was added to a security-disabled global groupRecords that an account was added as a member of a security-disabled global (distribution) group. Generated only on domain controllers, with a separate event per member added.
4752securityA member was removed from a security-disabled global groupRecords that an account was removed from a security-disabled global (distribution) group. Generated only on domain controllers, with a separate event per member removed.
4754securityA security-enabled universal group was createdRecords the creation of a new security-enabled universal group: a group scope that, unlike local/global, can contain members from any domain in the forest and be granted access anywhere in the forest. Documented by Microsoft as field-identical to event 4731, generated for the universal scope. Generates only on domain controllers.
4755securityA security-enabled universal group was changedFires whenever a security-enabled universal group's tracked attributes change. Documented by Microsoft as field-identical to event 4735, generated for a universal group.
4756securityA member was added to a security-enabled universal groupRecords that an account was added as a member of a security-enabled universal group. Documented by Microsoft as field-identical to event 4732, generated for a universal group, which can be granted access forest-wide.
4757securityA member was removed from a security-enabled universal groupRecords that an account was removed from a security-enabled universal group. Documented by Microsoft as field-identical to event 4733, generated for a universal group.
4758securityA security-enabled universal group was deletedRecords the deletion of a security-enabled universal group. Documented by Microsoft as field-identical to event 4734, generated for a universal group.
4764securityA group's type was changedRecords a change to a group's type (for example, converting a security-enabled group to security-disabled (distribution), or changing its scope between local/global/universal) showing both the before and after type. Generates only on domain controllers, for both security and distribution groups.
4767securityA user account was unlockedRecords that a previously locked-out user account was unlocked, identifying who performed the unlock and which account was affected.
4768securityA Kerberos authentication ticket (TGT) was requestedLogged only on a domain controller every time the Key Distribution Center (KDC) issues, or fails to issue, a Kerberos Ticket Granting Ticket (TGT). Records the requesting account, client IP, pre-authentication type, ticket/session encryption types, and a Result Code identifying the reason for any failure. Result Codes 0x10 and 0x18 never appear here. Microsoft's documentation states those failures generate event 4771 instead.
4769securityA Kerberos service ticket was requestedLogged only on a domain controller each time the KDC receives a Kerberos Ticket Granting Service (TGS) ticket request. Records the requesting account, the target Service Name/SID, client IP, ticket encryption type, and a Failure Code for unsuccessful requests. Microsoft's own guidance notes that Failure Code 0x20 (an expired service ticket) is routine and has little to no security relevance.
4770securityA Kerberos service ticket was renewedLogged only on a domain controller for every renewal of an existing Kerberos TGS ticket. Records the requesting account, the service the ticket is for, client IP, and ticket options/encryption type.
4771securityKerberos pre-authentication failedLogged only on a domain controller when the KDC fails to issue a TGT specifically because Kerberos pre-authentication failed. Records the account, client IP, and a Failure Code (e.g., 0x18 = wrong password; 0x10 = KDC has no support for the PADATA/pre-authentication type, often a smart-card certificate/CA issue). Not generated for accounts configured with 'Do not require Kerberos preauthentication' (4768 covers those instead).
4772securityA Kerberos authentication ticket request failedA defined Windows security event ID that, per Microsoft's own documentation, currently doesn't generate. It is a defined event that is never invoked by the operating system; a Failure instance of event 4768 is generated instead.
4773securityA Kerberos service ticket request failedA defined Windows security event ID that, per Microsoft's own documentation, currently doesn't generate. It is a defined event that is never invoked by the operating system; a Failure instance of event 4769 is generated instead.
4774securityAn account was mapped for logonMicrosoft's documented schema for this event records an Authentication Package, an Account UPN, and a Mapped Name, indicating an account was mapped for logon (e.g., certificate- or alternate-identity-to-account mapping). Microsoft's reference page provides only this bare schema, with no narrative description, example, required-role, or minimum-OS information.
4775securityAn account could not be mapped for logonA defined Windows security event whose schema records an Authentication Package and Account Name, but Microsoft's own documentation states plainly: 'It appears that this event never occurs.'
4776securityThe computer attempted to validate the credentials for an accountLogged on whichever computer is authoritative for an account's credentials (a domain controller for domain accounts, or the local machine for local accounts) whenever NTLM credential validation occurs. Records the Logon Account, the Source Workstation the request originated from, and an Error Code for failures. It shows only the source workstation, not the destination computer being accessed, and does not fire when a domain account logs on locally to a domain controller.
4781securityThe name of an account was changedRecords a change to a user or computer account's sAMAccountName (logon name), showing both the old and new account names.
4946securityA change has been made to Windows Firewall exception list. A rule was addedGenerated when a new rule is added locally to Windows Firewall (e.g., via `netsh`, PowerShell's `New-NetFirewallRule`, or the Windows Firewall with Advanced Security console); records the affected profile(s) (Domain/Private/Public/All) plus the new rule's unique ID (GUID) and name. Does not generate when a rule is added via Group Policy.
4947securityA change has been made to Windows Firewall exception list. A rule was modifiedGenerated when an existing local Windows Firewall rule is modified. Records the affected profile(s) and the modified rule's unique ID (GUID) and name. Does not generate when a rule is modified via Group Policy.
4948securityA change has been made to Windows Firewall exception list. A rule was deletedGenerated when a local Windows Firewall rule is deleted. Records the affected profile(s) and the deleted rule's unique ID (GUID) and name. Does not generate when a rule is deleted via Group Policy.
4950securityA Windows Firewall setting has changedGenerated when a local Windows Firewall profile-level setting changes (for example the Default Outbound Action, or whether the firewall is enabled for a profile) recording the affected profile plus the setting's name and new value. Does not generate when the setting is changed via Group Policy.
5140securityA network share object was accessedGenerated once per session, on the first access attempt, whenever a network share object is accessed. Records the requesting account, source IP address/port, the share name and its local (NTFS) path, and a coarse access mask (always 'ReadData (or ListDirectory)' for this event).
5145securityA network share object was checked to see whether client can be granted desired accessGenerated on every access to a file or folder within a network share, recording the specific relative target file/folder name, the detailed access rights requested (e.g., ReadData, WriteData, Delete, ReadAttributes), and the access-check result showing which ACE granted or denied each right. Per Microsoft's documentation, failure events are generated only when access is denied at the share level, not the NTFS level.
7045securityA service was installed in the systemLogged to the System channel (source: Service Control Manager) whenever a new service is installed, recording the Service Name, the full Service File Name/ImagePath to its executable, Service Type, Service Start Type, and the Service Account it runs as.
1sysmonProcess creationLogs the creation of a new process, capturing the full command line (for both the new process and its parent), a ProcessGuid for reliable correlation across events, and a hash of the executable image (SHA1 by default, or MD5/SHA256/IMPHASH).
2sysmonA process changed a file creation timeRecords when a process explicitly modifies a file's creation timestamp, helping track the real creation time of a file.
3sysmonNetwork connectionLogs TCP/UDP network connections initiated by a process, including source/destination hostnames, IP addresses, port numbers, and IPv6 status. Disabled by default because of the volume it generates.
4sysmonSysmon service state changedReports the state of the Sysmon service itself: that it started or stopped.
5sysmonProcess terminatedReports when a process ends, providing the UtcTime, ProcessGuid, and ProcessId of the process.
6sysmonDriver loadedLogs when a kernel driver is loaded, including configured file hashes and signature information (verified asynchronously, so it also flags a file removed right after loading).
7sysmonImage loadedLogs when a module (DLL) is loaded into a specific process, including hash and signature information. Disabled by default and must be explicitly configured (with the -l option) because of the high event volume it produces.
8sysmonCreateRemoteThreadDetects when one process creates a thread in another process, recording the source and target process along with the inferred start address, module, and function of the new thread.
9sysmonRawAccessReadDetects when a process conducts read operations from a drive using the \\.\ device-path notation, bypassing normal file-system APIs.
10sysmonProcessAccessReports when one process opens a handle to another process: an operation typically followed by information queries or reading/writing that process's memory.
11sysmonFileCreateLogs file creation and overwrite operations, including the target path and the process that performed it.
12sysmonRegistryEvent (Object create and delete)Logs the creation and deletion of registry keys and values.
13sysmonRegistryEvent (Value Set)Logs registry value modifications, recording the data written for DWORD and QWORD value types.
14sysmonRegistryEvent (Key and Value Rename)Logs registry key and value rename operations, recording the new name of the renamed key or value.
15sysmonFileCreateStreamHashLogs the creation of a named file stream (alternate data stream) on a file, along with a hash of both the main file content (unnamed stream) and the named stream's content.
16sysmonServiceConfigurationChangeLogs changes to the Sysmon configuration itself, such as when filtering rules are updated.
17sysmonPipeEvent (Pipe Created)Logs the creation of a named pipe, used for interprocess communication.
18sysmonPipeEvent (Pipe Connected)Logs when a client connects to an existing named-pipe server.
19sysmonWmiEvent (WmiEventFilter activity detected)Logs the registration of a WMI event filter, recording the WMI namespace, filter name, and filter expression.
20sysmonWmiEvent (WmiEventConsumer activity detected)Logs the registration of a WMI event consumer (the action that executes when the bound filter's condition fires) recording the consumer name, log, and destination.
21sysmonWmiEvent (WmiEventConsumerToFilter activity detected)Logs when a WMI consumer binds to a filter, recording the consumer name and filter path that completes the subscription.
22sysmonDNSEvent (DNS query)Logs DNS queries made by a process, whether the result succeeded, failed, was cached, or not. Telemetry for this event was added for Windows 8.1 and is not available on Windows 7 and earlier.
23sysmonFileDelete (File Delete archived)Logs a file deletion and additionally saves the deleted file into the configured ArchiveDirectory (default C:\Sysmon).
24sysmonClipboardChange (New content in the clipboard)Logs when the contents of the Windows system clipboard change.
25sysmonProcessTampering (Process image change)Detects process-hiding techniques (such as process hollowing or herpaderping) where the in-memory executable image no longer matches what was originally mapped from disk.
26sysmonFileDeleteDetected (File Delete logged)Logs a file deletion, functioning like Event 23 (FileDelete) but without archiving a copy of the deleted file, reducing disk overhead compared to the archiving variant.
27sysmonFileBlockExecutableLogs when Sysmon detects and actively blocks the creation of an executable (PE-format) file, preventing it from being written.
28sysmonFileBlockShreddingLogs when Sysmon detects and blocks a file-shredding (secure delete/overwrite) operation performed by tools such as Sysinternals SDelete.
29sysmonFileExecutableDetectedLogs when Sysmon detects the creation of a new executable (PE-format) file on disk, without blocking it.
4657securityA registry value was modifiedRecords that a specific registry key VALUE (not the key itself) was modified. It generates only when 'Set Value' auditing is configured in the target key's SACL, and fires once per modified value, capturing the Operation Type (new value created, value deleted, or existing value modified) plus the value's old and new content and types.
4662securityAn operation was performed on an objectGenerated on a domain controller every time an operation is performed against an Active Directory object whose SACL is configured to audit it, which captures the object's type and distinguished name, the operation performed, the specific access rights used (Accesses/Access Mask), and the Properties field listing the GUIDs of the specific attributes or extended rights involved. One 4662 is generated per operation type performed.
4741securityA computer account was createdGenerated only on a domain controller every time a new computer object is created in Active Directory. Captures who created it (Subject), the new machine account's name and SID, and a snapshot of its initial attributes: SAM account name, UAC flags, primary group, password-last-set, DNS host name, and registered SPNs.
4742securityA computer account was changedGenerated 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 '-'.
4743securityA computer account was deletedGenerated on a domain controller every time a computer object is deleted from Active Directory. Records the Subject who performed the deletion and the Target Computer's name and SID: a much smaller event than 4741/4742 since there are no remaining attributes to enumerate.
6416securityA new external device was recognized by the SystemGenerated every time Plug and Play recognizes a new external device on the system: for example, a device being connected or enabled for the first time. Captures the device's instance path, description, hardware/class GUIDs, and physical bus location, and is logged on the machine where the device was attached.
4794securityAn attempt was made to set the Directory Services Restore Mode administrator passwordGenerated only on domain controllers, every time the Directory Services Restore Mode (DSRM) administrator password is changed. Captured as a Success or Failure event depending on the outcome. It records the Subject who made the change, their Logon ID, and the Caller Workstation the request came from.
4964securitySpecial groups have been assigned to a new logonFires whenever an account that's a member of an administrator-defined 'Special Group': a list of security-critical group SIDs (e.g. Domain Admins, Enterprise Admins, or a custom service-account group) configured in the registry. Successfully logs on. The event lists the New Logon account and the specific Special Group SID(s) it belongs to.
4661securityA handle to an object was requestedGenerated when a handle is requested to either an Active Directory object (on a domain controller) or a Security Account Manager (SAM) object (a local group, group, user account, domain, or computer account) recording the requesting Subject, the Object Type/Name, and the specific access rights requested. A Failure event means the requested access was declined; it only generates if Success auditing is enabled for the Audit Handle Manipulation subcategory.
4670securityPermissions on an object were changedGenerated when the DACL (permissions) on a file system, registry, or security-token object is changed, recording the Subject who made the change and both the Original and New Security Descriptor in SDDL. It does not fire on SACL (auditing-ACL) changes, and needs 'Change Permissions'/'Take Ownership' (files) or 'Write DAC'/'Write Owner' (registry) set in the object's own SACL before it will generate.
5136securityA directory service object was modifiedGenerated every time an audited attribute of an Active Directory object is modified, provided the object's SACL has a 'Write' auditing entry for that attribute. A single change typically produces two 5136 events sharing the same Correlation ID, one 'Value Deleted' (the prior value) and one 'Value Added' (the new value), plus the object's DN, GUID, class, and the specific LDAP attribute name changed.
5137securityA directory service object was createdGenerated every time a new Active Directory object is created, provided the parent container's SACL has a 'Create' auditing entry for that object class. Records the new object's DN, GUID, and class (user, computer, group, groupPolicyContainer, etc.), along with the Subject who created it.
5138securityA directory service object was undeletedGenerated on an Active Directory domain controller whenever an AD object is undeleted, for example, restored from the Active Directory Recycle Bin. It only fires if the destination container has a matching 'Create' auditing entry in its SACL for that object class. Records the requesting Subject, the AD domain, the object's Old DN (its tombstone path under CN=Deleted Objects), New DN (the container it was restored into), GUID, and object Class.
5139securityA directory service object was movedGenerated on an Active Directory domain controller whenever an AD object is moved between containers, provided the destination container has a matching 'Create' auditing entry in its SACL for that object class. Records the requesting Subject, the AD domain, the object's Old DN (pre-move location), New DN (destination container), GUID, and object Class.
5141securityA directory service object was deletedGenerated on an Active Directory domain controller whenever an AD object is deleted, provided the object has a matching 'Delete' auditing entry in its SACL. Records the requesting Subject, the AD domain, the deleted object's DN, GUID, and object Class, plus a Tree Delete flag indicating whether the 'Delete Subtree' server control was used to remove an entire branch (e.g. an OU and everything under it) in one operation.
4765securitySID History was added to an accountGenerated on a domain controller whenever a value is added to an account's sIDHistory attribute. Records the Subject who performed the operation, the Target Account the SID History was added to, the Source Account the historical SID came from, and the specific SID(s) added in the SID List.
4766securityAn attempt to add SID History to an account failedGenerated on a domain controller when an attempt to add a value to an account's sIDHistory attribute fails. Records the Subject, the Target Account the addition was attempted against, and the Source Account name the SID would have come from. Unlike its success counterpart (4765), Microsoft's own event schema hard-codes the Subject's Security ID to a placeholder rather than substituting a real SID, and the Source Account section carries only an Account Name with no SID or SID List field, so the specific SID and failure reason aren't captured in the event itself.
4777securityThe domain controller failed to validate the credentials for an accountA defined Windows security event ID that, per Microsoft's own documentation, currently doesn't generate. It is a defined event that is never invoked by the operating system; a Failure instance of event 4776 is generated instead.
4778securityA session was reconnected to a Window StationGenerated when a user reconnects to an existing, disconnected Terminal Services (RDP) session, switches back to a desktop via Fast User Switching, or reconnects to a Hyper-V Enhanced Session. Records the Subject account, the Session Name the session reconnected to, and (for a network reconnect), the Client Name and Client Address it came from.
4779securityA session was disconnected from a Window StationGenerated when a user disconnects from an existing Terminal Services (RDP) session, leaving it running and logged on in the background rather than logging off, switches away from a desktop via Fast User Switching, or disconnects from a Hyper-V Enhanced Session. Records the Subject account, the Session Name that was disconnected, and (for a network session), the Client Name and Client Address it disconnected from.
4704securityA user right was assignedGenerated every time the local user rights policy changes and a user right is assigned to an account: a separate event fires per right/account combination. Records the Subject who made the change, the Target Account the right was assigned to, and the specific privilege in the New Right\User Right field (e.g. SeDebugPrivilege, SeServiceLogonRight).
4705securityA user right was removedGenerated every time the local user rights policy changes and a user right is removed from an account: a separate event fires per right/account combination. Records the Subject who made the change, the Target Account the right was removed from, and the specific privilege in the Removed Right\User Right field.
4616securityThe system time was changedGenerated every time the system clock is changed, and is always logged regardless of whether the Security State Change subcategory is itself audited. Records the Subject that requested the change, the Process ID and Name of the process that made it, and both the Previous Time and New Time in UTC.

Related

All references