Yes, this behavior is by design. Windows Server does not generate native Security Event Log entries for credential add, modify, or delete operations in Credential Manager, even with Advanced Audit Policy enabled. The only credential-related events exposed are 5376 and 5377, which correspond to backup and restore operations.
Windows Server – Can We Audit Credential Manager Add, Modify, and Delete Operations?
Hello Team,
We would like to confirm whether Windows Server provides native audit logging for Windows Credential Manager operations.
Specifically, we are looking to understand:
- Can Windows log when a credential is added in Credential Manager?
Can Windows log when a credential is modified?
Can Windows log when a credential is deleted?
During our investigation, we observed Security Event IDs:
5376 (Credential Manager credentials were backed up)
5377 (Credential Manager credentials were restored)
However, we were unable to find any event logs related to credential add, modify, or delete operations.
Our questions:
Is this behavior by design?
Does Windows Server natively support auditing these Credential Manager operations?
If not, what is the recommended or supported method to monitor or audit Credential Manager changes in a production environment?
Environment:
Windows Server 2019 / 2022
Domain joined
Advanced audit policies enabled
We require official clarification for audit and compliance documentation purposes.
Thank you
Windows for business | Windows Server | Devices and deployment | Other
2 answers
Sort by: Most helpful
-
Harry Phan 16,010 Reputation points Independent Advisor
2026-02-23T17:38:10.66+00:00 -
Q&A Assist2026-02-17T16:10:13.54+00:00 AI generated content. This question contains an answer created with AI from Q&A Assist. Learn moreWindows Server does not natively support auditing for add, modify, or delete operations specifically related to Windows Credential Manager. The Security Event IDs you mentioned (5376 and 5377) are related to the backup and restoration of Credential Manager credentials but do not cover the operations of adding, modifying, or deleting credentials.
This behavior appears to be by design, as there are no built-in audit logs for these specific actions. To monitor or audit changes to Credential Manager in a production environment, you may need to consider alternative methods, such as using third-party auditing tools or implementing custom logging solutions that can track these operations at the application level.
For compliance and audit documentation purposes, it is advisable to document this limitation and the recommended alternative methods for monitoring Credential Manager changes.
References: