AI evidence you can export: trust passport and audit package.
Praesidia packages the evidence an auditor, regulator or buyer asks for into exports: a signed AI bill of materials (AIBOM) per AI system, a trust passport you choose to publish, and an audit package for a chosen period with the signed evidence bundle inside. A screenshot of a dashboard proves nothing; the signed bundle is what your auditor checks offline, without logging in to Praesidia.
One export for a chosen period. The package is for reading; the signed bundle inside it is what an auditor checks. See the check they run.
Three kinds of evidence you can export
A signed bill of materials per AI system
Every model, prompt, tool, data source and policy an AI system uses, recorded as a signed version you can compare with the last release.
A trust passport you choose to publish
A public page, badge and PDF showing the posture of one AI system, and a way to check the passports your own vendors send you.
An audit trail that stands on its own
Signed records your auditor verifies offline with a verifier we hand to them, so the answer does not depend on trusting our console.
Know exactly what changed between two releases
An AI system is more than its code. Its bill of materials (AIBOM) lists the models and their versions, prompts, frameworks and packages, MCP servers and their tools, skills, data sources and vector stores, identities, policies and deployment artefacts. Each snapshot is signed; any two can be compared.
Components and the dependencies between them are compared separately, so a new connection between two unchanged parts still shows up.
- Export any snapshot as it is stored, as CycloneDX for the tools your security team already runs, or as a self-contained file that carries what it needs to be verified offline.
- Attach the CycloneDX software bill of materials your build already produces from a connected GitHub or GitLab repository, and its packages and frameworks fill in the AIBOM.
- A new model, tool or data source on a system can reopen its risk review; see risk management.
Answer the security questionnaire before it arrives
Each AI system has a trust passport: a signed summary of its posture that you can keep private or publish as a public page, an embeddable badge and a PDF. A passport is private until you make it public.
- Posture
- Identity, guardrails, audit trail and spend cap in place
- Testing
- Red-team results and attestations
- Regulation
- Frameworks mapped and regulatory classification
- Make-up
- Models, permissions, data categories and the AIBOM
It also records the AI system's incidents and an evidence root that ties the passport to the signed audit trail behind it.
Publish
Link the public page from your own trust center, embed the badge, or attach the PDF to a procurement reply.
Verify a vendor's passport
Import the passport an AI vendor sends you. Praesidia checks its signature against the vendor keys you pinned and tells you whether it is valid, invalid or unsigned.
Hold vendors to your bar
Set the frameworks you require, the highest residual risk you accept and the controls you expect, and see which rules an imported passport meets.
A record nobody can quietly edit, including us
Praesidia records the decisions it makes in an append-only, hash-chained audit trail, signed under the default configuration; an operator can turn signing off. Export a bundle for any period and your auditor checks it offline: whether anything was altered since it was signed, or added or removed within the chain.
- 1
An agent's call is decided, and the decision is recorded with who asked, what they asked for and which rule applied.
- 2
The record is signed and joined to the chain of records before it.
- 3
You export a signed bundle for the period your auditor asks about.
- 4
They run the verifier on their own machine and read a pass or fail for each check.
What it checks and what it does not, step by step: verify your audit trail.
What each piece of evidence is, and where it stops
- AI bill of materials
- A signed, versioned snapshot per AI system, taken when you ask for one from the app or the API. Snapshots can be compared, exported as stored, as CycloneDX or with their verification material attached, and checked against their signature. In every plan.
- Trust passport
- Signed, private by default, and public only for the AI systems you choose. Public passports are served without a login so a buyer can check them. Importing and verifying vendor passports is in every plan.
- Audit package
- An export for a chosen period that bundles an executive summary, inventory, risk register, controls, evaluations, incidents, policies and the signed evidence bundle, with verification steps. The organization owner can export it in every plan; where a plan has more than one member (Advanced and Enterprise), compliance officers can too.
- Reports
-
- A weekly executive report, also as a PDF, for organization owners.
- Incident evidence bundles and regulator reports; see incident response.
- Forensic search across audit records Advanced
- Evidence coverage per framework and the ISO/IEC 42001 gap view Enterprise
- Getting the verifier
- The offline verifier is handed to customers and their auditors directly; it is not a public download yet. Ask your Praesidia contact.
- What it is not
- Evidence is not certification. A signed record proves what was recorded was not changed afterwards; it does not prove that every action was captured, and a passport reports posture rather than guaranteeing it. The limits of the check are listed on verify your audit trail.
Works with
Runtimes whose tested recipe reaches evidence grade A in the catalog. Each recipe is limited to the setup its page lists, and one recorded action can still grade lower, so check the grade on the action. See the full runtime catalog.
Read more: tamper-evident audit logs · compliance mappings · Trust Center. Then: incident response · the whole platform.
Common questions about AI evidence
An AI bill of materials (AIBOM) lists what an AI system is built from: its models and their versions, prompts, tools, data sources and policies. Praesidia keeps one per AI system as signed, versioned snapshots you can compare release to release and export as CycloneDX.
A signed summary of one AI system's posture, private until you choose to publish it as a public page, a badge or a PDF. You can also import the passports your vendors send you and check their signatures against the vendor keys you pinned.
One export for a chosen period: an executive summary, the AI inventory, the risk register, controls, evaluations, incidents, policies and the signed evidence bundle, with the steps your auditor follows to verify it. The organization owner can export it in every plan; on plans with more than one member, compliance officers can too.
Evidence is what you export; proof is the check. The audit package and the AIBOM are for reading and sharing; the signed bundle inside the package is what an auditor verifies offline, on their own machine. The AI agent audit trail page covers that check, and verify your audit trail lists what it proves and what it does not.
No. Evidence is not certification, and a passport reports posture rather than guaranteeing it. A signed record shows it was not changed afterwards. It does not show that every action was captured.
Go deeper
- The AI agent audit trail guide — what a record of agent activity must contain, and how it is checked.
- EU AI Act Article 12 logging for AI agents — the events to log, and who keeps the logs.
- Tamper-evident audit logs — signing, chaining and anchoring, explained.
- AI agent supply chain security — the models, MCP servers, tools and prompts an agent depends on.
- AIBOM and AI agent audit trail, defined in the glossary.
Check the proof before you trust the product
Read exactly what the verifier checks, then connect one AI system and export its first signed record.