The FireAI Security Blog

By FireAI Security & Research Team · Published

Gatekeeper, XProtect and Notarization: What macOS Actually Catches — and Misses

Gatekeeper, XProtect and Notarization: What macOS Actually Catches — and Misses

It is worth knowing what macOS is already doing for you, in plain terms, straight from Apple’s own security documentation — and just as importantly, what Apple itself says these systems are not designed to do.

The three layers

  • Gatekeeper checks, before an app first opens, whether it is signed by a known developer and, for apps from outside the App Store, whether Apple has notarized it.
  • Notarization means Apple scanned the app for known malware before it shipped, and can later revoke that approval — Apple checks for revocations in the background far more often than regular software updates run.
  • XProtect uses signature-based rules, updated independently of full macOS updates, to detect and remove known malware when an app launches, changes, or a new signature arrives — plus a behavioral-analysis engine aimed at malware it has not seen before.

What Apple itself says these do not do

Apple’s own documentation describes this as layered defense, not a guarantee: it explicitly notes that XProtect’s signature-based rules can still be extended to catch variants, implying — and security researchers have long confirmed — that a genuinely new or modified threat can operate for a period before a signature exists for it.

This is not a criticism of Apple’s approach; every major operating system faces the same trade-off between blocking known threats immediately and waiting to confirm a new one is genuinely malicious before flagging it. It is simply a reason not to treat "my Mac has Gatekeeper and XProtect" as the end of the conversation about what is safe to run.

None of these three systems inspect what a legitimate, correctly signed, already-approved app does after it opens — including which servers it contacts, in which country, and how often, or whether that behavior changes after a routine update replaces the code entirely. That is a different, complementary job: watching behavior at the network level, continuously, rather than checking a file once against a list before it ever runs.

How FireAI and HisnLabs fit in

Apple’s own documentation is explicit that these layers are not complete protection — which is exactly the gap FireAI is built to sit in: not replacing Gatekeeper and XProtect, but watching what actually leaves your Mac after they have done their part.

FireAI is HisnLabs’ own product: an on-device AI firewall for Mac. It shows every connection your apps make, in plain language, and lets you decide what leaves your Mac — its AI runs locally, so your traffic is never sent to us or anyone else. HisnLabs’ security research team is the group that keeps that decision-making accurate: cataloguing which domains are ordinary telemetry versus a real product, tracking the country and network behind a connection, and training the on-device model (its Autopilot feature) on real traffic patterns, all without any of it leaving your Mac.

You can read the technical decisions behind it, or try FireAI for 17 days, at FireAI, by HisnLabs.

Sources