Trust & residency
Security controls you can verify.
See what Covenant has tested with synthetic identities and what needs to pass before we accept real customer accounts.
Verified controls
- Passkey enrollmentVerified
- OpenID ConnectPKCE S256
- Refresh-token reuseRejected
- Reseller revocationVerified
Requirements before launch
- Processor chainVerify per region
- Tenant isolation and restoreRun in staging
- Independent assessmentReview and retest
Verified in the local build
The browser smoke test runs real OpenID Connect against a dedicated local Keycloak realm. The automated suite checks the console’s handling of access and session changes.
Sign-in and tokens
The Northline sample uses an authorization code with PKCE S256. The browser test checks passkey enrollment and verification, signed ID tokens, five-minute access tokens, and rejection of refresh-token reuse.
Browser sessions
The console keeps session state on the server, renews the session on sign-in and fresh verification, and verifies the origin and session-bound CSRF value on requests that change data.
Workspace permissions
Access is checked against current membership. Issuing invitations and changing reseller grants require recent verification. Tests exercise revocation and confirm the change appears in the workspace audit log.
Required before production
Each region needs a separate review before real customer identities can be onboarded.
Tenant isolation and recovery
Prove access isolation across unrelated customer projects and verify what happens to active sessions after offboarding. Rehearse backup restoration and rollback.
Operational controls
Confirm the processor chain, private administrative access, signing-key and secret rotation, and incident ownership. Require phishing-resistant fresh verification for privileged operations.
Independent assessment
Review the pilot scope, fix and retest findings, and record the release decision for the region.