1. Click Start, and then open the GPMC.
2. In the navigation menu, click Forest: <DomainName>, where DomainName is the name of your domain, and then click the Domains folder.
3. Right-click the domain name. If you:
   • Already have an AD Sensor GPO — Select Link an Existing GPO, and then click Edit.
   • Do not have an existing AD Sensor GPO — Create a new GPO:
     1. Select Create a GPO in this domain, and Link it here.
     2. In the New GPO dialog box, enter a name for the new GPO.
     3. Verify that the Source Starter GPO menu says (none).
     4. Click OK.
        Tip:

        To assign a security group and make sure that Agent is deployed to the correct group of computers, see Assign Security Group Filters to the GPO.

     5. Right-click the new GPO, and then click Enforced to enable it.

        The GPO is enabled. A lock appears on the GPO icon in the navigation menu.

     6. Right-click the new GPO, and then select Edit.

1. Set the Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings policy to Enabled:
   1. In the Group Policy Management Editor navigation menu, click Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options.
   2. Right-click Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings, and then select Properties.
   3. Click the Security Policy Setting tab.
   4. Select the Define this policy setting checkbox, and then select Enabled.
   5. Click OK.

      See the Microsoft documentation for this security option for more information.

2. In the Group Policy Management Editor, in the navigation menu, click Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Audit Policies.
   Tip:

   Resize the window and enable tree view to completely view the policy tree.

   

3. Edit the audit policy settings:
   1. In the Audit Policies section, select the category. For example, Account Logon.
   2. Double-click the corresponding subcategory. For example, Audit Credential Validation.
   3. Edit the policy setting as indicated in the table.
   4. Verify that each setting has these checkboxes selected:
      • Configure the following audit events
      • Success or Failure, according to the Audit Events listed in the table.

   This table lists the policy setting checkboxes to select:

   Category	Subcategory	Audit event settings
   Account Logon	Audit Credential Validation	Success and Failure
   Account Logon	Audit Kerberos Authentication Service	Success and Failure
   Account Logon	Audit Kerberos Service Ticket Operations	Success and Failure
   Account Logon	Audit Other Account Logon Events	Success and Failure
   Account Management	Audit Computer Account Management	Success and Failure
   Account Management	Audit Other Account Management Events	Success and Failure
   Account Management	Audit Security Group Management	Success and Failure
   Account Management	Audit User Account Management	Success and Failure
   Detailed Tracking	Audit DPAPI Activity	Success
   Detailed Tracking	Audit Process Creation	Success
   Detailed Tracking	Audit Process Termination	Success
   Detailed Tracking	Audit Token Right Adjusted	Success
   DS Access	Audit Directory Service Access	Success
   DS Access	Audit Directory Service Changes	Success
   Logon/Logoff	Audit Account Lockout	Success and Failure
   Logon/Logoff	Audit Logoff	Success and Failure
   Logon/Logoff	Audit Logon	Success and Failure
   Logon/Logoff	Audit Network Policy Server	Success and Failure
   Logon/Logoff	Audit Other Logon/Logoff Events	Success and Failure
   Logon/Logoff	Audit Special Logon	Success and Failure
   Object Access	Audit Detailed File Share	Success and Failure
   Policy Change	Audit Audit Policy Change	Success and Failure
   Policy Change	Audit Authentication Policy Change	Success and Failure
   Policy Change	Audit Authorization Policy Change	Success and Failure
   Policy Change	Audit MPSSVC Rule-Level Policy Change	Success
   Privilege Use	Audit Sensitive Privilege Use	Success and Failure
   System	Audit IPsec Driver	Success
   System	Audit Other System Events	Success and Failure
   System	Audit Security State Change	Success and Failure
   System	Audit Security System Extension	Success and Failure
   System	Audit System Integrity	Success and Failure

4. In the same Group Policy, enable these command-line policies:
   Note:

   These configuration options do not appear unless the functional level of the domain is Windows Server 2012 R2 or higher. See Active Directory Domain Services Functional Levels in Windows Server for more information.

   • Click Computer Configuration > Policies > Administrative Templates > System > Audit Process Creation, and then set Include command line in process creation events to Enabled.

     

   • Click Computer Configuration > Policies > Administrative Templates > Windows Components > Windows PowerShell, and then set Turn on PowerShell Script Block Logging to Enabled.

     

5. Close the Group Policy Management Editor window after completing all audit and command-line policy changes.
6. In the navigation menu, click AWN Audit Policy.
7. Click the Settings tab.
8. Compare the policy configuration settings to the audit policy settings you edited earlier in this procedure.
   Note:

   Even if the settings here are correct, they might not have been applied yet.

9. Verify that the AD audit settings were applied by running auditpol.exe /get /category:* on every DC in your environment. Review the results of the command against the settings from the previous step. If the results are incorrect or return No Auditing:
   1. Run gpupdate /force, followed by auditpol.exe /get /category:* again. If the results are still incorrect, proceed to the next step.
   2. Navigate back to Audit Policies and complete these steps for those that did not update:
      Note:

      You do not need to follow this procedure for every policy. You only need to do this for one policy.

      1. Clear the applicable checkboxes, and then click Apply.
      2. Reselect the appropriate checkboxes, and then click Apply.
      3. Run gpupdate /force.
      4. Run auditpol.exe /get /category:* again. If the results are still incorrect, proceed to the next step.
   3. Run gpresult /h auditsettings.html and send the HTML file that is created to Arctic Wolf for further investigation.

The Arctic Wolf GPO requires precedence over other GPOs.

1. In the navigation menu, click Forest: DomainName, where DomainName is the name of your domain, and then click the Domains folder.
2. Click the Linked Group Policy Objects tab.
3. In the GPO column, locate and click the Arctic Wolf GPO, and then use the up and down arrows to move the GPO to the top of the list.
4. Verify that the Arctic Wolf GPO has these settings:
   • Link Order — 1.
   • Enforced — Yes.
5. Close the Group Policy Management window.

1. Click Start > Windows PowerShell or Command Prompt.
2. Run this command:
   SHELLCopy

   gpupdate /force

   gpupdate /force

   Note:

   If you are prompted to sign off or restart after the user and computer policy updates complete, press N, and then press Enter.

3. Close Windows PowerShell or the Command Prompt.

   The audit settings are now successfully applied with Group Policy.

You can run the Arctic Wolf PowerShell script awn_gpo_checker.ps1 to validate your GPO Audit Policy against Arctic Wolf's recommended settings. The script does not make any changes to your environment configuration.

1. Download awn_gpo_checker.zip.
2. Unzip the script.
3. Open a PowerShell terminal with Administrator permissions and go to the location of the unzipped script.
4. Run the script by entering this command
   CODECopy

   .\awn_gpo_checker.ps1

   .\awn_gpo_checker.ps1

   Note: With Administrator permission, you can also run the script in PowerShell ISE.
   The script displays the results in the terminal and creates this file:

   • AWN_GPO_Results.txt
5. Reconfigure the GPO Audit Policy configuration for any failed tests based on the remediation steps displayed in the script output.
6. Re-run the script to make sure that all tests pass after making changes to the GPO.
7. If there are any failures or you need any further assistance with the GPO Audit Policy settings, attach the AWN_GPO_Results.txt file to your ticket.