Compliance Frameworks

Beyond AI-specific frameworks, chio's primitives also supply evidence that aligns with classic security and privacy frameworks. This page collects the mappings for SOC 2 Type II, HIPAA, PCI DSS v4.0, and the OWASP LLM Top 10 (2025 edition). For each, the framing is the same: chio's shipped controls map onto named control requirements, producing signed evidence that a compliance program can reference.

SOC 2 Type II

SOC 2 evaluates a service organization against Trust Services Criteria covering security, availability, processing integrity, confidentiality, and privacy. Type II specifically tests operating effectiveness over a period, so the evidence story matters as much as the control story.

HIPAA Security Rule

The HIPAA Security Rule imposes administrative, physical, and technical safeguards on electronic protected health information (ePHI). Chio's tool-governance layer aligns with the technical safeguards under 45 CFR Part 164, Subpart C.

PCI DSS v4.0

PCI DSS v4.0 protects cardholder data and sensitive authentication data across people, processes, and technology. Chio does not itself process, store, or transmit cardholder data, but agent systems governed by chio routinely call payment gateways or CRMs that hold card data. Chio's role is to reduce PCI scope of the agent layer by enforcing which tools an agent may touch, under which conditions.

OWASP LLM Top 10 (2025)

The OWASP Top 10 for LLM Applications (2025 edition) names the most critical security risks for LLM-based software. Chio governs the tool-invocation boundary, which is where most "LLM does something in the real world" risks concentrate.

Four of the ten risks have strong coverage at chio's boundary (LLM02, LLM05, LLM06, LLM10). Five are partially covered because the root cause sits inside the model; chio complements rather than replaces model-layer defenses. One (LLM04) is out of scope at the tool-governance layer.

Exporting Evidence Bundles

Every framework above benefits from the same evidence pipeline: chio evidence export. The command assembles a signed bundle that an auditor can verify offline.

# Assemble an evidence bundle covering the quarter.
$ chio evidence export \
    --policy ./policy.yaml \
    --receipt-db ./receipts.sqlite3 \
    --since 2026-01-01T00:00:00Z \
    --until 2026-03-31T23:59:59Z \
    --output ./q1-evidence-bundle

# Bundle contents:
#   policy.yaml                   (signed policy artifact)
#   policy-hash.txt               (the hash embedded in every receipt)
#   receipts/                     (receipts for the window, by day)
#   checkpoints/                  (Merkle checkpoints covering the batch ranges)
#   manifests/                    (every ToolManifest referenced by the receipts)
#   session-certificate.json      (signed summary of the operational posture)
#   integrity.json                (Ed25519 signature over the bundle manifest)

# Verify a bundle offline.
$ chio evidence verify \
    --bundle ./q1-evidence-bundle \
    --kernel-pubkey ed25519:80f2b577... \
    --issuer-pubkey ed25519:ac34d1e9...

What the bundle proves to an auditor:

• The receipts were produced by the named kernel keypair (Ed25519 signature on each receipt).
• The checkpoint chain is intact (signed Merkle roots cover the included batches, and inclusion proofs are reproducible).
• The policy hash embedded in every receipt matches the policy artifact shipped inside the bundle.
• Every referenced tool manifest is signed by its issuer.

Cross-Framework Summary

Non-Goals

• No claim that chio is SOC 2 certified, HIPAA attested, or PCI DSS assessed as a service. These frameworks apply to organizations; chio is infrastructure.
• No substitute for network-layer controls, physical security, workforce training, or legal review. Chio complements those controls at the agent boundary; it does not replace them.
• No universal risk score across frameworks. Chio emits the evidence; the compliance program translates it into each framework's language.

For the operator-facing command surface that produces these bundles, continue with the CLI reference. For the data model of receipts themselves, see Receipt Format.