> 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/unusual-cim-repository-file-access.md).

# Unusual CIM repository file access

### 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 with eXtended Threat Hunting (XTH)                 |
| Detector Tags        | Microsoft SCCM Analytics                                     |
| ATT\&CK Tactic       | Credential Access (TA0006)                                   |
| ATT\&CK Technique    | Unsecured Credentials (T1552), OS Credential Dumping (T1003) |
| Severity             | Low                                                          |

### Description

An uncommon process accessed the CIM repository file, potentially to retrieve stored NNA credentials for unauthorized use.

### Attacker's Goals

* Attackers can retrieve plaintext domain credentials, which may be used for proxying tools into the environment over command and control (C2).
* If the credentials are overprivileged, this technique may enable lateral movement to other clients or sensitive systems.
* Determine whether this was a legitimate action.

### Investigative actions

* Follow process, user, and host activities.
* Investigate if the retrieved credentials match any known accounts or if there is any abnormal access to distribution points or other critical resources.
* Verify the presence of unauthorized tools or processes like SharpDPAPI or SharpSCCM that could have been used for credential extraction or decryption.
* Review relevant system logs (event logs, SCCM logs, etc.) for any signs of unusual activity or access patterns related to the NAA or other credentials.

### Variations

<details>

<summary>Suspicious CIM repository file access</summary>

**Synopsis**

| Field             | Value                                                        |
| ----------------- | ------------------------------------------------------------ |
| ATT\&CK Tactic    | Credential Access (TA0006)                                   |
| ATT\&CK Technique | Unsecured Credentials (T1552), OS Credential Dumping (T1003) |
| Severity          | Medium                                                       |

**Description**

An unusual process with suspicious characteristics accessed the CIM repository file, causing this attempt to be flagged as suspicious.

**Attacker's Goals**

* Attackers can retrieve plaintext domain credentials, which may be used for proxying tools into the environment over command and control (C2).
* If the credentials are overprivileged, this technique may enable lateral movement to other clients or sensitive systems.
* Determine whether this was a legitimate action.

**Investigative actions**

* Follow process, user, and host activities.
* Investigate if the retrieved credentials match any known accounts or if there is any abnormal access to distribution points or other critical resources.
* Verify the presence of unauthorized tools or processes like SharpDPAPI or SharpSCCM that could have been used for credential extraction or decryption.
* Review relevant system logs (event logs, SCCM logs, etc.) for any signs of unusual activity or access patterns related to the NAA or other credentials.

</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 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/unusual-cim-repository-file-access.md?ask=<question>&goal=<endgoal>
```

`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.