AN1244: Analytic 1244
Detect user-initiated kextload commands or modifications to /Library/Extensions. Correlate with changes to KextPolicy database or unauthorized developer signing identities. Alert on attempts to disable SIP or load legacy extensions from unsigned sources.
Analyst context for executives and security teams
This analytic is about watching for macOS kernel extension activity, especially user-initiated kextload commands, changes under /Library/Extensions, related KextPolicy database changes, unauthorized developer signing identities, attempts to disable System Integrity Protection, or loading legacy unsigned extensions. For leaders, the value is not just detecting a command; it is validating whether the organization can see and control high-risk macOS extension behavior that may affect endpoint integrity and incident response confidence.
Executive priority
Prioritize this where macOS endpoints are business-critical, privileged users rely on them, or compliance evidence requires proof of endpoint hardening and monitoring. The key leadership question is whether security teams can distinguish approved macOS extension management from unauthorized or policy-weakening changes. This supports resilience by reducing blind spots around endpoint integrity, change control, and investigation readiness on macOS systems.
Technical view
SOC and detection teams should validate visibility for macOS process execution involving kextload, file-system changes to /Library/Extensions, changes to the KextPolicy database, developer signing identity context, attempts to disable SIP, and attempts to load legacy or unsigned extensions. Because no ATT&CK tactic or relationship context is supplied, this should be treated as a focused macOS detection analytic rather than mapped to a broader intrusion sequence without local evidence.
Likely telemetry
- macOS process execution telemetry for user-initiated kextload commands
- File creation, modification, and permission-change telemetry for /Library/Extensions
- KextPolicy database change evidence
- Code-signing or developer identity metadata for kernel extensions
- System Integrity Protection status or configuration-change telemetry
Detection direction
- Confirm that macOS telemetry captures both command execution and file/database changes; relying on only one source can miss the full behavior described by the analytic.
- Tune allowlists for approved enterprise software, device drivers, and administrative maintenance to reduce false positives while preserving alerts for unauthorized signing identities or unsigned legacy extensions.
- Correlate extension load attempts with SIP status changes and KextPolicy modifications to raise confidence and support triage.
- Validate whether standard endpoint logging actually records the required macOS-specific artifacts; this analytic depends on platform-specific visibility.
- Do not infer adversary activity from kextload alone; require context such as unauthorized identity, unexpected path changes, unsigned source, or policy weakening.
Mitigation priorities
- Maintain an approved inventory of kernel extensions, developer identities, and legitimate administrative workflows on macOS.
- Restrict who can perform privileged extension-management actions and ensure administrative activity is attributable to a user or management system.
- Harden macOS configuration around SIP and extension policy where business operations allow.
- Use change-control evidence for /Library/Extensions and KextPolicy-related changes so SOC and IR teams can quickly separate expected administration from suspicious activity.
- Periodically test detection coverage on representative macOS builds to confirm telemetry collection, alert routing, and triage procedures.
Analyst notes and limits
This is a detection analytic object, not a technique description. The official content is specific to macOS and focuses on kextload, /Library/Extensions, KextPolicy, signing identities, SIP, and unsigned legacy extensions. There are no supplied ATT&CK tactics, relationships, aliases, labels, or separate official detection text, so the take is limited to defensive validation and monitoring direction supported by the description.
No relationship context, tactics, or official detection implementation were provided. Local baselines, approved software lists, endpoint logging configuration, and macOS fleet composition are required to determine priority, false-positive rates, and actual coverage.
Analytic 1244
Detect user-initiated kextload commands or modifications to /Library/Extensions. Correlate with changes to KextPolicy database or unauthorized developer signing identities. Alert on attempts to disable SIP or load legacy extensions from unsigned sources.
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 | f4f73007f0f8… |
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 AN1244Open 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.