Detections
Analytics

17.2.2 Ensure 'Audit Security Group Management' 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

Information

This subcategory reports each event of security group management, such as when a security group is created, changed, or deleted or when a member is added to or removed from a security group. If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of security group accounts. Events for this subcategory include:

4727: A security-enabled global group was created.

4728: A member was added to a security-enabled global group.

4729: A member was removed from a security-enabled global group.

4730: A security-enabled global group was deleted.

4731: A security-enabled local group was created.

4732: A member was added to a security-enabled local group.

4733: A member was removed from a security-enabled local group.

4734: A security-enabled local group was deleted.

4735: A security-enabled local group was changed.

4737: A security-enabled global group was changed.

4754: A security-enabled universal group was created.

4755: A security-enabled universal group was changed.

4756: A member was added to a security-enabled universal group.

4757: A member was removed from a security-enabled universal group.

4758: A security-enabled universal group was deleted.

4764: A group's type was changed.

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

Rationale:

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

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.

Solution

To establish the recommended configuration, set the following Device Configuration Policy to include Success:

To access the Device Configuration Policy from the Intune Home page:

Click Devices

Click Configuration profiles

Click Create profile

Select the platform (Windows 10 and later)

Select the profile (Custom)

Enter a Name

Click Add

Enter the Details below

Name: <Enter name>
Description: <Enter Description>
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Audit/AccountManagement_AuditSecurityGroupManagement
Data type: Integer
Value: 1

Select Save

Continue through the Wizard to complete the creation of the profile (profile assignments, applicability etc.)

OR

To access the Device Configuration Policy from the Intune Home page:

Click Devices

Click Configuration profiles

Click Create profile

Select the platform (Windows 10 and later)

Select the profile (Settings Picker)

Click Create

Enter a Name

Click Add settings

Configure the following Setting:

Path: Auditing
Setting Name: Audit Security Group Management
Configuration: Success

Continue through the Wizard to complete the creation of the profile (profile assignments, applicability etc.)

Note: More than one configuration setting from each of the Configuration profiles (ex: Administrative Templates, Custom etc.) can be added to each Device Configuration Policy.

Default Value:

Success.

See Also

https://workbench.cisecurity.org/benchmarks/14664

Item Details

References: CSCv7|6.3, CSCv7|16.6

Plugin: Windows

Control ID: dad16c852b9e669217454c72b53c89e7c0d909f188a6ab90f918a8214064c893