Security architecture

Protect the authority behind your software.

PipKey's production controls are built around protected secrets, signed assertions, explicit trust boundaries, audit evidence and verified recovery.

Controls

Security is part of the product model.

The current 1.0.0 baseline protects licence credentials and privileged operations without treating documentation or configuration labels as proof on their own.

No stored raw licence keys

Licence keys are returned once and protected server-side using keyed digests rather than persisted plaintext credentials.

Signed assertions

Ed25519 signing protects offline entitlement assertions and product-delivery metadata.

Least privilege

Administrator and service access is constrained by explicit scopes, audience and environment boundaries.

Append-only migrations

Production schema changes use versioned, checksum-controlled migration history with compatibility and recovery review.

Tamper-evident evidence

Privileged and licence-affecting operations generate structured audit and outbox evidence without secret disclosure.

Verified recovery

Local backups, isolated restore verification and encrypted independent offsite recovery are part of the production baseline.

Production operations

A release is not complete because containers are running.

Production acceptance requires reviewed source, exact-head automation, package integrity, current recovery evidence, controlled deployment, running-image verification and documentation close-out.

  • Version-specific production change control
  • Running image and public metadata verification
  • Local backup plus isolated restore evidence
  • Encrypted independent offsite recovery
  • UFW, Fail2ban and clock-synchronisation checks
  • No production secrets in source control