> 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/suspicious-certutil-ad-cs-contact.md).

# Suspicious Certutil AD CS contact

### Synopsis

| Field                | Value                                                                                |
| -------------------- | ------------------------------------------------------------------------------------ |
| Activation Period    | 14 Days                                                                              |
| Training Period      | 30 Days                                                                              |
| Test Period          | N/A (single event)                                                                   |
| Deduplication Period | 1 Day                                                                                |
| Required Data        | XDR Agent                                                                            |
| Detector Tags        | Active Directory Certificate Services Analytics                                      |
| ATT\&CK Tactic       | Discovery (TA0007), Credential Access (TA0006)                                       |
| ATT\&CK Technique    | System Service Discovery (T1007), Steal or Forge Authentication Certificates (T1649) |
| Severity             | Low                                                                                  |

### Description

A suspicious occurrence of Certutil attempted to contact the AD CS Request Interface.

### Attacker's Goals

* An attacker might look for AD CS servers, certificate templates or request certificates.
* With the wrong setting or loose vulnerable templates or enabled enrollment, the attacker will be able to authenticate as users on the network.

### Investigative actions

* Look at further action done by the user.
* Investigate whether other non-standard operations were done regarding the AD CS.

### Variations

<details>

<summary>Suspicious Certutil AD CS Admin Interface contact</summary>

**Synopsis**

| Field             | Value                                                                                |
| ----------------- | ------------------------------------------------------------------------------------ |
| ATT\&CK Tactic    | Discovery (TA0007), Credential Access (TA0006)                                       |
| ATT\&CK Technique | System Service Discovery (T1007), Steal or Forge Authentication Certificates (T1649) |
| Severity          | Medium                                                                               |

**Description**

A suspicious occurrence of Certutil attempted to contact the AD CS Admin Interface.

**Attacker's Goals**

* An attacker might look for AD CS servers, certificate templates or request certificates.
* With the wrong setting or loose vulnerable templates or enabled enrollment, the attacker will be able to authenticate as users on the network.

**Investigative actions**

* Look at further action done by the user.
* Investigate whether other non-standard operations were done regarding the AD CS.

</details>


---

# 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/suspicious-certutil-ad-cs-contact.md?ask=<question>&goal=<user_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.
