> 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-certificate-was-issued-with-a-mismatch.md).
# A user certificate was issued with a mismatch
### 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 | Persistence (TA0003), Privilege Escalation (TA0004), Credential Access (TA0006) |
| ATT\&CK Technique | Account Manipulation (T1098), Valid Accounts (T1078), Steal or Forge Authentication Certificates (T1649) |
| Severity | Informational |
### Description
A certificate was issued to a user who was not the requester, this may indicate a certificate manipulation.
### Attacker's Goals
Attackers may try to obtain certificates for privileged accounts or systems they do not normally have access to, to gain elevated access and move laterally within the network.
### Investigative actions
* Verify the activity with the performing user.
* Identify if the requester is a user or system that normally requests certificates on behalf of other entities (e.g., a Mobile Device Management system).
* Search for further indicators of potential compromise, including atypical login behaviors, unauthorized attempts at privilege escalation, or lateral movements within the network attributed to the requester.
* Examine whether the mismatch between the requester and the subject is consistent with known and anticipated practices, or if it represents an unusual deviation.
* Check for possible certificate authentications with the subject user.
### Variations
Suspicious certificate issuance with a mismatch
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004), Credential Access (TA0006) |
| ATT\&CK Technique | Account Manipulation (T1098), Valid Accounts (T1078), Steal or Forge Authentication Certificates (T1649) |
| Severity | Low |
**Description**
A user certificate was issued with a mismatch. This requester doesn't usually ask for a certificates on behalf of another subject. This may indicate a certificate manipulation.
**Attacker's Goals**
Attackers may try to obtain certificates for privileged accounts or systems they do not normally have access to, to gain elevated access and move laterally within the network.
**Investigative actions**
* Verify the activity with the performing user.
* Identify if the requester is a user or system that normally requests certificates on behalf of other entities (e.g., a Mobile Device Management system).
* Search for further indicators of potential compromise, including atypical login behaviors, unauthorized attempts at privilege escalation, or lateral movements within the network attributed to the requester.
* Examine whether the mismatch between the requester and the subject is consistent with known and anticipated practices, or if it represents an unusual deviation.
* Check for possible certificate authentications with the subject user.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-user-certificate-was-issued-with-a-mismatch.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.