17.9.5 Ensure 'Audit System Integrity' is set to 'Success and Failure'

Information

This subcategory reports on violations of integrity of the security subsystem. Events for this subcategory include:

4612 : Internal resources allocated for the queuing of audit messages have been exhausted, leading to the loss of some audits.

4615 : Invalid use of LPC port.

4618 : A monitored security event pattern has occurred.

4816 : RPC detected an integrity violation while decrypting an incoming message.

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.

5056: A cryptographic self test was performed.

5057: A cryptographic primitive operation failed.

5060: Verification operation failed.

5061: Cryptographic operation.

5062: A kernel-mode cryptographic self test was performed.

The recommended state for this setting is: Success and Failure.

Rationale:

Auditing these events may be useful when investigating a security incident.

Solution

To establish the recommended configuration via GP, set the following UI path to Success and Failure:

Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System\Audit System Integrity

Impact:

If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.

Default Value:

Success and Failure.

References:

CCE-37132-8

See Also

https://workbench.cisecurity.org/files/2742