Glacis generates signed receipts when controls execute. Those receipts can be assembled into evidence packs for enterprise security reviews, audits, customer trust, insurance, regulatory evidence, and internal assurance.
Receipts are generated at runtime. Evidence packs are assembled from receipts. Receipts prove control execution without exposing the underlying sensitive content.
A signed runtime receipt, generated when a control executes. Workflow, control, decision, signed verification metadata — immutable once signed.
GLACIS Attestation Receipt ─────────────────────────────────────── Receipt ID: att_7f3a2b1c-e4d5-4a8f-9b2e-1c3d4e5f6a7b Timestamp: 2026-03-14T14:23:47.891Z Epoch: 1773498228 AI System: Clinical Documentation Assistant (v2.4.1) Model: gpt-4o-2024-08-06 Provider: Azure OpenAI (East US 2) ┌─ Policy Evaluation ───────────────────────────────┐ │ Policy: prod/clinical-docs/v3 │ │ Decision: PERMIT │ │ Controls Applied: │ │ ✓ PHI detection — 0 entities found │ │ ✓ Jailbreak guard — score: 0.02 (threshold: 0.7) │ │ ✓ Toxicity filter — score: 0.01 (threshold: 0.5) │ │ ✓ Token budget — 847 / 4096 │ │ Confidence: 0.98 │ └───────────────────────────────────────────────────┘ ┌─ Cryptographic Proof ─────────────────────────────┐ │ Local Content Hash: a7f3...2b1c (SHA-256, local) │ │ Exported Commit: e4d5...4a8f (HMAC-SHA-256) │ │ Signature: ECDSA-P256 │ │ Witness Status: 3/5 witnesses confirmed │ │ Transparency Log: anchored ✓ │ │ Inclusion Proof: verified ✓ │ └───────────────────────────────────────────────────┘ ┌─ Zero Sensitive-Data Egress Verification ────────────────────────┐ │ Plaintext Egress: 0 bytes of plaintext content │ │ Boundary: Only HMAC’d commitments crossed │ │ Storage: Customer environment (local CAS) │ └───────────────────────────────────────────────────┘
Every field in the receipt exists for a reason. Here’s what your compliance team and auditors care about.
“Did the AI follow the rules?” Shows permit, deny, or escalate — and which controls ran against the request before it was allowed through.
“What guardrails were active?” PHI detection, jailbreak prevention, toxicity filtering — with scores proving each control executed, not just that it was configured.
“Which AI made this decision?” Exact model version, provider, and configuration — captured at the moment of inference, not reconstructed from logs.
“Can anyone tamper with this?” Signed with ECDSA. Hashed. Witnessed by independent third parties. Anchored in a transparency log that anyone can audit.
“Did any plaintext leave?” Proves 0 bytes of plaintext content crossed the trust boundary. Only HMAC’d commitments were exported — prompts, responses, and PHI never left your environment.
“When exactly?” Millisecond precision. Bound to system state at the time of the decision. Not a log entry written after the fact — a commitment sealed at runtime.
Receipts assemble into one structured artifact for the customer security review, the audit, the regulator, the insurer, and the internal incident review — consumable without calling a meeting.
X decisions attested across Y AI systems over Z days. One number that tells the board how much of your AI estate is covered.
Every safety control, every execution, pass/fail rates. Not a policy document saying controls exist — proof they ran.
How receipts map to ISO 42001, NIST AI RMF, and EU AI Act controls. One evidence base, multiple frameworks.
Queryable log of every decision — searchable by date, system, outcome, or control. Your auditors don’t wait for you to pull reports.
Machine-readable format for auditors and downstream compliance tools. No more spreadsheets — structured data that feeds directly into GRC platforms.
Glacis runs inside your infrastructure. Local runtime controls evaluate the workflow, the receipt is signed locally, and only the receipt — never the prompt, output, PHI, customer data, code, or proprietary context — gets shared.
Logging this costs less than your current observability stack. Every receipt is structured, queryable, and stored in your environment.
Walk a live evidence pack with the Glacis team in the Agent Runtime Security Sprint — mapped to your frameworks, your customer security review, and your regulatory surface.
Book the Agent Runtime Security Sprint