How to Detect Who Enabled a User Account in Active Directory

Native Auditing vs. Netwrix Auditor for Active Directory

We never share your data. Privacy Policy
Native Auditing Netwrix Auditor for Active Directory
  1. Run gpedit.msc → Create a new GPO → Edit it : Go to "Computer Configuration" → Policies → Windows Settings → Security Settings → Local Policies → Audit Policy:
    • Audit account management → Define → Success.
  2. Go to Event Log → Define:
    • Set the maximum security log size to 4 GB
    • Set the retention method for the security log to "Overwrite events as needed".
  3. Link the new GPO to OU with User Accounts: Go to "Group Policy Management" → Right-click the defined OU → Choose "Link an Existing GPO" → Choose the created GPO.
  4. Force a Group Policy update: Go to "Group Policy Management" → Right-click the defined OU → Click "Group Policy Update".
  5. Run adsiedit.msc → Connect to the Default naming context → Right-click the domain DNS object with the name of your domain → Click Properties → Select the Security (Tab) → Click Advanced (Button) → Select Auditing (Tab) → Add the principal "Everyone" → Type "Success" → Apply this to "This object and descendant objects" → Click Permissions → Select all check boxes except the following:
    • Full control
    • List contents
    • Read all properties
    • Read permissions → Click "OK".
  6. Open Event Viewer and search the security log for event ID 4722 (a user account was enabled).

  1. Run Netwrix Auditor → Click "Search" → Choose "Advanced" → Set up the following filters:Audited system = Active Directory Object type = User.
  2. Then click "Modify".
  3. Type "enabled" into the search field and click "Search".
  4. After that, you will see who enabled user accounts in your domain.

Secure Your Infrastructure by Identifying the Recently Enabled Accounts

If an account is enabled without reasonable cause, it may be a sign that an attacker is trying to gain access to the network. Constant monitoring of recently enabled accounts pinpoints who is trying to get unauthorized access to the system and helps to quickly remedy the issue.

Join the discussion