Security & trust

Trust should be engineered, not assumed.

A governance product should be precise about its own controls. Below is what Certaion implements today, and what is planned. No compliance certification is claimed.

Implemented today

  • Authenticated access with organization-scoped records and owner or admin access rules
  • Server-side policy evaluation with recorded inputs, policy version and fail-closed default
  • Approval separation, decision reasons and self-approval flagging
  • SHA-256 evidence digests recomputed on verification
  • Identity and policy change history kept as appended events
  • Audit export in CSV and JSON
  • API keys stored as hashes only, never in plaintext

Planned, not implemented

  • External identity verification with third-party attestation
  • Signed webhook delivery for approval and evidence events
  • SSO and SCIM provisioning for workforce identity
  • Independent penetration test and published report
  • SOC 2 Type II and ISO 27001 certification programs

Compliance statement

Certaion does not claim SOC 2, ISO 27001, GDPR certification or any other attestation. Where a customer requires a specific control framework, that is a contractual conversation and must be verified independently. Descriptions on this site describe product behaviour, not a certification status.

Least-privilege authorization

Policies start from deny and grant only the resources and actions an agent needs.

Explicit policy decisions

Every evaluation returns a recorded effect, the policy version and the inputs it used.

Human oversight

High-risk actions can require approval, with the requester separated from the approver where possible.

Tenant isolation

Records are scoped to the organization that created them, enforced by access rules on every read and write.

Evidence integrity

Each action record carries a SHA-256 digest over its canonical fields, re-checkable at any time.

Auditability

Policy changes, identity changes and approval decisions are kept as history, not overwritten.

Clear ownership

An agent without a named owner cannot be treated as governed.

Transparent verification status

Internal registration, integration-reported execution and integrity verification are shown as distinct states.

Security & trust

Trust should be engineered, not assumed.

Certaion is built around explicit decisions and checkable records. We separate what is implemented today from what is planned, because a governance product should not overstate its own controls.

Least-privilege authorization

Policies start from deny and grant only the resources and actions an agent needs.

Explicit policy decisions

Every evaluation returns a recorded effect, the policy version and the inputs it used.

Human oversight

High-risk actions can require approval, with the requester separated from the approver where possible.

Tenant isolation

Records are scoped to the organization that created them, enforced by access rules on every read and write.

Evidence integrity

Each action record carries a SHA-256 digest over its canonical fields, re-checkable at any time.

Auditability

Policy changes, identity changes and approval decisions are kept as history, not overwritten.

Clear ownership

An agent without a named owner cannot be treated as governed.

Transparent verification status

Internal registration, integration-reported execution and integrity verification are shown as distinct states.

Capability status

last reviewed · today
  • Organization-scoped access rulesImplemented
  • Server-side policy evaluationImplemented
  • Approval separation and historyImplemented
  • SHA-256 evidence digestsImplemented
  • Audit export (CSV / JSON)Implemented
  • External identity verificationPlanned
  • Signed webhook deliveryPlanned
  • SOC 2 / ISO 27001 certificationNot claimed

Found something that does not match this page?

Tell us. Security disclosures and corrections to the statements above are treated as a priority.