Detections
Analytics
17.2.3 Ensure 'Audit User Account Management' is set to 'Success and Failure'
Warning! Audit Deprecated
This audit has been deprecated and will be removed in a future update.
View Next Audit VersionInformation
This subcategory reports each event of user account management, such as when a user account is created, changed, or deleted; a user account is renamed, disabled, or enabled; or a password is set or changed. If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user accounts. Events for this subcategory include:4720: A user account was created.
4722: A user account was enabled.
4723: An attempt was made to change an account's password.
4724: An attempt was made to reset an account's password.
4725: A user account was disabled.
4726: A user account was deleted.
4738: A user account was changed.
4740: A user account was locked out.
4765: SID History was added to an account.
4766: An attempt to add SID History to an account failed.
4767: A user account was unlocked.
4780: The ACL was set on accounts which are members of administrators groups.
4781: The name of an account was changed:
4794: An attempt was made to set the Directory Services Restore Mode.
5376: Credential Manager credentials were backed up.
5377: Credential Manager credentials were restored from a backup.
The recommended state for this setting is: Success and Failure.
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 Success and Failure: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_AuditUserAccountManagement
Data type: Integer
Value: 3
Select Save
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
Item Details
References: CSCv7|6.3
Plugin: Windows
Control ID: 55dd579a6d7e230396a7501a90fb948483527969f1534af7ef0006e892134046