17.9.4 Ensure 'Audit Security System Extension' is set to include 'Success'

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version


This subcategory reports the loading of extension code such as authentication packages by the security subsystem. Events for this subcategory include:

4610: An authentication package has been loaded by the Local Security Authority.

4611: A trusted logon process has been registered with the Local Security Authority.

4614: A notification package has been loaded by the Security Account Manager.

4622: A security package has been loaded by the Local Security Authority.

4697: A service was installed in the system.

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


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


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

auditpol /set /subcategory:'Security System Extension' /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.


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:

No Auditing.

See Also