Live Active security incident? Get immediate response
MITRE ATT&CK® Detection Strategy

DET0288: Detect Gatekeeper Bypass via Quarantine Flag and Trust Control Manipulation

DET0288 is a detection strategy for identifying attempts to bypass Apple Gatekeeper by manipulating quarantine and trust-related controls. For leaders, the...

EnterpriseDET0288Detection StrategyObject v1.0 Modified
Glexia's Take

Analyst context for executives and security teams

Analyst confidence Medium

DET0288 is a detection strategy for identifying attempts to bypass Apple Gatekeeper by manipulating quarantine and trust-related controls. For leaders, the decision value is not the detection strategy text itself—MITRE provides no official description or detection logic here—but the relationship to Gatekeeper Bypass (T1553.001), a macOS defense-impairment behavior that can allow untrusted applications to run with fewer user-facing warnings or policy checks.

Executive priority

Prioritize this as a macOS endpoint trust-control validation item. Ask whether the organization can prove, with evidence, that it monitors changes to quarantine attributes and Gatekeeper-related trust decisions on managed macOS systems. This matters for incident readiness, audit evidence, and resilience because bypassing local execution safeguards can reduce the effectiveness of user prompts, code-signing expectations, notarization checks, and endpoint policy assumptions.

Technical view

SOC and detection engineering teams should treat DET0288 as a prompt to validate coverage for the related ATT&CK technique T1553.001 Gatekeeper Bypass under defense impairment on macOS. Because the detection strategy object has no official detection content, teams should derive local analytic requirements from the related technique context: monitor for suspicious modification of file quarantine attributes, trust-control state changes, and execution of applications that should have triggered Gatekeeper review. IR teams should preserve file metadata, endpoint security logs, process execution history, and policy state around first-run application execution.

Likely telemetry

  • macOS endpoint security or EDR events
  • File metadata and extended attribute change evidence, especially quarantine-related attributes
  • Process execution telemetry for newly downloaded or first-run applications
  • Gatekeeper, code-signing, notarization, or security policy decision logs where available
  • MDM or endpoint configuration state for Gatekeeper and related macOS security controls

Detection direction

  • Validate that telemetry can show both the trust-control change and the later execution event; either alone may be insufficient for confident triage.
  • Tune analytics around unexpected quarantine attribute removal or trust-state manipulation followed by application launch.
  • Compare detections against managed software deployment workflows to reduce false positives from legitimate administrative packaging, migration, or developer activity.
  • Use relationship context from T1553.001 to scope detection to macOS defense-impairment behavior, since the DET0288 object itself does not list platforms or tactics.
  • Confirm whether managed detection workflows collect the macOS-specific evidence needed before claiming coverage.

Mitigation priorities

  • Maintain enforced macOS security baselines for Gatekeeper, code-signing, notarization, and related policy controls where applicable.
  • Use MDM or endpoint management to validate configuration drift and unauthorized changes to trust settings.
  • Restrict unnecessary local administrative capability where it could allow security-control manipulation.
  • Ensure EDR and logging policies retain file attribute, process execution, and security policy evidence needed for investigation.
  • Document detection and response evidence for compliance readiness and incident response playbooks.
Analyst notes and limits

This take is based on the detection strategy metadata and its ATT&CK relationship to T1553.001 Gatekeeper Bypass. The supplied DET0288 object does not include official description, detection text, tactics, or platforms; the macOS and defense-impairment framing comes from the related technique context.

No official DET0288 detection logic, analytic pseudocode, data sources, mitigations, or procedure examples were supplied. Local macOS configuration, EDR visibility, MDM controls, and software deployment practices are required to determine real coverage and false-positive behavior.

Official MITRE ATT&CK definition

Detect Gatekeeper Bypass via Quarantine Flag and Trust Control Manipulation

No official description is available in the imported ATT&CK source object.

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

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.

ATT&CK relationship table

Techniques used

This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.

1 rows
Domain ID Name Relationship / procedure
Enterprise T1553.001 Gatekeeper Bypass Sub-technique This object detects Gatekeeper Bypass.
Relationship explorer

All related ATT&CK context

Change history

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 .

ATT&CK release
19.1
Object version
1.0
Created
Modified
Raw hash
e8c51e335ac8f865...
Imported snapshots across ATT&CK releases (1)
Release Bundle imported Object version Modified Status Raw hash
19.1 1.0 Current bundle e8c51e335ac8…
Raw source

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.

Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    mitre-attack DET0288
    Open source URL
Source and licensing

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.