audit-trust-and-safety

Auditing changes to CSP policies and trust API surfaces involves enforcing a structured evaluation of surface contracts, attestation integrity, key-hash authentication, and safety-evidence workflows. This process detects governance risks and generates a mitigation report before deployment.

Attestation integrity is the validation of trust signals within attestation pipelines, typically found in /.well-known/* or /attestations/* paths. You need to audit it when changes impact instance-auth flows or safety-evidence workflows to prevent weakening your security posture.

Generate governance-ready audit reports by applying a structured evaluation to changes touching safety-evidence pipelines and CSP directives. The resulting report summarizes risk, impacted surfaces, and recommended mitigations to facilitate cross-team collaboration.

Yes, you can audit changes across both web and API layers. The evaluation explicitly covers CSP policies, instance-auth, and trust API surfaces spanning both layers, ensuring comprehensive governance and risk documentation for the entire deployment.

Yes, reviewing instance-auth key-hash authentication supports MCP tooling compliance checks. The audit enables traceability for changes, evidence requirements, and compliance checks across MCP tooling and deployment pipelines.