Configuration
Configure AD CS auditing in ADAudit Plus
ADAudit Plus already collects Security log events from Domain Controllers (as part of Active Directory auditing) and from Windows Servers (as part of Windows Server auditing). AD CS auditing reads additional AD CS-specific Security log events from those same configured machines — no separate ADAudit Plus onboarding step is needed specifically for AD CS.
The steps below confirm whether the target machine is already in scope. If it is not yet configured, follow the respective auditing guide to add it first, then return to configure the AD CS-specific audit settings in Configure audit policies.
Domain Controllers
Domain Controllers are configured in ADAudit Plus as part of Active Directory auditing. Once a Domain Controller is in scope, ADAudit Plus reads its AD CS Security log events automatically alongside the standard Security log.
- Already configured: Confirm the Domain Controller is in the monitored scope under Configuration → Data Sources → Domains and Controllers, then proceed to Configure audit policies.
- Not yet configured: Follow Configure AD CS auditing in ADAudit Plus of the Active Directory Auditing Guide to add the domain and Domain Controllers, then return to Configure audit policies.
| Item | Value |
|---|---|
| License required | Domain Controllers license |
| Audit policy reference | AD Auditing Guide — Configure audit policies |
Windows Servers
Windows Servers are configured in ADAudit Plus as part of Windows Server auditing. Once a server is in scope, ADAudit Plus reads its AD CS Security log events automatically alongside the standard Security log.
- Already configured: Confirm the server is listed under Configuration → Data Sources → Member Servers, then proceed to Configure audit policies.
- Not yet configured: Follow Configure AD CS auditing in ADAudit Plus of the Windows Server Auditing Guide to add it, then return to Configure audit policies.
| Item | Value |
|---|---|
| License required | Member Servers add-on |
| Audit policy reference | Windows Server Auditing Guide — Configure audit policies |
Choose automatic or manual audit policy configuration
The choice between automatic and manual audit policy configuration is made during the data source setup in the respective auditing guide. For AD CS auditing, the same choice determines how the AD CS-specific policy (Audit Certification Services) and the CA auditing settings are applied:
| Method | What ADAudit Plus does for AD CS | What you must do |
|---|---|---|
| Automatic | Applies both the standard audit policies and the AD CS-specific Audit Certification Services subcategory in a single workflow. | Confirm permissions, wait for GPO replication, enable CA auditing categories, and verify. See Automatic configuration. |
| Manual | Monitors only — does not modify any GPO settings. | Complete standard audit policy steps from the respective guide, then add the Audit Certification Services subcategory as described in Configure advanced audit policies. |
⚠️ Important: Regardless of the audit policy method, you must always manually enable the CA auditing categories in the Certificate Authority console (Configure CA auditing categories). ADAudit Plus does not configure CA console settings automatically.
Configure audit policies
Standard Windows audit policy configuration for each host type is covered in the respective auditing guides:
- Domain Controllers — Active Directory Auditing Guide
- Windows Servers — Windows Server Auditing Guide
AD CS auditing requires one additional audit subcategory beyond those standard policies: Audit Certification Services (under Object Access). This is the setting that directs Windows to write AD CS event IDs to the Security log. This section covers only that addition.
Automatic configuration
When you choose automatic configuration in ADAudit Plus, the product applies both the standard audit policies and the AD CS-specific subcategory in a single workflow. No additional manual steps are required for the audit policy itself.
In addition to the standard audit policy settings covered in the respective guide, ADAudit Plus applies the following AD CS-specific setting:
| Setting | Policy name | Event IDs generated |
|---|---|---|
| Audit Certification Services | Audit Certification Services — under Object Access in Advanced Audit Policy Configuration | 4869, 4870, 4873, 4874, 4882, 4883, 4884, 4885, 4886, 4887, 4888, 4889, 4890, 4891, 4892, 4896, 4898, 4899, 4900 |
| Scope | Where to start |
|---|---|
| Domain Controller | Configuration → Data Sources → Domains and Controllers → audit policy workflow |
| Windows member server | Configuration → Data Sources → Member Servers → Audit Policy: Configure |
- Open the relevant ADAudit Plus configuration page for the target host type.
- Choose the option to configure audit policy automatically.
- Allow ADAudit Plus to complete the configuration and wait for Group Policy replication.
- Validate the result as described in Verify audit policies are applied.
Note: Automatic configuration is still GPO-based. If GPO creation, editing, or linking is blocked by your environment, use the manual workflow in Manual configuration overview.
Manual configuration overview
Use manual configuration when:
- Automatic policy application is not available in your environment.
- You need change-controlled GPO edits.
- You want to validate or adjust an existing audit baseline.
Complete the standard audit policy steps in the respective guide for your host type first, then add the Audit Certification Services subcategory in Configure advanced audit policies to the same GPO.
| Server type | Standard audit policy steps | GPO to edit |
|---|---|---|
| AD CS on a Domain Controller | AD Auditing Guide — Configure audit policies | Default Domain Controllers Policy |
| AD CS on a Windows member server | Windows Server Auditing Guide — Configure audit policies | ADAuditPlusMSPolicy |
Tip: If you audit a Domain Controller and a Windows member server CA, configure each GPO separately so the correct settings apply to the correct scope.
Configure advanced audit policies
Use this procedure to enable Audit Certification Services through Advanced Audit Policy Configuration.
- Log in to a computer that has the Group Policy Management Console (GPMC) installed using Domain Admin credentials.
- Open Group Policy Management.
- Based on your setup, right-click Default Domain Controllers Policy or ADAuditPlusMSPolicy, then click Edit.
- Navigate to Computer Configuration → Policies → Windows Settings → Security Settings → Advanced Audit Policy Configuration → Audit Policies.
- Click Object Access.
- In the right pane, right-click Audit Certification Services, then click Properties.
- Select Success and Failure.
- Click OK.
| Setting | Required value |
|---|---|
| Audit subcategory | Audit Certification Services |
| Success | Enabled |
| Failure | Enabled |
Enforce advanced audit policy settings
After you enable advanced audit policies, force Windows to apply the advanced subcategory settings over legacy category settings.
- In Group Policy Management, edit the same GPO used in Configure advanced audit policies.
- Navigate to Computer Configuration → Policies → Windows Settings → Security Settings → Local Policies → Security Options.
- In the right pane, right-click Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings, then click Properties.
- Select Enabled.
- Click OK.
| Setting | Required value |
|---|---|
| Policy | Audit: Force audit policy subcategory settings to override audit policy category settings |
| Value | Enabled |
Recommended audit policy settings for AD CS
Use the following baseline for AD CS auditing.
| Policy type | Path | Setting | Recommended value |
|---|---|---|---|
| Advanced | Advanced Audit Policy Configuration → Audit Policies → Object Access | Audit Certification Services | Success and Failure |
| Advanced | Security Options | Force audit policy subcategory settings to override audit policy category settings | Enabled |
Enable auditing on AD CS servers
Important: ADAudit Plus does not configure CA auditing settings automatically. The steps in this section must be performed manually on each AD CS server, regardless of whether you used automatic or manual audit policy configuration in Configure audit policies. Without completing these steps, AD CS events will not be written to the Security log.
Configure CA auditing categories
After Windows audit policy is enabled, configure the CA so it writes the required categories to the Security log. This step is always performed manually in the Certificate Authority management console on the AD CS server.
- Log in to the AD CS server using Domain Admin credentials.
- Open the Certificate Authority management console.
- Right-click the CA, then click Properties.
- Open the Auditing tab.
- Select the required auditing categories.
- Click OK to save the change.
Enable at least the following categories in the CA console. The table shows which ADAudit Plus reports each category feeds.
| CA auditing category | Why enable it | ADAudit Plus report | Event IDs |
|---|---|---|---|
| Change CA configuration | Tracks operational and configuration changes on the CA. | CA Property Changes | 4885, 4891, 4892 |
| Change CA security settings | Tracks permission and security-related changes on the CA. | CA Property Changes | 4882, 4890 |
| Issue and manage certificate requests | Tracks request receipt, approval, denial, pending status, and modification activity. | Certificate Request Status, Certificate Request Modifications | 4869, 4873, 4874, 4884, 4886, 4887, 4888, 4889, 4896 |
| Revoke certificates and publish CRLs | Tracks certificate revocation activity. | Certificate Request Status | 4870 |
| Store and retrieve archived keys | Tracks sensitive archived key recovery operations. | Certificate Private Key Retrievals | 4883 |
Note: The Certificate Template Changes report (event IDs 4898, 4899, 4900) is enabled separately using the certutil command in Enable certificate template change monitoring, not through the CA console Auditing tab.
Important: Enabling Windows audit policy alone is not enough. If the CA auditing check boxes are not enabled on the AD CS server, the required CA operations will not be written to the Security log.
Enable certificate template change monitoring
To audit changes related to certificate templates issued by Enterprise CAs, enable certificate template load auditing. This step is always performed manually by running the certutil command on the AD CS server.
- Open Command Prompt as an administrator on the AD CS server.
- Run the following command:
certutil -setreg policy\EditFlags +EDITF_AUDITCERTTEMPLATELOAD
- Record the change in your PKI change-control process.
- Proceed to the verification workflow in Verify the configuration to confirm that template-related activity becomes visible in the expected logs and reports.
Verify the configuration
Use the following steps to confirm that AD CS auditing is configured correctly end to end.
Verify CA auditing is enabled
- On the AD CS server, open the Certificate Authority console.
- Right-click the CA, then click Properties.
- Open the Auditing tab.
- Confirm that the required categories are selected.
- Record the enabled categories for your operations baseline.
Use this checklist during verification:
| Verification item | Expected result |
|---|---|
| Change CA configuration | Enabled |
| Change CA security settings | Enabled |
| Issue and manage certificate requests | Enabled |
| Revoke certificates and publish CRLs | Enabled |
| Store and retrieve archived keys | Enabled |
Verify audit policies are applied
- Run Group Policy update on the AD CS server, or wait for normal policy refresh.
- Open an elevated Command Prompt.
- Run the following command:
auditpol /get /subcategory:"Certification Services"
- Confirm that Success and Failure are enabled.
- If the result is not correct, review the GPO used in Configure audit policies.
If you need a broader verification view, run:
auditpol /get /category:*
Verify AD CS events in Event Viewer
- Open Event Viewer on the AD CS server.
- Navigate to Windows Logs → Security.
- Perform a controlled validation action if change control allows it, such as submitting a test certificate request, denying a request in a lab, or publishing a CRL.
- Confirm that the expected event IDs appear in the Security log.
- Note the event timestamps and compare them with ADAudit Plus report timestamps.
Use the following event IDs during verification.
| Verification scenario | Event IDs to look for | Report |
|---|---|---|
| Certificate request received | 4886 | Certificate Request Status |
| Certificate request approved | 4887 | Certificate Request Status |
| Certificate request denied | 4888 | Certificate Request Status |
| Certificate revoked | 4870 | Certificate Request Status |
| Certificate request resubmitted | 4869 | Certificate Request Status |
| Request extension or attribute changed | 4873, 4874 | Certificate Request Modifications |
| Archived key retrieved | 4883 | Certificate Private Key Retrievals |
| CA security permissions changed | 4882 | CA Property Changes |
| CA configuration changed | 4891, 4892 | CA Property Changes |
| Certificate template changed | 4899, 4900 | Certificate Template Changes |
⚠️Important: Perform validation actions only within your change-control and PKI operational process. Do not generate test certificate operations on a production CA without approval.
Verify data in ADAudit Plus reports
- Return to the ADAudit Plus web console.
- Navigate to Server → Server Auditing → AD CS Activity.
- Open AD CS Activity Overview for a summary, or open the specific report matching your validation action.
- Filter by the AD CS server name and the time range of the test.
- Confirm that the server name, user, action, and timestamp match the Security log event.
- If you created an alert profile, confirm that the alert triggered as expected.
Use this result matrix while validating:
| Validation step | Expected result |
|---|---|
| Security log event exists | Event is visible on the AD CS server |
| ADAudit Plus report entry exists | Matching event appears in the report output |
| Timestamp alignment | Timestamps are reasonably aligned after collection latency |
| Actor and server context | User, server, and action details are resolved correctly |
| Alert action | The configured notification is triggered for matching rules |