This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Windows Security Event IDs
Category Subcategory
System System Integrity 1102 517 Medium/High Y
System Security State Change 4608 512 Low
System Security State Change 4609 513 Low
System Security System Extension 4610 514 Low
System Security System Extension 4611 515 Low
System System Integrity 4612 516 Low
System Security System Extension 4614 518 Low
System System Integrity 4615 519 Low
System Security State Change 4616 520 Low
System System Integrity 4618 - High Y
System Security State Change 4621 - Medium
System Security System Extension 4622 - Low
Logon/Logoff Logon 4624 528,540 Low
Logon/Logoff Logon 4625 Low
Logon/Logoff Logoff 4634 538 Low
? ? 550 High
Logon/Logoff IPsec Main Mode 4646 - Medium
Logon/Logoff Logoff 4647 551 Low
Logon/Logoff Logon 4648 552 Low
Logon/Logoff Other Logon/Logoff Events 4649 - High
Logon/Logoff IPsec Main Mode 4650 - Low
Logon/Logoff IPsec Main Mode 4651 - Low
Logon/Logoff IPsec Main Mode 4652 - Low
Logon/Logoff IPsec Main Mode 4653 - Low
Logon/Logoff IPsec Quick Mode 4654 - Low
Logon/Logoff IPsec Main Mode 4655 - Low
Object Access Handle Manipulation 4656 560 Low
Object Access Registry 4657 567 Low
Object Access 4658 562 Low
Object Access Special 4659 - Low
Object Access Special 4660 564 Low
Object Access Special 4661 565 Low
DS Access Directory Service Access 4662 566 Low
Object Access Special 4663 567 Low
Object Access File System 4664 - Low
Object Access Application Generated 4665 - Low
Object Access Application Generated 4666 - Low
Object Access Application Generated 4667 - Low
Object Access Application Generated 4668 - Low
Policy Change Subcategory (special) 4670 - Low
Object Access Other Object Access Events 4671 - Low
Privilege Use 4672 576 Low
Privilege Use 4673 577 Low
Privilege Use 4674 578 Low
Logon/Logoff Logon 4675 - Medium
Detailed Tracking Process Creation 4688 592 Low
Detailed Tracking Process Creation 4689 593 Low
Object Access Handle Manipulation 4690 594 Low
Object Access Other Object Access Events 4691 595 Low
Detailed Tracking DPAPI Activity 4692 - High
Detailed Tracking DPAPI Activity 4693 - High
Detailed Tracking DPAPI Activity 4694 - High
Vista/W2K8\Win7 Event ID
W2K3/XP Legacy
Possible Criticality
529-537,539
Sensitive Privilege Use / Non Sensitive Privilege Use
Sensitive Privilege Use / Non Sensitive Privilege Use
Sensitive Privilege Use / Non Sensitive Privilege Use
B32
This event can be generated by a resource manager when you enable a subcategory of Object Access.
B33
This event can be generated by a resource manager when you enable a subcategory of Object Access.
B34
This event can be generated by a resource manager when you enable a subcategory of Object Access.
B36
This event can be generated by a resource manager when you enable a subcategory of Object Access.
Detailed Tracking DPAPI Activity 4695 - High
Detailed Tracking Process Creation 4696 600 Low
Detailed Tracking 4697 601 Low
Object Access Other Object Access Events 4698 602 Low
Object Access Other Object Access Events 4699 602 Low
Object Access Other Object Access Events 4700 602 Low
Object Access Other Object Access Events 4701 602 Low
Object Access Other Object Access Events 4702 602 Low
An authentication package has been loaded by the Local Security Authority.
A trusted logon process has been registered with the Local Security Authority.
Internal resources allocated for the queuing of audit messages have been exhausted, leading to the loss of some audits.
A notification package has been loaded by the Security Account Manager.
Invalid use of LPC port.
The system time was changed.
A monitored security event pattern has occurred.
A security package has been loaded by the Local Security Authority.
An account was successfully logged on.
An account failed to log on.
An account was logged off.
Possible denial of service (DOS) attack
IKE DoS-prevention mode started.
User initiated logoff.
A logon was attempted using explicit credentials.
A replay attack was detected.
An IPsec Main Mode security association was established. Extended Mode was not enabled. Certificate authentication was not used.
An IPsec Main Mode security association was established. Extended Mode was not enabled. A certificate was used for authentication.
An IPsec Main Mode negotiation failed.
An IPsec Main Mode negotiation failed.
An IPsec Quick Mode negotiation failed.
An IPsec Main Mode security association ended.
A handle to an object was requested.
A registry value was modified.
The handle to an object was closed.
A handle to an object was requested with intent to delete.
An object was deleted.
A handle to an object was requested.
An operation was performed on an object.
An attempt was made to access an object.
An attempt was made to create a hard link.
An attempt was made to create an application client context.
An application attempted an operation:
An application client context was deleted.
An application was initialized.
Permissions on an object were changed.
An application attempted to access a blocked ordinal through the TBS.
Special privileges assigned to new logon.
A privileged service was called.
An operation was attempted on a privileged object.
SIDs were filtered.
A new process has been created.
A process has exited.
An attempt was made to duplicate a handle to an object.
Indirect access to an object was requested.
Backup of data protection master key was attempted.
Recovery of data protection master key was attempted.
Protection of auditable protected data was attempted.
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.
Unprotection of auditable protected data was attempted.
A primary token was assigned to process.
Attempt to install a service
A scheduled task was created.
A scheduled task was deleted.
A scheduled task was enabled.
A scheduled task was disabled.
A scheduled task was updated.
A user right was assigned.
A user right was removed.
A new trust was created to a domain.
A trust to a domain was removed.
IPsec Services was started.
IPsec Services was disabled.
IPsec Services encountered a potentially serious failure.
Kerberos policy was changed.
Encrypted data recovery policy was changed.
The audit policy (SACL) on an object was changed.
Trusted domain information was modified.
System security access was granted to an account.
System security access was removed from an account.
System audit policy was changed.
A user account was created.
A user account was enabled.
An attempt was made to change an account's password.
An attempt was made to reset an account's password.
A user account was disabled.
A user account was deleted.
A security-enabled global group was created.
A member was added to a security-enabled global group.
A member was removed from a security-enabled global group.
A security-enabled global group was deleted.
A security-enabled local group was created.
A member was added to a security-enabled local group.
A member was removed from a security-enabled local group.
A security-enabled local group was deleted.
A security-enabled local group was changed.
A security-enabled global group was changed.
A user account was changed.
Domain Policy was changed.
A user account was locked out.
A computer account was changed.
A computer account was changed.
A computer account was deleted.
A security-disabled local group was created.
A security-disabled local group was changed.
A member was added to a security-disabled local group.
A member was removed from a security-disabled local group.
A security-disabled local group was deleted.
A security-disabled global group was created.
A security-disabled global group was changed.
May contain any one of the following: PAStore Engine applied locally cached copy of Active Directory storage IPsec policy on the computer.PAStore Engine applied Active Directory storage IPsec policy on the computer.PAStore Engine applied local registry storage IPsec policy on the computer.PAStore Engine failed to apply locally cached copy of Active Directory storage IPsec policy on the computer.PAStore Engine failed to apply Active Directory storage IPsec policy on the computer.PAStore Engine failed to apply local registry storage IPsec policy on the computer.PAStore Engine failed to apply some rules of the active IPsec policy on the computer.PAStore Engine failed to load directory storage IPsec policy on the computer.PAStore Engine loaded directory storage IPsec policy on the computer.PAStore Engine failed to load local storage IPsec policy on the computer.PAStore Engine loaded local storage IPsec policy on the computer.PAStore Engine polled for changes to the active IPsec policy and detected no changes.
A member was added to a security-disabled global group.
A member was removed from a security-disabled global group.
A security-disabled global group was deleted.
A security-enabled universal group was created.
A security-enabled universal group was changed.
A member was added to a security-enabled universal group.
A member was removed from a security-enabled universal group.
A security-enabled universal group was deleted.
A security-disabled universal group was created.
A security-disabled universal group was changed.
A member was added to a security-disabled universal group.
A member was removed from a security-disabled universal group.
A security-disabled grouop was deleted
A group’s type was changed.
SID History was added to an account.
An attempt to add SID History to an account failed.
A user account was unlocked.
A Kerberos authentication ticket (TGT) was requested.
A Kerberos service ticket was requested.
A Kerberos service ticket was renewed.
Kerberos pre-authentication failed.
A Kerberos authentication ticket request failed.
A Kerberos service ticket request failed
An account was mapped for logon.
An account could not be mapped for logon.
The domain controller attempted to validate the credentials for an account.
The domain controller failed to validate the credentials for an account.
A session was reconnected to a Window Station.
A session was disconnected from a Window Station.
The ACL was set on accounts which are members of administrators groups.
The name of an account was changed:
The password hash an account was accessed.
A basic application group was created.
A basic application group was changed.
A member was added to a basic application group.
A member was removed from a basic application group.
A non-member was added to a basic application group.
A non-member was removed from a basic application group.
A basic application group was deleted.
An LDAP query group was created.
A basic application group was changed.
An LDAP query group was deleted.
The Password Policy Checking API was called.
An attempt was made to set the Directory Services Restore Mode.
The workstation was locked.
The workstation was unlocked.
The screen saver was invoked.
The screen saver was dismissed.
RPC detected an integrity violation while decrypting an incoming message.
A namespace collision was detected.
A trusted forest information entry was added.
A trusted forest information entry was removed.
A trusted forest information entry was modified.
The certificate manager denied a pending certificate request.
Certificate Services received a resubmitted certificate request.
Certificate Services revoked a certificate.
Certificate Services received a request to publish the certificate revocation list (CRL).
Certificate Services published the certificate revocation list (CRL).
A certificate request extension changed.
One or more certificate request attributes changed.
Certificate Services received a request to shut down.
Certificate Services backup started.
Certificate Services backup completed.
Certificate Services restore started.
Certificate Services restore completed.
Certificate Services started.
Certificate Services stopped.
The security permissions for Certificate Services changed.
Certificate Services retrieved an archived key.
Certificate Services imported a certificate into its database.
The audit filter for Certificate Services changed.
Certificate Services received a certificate request.
Certificate Services approved a certificate request and issued a certificate.
Certificate Services denied a certificate request.
Certificate Services set the status of a certificate request to pending.
The certificate manager settings for Certificate Services changed.
A configuration entry changed in Certificate Services.
A property of Certificate Services changed.
Certificate Services archived a key.
Certificate Services imported and archived a key.
Certificate Services published the CA certificate to Active Directory Domain Services.
One or more rows have been deleted from the certificate database.
Role separation enabled:
Certificate Services loaded a template.
The Per-user audit policy table was created.
An attempt was made to register a security event source.
An attempt was made to unregister a security event source.
The CrashOnAuditFail value has changed.
Auditing settings on object were changed.
Special Groups Logon table modified.
The local policy settings for the TBS were changed.
The group policy settings for the TBS were changed.
Per User Audit Policy was changed.
An Active Directory replica source naming context was established.
An Active Directory replica source naming context was removed.
An Active Directory replica source naming context was modified.
An Active Directory replica destination naming context was modified.
Synchronization of a replica of an Active Directory naming context has begun.
Synchronization of a replica of an Active Directory naming context has ended.
Attributes of an Active Directory object were replicated.
Replication failure begins.
Replication failure ends.
A lingering object was removed from a replica.
The following policy was active when the Windows Firewall started.
A rule was listed when the Windows Firewall started.
A change has been made to Windows Firewall exception list. A rule was added.
A change has been made to Windows Firewall exception list. A rule was modified.
A change has been made to Windows Firewall exception list. A rule was deleted.
Windows Firewall settings were restored to the default values.
A Windows Firewall setting has changed.
A rule has been ignored because its major version number was not recognized by Windows Firewall.
A rule has been ignored by Windows Firewall because it could not parse the rule.
Windows Firewall Group Policy settings have changed. The new settings have been applied.
Windows Firewall has changed the active profile.
Windows Firewall did not apply the following rule:
Windows Firewall did not apply the following rule because the rule referred to items not configured on this computer:
IPsec dropped an inbound packet that failed a replay check. If this problem persists, it could indicate a replay attack against this computer.
Special groups have been assigned to a new logon.
Parts of a rule have been ignored because its minor version number was not recognized by Windows Firewall. The other parts of the rule will be enforced.
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.
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.
IPsec dropped an inbound clear text packet that should have been secured. This is usually due to the remote computer changing its IPsec policy without informing this computer. This could also be a spoofing attack attempt.
IPsec Main Mode and Extended Mode security associations were established.
IPsec Main Mode and Extended Mode security associations were established.
IPsec Main Mode and Extended Mode security associations were established.
IPsec Main Mode and Extended Mode security associations were established.
An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted.
An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted.
The state of a transaction has changed.
The Windows Firewall Service has started successfully.
The Windows Firewall Service has been stopped.
The Windows Firewall Service was unable to parse the new security policy. The service will continue with currently enforced policy.
The Windows Firewall Service failed to initialize the driver. The service will continue to enforce the current policy.
The Windows Firewall Service failed to start.
The Windows Firewall Service blocked an application from accepting incoming connections on the network.
Windows Firewall was unable to notify the user that it blocked an application from accepting incoming connections on the network.
The Windows Firewall Driver has started successfully.
The Windows Firewall Driver has been stopped.
The Windows Firewall Driver failed to start.
The Windows Firewall Driver detected critical runtime error. Terminating.
A registry key was virtualized.
A change has been made to IPsec settings. An Authentication Set was added.
A change has been made to IPsec settings. An Authentication Set was modified.
A change has been made to IPsec settings. An Authentication Set was deleted.
A change has been made to IPsec settings. A Connection Security Rule was added.
A change has been made to IPsec settings. A Connection Security Rule was modified.
A change has been made to IPsec settings. A Connection Security Rule was deleted.
A change has been made to IPsec settings. A Crypto Set was added.
A change has been made to IPsec settings. A Crypto Set was modified.
A change has been made to IPsec settings. A Crypto Set was deleted.
An IPsec Security Association was deleted.
An attempt to programmatically disable the Windows Firewall using a call to InetFwProfile.FirewallEnabled(False)
A file was virtualized.
A cryptographic self test was performed.
A cryptographic primitive operation failed.
Key file operation.
Key migration operation.
Verification operation failed.
Cryptographic operation.
A kernel-mode cryptographic self test was performed.
A cryptographic provider operation was attempted.
A cryptographic context operation was attempted.
A cryptographic context modification was attempted.
A cryptographic function operation was attempted.
A cryptographic function modification was attempted.
A cryptographic function provider operation was attempted.
A cryptographic function property operation was attempted.
A cryptographic function property modification was attempted.
OCSP Responder Service Started
OCSP Responder Service Stopped
A configuration entry changed in OCSP Responder Service
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 may also indicate interoperability problems with other IPsec implementations. In that case, if connectivity is not impeded, then these events can be ignored.
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.
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.
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.
The Windows Firewall Service was unable to retrieve the security policy from the local storage. The service will continue enforcing the current policy.
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.
A configuration entry changed in OCSP Responder Service
A security setting was updated on the OCSP Responder Service
A request was submitted to the OCSP Responder Service
Signing Certificate was automatically updated by the OCSP Responder Service
The OCSP Revocation Provider successfully updated the revocation information
A directory service object was modified.
A directory service object was created.
A directory service object was undeleted.
A directory service object was moved.
A network share object was accessed.
A directory service object was deleted.
The Windows Filtering Platform blocked a packet.
A more restrictive Windows Filtering Platform filter has blocked a packet.
The Windows Filtering Platform has permitted an application or service to listen on a port for incoming connections.
The Windows Filtering Platform has blocked an application or service from listening on a port for incoming connections.
The Windows Filtering Platform has allowed a connection.
The Windows Filtering Platform has blocked a connection.
The Windows Filtering Platform has permitted a bind to a local port.
The Windows Filtering Platform has blocked a bind to a local port.
Credential Manager credentials were backed up.
Credential Manager credentials were restored from a backup.
The requested credentials delegation was disallowed by policy.
The following callout was present when the Windows Filtering Platform Base Filtering Engine started.
The following filter was present when the Windows Filtering Platform Base Filtering Engine started.
The following provider was present when the Windows Filtering Platform Base Filtering Engine started.
The following provider context was present when the Windows Filtering Platform Base Filtering Engine started.
The following sub-layer was present when the Windows Filtering Platform Base Filtering Engine started.
A Windows Filtering Platform callout has been changed.
A Windows Filtering Platform filter has been changed.
A Windows Filtering Platform provider has been changed.
A Windows Filtering Platform provider context has been changed.
A Windows Filtering Platform sub-layer has been changed.
An IPsec Quick Mode security association was established.
An IPsec Quick Mode security association ended.
An IPsec negotiation with a remote computer failed because the IKE and AuthIP IPsec Keying Modules (IKEEXT) service is not started.
PAStore Engine applied Active Directory storage IPsec policy on the computer.
PAStore Engine failed to apply Active Directory storage IPsec policy on the computer.
PAStore Engine applied locally cached copy of Active Directory storage IPsec policy on the computer.
PAStore Engine failed to apply locally cached copy of Active Directory storage IPsec policy on the computer.
PAStore Engine applied local registry storage IPsec policy on the computer.
PAStore Engine failed to apply local registry storage IPsec policy on the computer.
PAStore Engine polled for changes to the active IPsec policy and detected no changes.
PAStore Engine polled for changes to the active IPsec policy, detected changes, and applied them to IPsec Services.
PAStore Engine received a control for forced reloading of IPsec policy and processed the control successfully.
PAStore Engine loaded local storage IPsec policy on the computer.
PAStore Engine failed to load local storage IPsec policy on the computer.
PAStore Engine loaded directory storage IPsec policy on the computer.
PAStore Engine failed to load directory storage IPsec policy on the computer.
PAStore Engine failed to add quick mode filter.
IPsec Services has started successfully.
PAStore Engine failed to apply some rules of the active IPsec policy on the computer. Use the IP Security Monitor snap-in to diagnose the problem.
PAStore Engine 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.
PAStore Engine 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.
PAStore Engine 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.
IPsec Services has been shut down successfully. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks.
IPsec Services failed to initialize RPC server. IPsec Services could not be started.
A request was made to authenticate to a wireless network.
A request was made to authenticate to a wired network.
A Remote Procedure Call (RPC) was attempted.
An object in the COM+ Catalog was modified.
An object was deleted from the COM+ Catalog.
An object was added to the COM+ Catalog.
The previous system shutdown was unexpected
Security policy in the group policy objects has been applied successfully.
One or more errors occurred while processing security policy in the group policy objects.
Network Policy Server granted access to a user.
Network Policy Server denied access to a user.
Network Policy Server discarded the request for a user.
Network Policy Server discarded the accounting request for a user.
Network Policy Server quarantined a user.
Network Policy Server granted access to a user but put it on probation because the host did not meet the defined health policy.
Network Policy Server granted full access to a user because the host met the defined health policy.
Network Policy Server locked the user account due to repeated failed authentication attempts.
Network Policy Server unlocked the user account.
General account database changed
A handle to an object was requested.
Object open for delete
User Account Type Changed
Quality of Service Policy changed
IPSec policy agent started
IPSec policy agent disabled
IPSec policy agent
IPSec policy agent encountered a potential serious failure
Encyption of volume started
Encryption of volume stopped
Encryption of volume completed
Decryption of volume started
Decryption of volume stopped
Decryption of volume completed
Conversion worker thread for volume started
Conversion worker thread for volume temporarily stopped
An error was encountered converting volume
The conversion operation on volume %2 encountered a bad sector error. Please validate the data on this volume
An attempt to automatically restart conversion on volume %2 failed.
Metadata write: Volume %2 returning errors while trying to modify metadata. If failures continue, decrypt volume
Volume %2 contains bad clusters. These clusters will be skipped during conversion.
IPsec Services 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.
IPsec Services has experienced a critical failure and has been shut down. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks.
IPsec Services 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.
Metadata rebuild: An attempt to write a copy of metadata on volume %2 failed and may appear as disk corruption. If failures continue, decrypt volume.
Initial state check: Rolling volume conversion transaction on %2.
Notes
Medium if changed by user
Alert on abnormal occurrence
Alert on abnormal occurrence
Alert on abnormal occurrence
Medium on servers
Medium - report
Medium-report w/ elevated user???
Medium-email w/ elevated groups
Medium-report w/ elevated groups
Medium-email w/ elevated groups
Medium-email w/ elevated groups
Medium - report
Investigate in future if AL enabled
Medium-email w/ elevated groups
Medium-email w/ elevated groups
Medium-email w/ elevated groups
Medium-email w/ elevated groups
Generate alert on abnormal occurrence
Don't generate events
Don't generate events
Generate alert on abnormal occurrence
Generate alert on abnormal occurrence
Cannot generate
Usually legitimate, can be ignored
Just noise on startup
Need to verify XP event ID
Need to define grps, push regedit
High/Med-for abnormal
Normal or could be indicitive of malware or buffer overflow
May not exist?
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Taken from http://technet.microsoft.com/en-us/library/dd363902(WS.10).aspx
Event ID
4608
4609
4610
4611
4612
4614
4615
4616
4618
4621
4622
4624
4625
4634
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4670
4671
4672
4673
4674
4675
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4704
4705
4706
4707
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4800
4801
4802
4803
4816
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4902
4904
4905
4906
4907
4908
4909
4910
4912
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4956
4957
4958
4960
4961
4962
4963
4964
4965
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
5024
5025
5027
5028
5029
5030
5031
5032
5033
5034
5035
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5120
5121
5122
5123
5124
5125
5126
5127
5136
5137
5138
5139
5140
5141
5152
5153
5154
5155
5156
5157
5158
5159
5376
5377
5378
5440
5441
5442
5443
5444
5446
5447
5448
5449
5450
5451
5452
5453
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5471
5472
5473
5474
5477
5478
5479
5480
5483
5484
5485
5632
5633
5712
5888
5889
5890
6144
6145
6272
6273
6274
6275
6276
6277
6278
6279
6280
8191
Detailed Message
Windows is starting up.This event is logged when LSASS.EXE starts and the auditing subsystem is initialized.
Windows is shutting down.All logon sessions will be terminated by this shutdown.
An authentication package has been loaded by the Local Security Authority.This authentication package will be used to authenticate logon attempts.
Authentication Package Name: %1
This logon process will be trusted to submit logon requests.
Internal resources allocated for the queuing of audit messages have been exhausted, leading to the loss of some audits.
Number of audit messages discarded: %1
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.
A notification package has been loaded by the Security Account Manager.This package will be notified of any account or password changes.
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.
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.
Alert Information: Computer: %2 Event ID: %1 Number of Events: %7 Duration: %8
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.
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.
Value of CrashOnAuditFail: %1
This event is logged after a system reboots following CrashOnAuditFail.
A security package has been loaded by the Local Security Authority.
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 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.
1%
Account Name: %2 Account Domain: %3 Logon ID: %4
Logon Type: %11
Account For Which Logon Failed: Security ID: %5 Account Name: %6 Account Domain: %7
Failure Information: Failure Reason: %9 Status: %8 Sub Status: %10
Process Information: Caller Process ID: %18 Caller Process Name: %19
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.
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 but the token reference count is not zero and the logon session cannot be destroyed. No further user-initiated activity can occur. This event can be interpreted as a logoff event.
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.
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.
An IPsec Main Mode security association was established. Extended Mode was not enabled. Certificate authentication was not used.
Local Endpoint: Principal Name: %1 Network Address: %3 Keying Module Port: %4
Process Information: New Process ID: %5 New Process Name: %6 Token Elevation Type: %7 Creator Process ID: %8
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.
Attributes: SAM Account Name: %9 Display Name: %10 User Principal Name: %11 Home Directory: %12 Home Drive: %13 Script Path: %14 Profile Path: %15 User Workstations: %16 Password Last Set: %17 Account Expires: %18 Primary Group ID: %19 Allowed To Delegate To: %20 Old UAC Value: %21 New UAC Value: %22 User Account Control: %23 User Parameters: %24 SID History: %25 Logon Hours: %26
Attributes: SAM Account Name: %9 Display Name: %10 User Principal Name: %11 Home Directory: %12 Home Drive: %13 Script Path: %14 Profile Path: %15 User Workstations: %16 Password Last Set: %17 Account Expires: %18 Primary Group ID: %19 AllowedToDelegateTo: %20 Old UAC Value: %21 New UAC Value: %22 User Account Control: %23 User Parameters: %24 SID History: %25 Logon Hours: %26 DNS Host Name: %27 Service Principal Names: %28
Computer Account That Was Changed: Security ID: %4 Account Name: %2 Account Domain: %3
Changed Attributes: SAM Account Name: %10 Display Name: %11 User Principal Name: %12 Home Directory: %13 Home Drive: %14 Script Path: %15 Profile Path: %16 User Workstations: %17 Password Last Set: %18 Account Expires: %19 Primary Group ID: %20 AllowedToDelegateTo: %21 Old UAC Value: %22 New UAC Value: %23 User Account Control: %24 User Parameters: %25 SID History: %26 Logon Hours: %27 DNS Host Name: %28 Service Principal Names: %29
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.
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.
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.
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.
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.
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.
Process Information: Process ID: %11 Process Name: %12
Auditing Settings: Original Security Descriptor: %9 New Security Descriptor: %10
Special Groups Logon table modified.
Special Groups: %1
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.
The local policy settings for the TBS were changed.
Old Blocked Ordinals: %1New Blocked Ordinals: %2
The group policy settings for the TBS were changed.
Group Policy Setting: Ignore Default Settings Old Value: %1 New Value: %2
Group Policy Setting: Ignore Local Settings Old Value: %3 New Value: %4
A rule was listed when the Windows Firewall started. Profile used: %1
Rule: Rule ID: %2 Rule Name: %3
Windows Firewall settings were restored to the default values.
Windows Firewall Group Policy settings has changed. The new settings have been applied.
A change has been made to Windows Firewall exception list. A rule was added. Profile Changed: %1
Added Rule: Rule ID: %2 Rule Name: %3
A change has been made to Windows Firewall exception list. A rule was modified. Profile Changed: %1
Modified Rule: Rule ID: %2 Rule Name: %3
A change has been made to Windows Firewall exception list. A rule was deleted. Profile Changed: %1
Deleted Rule: Rule ID: %2 Rule Name: %3
A Windows Firewall setting has changed. Profile That Was Changed: %1
New Setting: Type: %2 Value: %3
A rule has been ignored because its major version number was not recognized by Windows Firewall. Profile: %1
Ignored Rule: ID: %2 Name: %3
Parts of a rule have been ignored because its minor version number was not recognized by Windows Firewall. The other parts of the rule will be enforced. Profile: %1
Partially Ignored Rule: ID: %2 Name: %3
A rule has been ignored by Windows Firewall because it could not parse the rule. Profile: %1
Reason for Rejection: %2
Rule: ID: %3 Name: %4
Windows Firewall has changed the active profile.
New Active Profile: %1
Windows Firewall did not apply the following rule:
Rule Information: ID: %1 Name: %2
Error Information: Reason: %3 resolved to an empty set.
Windows Firewall did not apply the following rule because the rule referred to items not configured on this computer:
Rule Information: ID: %1 Name: %2
Error Information: Error: %3 Reason: %4
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.
Remote Network Address: %1Inbound SA SPI: %2
IPsec dropped an inbound packet that failed a replay check. If this problem persists, it could indicate a replay attack against this computer.
Remote Network Address: %1Inbound SA SPI: %2
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.
Remote Network Address: %1Inbound SA SPI: %2
IPsec dropped an inbound clear text packet that should have been secured. This is usually due to the remote computer changing its IPsec policy without informing this computer. This could also be a spoofing attack attempt.
New Logon: Security ID: %6 Account Name: %7 Account Domain: %8 Logon ID: %9 Logon GUID: %10 Special Groups Assigned: %11
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 may also indicate interoperability problems with other IPsec implementations. In that case, if connectivity is not impeded, then these events can be ignored.
Remote Network Address: %1Inbound SA SPI: %2
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.
Local Network Address: %1Remote Network Address: %2Keying Module Name: %3
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.
Local Network Address: %1Remote Network Address: %2Keying Module Name: %3
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.
Local Network Address: %1Remote Network Address: %2Keying Module Name: %3
IPsec Main Mode and Extended Mode security associations were established.
Main Mode Local Endpoint: Principal Name: %1 Network Address: %3 Keying Module Port: %4
Main Mode Remote Endpoint: Principal Name: %2 Network Address: %5 Keying Module Port: %6
Process Information: Process ID: %8 Process Name: %9
The Windows Firewall Service was unable to retrieve the security policy from the local storage. The service will continue enforcing the current policy.
Error Code: %1
The Windows Firewall Service was unable to parse the new security policy. The service will continue with currently enforced policy.
Error Code: %1
The Windows Firewall Service failed to initialize the driver. The service will continue to enforce the current policy.
Error Code: %1
The Windows Firewall Service failed to start.
Error Code: %1
The Windows Firewall Service blocked an application from accepting incoming connections on the network.
Profiles: %1Application: %2
Windows Firewall was unable to notify the user that it blocked an application from accepting incoming connections on the network.
Error Code: %1
The Windows Firewall Driver failed to start.
Error Code: %1
The Windows Firewall Driver detected critical runtime error. Terminating.
Error Code: %1
0x8000000000000000 message: 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.
A change has been made to IPsec settings. A Connection Security Rule was deleted. Profile Changed: %1
Deleted Connection Security Rule: ID: %2 Name: %3
A change has been made to IPsec settings. A Crypto Set was added. Profile Changed: %1
Added Crypto Set: ID: %2 Name: %3
A change has been made to IPsec settings. A Crypto Set was modified. Profile Changed: %1
Modified Crypto Set: ID: %2 Name: %3
A change has been made to IPsec settings. A Crypto Set was deleted. Profile Changed: %1
Deleted Crypto Set: ID: %2 Name: %3
An IPsec Security Association was deleted. Profile Changed: %1
Deleted SA: ID: %2 Name: %3
An attempt to programmatically disable the Windows Firewall using a call to INetFwProfile.FirewallEnabled(FALSE) interface was rejected because this API is not supported on Windows Vista. This has most likely occurred due to a program which is incompatible with Windows Vista. Please contact the program's manufacturer to make sure you have a Windows Vista compatible program version.
Error Code: E_NOTIMPLCaller Process Name: %1Process Id: %2Publisher: %3
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.
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.
The requested credentials delegation was disallowed by policy.
The following provider was present when the Windows Filtering Platform Base Filtering Engine started. Provider ID: %1Provider Name: %2Provider Type: %3
The following provider context was present when the Windows Filtering Platform Base Filtering Engine started. Provider ID: %1Provider Name: %2Provider Context ID: %3Provider Context Name: %4Provider Context Type: %5
The following sub-layer was present when the Windows Filtering Platform Base Filtering Engine started. Provider ID: %1Provider Name: %2Sub-layer ID: %3Sub-layer Name: %4Sub-layer Type: %5Weight: %6
A Windows Filtering Platform callout has been changed. Subject: Security ID: %2 Account Name: %3
Additional Information: Protocol: %7 Quick Mode SA ID: %8
PAStore Engine applied Active Directory storage IPsec policy on the computer.
Policy: %1
PAStore Engine failed to apply Active Directory storage IPsec policy on the computer.
DN: %1Error code: %2
PAStore Engine applied locally cached copy of Active Directory storage IPsec policy on the computer.
Policy: %1
PAStore Engine polled for changes to the active IPsec policy and detected no changes.
PAStore Engine polled for changes to the active IPsec policy, detected changes, and applied them to IPsec Services.
PAStore Engine received a control for forced reloading of IPsec policy and processed the control successfully.
PAStore Engine 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.
IPsec Services has started successfully.
IPsec Services has been shut down successfully. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks.
PAStore Engine failed to apply locally cached copy of Active Directory storage IPsec policy on the computer.
Policy: %1Error Code: %2
PAStore Engine applied local registry storage IPsec policy on the computer.
Policy: %1
PAStore Engine failed to apply local registry storage IPsec policy on the computer.
Policy: %1Error Code: %2
PAStore Engine failed to apply some rules of the active IPsec policy on the computer. Use the IP Security Monitor snap-in to diagnose the problem.
Policy: %1Error Code: %2
PAStore Engine 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.
PAStore Engine 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.
PAStore Engine loaded local storage IPsec policy on the computer.
Policy: %1
PAStore Engine failed to load local storage IPsec policy on the computer.
Policy: %1Error Code: %2
PAStore Engine loaded directory storage IPsec policy on the computer.
Policy: %1
PAStore Engine failed to load directory storage IPsec policy on the computer.
Policy: %1Error Code: %2
PAStore Engine failed to add quick mode filter.
Quick Mode Filter: %1Error Code: %2
IPsec Services 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.
IPsec Services failed to initialize RPC server. IPsec Services could not be started.
Error Code: %1
IPsec Services has experienced a critical failure and has been shut down. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks.
Error Code: %1
IPsec Services 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.
A request was made to authenticate to a wireless network.
Quarantine Information: Result: %25 Extended-Result: %26 Session Identifier: %27 Help URL: %28 System Health Validator Result(s): %29
0x8000000000000000 message: 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.