> 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/scripting-engine-connected-to-a-rare-external-host.md).

# Scripting engine connected to a rare external host

### 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        | EDR Windows C2 Analytics                                                      |
| ATT\&CK Tactic       | Command and Control (TA0011), Execution (TA0002)                              |
| ATT\&CK Technique    | Application Layer Protocol (T1071), Command and Scripting Interpreter (T1059) |
| Severity             | Low                                                                           |

### Description

Scripts connecting to external IP addresses may be sanctioned IT scripts. However, when those external IP addresses are only receiving connections from a few specific endpoints in the organization, these scripts may be an indicator of more suspicious activity. Security testers and adversaries use offensive frameworks that employ forms of scripting which result in this type of network activity.

### Attacker's Goals

Connect to the attacker's Command and Control server.

### Investigative actions

* Check the external address the process connects to.
* Fetch and investigate the executed script.

### Variations

<details>

<summary>Scripting engine failed to connect to a rare external host</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011), Execution (TA0002)                              |
| ATT\&CK Technique | Application Layer Protocol (T1071), Command and Scripting Interpreter (T1059) |
| Severity          | Informational                                                                 |

**Description**

Scripts connecting to external IP addresses may be sanctioned IT scripts. However, when those external IP addresses are only receiving connections from a few specific endpoints in the organization, these scripts may be an indicator of more suspicious activity. Security testers and adversaries use offensive frameworks that employ forms of scripting which result in this type of network activity.

**Attacker's Goals**

Connect to the attacker's Command and Control server.

**Investigative actions**

* Check the external address the process connects to.
* Fetch and investigate the executed script.

</details>

<details>

<summary>Scripting engine with a modified image name connected to a rare external host</summary>

**Synopsis**

| Field             | Value                                                                                               |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011), Execution (TA0002), Stealth (TA0005)                                  |
| ATT\&CK Technique | Application Layer Protocol (T1071), Command and Scripting Interpreter (T1059), Masquerading (T1036) |
| Severity          | Low                                                                                                 |

**Description**

Scripts connecting to external IP addresses may be sanctioned IT scripts. However, when those external IP addresses are only receiving connections from a few specific endpoints in the organization, these scripts may be an indicator of more suspicious activity. Security testers and adversaries use offensive frameworks that employ forms of scripting which result in this type of network activity.

**Attacker's Goals**

Connect to the attacker's Command and Control server.

**Investigative actions**

* Check the external address the process connects to.
* Fetch and investigate the executed script.

</details>

<details>

<summary>Windows LOLBIN scripting engine connected to a rare external host</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011), Execution (TA0002)                              |
| ATT\&CK Technique | Application Layer Protocol (T1071), Command and Scripting Interpreter (T1059) |
| Severity          | Medium                                                                        |

**Description**

Scripts connecting to external IP addresses may be sanctioned IT scripts. However, when those external IP addresses are only receiving connections from a few specific endpoints in the organization, these scripts may be an indicator of more suspicious activity. Security testers and adversaries use offensive frameworks that employ forms of scripting which result in this type of network activity.

**Attacker's Goals**

Connect to the attacker's Command and Control server.

**Investigative actions**

* Check the external address the process connects to.
* Fetch and investigate the executed script.

</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/scripting-engine-connected-to-a-rare-external-host.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.
