From Windows 2003 Member Server Security Technical Implementation Guide
Part of Auditing Configuration
Associated with IA controls: ECAR-3, ECAR-2
Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
Configure the system to audit the following categories as outlined. Audit account logon events - Success, Failure Audit account management - Success, Failure Audit logon events - Success, Failure Audit object access - Failure Audit policy change - Success Audit privilege use - Failure Audit system events - Success
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer