.zipAudit pack per scan snapshot
Executive report as PDF; findings, their activity history and control owners as CSV; scan metadata as JSON; plus a README. Tenant-wide registers – data-subject requests, incidents, risk assessments – are included only when the export is created with administrator rights.
00_manifest.jsonManifest with SHA-256 per file
Lists the scan, UTC timestamps, the contents, the SHA-256 value and size of every file, the method version of the assessment and the statement limits of the pack.
00_manifest.json.sigManifest signature
The manifest is signed with Ed25519: 00_manifest.json.sig holds the signature (base64) over the exact bytes of 00_manifest.json, 00_manifest.signer.json the key details. Because the manifest lists the SHA-256 value of every file, the signature covers the whole pack. The public keys are published with key ID, algorithm and validity period at https://agentic360.de/api/v1/public/audit-signing-keys; after a key rotation, older keys stay listed.
02_findings.csvFindings with review status
Per finding: framework, control ID, severity, status, recommendation and owner. Plus review status, the four-eyes marker (independently reviewed, self-review or undetermined), risk acceptances with expiry and reason, and the closure reason.
03_audit_trail.csvActivity history
Every entry on a finding with its type, author and UTC timestamp.
PDFAudit report per agent answer
For a single chat answer: question, answer, linked sources, the answering agent, the model used, the guardrail status and the timestamps. The input and output of every answer are checked by the guardrails; the result is recorded with the answer.
JSONInput/output hash and policy provenance
For every answer the platform stores the SHA-256 value of the input – the text the model pipeline received – and of the stored output (scheme version 1: NFC-normalised UTF-8, no whitespace trimming). The policy provenance section of the audit report names the guardrail configuration the answer was checked with – its fingerprint is the SHA-256 value over the configuration actually applied, kept as an append-only snapshot – and, for MCP tool calls, the OPA policy decisions with package, mode, verdict and module including policy version and hash. If the guardrail check was unavailable, that is recorded with the answer. Policy texts have an immutable version history with validity periods. The audit report is available as PDF and as JSON.
citationSource references
The explanation view lists, for every linked source, the document and, where available, the section or page, the quoted excerpt, the document version and the retrieval time – so you can open the passage in the original.
SHA-256Hash-chained event log
Per engagement, creation, scan start and end, attestation, delivery and report generation are logged as a SHA-256 chain. The database permits neither changing nor deleting entries.
scanRepeatable evidence collection
On every scan the platform collects the evidence afresh from the connected systems. Scans can be scheduled to repeat, so snapshots do not only appear on the due date.
Formats: ZIP with PDF, CSV and JSON · engagement report as PDF or DOCX · audit report for single answers as PDF or JSON