Skip to main content
Truthlocks uses authenticated workspace context, application authorization, database isolation, and cryptographic verification for distinct purposes.

Infrastructure

The current recovery deployment uses Google Cloud. Older claims that all infrastructure runs on AWS, or that AWS Shield protects this deployment, are obsolete. Infrastructure encryption and access controls must be assessed against the deployed services and configuration.

Application controls

  • Workspace identity comes from authenticated credentials. Caller-supplied tenant headers do not select another workspace.
  • Database row-level security and application checks are used to restrict tenant data access. Their effectiveness depends on correct policies, roles, and query paths.
  • User roles and service-key permissions are different. An API key does not automatically provide a user’s role or reviewer identity.
  • MFA is available in supported sign-in flows; its availability is not evidence that every account has enrolled or that every administrative path enforces it.

Cryptographic evidence

A valid signature and inclusion proof establish specific integrity properties. They do not establish the truth of the signed claims. Some MAIP tracking receipts currently contain system markers rather than cryptographic signatures; consult the operation reference before using a receipt as proof.

Assurance evidence

Do not infer an independent security audit, penetration-test schedule, certification, or review of every change from this page. Request current evidence covering the services and deployment you intend to use. See data location and compliance.