Skip to content

Security

Security and control

Review the documented boundaries for credentials, permissions, approvals and audit evidence.

Read security guidanceContact WAYLOCK

Principles

Authority that can be inspected

Security principles

Least privilege
Bound identity, permission, scope and current versions.
Human review
Bind approval to the exact request.
Execution certainty
Uncertain outcomes enter reconciliation.
Audit evidence
Preserve decisions and consequential actions.

Boundaries

What the browser never holds

The control plane keeps its session server-side. Pairing codes are shown once, and private keys stay with the integration that owns them.

  • SessionsSigned in with your identity provider; the session stays on the server.
  • Pairing codesSingle-use and short-lived. They pair; they are not credentials.
  • Private keysThe integration signs. WAYLOCK never asks for a private key.

Read the security guidance.

Credential, pairing and approval boundaries for integrations, in one place.

Read security guidanceGet started