Audit Your Microsoft Active Directory Services Like a Pro with Microsoft Sentinel
This blog post explains how to enable and configure advanced auditing for Active Directory Certificate Services (ADCS), and how to collect and send the resulting logs to Microsoft Sentinel. By default, logging for ADCS is not enabled, which means you may miss important insights about your environment.
Please remember that you need to carry out the same activities on all your ADCS servers.
What do you need?
In order to complete the steps described in this post, you will need:
- Azure Log Analytics workspace
- Microsoft Sentinel
- Azure Arc connect server
You may be wondering why Azure Arc is needed for ADCS auditing. In this case, it is assumed that you are not using Defender for Cloud or Microsoft Sentinel to forward all security events. If you use the Defender for Cloud or Security Events connector in Sentinel, you have four different configuration options:
- All Events
The Common events option only includes around 150 different events from the security log, and does not include specific ADCS event IDs. While you could set your Security Events connector or Defender for Cloud to forward all logs, this may not be desirable. Azure Arc and the Azure Monitoring Agent allow you to define your own Data Collector Rules and collect only the events you need.
The first step is ensuring auditing is enabled on your ADCS servers.
Run the auditpol command and ensure that “Certificate Services” and “Registry” advanced auditing are enabled.
auditpol /get /category:*
You can configure advanced auditing settings using the auditpol /set command or Group Policy.
auditpol /set /subcategory:"Certification Services" /success:enable /failure:enable
The next step is to enable auditing through the ACS snap-in. To do that, follow the steps on your ADCS server:
- Open Server Manager
- Select Tools -> Certification Authority
- Right-click your CA name and choose properties
- Select Auditing
- Enable the auditing settings you need
- Back up and restore the CA database
- Change CA configuration
- Change CA security settings
- Issue and manage certificate requests
- Revoke certificates and publish CRLs
- Store and retrieve archived keys
- Start and stop ADCS service
The next step is to enable the certificate template changes using the certutil command:
certutil –setreg policy\EditFlags +EDITF_AUDITCERTTEMPLATELOAD
Because some changes can be done directly through the registry, we need to enable registry auditing. To do that, we need to do this:
- Open Regedit on your ADCS server
- Browse the following key
- Right-click Configuration and choose Permissions
- Click Advanced
- Choose Auditing and click Add
- Set the principal to Authenticated Users and configure the following permissions
- Set Value
- Create SubKey
- Write DAC
- Write Owner
- Read Control
Reboot your server and verify the changes. After the reboot, you should see different event IDs in your Security logs.
Now that we have the ADCS auditing up and running, we can continue with the Azure Arc and Sentinel.
Azure Arc configuration
For Azure Arc configuration, follow this guide - Connect hybrid machine with Azure Arc enabled servers - Azure Arc | Microsoft Docs
Now that you have Azure Arc up and running, we can continue with the Data Collection Rules. In Microsoft Sentinel, we have a new connector called Windows Security Events. This connector allows us to define custom log policies for Azure Arc-enabled servers. In the Data Collector Rules, you need to specify the XPATH queries.
Security!*[System[(EventID=4882 or EventID=4899)]]
You can test your XPATH queries using the Get-WinEvent PowerShell cmdlet.
Are you looking to improve your organization's security and gain better visibility into potential threats? Contact me today and I can help you implement Microsoft Sentinel, a powerful security platform that uses artificial intelligence and machine learning to help you detect, investigate, and respond to security incidents.