Why this matters
A JSON or CSV export is plain data that anyone could have edited. A signed credential lets a verifier confirm that the record was signed by the holder of a specific DID key and has not changed since signing. That can be useful as supporting evidence for logging and monitoring controls (for example EU AI Act Article 12 or SOC 2 CC7.2), but it does not by itself satisfy either.Quick start
Export options
Format
ldp_vc (default), JSON-LD with an embedded proof of type JsonWebSignature2020 that carries a compact EdDSA JWS over the credential body. Pass the credential object to verifyCredential().
jwt_vc, JWT-encoded credential. The result.jwts array contains the compact JWT strings. Pass those to verifyCredential().
Output shape
individual (default), one credential per audit record.
presentation, a single Verifiable Presentation wrapping all credentials. Useful when submitting a batch to an auditor as a single signed document.
format: 'jwt_vc' the presentation is returned unsigned; only the individual JWTs are signed.
Filtering
Pass afilter function to select a subset of records before signing. Useful for exporting only denials, or records for a specific agent.
Credential subject schema
Each credential carries aTheAuthAuditCredential type with the following subject:
The
@context array includes both https://www.w3.org/ns/credentials/v2 and https://theauth.dev/contexts/audit/v1.jsonld. The theauth context URL is a stable identifier for this schema, it does not need to resolve at runtime.
Limits to know about
Credentials are issued with a 24 hour expiry, and the verifier rejects expired credentials. Export close to the time you hand evidence to a reviewer, or re-export when needed. A signature shows who signed a record and that it is unchanged since signing. It does not show that the underlying audit log was complete, and it does not replace your own controls, auditor review, or legal advice.Control mapping
The export can serve as supporting evidence for EU AI Act Article 12 (record-keeping) and SOC 2 CC7.2 (evaluating security events). See the compliance overview for the mapping and its caveats.Related
- Audit trail, how audit logging works and how to query records
- Compliance, control mapping for EU AI Act, SOC 2, and ISO 42001
- DID (Decentralized Identifiers), issuer identity and key management
- SOC 2 compliance report, coming soon
- EU AI Act conformity assessment, coming soon