Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Notarization
Cyber Security

Notarization

← Back to Glossary
By NHI Mgmt Group Updated November 5, 2026 Domain: Cyber Security

Notarization is Apple’s review and ticketing process for macOS software that is intended to increase trust in executables. It can block known bad code, but it is not a permanent guarantee. If a notarization ticket is revoked or a sample is re-signed, the same malware family may still reappear.

What notarization does in macOS trust decisions

Apple’s notarization process is a trust signal, not a guarantee of safety. It sits between code signing and user execution choices, helping macOS identify software that has at least passed Apple’s review and ticketing workflow, but it does not prove the software will stay benign over time.

For defenders, the key idea is that notarization changes the default trust posture of a macOS executable without eliminating the need for other controls. A notarized binary can still be malicious, especially when attackers abuse a trusted distribution path or when a ticket is later revoked.

Why notarization matters to macOS security

Notarization is important because it raises the cost of simple malware delivery and gives Apple a revocation point. In practice, that can reduce exposure to unsigned or previously flagged code, but it also means the control depends on Apple’s review, ticket status, and the broader macOS execution model rather than on a permanent verdict about the software.

The security value comes from trust signalling, ecosystem filtering, and downstream enforcement in Gatekeeper-related workflows. That makes notarization part of a layered macOS security posture, especially where organisations are trying to limit untrusted software execution on managed endpoints. For a broader enterprise view of those controls, see the macOS Security Guide for Enterprises.

How notarization fails in the real world

Notarization can fail as a security boundary when attackers obtain a notarization ticket for code that later changes behaviour, when a family is re-signed and redistributed, or when users treat the presence of a ticket as proof that a file is safe. It is also weaker against campaigns that combine legitimate macOS trust signals with social engineering or post-delivery tampering.

Because revocation can occur after initial approval, the most important operational question is not whether software was notarized once, but whether the organisation can still trust the current sample in circulation. That is why notarization should be treated as a control point in a larger chain of provenance, reputation, and endpoint enforcement.

What practitioners should verify and monitor

Practitioners should verify notarization status as part of software intake, but they should pair that check with inventory, vendor provenance, and endpoint visibility. If a sample is re-signed, repackaged, or redistributed under a different delivery path, the original ticket may no longer be a reliable indicator of safety.

Monitoring should focus on whether a trusted sample has been revoked, whether the same family is resurfacing under fresh signatures, and whether managed devices are actually enforcing Apple platform controls consistently. In other words, notarization is only useful when it is embedded in a process that can notice drift, revocation, and reappearance of the same malware lineage.

How notarization fits with other macOS controls

Notarization works best when it complements stronger endpoint and configuration controls rather than replacing them. Gatekeeper, XProtect, System Integrity Protection, TCC restrictions, MDM policy, and application allowlisting all help reduce the chance that a notarized sample becomes an operational foothold.

That layered approach matters because notarization is a review mechanism with lifecycle limits, not a standing entitlement to run. If Apple later revokes a ticket, or if a sample is modified and reintroduced, the rest of the macOS control stack determines how quickly the threat is blocked, detected, or contained.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5SI-3 — Malicious Code ProtectionNotarization supports malware screening and revocation workflows that reduce malicious code exposure.
CM-7 — Least FunctionalityNotarization works alongside execution restriction to limit what software can run on endpoints.
SI-7 — Software, Firmware, and Information IntegrityTicket revocation and re-signing concerns map to integrity verification for software trust.
Recommendation — Use SI-3 to block, scan, and quarantine untrusted macOS executables before execution. Apply CM-7 to restrict execution to approved software sources and necessary applications. Use SI-7 to verify software integrity and detect tampering or repackaging after approval.
CIS Controls v8CIS-2 — Inventory and Control of Software AssetsNotarization checks are only useful when tied to knowing which software is present and where.
CIS-10 — Malware DefensesNotarization is a malware-exposure control that complements endpoint malware prevention and detection.
Recommendation — Maintain software inventory so you can confirm which macOS binaries were notarized and deployed. Use malware defenses to detect, block, and investigate notarized samples that later turn malicious.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org