> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-user-modified-the-ca-audit-policy.md).
# A user modified the CA audit policy
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Windows Event Collector OR XDR Agent with eXtended Threat Hunting (XTH)
|
| Detection Modules | Identity Analytics |
| Detector Tags | Active Directory Certificate Services Analytics |
| ATT\&CK Tactic | Defense Evasion (TA0005) |
| ATT\&CK Technique | Impair Defenses: Disable Windows Event Logging (T1562.002) |
| Severity | Low |
### Description
A user modified the CA audit policy.
* This may indicate that an attacker is attempting to cover their tracks before an AD CS attack.
### Attacker's Goals
An attacker is attempting to cover their tracks before an AD CS attack.
### Investigative actions
* Check the user account modifying the CA audit policy and verify its activity.
* Review AD CS logs to identify any unauthorized certificate issuances, modifications, or template changes.
* Examine recent activity from the user account, including logon patterns and privilege changes.
* Continue monitoring the account for any subsequent actions that may indicate suspicious behavior.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-user-modified-the-ca-audit-policy.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.