SECURITY MODEL — CURRENT

These are current product boundaries, expressed in terms that can be inspected in the architecture and verified in the running system.

The origin is hardware you control. Applications are published through an outbound edge path, without exposing an inbound app port or publishing the Mac as the application origin in DNS.

FIG. 01 — THE PATH OF ONE AUTHORIZED REQUEST

and the fate of everything else

Animated cross-section of the enforcement stack. An authorized request descends six layers — public edge TLS, access policy, signed envelope, the outbound-only OriginLink tunnel, runtime-agent verification, and the isolated capsule — collecting a stamp at each layer. An unauthorized request is dropped at the access-policy layer and logged. A probe aimed directly at the origin finds no listening port. The traffic is simulated; the order is the production order.

FIG. 01 · six enforcement layers between the public internet and the app on your Mac. Simulated traffic — the order is the production order.
  1. LAW 01

    The Mac does not open an inbound application port, and its address is not published as the application origin in DNS.

    enforced by: outbound-only application publishing through OriginLink
  2. LAW 02

    The Mac initiates the encrypted connection that carries authorized application traffic.

    enforced by: the signed OriginLink gateway
  3. LAW 03

    The sandboxed Mac app and CLI never receive Docker socket or Keychain access.

    enforced by: signed typed XPC; the runtime agent is the sole local broker
  4. LAW 04

    Source is sealed once, then the immutable image is built and inspected before application or database resources are created.

    enforced by: one deployment plan and durable prepared-artifact evidence
  5. LAW 05

    Every public hostname maps to an authorized route scoped to the application, device, and workspace.

    enforced by: signed route bindings rather than arbitrary network targets
  6. LAW 06

    Forwarded requests use signed envelopes with freshness and replay protection before reaching the application path.

    enforced by: current signed request-envelope verification
  7. LAW 07

    Managed applications run non-root, read-only, capability-free, resource-capped, and isolated from the host and sibling apps.

    enforced by: Docker runtime policy, network boundaries, and per-app resources
  8. LAW 08

    Secrets are scoped per application, stored through Keychain-backed state, and kept out of image builds and diagnostics.

    enforced by: runtime-only delivery plus redaction at every output boundary
  9. LAW 09

    Device identity uses a nonextractable P-256 key held by the login Keychain, with bounded authorization sessions.

    enforced by: device-bound signing through macOS security services
  10. LAW 10

    Privacy is decided before traffic reaches the application: private, people and teams, password, workspace, or public.

    enforced by: edge access policy and signed application identity

one authority boundary: the signed runtime on your Mac.

Get the Mac betaBack to the site