windows-security-ids

4608  - Windows is starting up. This event is logged when LSASS.EXE starts and the auditing subsystem is initialized.
4609  - Windows is shutting down. All logon sessions will be terminated by this shutdown.
4610  - An authentication package has been loaded by the Local Security Authority. This authentication package will be used to authenticate logon attempts.
4611  - A trusted logon process has been registered with the Local Security Authority. This logon process will be trusted to submit logon requests.
4612  - Internal resources allocated for the queuing of audit messages have been exhausted, leading to the loss of some audits. This event is generated when audit queues are filled and events must be discarded. This most commonly occurs when security events are being generated faster than they are being written to disk, or when the auditing system loses connectivity to the event log, such as when the event log service is stopped.
4614  - A notification package has been loaded by the Security Account Manager. This package will be notified of any account or password changes.
4615  - Invalid use of LPC port. Windows Local Security Authority (LSA) communicates with the Windows kernel using Local Procedure Call (LPC) ports. If you see this event, an application has inadvertently or intentionally accessed this port which is reserved exclusively for LSA's use. The application (process) should be investigated to ensure that it is not attempting to tamper with this communications channel.
4616  - The system time was changed. This event is generated when the system time is changed. It is normal for the Windows Time Service, which runs with System privilege, to change the system time on a regular basis. Other system time changes may be indicative of attempts to tamper with the computer.
4618  - A monitored security event pattern has occurred. This event is generated when Windows is configured to generate alerts in accordance with the Common Criteria Security Audit Analysis requirements (FAU_SAA) and an auditable event pattern occurs.
4621  - Administrator recovered system from CrashOnAuditFail. Users who are not administrators will now be allowed to log on. Some auditable activity might not have been recorded. This event is logged after a system reboots following CrashOnAuditFail.
4622  - A security package has been loaded by the Local Security Authority.
4624  - An account was successfully logged on. This event is generated when a logon session is created. It is generated on the computer that was accessed. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network). The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The impersonation level field indicates the extent to which a process in the logon session can impersonate. The authentication information fields provide detailed information about this specific logon request. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
4625  - An account failed to log on. This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
4626  - User / Device claims information. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network). The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on. This event is generated when the Audit User/Device claims subcategory is configured and the user’s logon token contains user/device claims information. The Logon ID field can be used to correlate this event with the corresponding user logon event as well as to any other security audit events generated during this logon session.
4627  - Group membership information. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network). The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on. This event is generated when the Audit Group Membership subcategory is configured. The Logon ID field can be used to correlate this event with the corresponding user logon event as well as to any other security audit events generated during this logon session.
4634  - An account was logged off. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer. This event is generated when a logoff is initiated. No further user-initiated activity can occur. This event can be interpreted as a logoff event.
4648  - A logon was attempted using explicit credentials. This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
4649  - A replay attack was detected. This event indicates that a Kerberos replay attack was detected- a request was received twice with identical information. This condition could be caused by network misconfiguration.
4650  - An IPsec main mode security association was established. Extended mode was not enabled. Certificate authentication was not used.
4651  - An IPsec main mode security association was established. Extended mode was not enabled. A certificate was used for authentication.
4652  - An IPsec main mode negotiation failed.
4653  - An IPsec main mode negotiation failed.
4654  - An IPsec quick mode negotiation failed.
4655  - An IPsec main mode security association ended.
4656  - A handle to an object was requested.
4657  - A registry value was modified.
4658  - The handle to an object was closed.
4659  - A handle to an object was requested with intent to delete.
4660  - An object was deleted.
4661  - A handle to an object was requested.
4662  - An operation was performed on an object.
4663  - An attempt was made to access an object.
4664  - An attempt was made to create a hard link.
4665  - An attempt was made to create an application client context.
4667  - An application client context was deleted.
4668  - An application was initialized.
4670  - Permissions on an object were changed.
4671  - An application attempted to access a blocked ordinal through the TBS.
4672  - Special privileges assigned to new logon.
4673  - A privileged service was called.
4674  - An operation was attempted on a privileged object.
4675  - SIDs were filtered.
4688  - A new process has been created. Token Elevation Type indicates the type of token that was assigned to the new process in accordance with User Account Control policy. Type 1 is a full token with no privileges removed or groups disabled. A full token is only used if User Account Control is disabled or if the user is the built-in Administrator account or a service account. Type 2 is an elevated token with no privileges removed or groups disabled. An elevated token is used when User Account Control is enabled and the user chooses to start the program using Run as administrator. An elevated token is also used when an application is configured to always require administrative privilege or to always require maximum privilege, and the user is a member of the Administrators group. Type 3 is a limited token with administrative privileges removed and administrative groups disabled. The limited token is used when User Account Control is enabled, the application does not require administrative privilege, and the user does not choose to start the program using Run as administrator.
4689  - A process has exited.
4690  - An attempt was made to duplicate a handle to an object.
4691  - Indirect access to an object was requested.
4692  - Backup of data protection master key was attempted.
4693  - Recovery of data protection master key was attempted.
4694  - Protection of auditable protected data was attempted.
4695  - Unprotection of auditable protected data was attempted.
4696  - A primary token was assigned to process.
4697  - A service was installed in the system.
4698  - A scheduled task was created.
4699  - A scheduled task was deleted.
4700  - A scheduled task was enabled.
4701  - A scheduled task was disabled.
4702  - A scheduled task was updated.
4703  - A token right was adjusted.
4704  - A user right was assigned.
4705  - A user right was removed.
4706  - A new trust was created to a domain.
4707  - A trust to a domain was removed.
4709  - The IPsec Policy Agent service was started.
4710  - The IPsec Policy Agent service was disabled.
4712  - IPsec Policy Agent encountered a potentially serious failure.
4713  - Kerberos policy was changed.
4714  - Data Recovery Agent group policy for Encrypting File System (EFS) has changed. The new changes have been applied.
4715  - The audit policy (SACL) on an object was changed.
4716  - Trusted domain information was modified.
4717  - System security access was granted to an account.
4718  - System security access was removed from an account.
4719  - System audit policy was changed.
4720  - A user account was created.
4722  - A user account was enabled.
4723  - An attempt was made to change an account's password.
4724  - An attempt was made to reset an account's password.
4725  - A user account was disabled.
4726  - A user account was deleted.
4727  - A security-enabled global group was created.
4728  - A member was added to a security-enabled global group.
4729  - A member was removed from a security-enabled global group.
4730  - A security-enabled global group was deleted.
4731  - A security-enabled local group was created.
4732  - A member was added to a security-enabled local group.
4733  - A member was removed from a security-enabled local group.
4734  - A security-enabled local group was deleted.
4735  - A security-enabled local group was changed.
4737  - A security-enabled global group was changed.
4738  - A user account was changed.
4739  - Domain Policy was changed.
4740  - A user account was locked out.
4741  - A computer account was created.
4742  - A computer account was changed.
4743  - A computer account was deleted.
4744  - A security-disabled local group was created.
4745  - A security-disabled local group was changed.
4746  - A member was added to a security-disabled local group.
4747  - A member was removed from a security-disabled local group.
4748  - A security-disabled local group was deleted.
4749  - A security-disabled global group was created.
4750  - A security-disabled global group was changed.
4751  - A member was added to a security-disabled global group.
4752  - A member was removed from a security-disabled global group.
4753  - A security-disabled global group was deleted.
4754  - A security-enabled universal group was created.
4755  - A security-enabled universal group was changed.
4756  - A member was added to a security-enabled universal group.
4757  - A member was removed from a security-enabled universal group.
4758  - A security-enabled universal group was deleted.
4759  - A security-disabled universal group was created.
4760  - A security-disabled universal group was changed.
4761  - A member was added to a security-disabled universal group.
4762  - A member was removed from a security-disabled universal group.
4763  - A security-disabled universal group was deleted.
4764  - A group’s type was changed.
4765  - SID History was added to an account.
4766  - An attempt to add SID History to an account failed. Source Account
4767  - A user account was unlocked.
4768  - A Kerberos authentication ticket (TGT) was requested. Certificate information is only provided if a certificate was used for pre-authentication. Pre-authentication types, ticket options, encryption types and result codes are defined in RFC 4120.
4769  - A Kerberos service ticket was requested. This event is generated every time access is requested to a resource such as a computer or a Windows service. The service name indicates the resource to which access was requested. This event can be correlated with Windows logon events by comparing the Logon GUID fields in each event. The logon event occurs on the machine that was accessed, which is often a different machine than the domain controller which issued the service ticket. Ticket options, encryption types, and failure codes are defined in RFC 4120.
4770  - A Kerberos service ticket was renewed. Ticket options and encryption types are defined in RFC 4120.
4771  - Kerberos pre-authentication failed. Certificate information is only provided if a certificate was used for pre-authentication. Pre-authentication types, ticket options and failure codes are defined in RFC 4120. If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.
4772  - A Kerberos authentication ticket request failed. Ticket options and failure codes are defined in RFC 4120.
4773  - A Kerberos service ticket request failed. Ticket options and failure codes are defined in RFC 4120.
4774  - An account was mapped for logon.
4775  - An account could not be mapped for logon.
4776  - The computer attempted to validate the credentials for an account.
4777  - The domain controller failed to validate the credentials for an account.
4778  - A session was reconnected to a Window Station. This event is generated when a user reconnects to an existing Terminal Services session, or when a user switches to an existing desktop using Fast User Switching.
4779  - A session was disconnected from a Window Station. This event is generated when a user disconnects from an existing Terminal Services session, or when a user switches away from an existing desktop using Fast User Switching.
4780  - The ACL was set on accounts which are members of administrators groups. Every hour, the Windows domain controller that holds the primary domain controller (PDC) Flexible Single Master Operation (FSMO) role compares the ACL on all security principal accounts (users, groups, and machine accounts) present for its domain in Active Directory and that are in administrative groups against the ACL on the AdminSDHolder object. If the ACL on the principal account differs from the ACL on the AdminSDHolder object, then the ACL on the principal account is reset to match the ACL on the AdminSDHolder object and this event is generated.
4782  - The password hash an account was accessed.
4783  - A basic application group was created.
4784  - A basic application group was changed.
4785  - A member was added to a basic application group.
4786  - A member was removed from a basic application group.
4787  - A non-member was added to a basic application group. A non-member is an account that is explicitly excluded from membership in a basic application group. Even if the account is specified as a member of the application group, either explicitly or through nested group membership, the account will not be treated as a group member if it is listed as a non-member.
4788  - A non-member was removed from a basic application group. A non-member is an account that is explicitly excluded from membership in a basic application group. Even if the account is specified as a member of the application group, either explicitly or through nested group membership, the account will not be treated as a group member if it is listed as a non-member.
4789  - A basic application group was deleted.
4790  - An LDAP query group was created.
4791  - A basic application group was changed.
4792  - An LDAP query group was deleted.
4793  - The Password Policy Checking API was called.
4794  - An attempt was made to set the Directory Services Restore Mode administrator password.
4797  - An attempt was made to query the existence of a blank password for an account.
4798  - A user's local group membership was enumerated.
4799  - A security-enabled local group membership was enumerated.
4800  - The workstation was locked.
4801  - The workstation was unlocked.
4802  - The screen saver was invoked.
4803  - The screen saver was dismissed.
4816  - RPC detected an integrity violation while decrypting an incoming message.
4817  - Auditing settings on object were changed.
4818  - Proposed Central Access Policy does not grant the same access permissions as the current Central Access Policy.
4819  - Central Access Policies on the machine have been changed.
4820  - A Kerberos Ticket-granting-ticket (TGT) was denied because the device does not meet the access control restrictions. Certificate information is only provided if a certificate was used for pre-authentication. Pre-authentication types, ticket options, encryption types and result codes are defined in RFC 4120.
4821  - A Kerberos service ticket was denied because the user, device, or both does not meet the access control restrictions. This event is generated every time access is requested to a resource such as a computer or a Windows service. The service name indicates the resource to which access was requested. This event can be correlated with Windows logon events by comparing the Logon GUID fields in each event. The logon event occurs on the machine that was accessed, which is often a different machine than the domain controller which issued the service ticket. Ticket options, encryption types, and failure codes are defined in RFC 4120.
4822  - NTLM authentication failed because the account was a member of the Protected User group.
4823  - NTLM authentication failed because access control restrictions are required.
4824  - Kerberos preauthentication by using DES or RC4 failed because the account was a member of the Protected User group. Certificate information is only provided if a certificate was used for pre-authentication. Pre-authentication types, ticket options and failure codes are defined in RFC 4120. If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.
4825  - A user was denied the access to Remote Desktop. By default, users are allowed to connect only if they are members of the Remote Desktop Users group or Administrators group. This event is generated when an authenticated user who is not allowed to log on remotely attempts to connect to this computer through Remote Desktop.
4826  - Boot Configuration Data loaded.
4830  - SID History was removed from an account.
4864  - A namespace collision was detected.
4865  - A trusted forest information entry was added.
4866  - A trusted forest information entry was removed.
4867  - A trusted forest information entry was modified.
4868  - The certificate manager denied a pending certificate request.
4869  - Certificate Services received a resubmitted certificate request.
4870  - Certificate Services revoked a certificate.
4871  - Certificate Services received a request to publish the certificate revocation list (CRL).
4872  - Certificate Services published the certificate revocation list (CRL).
4873  - A certificate request extension changed.
4874  - One or more certificate request attributes changed.
4875  - Certificate Services received a request to shut down.
4876  - Certificate Services backup started.
4877  - Certificate Services backup completed.
4878  - Certificate Services restore started.
4879  - Certificate Services restore completed.
4880  - Certificate Services started.
4881  - Certificate Services stopped.
4882  - The security permissions for Certificate Services changed.
4883  - Certificate Services retrieved an archived key.
4884  - Certificate Services imported a certificate into its database.
4885  - The audit filter for Certificate Services changed.
4886  - Certificate Services received a certificate request.
4887  - Certificate Services approved a certificate request and issued a certificate.
4888  - Certificate Services denied a certificate request.
4889  - Certificate Services set the status of a certificate request to pending.
4890  - The certificate manager settings for Certificate Services changed.
4891  - A configuration entry changed in Certificate Services.
4892  - A property of Certificate Services changed.
4893  - Certificate Services archived a key.
4894  - Certificate Services imported and archived a key.
4895  - Certificate Services published the CA certificate to Active Directory Domain Services.
4896  - One or more rows have been deleted from the certificate database.
4898  - Certificate Services loaded a template.
4899  - A Certificate Services template was updated.
4900  - Certificate Services template security was updated.
4902  - The Per-user audit policy table was created.
4904  - An attempt was made to register a security event source.
4905  - An attempt was made to unregister a security event source. Subject
4906  - The CrashOnAuditFail value has changed.
4907  - Auditing settings on object were changed.
4908  - Special Groups Logon table modified. This event is generated when the list of special groups is updated in the registry or through security policy. The updated list of special groups is indicated in the event.
4909  - The local policy settings for the TBS were changed.
4910  - The group policy settings for the TBS were changed.
4911  - Resource attributes of the object were changed.
4912  - Per User Audit Policy was changed.
4913  - Central Access Policy on the object was changed.
4928  - An Active Directory replica source naming context was established.
4929  - An Active Directory replica source naming context was removed.
4930  - An Active Directory replica source naming context was modified.
4931  - An Active Directory replica destination naming context was modified.
4932  - Synchronization of a replica of an Active Directory naming context has begun.
4933  - Synchronization of a replica of an Active Directory naming context has ended.
4934  - Attributes of an Active Directory object were replicated.
4935  - Replication failure begins.
4936  - Replication failure ends.
4937  - A lingering object was removed from a replica.
4944  - The following policy was active when the Windows Firewall started.
4945  - A rule was listed when the Windows Firewall started.
4946  - A change was made to the Windows Firewall exception list. A rule was added.
4947  - A change was made to the Windows Firewall exception list. A rule was modified.
4948  - A change was made to the Windows Firewall exception list. A rule was deleted.
4949  - Windows Firewall settings were restored to the default values.
4950  - A Windows Firewall setting was changed.
4951  - Windows Firewall ignored a rule because its major version number is not recognized.
4952  - Windows Firewall ignored parts of a rule because its minor version number is not recognized. Other parts of the rule will be enforced.
4953  - Windows Firewall ignored a rule because it could not be parsed.
4954  - Group Policy settings for Windows Firewall were changed, and the new settings were applied.
4956  - Windows Firewall changed the active profile.
4960  - IPsec dropped an inbound packet that failed an integrity check. If this problem persists, it could indicate a network issue or that packets are being modified in transit to this computer. Verify that the packets sent from the remote computer are the same as those received by this computer. This error might also indicate interoperability problems with other IPsec implementations.
4961  - IPsec dropped an inbound packet that failed a replay check. If this problem persists, it could indicate a replay attack against this computer.
4962  - IPsec dropped an inbound packet that failed a replay check. The inbound packet had too low a sequence number to ensure it was not a replay.
4963  - IPsec dropped an inbound clear text packet that should have been secured. If the remote computer is configured with a Request Outbound IPsec policy, this might be benign and expected. This can also be caused by the remote computer changing its IPsec policy without informing this computer. This could also be a spoofing attack attempt.
4964  - Special groups have been assigned to a new logon.
4965  - IPsec received a packet from a remote computer with an incorrect Security Parameter Index (SPI). This is usually caused by malfunctioning hardware that is corrupting packets. If these errors persist, verify that the packets sent from the remote computer are the same as those received by this computer. This error might also indicate interoperability problems with other IPsec implementations. In that case, if connectivity is not impeded, then these events can be ignored.
4976  - During main mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
4977  - During quick mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
4978  - During extended mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
4979  - IPsec main mode and extended mode security associations were established. Keying Module Name - 	AuthIP
4980  - IPsec main mode and extended mode security associations were established. Keying Module Name - 	AuthIP Authentication Method - 	SSL
4981  - IPsec main mode and extended mode security associations were established. Keying Module Name - 	AuthIP Authentication Method - 	SSL
4982  - IPsec main mode and extended mode security associations were established. Keying Module Name - 	AuthIP Authentication Method - 	SSL Authentication Method - 	SSL
4983  - An IPsec extended mode negotiation failed. The corresponding main mode security association has been deleted. Keying Module Name - 	AuthIP Authentication Method - 	SSL
4984  - An IPsec extended mode negotiation failed. The corresponding main mode security association has been deleted. Keying Module Name - 	AuthIP
4985  - The state of a transaction has changed.
5024  - The Windows Firewall service started successfully.
5025  - The Windows Firewall service was stopped.
5027  - The Windows Firewall service was unable to retrieve the security policy from the local storage. Windows Firewall will continue to enforce the current policy.
5028  - Windows Firewall was unable to parse the new security policy. Windows Firewall will continue to enforce the current policy.
5029  - The Windows Firewall service failed to initialize the driver. Windows Firewall will continue to enforce the current policy.
5030  - The Windows Firewall service failed to start.
5031  - Windows Firewall blocked an application from accepting incoming connections on the network.
5032  - Windows Firewall was unable to notify the user that it blocked an application from accepting incoming connections on the network.
5033  - The Windows Firewall Driver started successfully.
5034  - The Windows Firewall Driver was stopped.
5035  - The Windows Firewall Driver failed to start.
5037  - The Windows Firewall Driver detected a critical runtime error, terminating.
5038  - Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.
5039  - A registry key was virtualized.
5040  - A change was made to IPsec settings. An authentication set was added.
5041  - A change was made to IPsec settings. An authentication set was modified.
5042  - A change was made to IPsec settings. An authentication set was deleted.
5043  - A change was made to IPsec settings. A connection security rule was added.
5044  - A change was made to IPsec settings. A connection security rule was modified.
5045  - A change was made to IPsec settings. A connection security rule was deleted.
5046  - A change was made to IPsec settings. A crypto set was added.
5047  - A change was made to IPsec settings. A crypto set was modified.
5048  - A change was made to IPsec settings. A crypto set was deleted.
5049  - An IPsec security association was deleted.
5050  - An attempt to programmatically disable Windows Firewall using a call to INetFwProfile.FirewallEnabled(FALSE) interface was rejected because this API is not supported on this version of Windows. This is most likely due to a program that is incompatible with this version of Windows. Please contact the program's manufacturer to make sure you have a compatible program version. Error Code - 		E_NOTIMPL
5051  - A file was virtualized.
5056  - A cryptographic self test was performed.
5057  - A cryptographic primitive operation failed.
5058  - Key file operation.
5059  - Key migration operation.
5060  - Verification operation failed.
5061  - Cryptographic operation.
5062  - A kernel-mode cryptographic self test was performed.
5063  - A cryptographic provider operation was attempted.
5064  - A cryptographic context operation was attempted.
5065  - A cryptographic context modification was attempted.
5066  - A cryptographic function operation was attempted.
5067  - A cryptographic function modification was attempted.
5068  - A cryptographic function provider operation was attempted.
5069  - A cryptographic function property operation was attempted.
5070  - A cryptographic function property modification was attempted.
5071  - Key access denied by Microsoft key distribution service.
5120  - OCSP Responder Service Started.
5121  - OCSP Responder Service Stopped.
5122  - A Configuration entry changed in the OCSP Responder Service.
5123  - A configuration entry changed in the OCSP Responder Service.
5124  - A security setting was updated on OCSP Responder Service.
5125  - A request was submitted to OCSP Responder Service.
5126  - Signing Certificate was automatically updated by the OCSP Responder Service.
5127  - The OCSP Revocation Provider successfully updated the revocation information.
5136  - A directory service object was modified.
5137  - A directory service object was created.
5138  - A directory service object was undeleted.
5139  - A directory service object was moved.
5140  - A network share object was accessed.
5141  - A directory service object was deleted.
5142  - A network share object was added.
5143  - A network share object was modified.
5144  - A network share object was deleted.
5145  - A network share object was checked to see whether client can be granted desired access.
5146  - The Windows Filtering Platform has blocked a packet.
5147  - A more restrictive Windows Filtering Platform filter has blocked a packet.
5148  - The Windows Filtering Platform has detected a DoS attack and entered a defensive mode; packets associated with this attack will be discarded.
5149  - The DoS attack has subsided and normal processing is being resumed.
5150  - The Windows Filtering Platform has blocked a packet.
5151  - A more restrictive Windows Filtering Platform filter has blocked a packet.
5152  - The Windows Filtering Platform has blocked a packet.
5153  - A more restrictive Windows Filtering Platform filter has blocked a packet.
5154  - The Windows Filtering Platform has permitted an application or service to listen on a port for incoming connections.
5155  - The Windows Filtering Platform has blocked an application or service from listening on a port for incoming connections.
5156  - The Windows Filtering Platform has permitted a connection.
5157  - The Windows Filtering Platform has blocked a connection.
5158  - The Windows Filtering Platform has permitted a bind to a local port.
5159  - The Windows Filtering Platform has blocked a bind to a local port.
5168  - Spn check for SMB/SMB2 fails.
5169  - A directory service object was modified.
5170  - A directory service object was modified during a background cleanup task.
5376  - Credential Manager credentials were backed up. This event occurs when a user backs up their own Credential Manager credentials. A user (even an Administrator) cannot back up the credentials of an account other than his own.
5377  - Credential Manager credentials were restored from a backup. This event occurs when a user restores his Credential Manager credentials from a backup. A user (even an Administrator) cannot restore the credentials of an account other than his own.
5378  - The requested credentials delegation was disallowed by policy.
5379  - Credential Manager credentials were read. This event occurs when a user performs a read operation on stored credentials in Credential Manager.
5380  - Vault Find Credential. This event occurs when a user finds stored vault credentials.
5381  - Vault credentials were read. This event occurs when a user enumerates stored vault credentials.
5382  - Vault credentials were read. This event occurs when a user reads a stored vault credential.
5440  - The following callout was present when the Windows Filtering Platform Base Filtering Engine started.
5441  - The following filter was present when the Windows Filtering Platform Base Filtering Engine started.
5442  - The following provider was present when the Windows Filtering Platform Base Filtering Engine started.
5443  - The following provider context was present when the Windows Filtering Platform Base Filtering Engine started.
5444  - The following sub-layer was present when the Windows Filtering Platform Base Filtering Engine started.
5446  - A Windows Filtering Platform callout has been changed.
5447  - A Windows Filtering Platform filter has been changed.
5448  - A Windows Filtering Platform provider has been changed.
5449  - A Windows Filtering Platform provider context has been changed.
5450  - A Windows Filtering Platform sub-layer has been changed.
5451  - An IPsec quick mode security association was established.
5452  - An IPsec quick mode security association ended.
5453  - An IPsec negotiation with a remote computer failed because the IKE and AuthIP IPsec Keying Modules (IKEEXT) service is not started.
5456  - IPsec Policy Agent applied Active Directory storage IPsec policy on the computer.
5457  - IPsec Policy Agent failed to apply Active Directory storage IPsec policy on the computer.
5458  - IPsec Policy Agent applied locally cached copy of Active Directory storage IPsec policy on the computer.
5459  - IPsec Policy Agent failed to apply locally cached copy of Active Directory storage IPsec policy on the computer.
5460  - IPsec Policy Agent applied local registry storage IPsec policy on the computer.
5461  - IPsec Policy Agent failed to apply local registry storage IPsec policy on the computer.
5462  - IPsec Policy Agent failed to apply some rules of the active IPsec policy on the computer. Use the IP Security Monitor snap-in to diagnose the problem.
5463  - IPsec Policy Agent polled for changes to the active IPsec policy and detected no changes.
5464  - IPsec Policy Agent polled for changes to the active IPsec policy, detected changes, and applied them.
5465  - IPsec Policy Agent received a control for forced reloading of IPsec policy and processed the control successfully.
5466  - IPsec Policy Agent polled for changes to the Active Directory IPsec policy, determined that Active Directory cannot be reached, and will use the cached copy of the Active Directory IPsec policy instead. Any changes made to the Active Directory IPsec policy since the last poll could not be applied.
5467  - IPsec Policy Agent polled for changes to the Active Directory IPsec policy, determined that Active Directory can be reached, and found no changes to the policy. The cached copy of the Active Directory IPsec policy is no longer being used.
5468  - IPsec Policy Agent polled for changes to the Active Directory IPsec policy, determined that Active Directory can be reached, found changes to the policy, and applied those changes. The cached copy of the Active Directory IPsec policy is no longer being used.
5471  - IPsec Policy Agent loaded local storage IPsec policy on the computer.
5472  - IPsec Policy Agent failed to load local storage IPsec policy on the computer.
5473  - IPsec Policy Agent loaded directory storage IPsec policy on the computer.
5474  - IPsec Policy Agent failed to load directory storage IPsec policy on the computer.
5477  - IPsec Policy Agent failed to add quick mode filter.
5478  - The IPsec Policy Agent service was started.
5479  - The IPsec Policy Agent service was stopped. Stopping this service can put the computer at greater risk of network attack or expose the computer to potential security risks.
5480  - IPsec Policy Agent failed to get the complete list of network interfaces on the computer. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem.
5483  - The IPsec Policy Agent service failed to initialize its RPC server. The service could not be started.
5484  - The IPsec Policy Agent service experienced a critical failure and has shut down. The shutdown of this service can put the computer at greater risk of network attack or expose the computer to potential security risks.
5485  - IPsec Policy Agent failed to process some IPsec filters on a plug-and-play event for network interfaces. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem.
5632  - A request was made to authenticate to a wireless network.
5633  - A request was made to authenticate to a wired network. Additional Information
5712  - A Remote Procedure Call (RPC) was attempted.
5888  - An object in the COM+ Catalog was modified.
5889  - An object was deleted from the COM+ Catalog. This event occurs when an object is deleted from the COM+ catalog.
5890  - An object was added to the COM+ Catalog.
6144  - Security policy in the group policy objects has been applied successfully.
6145  - One or more errors occured while processing security policy in the group policy objects.
6272  - Network Policy Server granted access to a user.
6273  - Network Policy Server denied access to a user. Contact the Network Policy Server administrator for more information.
6274  - Network Policy Server discarded the request for a user. Contact the Network Policy Server administrator for more information.
6275  - Network Policy Server discarded the accounting request for a user. Contact the Network Policy Server administrator for more information.
6276  - Network Policy Server quarantined a user. Contact the Network Policy Server administrator for more information.
6277  - Network Policy Server granted access to a user but put it on probation because the host did not meet the defined health policy. Contact the Network Policy Server administrator for more information.
6278  - Network Policy Server granted full access to a user because the host met the defined health policy.
6279  - Network Policy Server locked the user account due to repeated failed authentication attempts.
6280  - Network Policy Server unlocked the user account.
6281  - Code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error.
6400  - BranchCache -  Received an incorrectly formatted response while discovering availability of content.
6401  - BranchCache -  Received invalid data from a peer. Data discarded.
6402  - BranchCache -  The message to the hosted cache offering it data is incorrectly formatted.
6403  - BranchCache -  The hosted cache sent an incorrectly formatted response to the client's message to offer it data.
6404  - BranchCache -  Hosted cache could not be authenticated using the provisioned SSL certificate.
6409  - BranchCache -  A service connection point object could not be parsed.
6410  - Code integrity determined that a file does not meet the security requirements to load into a process. This could be due to the use of shared sections or other issues.
6416  - A new external device was recognized by the system.
6417  - The FIPS mode crypto selftests succeeded.
6418  - The FIPS mode crypto selftests failed.
6419  - A request was made to disable a device.
6420  - A device was disabled.
6421  - A request was made to enable a device.
6422  - A device was enabled.
6423  - The installation of this device is forbidden by system policy.
6424  - The installation of this device was allowed, after having previously been forbidden by policy.
6425  - A network client used a legacy RPC method to modify authentication information on a trusted domain object. The authentication information was encrypted with a legacy encryption algorithm. Consider upgrading the client operating system or application to use the latest and more secure version of this method.
8191  - Highest System-Defined Audit Message Value.