Title

Auditing must be configured as required. (Cat II impact)

Discussion

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.

Check Content

Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Expand the "Local Policies" object and select "Audit Policy". Compare the settings in the Policy window with the following. If system does not audit the events listed below, this is a finding. 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

Fix Text

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

Additional Identifiers

Rule ID: SV-29742r2_rule

Vulnerability ID: V-6850

Group Title:

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.