> 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-remote-service-was-created-via-rpc-over-smb.md).

# A remote service was created via RPC over SMB

### 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        | Impacket Analytics                                                                                    |
| ATT\&CK Tactic       | Lateral Movement (TA0008), Execution (TA0002)                                                         |
| ATT\&CK Technique    | Remote Services: SMB/Windows Admin Shares (T1021.002), System Services: Service Execution (T1569.002) |
| Severity             | Low                                                                                                   |

### Description

A remote service was created via RPC over SMB.

### Attacker's Goals

Process creation on a remote host.

### Investigative actions

Check whether the new process is benign and that the new process is not doing suspicious activity.

### Variations

<details>

<summary>A remote service with an uncommon name was created via RPC over SMB</summary>

**Synopsis**

| Field             | Value                                                                                                 |
| ----------------- | ----------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Lateral Movement (TA0008), Execution (TA0002)                                                         |
| ATT\&CK Technique | Remote Services: SMB/Windows Admin Shares (T1021.002), System Services: Service Execution (T1569.002) |
| Severity          | Medium                                                                                                |

**Description**

A remote service was created via RPC over SMB.

**Attacker's Goals**

Process creation on a remote host.

**Investigative actions**

Check whether the new process is benign and that the new process is not doing suspicious activity.

</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/a-remote-service-was-created-via-rpc-over-smb.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.
