Docs · Getting started & concepts

Security

Private keys stay non-exportable and software-protected in Key Vault. The Mac holds public certs and device credentials only. Liminal Keys is not a qualified trust service provider (no QTSP / qualified electronic signature or seal services).

Private keys remain in cloud custody

Key Vault and database access stay behind Liminal. Console and Liminal Keys for Mac never receive private key bytes.

Console overview with cloud custody posture

Custody

Signing private keys are held as non-exportable keys in Key Vault and every signature is made in cloud custody. The product path does not export private keys to administrators, the Console UI, or Liminal Keys for Mac as downloadable key material.

  • Protection level (today): keys are software-protected and non-exportable in Key Vault. Hardware security module (HSM) custody is on the roadmap and is not available today.
  • Generated in Console (CSR): the key is created inside Key Vault and never leaves it.
  • Imported PKCS#12: the key passes once through the Liminal API, in memory, on its way into Key Vault. After that it is non-exportable.

What the Mac holds

  • Public certificate(s) for virtual identities
  • Device credential from enrollment (protect like a password)
  • Operational state for the Mac signing app (no private key bytes)

What Console holds

  • Tenant and identity metadata
  • Policy configuration (rules, confirmation flags, validity windows)
  • Device enrollment state
  • Sign audit and signing approvals with DigestHashHex — the 64-character uppercase SHA-256 hash of the signed digest — plus outcome and identifiers. Console shows the first 16 hex characters with copy for the full value; LK Approvals shows a truncated hash. Not stored: raw 32-byte digest bytes, CMS signatures, private key material, or full document bytes.

Electronic signatures and timestamps

Liminal Keys helps you create electronic signatures with your own certificate (for example Apple code-signing identities you import or complete via CSR). We do not issue publicly trusted TLS or document certificates except short-lived self-signed testing leaves labelled as untrusted by PDF readers and mail clients. Signatures are not presented as handwriting-equivalent, admissibility-guaranteed, or eIDAS-qualified.

Optional RFC 3161 document timestamps (for example via the agents MCP passthrough when configured) use a third-party time-stamping authority. Timestamping is off by default. When enabled, the default free TSA is FreeTSA — a non-qualified service with no presumption of legal time accuracy.

AI agent approval

Workspace AI agents sign through the same policy engine as Macs and CI. Policy rules can require Require approval before an agent sign proceeds; approvers act in the LK Approvals web app (optional web push). Pending approvals show the request label, optional preview images, and a truncated DigestHashHex (the server stores the full 64-character hash). Auto-sign and deny remain available. Agents never receive private key material.

Authorization model

Each sign is authorized only by applied, enabled policy rules for that tenant. A match requires identity, subject (user and/or group and/or device), operation (sign), and optional validity window. Missing context or no matching rule refuses the sign. On-Mac confirmation prompts are coming soon; currently, rules requiring confirmation deny matching signs.

Transport and identity

Production API and Console are served over HTTPS on liminalkeys.com hostnames. Console authentication uses Microsoft work or school accounts, Google, and Apple via Entra External ID for social sign-in. GitHub is not a Console IdP. Device enrollment uses short-lived codes issued by an authorized Console user.

Enterprise options

Available on request — use the same contact channel as product support.

HSM support

Hardware security module (HSM) support is on the roadmap. Contact us for more information or custom HSM integrations.

Contact us

On-premises instance

Self-hosted / on-premises deployment of Liminal Keys is available on request.

Contact us

Hard limits

  • No injection into Apple system signing tools
  • Supported Mac path: Liminal Keys for Mac + virtual certificates for Xcode and codesign
  • Marketing pages never request or display secrets
  • Audit and approvals never store raw 32-byte digest bytes, CMS signatures, private key bytes, or full document bytes (SHA-256 digest hash hex may appear for correlation)

← macOS agent · All docs