AN1200: Analytic 1200
Monitors Keychain database access and suspicious invocations of security and osascript utilities. Correlates process execution with attempts to dump or unlock Keychain data.
Analyst context for executives and security teams
AN1200 is a macOS-focused detection analytic for spotting suspicious access to Keychain data, especially when process activity involves the security or osascript utilities and appears tied to attempts to dump or unlock Keychain contents. For leaders, this matters because Keychain often protects credentials and secrets that can affect identity security, incident scope, and business continuity if exposed.
Executive priority
Prioritize this analytic where macOS systems are used by privileged users, administrators, developers, executives, or teams with access to sensitive business systems. The decision value is to confirm whether the organization can produce credible evidence of Keychain access, related process execution, and suspicious utility use during an incident. This supports faster credential-risk decisions, containment planning, and audit-ready proof that macOS credential stores are monitored.
Technical view
SOC and detection teams should validate telemetry for macOS process execution and Keychain database access, then correlate invocations of security and osascript with attempts to dump or unlock Keychain data. Because ATT&CK provides no separate detection logic for this analytic and no relationship context, teams should treat the official description as the detection objective rather than a complete rule. Tuning should account for legitimate administrative, user-support, scripting, and automation activity involving these utilities.
Likely telemetry
- macOS process execution events
- Command-line arguments for security and osascript
- Keychain database access events where available
- Parent-child process relationships involving shell, scripting, or administrative tools
- User, host, and timestamp context for correlation
Detection direction
- Confirm that macOS endpoint telemetry captures process names, command-line arguments, parent processes, users, and timestamps for security and osascript activity.
- Validate whether Keychain database access or unlock/dump attempts are visible in available endpoint, operating system, or security tooling.
- Correlate utility execution with Keychain access rather than alerting on utility use alone, because both security and osascript can have legitimate administrative or automation uses.
- Baseline known administrative scripts, helpdesk workflows, and user automation to reduce false positives.
- Review blind spots on unmanaged macOS devices, systems without command-line capture, and telemetry sources that do not expose Keychain access details.
Mitigation priorities
- Ensure macOS systems that handle sensitive access are covered by endpoint monitoring capable of process and command-line collection.
- Restrict and review administrative automation that invokes security or osascript where business operations allow.
- Use least-privilege practices for macOS users and administrators to reduce the value of exposed Keychain material.
- Include Keychain exposure checks in incident response playbooks for macOS credential-risk investigations.
- Maintain evidence retention sufficient to reconstruct user, process, and Keychain-access timelines during an investigation.
Analyst notes and limits
This object is a detection analytic, not a technique, and the supplied ATT&CK fields list macOS as the only platform. No tactics, related techniques, groups, software, campaigns, or mitigations were supplied. The take therefore focuses on validation of the stated analytic objective: monitoring Keychain database access and suspicious invocations of security and osascript utilities.
Official detection content is not provided, and no relationships are supplied. Local environment knowledge is required to define exact alert thresholds, distinguish legitimate automation from suspicious behavior, and determine whether Keychain access events are actually available in deployed telemetry.
Analytic 1200
Monitors Keychain database access and suspicious invocations of security and osascript utilities. Correlates process execution with attempts to dump or unlock Keychain data.
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
All related ATT&CK context
No relationships are available in the current normalized data for this object.
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates .
Imported snapshots across ATT&CK releases (1)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.1 | 1.0 | Current bundle | a4aff68f0b7a… |
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
-
[1]
mitre-attack AN1200Open source URL
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.