17.9.3 Ensure 'Audit Security State Change' is set to include 'Success'

Information

This subcategory reports changes in security state of the system, such as when the security subsystem starts and stops. Events for this subcategory include:

4608: Windows is starting up.

4609: Windows is shutting down.

4616: The system time was changed.

4621: 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.

The recommended state for this setting is to include: Success.

Rationale:

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

Solution

To establish the recommended configuration via auditpol.exe, perform the following:

auditpol /set /subcategory:'Security State Change' /success:enable

Note: Windows Server 2008 (non-R2) does not recognize nor respond to the Advanced Audit Policy Configuration GPO settings, so you cannot use them to deploy to that older OS. Microsoft did not add GPO support for those settings until Windows Server 2008 R2. You must use auditpol.exe to configure the audit settings on the older OS.


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.

See Also

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