> 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/uncommon-applescript-with-a-potential-discovery-command-was-executed-via-the-command-line.md).

# Uncommon AppleScript with a potential discovery command was executed via the command line

### 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        | AppleScript Analytics, EDR Discovery Analytics                                                   |
| ATT\&CK Tactic       | Execution (TA0002), Discovery (TA0007)                                                           |
| ATT\&CK Technique    | Command and Scripting Interpreter: AppleScript (T1059.002), System Information Discovery (T1082) |
| Severity             | Low                                                                                              |

### Description

The AppleScript interpreter process was executed via the command line containing a potential system information discovery command.

### Attacker's Goals

Discover system info to facilitate escalation, lateral movement, and defense evasion.

### Investigative actions

* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Verify whether the system information being gathered could facilitate further attack stages.

### Variations

<details>

<summary>Uncommon AppleScript with a potential discovery command was executed via the command line querying virtual environment information</summary>

**Synopsis**

| Field             | Value                                                                                                                                    |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Discovery (TA0007), Stealth (TA0005)                                                                                 |
| ATT\&CK Technique | Command and Scripting Interpreter: AppleScript (T1059.002), System Information Discovery (T1082), Virtualization/Sandbox Evasion (T1497) |
| Severity          | High                                                                                                                                     |

**Description**

The AppleScript interpreter process was executed via the command line containing a potential system information discovery command.

**Attacker's Goals**

Discover system info to facilitate escalation, lateral movement, and defense evasion.

**Investigative actions**

* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Verify whether the system information being gathered could facilitate further attack stages.

</details>

<details>

<summary>Uncommon AppleScript with a potential discovery command was executed via the command line, querying hardware or software information</summary>

**Synopsis**

| Field             | Value                                                                                            |
| ----------------- | ------------------------------------------------------------------------------------------------ |
| ATT\&CK Tactic    | Execution (TA0002), Discovery (TA0007)                                                           |
| ATT\&CK Technique | Command and Scripting Interpreter: AppleScript (T1059.002), System Information Discovery (T1082) |
| Severity          | Medium                                                                                           |

**Description**

The AppleScript interpreter process was executed via the command line containing a potential system information discovery command.

**Attacker's Goals**

Discover system info to facilitate escalation, lateral movement, and defense evasion.

**Investigative actions**

* Analyze the command line and determine whether it performs any malicious or suspicious actions.
* Check the events generated by the process or its children for potential malicious behavior.
* Verify whether the system information being gathered could facilitate further attack stages.

</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/uncommon-applescript-with-a-potential-discovery-command-was-executed-via-the-command-line.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.
