T1059.002 AppleScript

Unter-TechnikEnterprise

Adversaries may abuse AppleScript for execution. AppleScript is a macOS scripting language designed to control applications and parts of the OS via inter-application messages called AppleEvents. These AppleEvent messages can be sent independently or easily scripted with AppleScript. These events can locate open windows, send keystrokes, and interact with almost any open application locally or remotely. Scripts can be run from the command-line via <code>osascript /path/to/script</code> or <code>osascript -e "script here"</code>. Aside from the command line, scripts can be executed in numerous ways including Mail rules, Calendar.app alarms, and Automator workflows. AppleScripts can also be executed as plain text shell scripts by adding <code>#!/usr/bin/osascript</code> to the start of the script file. AppleScripts do not need to call <code>osascript</code> to execute. However, they may be executed from within mach-O binaries by using the macOS Native APIs <code>NSAppleScript</code> or <code>OSAScript</code>, both of which execute code independent of the <code>/usr/bin/osascript</code> command line utility. Adversaries may abuse AppleScript to execute various behaviors, such as interacting with an open SSH connection, moving to remote machines, and even presenting users with fake dialog boxes. These events cannot start applications remotely (they can start them locally), but they can interact with applications if they're already running remotely. On macOS 10.10 Yosemite and higher, AppleScript has the ability to execute Native APIs, which otherwise would require compilation and execution in a mach-O binary file format. Since this is a scripting language, it can be used to launch more common techniques as well such as a reverse shell via Python.

01

Plattformen

Plattformen, für die dies gilt.

macOS
02

Taktiken

ATT&CK-Taktiken, denen diese Technik dient.

03

Unter-Technik von

Die übergeordnete Entität.

04

Gegenmaßnahmen

ATT&CK-Gegenmaßnahmen, die dies verringern.

05

Erkannt durch (1)

Datenkomponenten, die dies erkennen.

06

NIST CSF 2.0 — Relevanzbereiche (Protect / Detect)

NIST-CSF-2.0-Bereiche mit dem größten Bezug (belegbasiert).

Abgeleitet aus MITRE CTID (Apache-2.0) und dem NIST-800-53-↔-CSF-Crosswalk (gemeinfrei). Eine indikative Relevanz entlang der Protect-/Detect-Achse — keine Compliance-Bewertung und keine Abdeckungsaussage.

08

Gruppen (1)

Zugehörige Bedrohungsgruppen.

09

Software (6)

Zugehörige Malware und Tools.

10

Erkannt durch (Sigma) (9)

Zugehörige Sigma-Erkennungsregeln.

11

Quelle

Wo diese Definition veröffentlicht ist.