Skip to main content
For auditors & examiners

What you receive from us as an auditor

This page is for external auditors, internal audit, statutory auditors and supervisory examiners. It describes which records your client can hand over from Agentic360, what they contain, what you can verify yourself and where the limits are.

What is in the evidence bundle

At its core is the audit pack: a ZIP archive that captures exactly one scan snapshot. Alongside it come audit reports for individual agent answers and the event log of the engagement.

.zip

Audit 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.json

Manifest 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.sig

Manifest 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.csv

Findings 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.csv

Activity history

Every entry on a finding with its type, author and UTC timestamp.

PDF

Audit 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.

JSON

Input/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.

citation

Source 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-256

Hash-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.

scan

Repeatable 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

How to verify it yourself

Seven steps for a sample. You can do the first three with your own tools, without access to the platform; the key list for the signature check is public.

  1. Check the pack is intact

    Compute the SHA-256 value of every file with a tool of your choice, such as sha256sum or Get-FileHash, and compare it with the entry in 00_manifest.json.

  2. Check the signature

    Fetch the published key list at https://agentic360.de/api/v1/public/audit-signing-keys and look up the key ID from 00_manifest.signer.json. Then verify 00_manifest.json.sig over the unchanged bytes of 00_manifest.json with the public key from the list. The README in the pack contains the commands – shasum, a short Python snippet using cryptography, or OpenSSL 3 or later.

  3. Draw a sample

    Pick findings from 02_findings.csv and trace in 03_audit_trail.csv who worked on them and when. Score and counts come from the same calculation as the dashboard and reports for the same scan.

  4. Trace an answer back to its source

    Ask for the audit report of an agent answer. Open the cited source – document, section or page, version – in the original and compare the excerpt.

  5. Recompute an answer hash

    Ask for the audit report of the same answer as JSON (GET /api/v1/chat/messages/{id}/audit-report?format=json). Compute the SHA-256 values of the user_content and assistant_content fields and compare them with the input and output hashes in the report. Do not copy the text from the PDF – its line breaks are layout; the report contains the instructions.

  6. Follow the approvals

    For each reviewed finding the four-eyes marker shows whether it was confirmed independently or by self-review. The attestation of an engagement is in the event log with the acting person and time.

  7. Have the chain checked

    The chain check recomputes every hash of the event log. It runs in the platform and requires administrator rights – ask to see it run. Result: chain intact with the last hash value, or the number of the first entry that does not match.

What we do not claim

The limits of the audit pack are also stated in its manifest.

  • “Automatically verifiable” means the platform collects the evidence for that control by machine from connected systems. It is not a statement about legal conformity – that judgement is yours.
  • The audit pack contains automated check results of one scan snapshot; unless marked otherwise, they have not been reviewed by a compliance professional. It is neither a certification nor a declaration of conformity.
  • Agentic360 is ISO 27001-aligned but not certified – neither against ISO 27001 nor against any of the other standards we name.
  • Hash values show that files and log entries have not been altered afterwards, not that their content is correct. Likewise, the signature proves the integrity and origin of the pack, not the correctness of its content. It covers the manifest including generated_at, but not the signed_at time in 00_manifest.signer.json.
  • Input/output hashes and policy provenance are recorded from 18 October 2026; older answers are marked “not recorded (before introduction)” (in German reports “nicht erfasst (vor Einführung)”). Static .rego files are identified by content hash only, the hallucination threshold is environment configuration, and generated policies are not queried on answer paths.
  • Evidence files are not part of the pack; evidence references point to records in the platform.
  • Dates in the findings are internal remediation targets, not statutory deadlines. A cover letter to an authority is added only on explicit request and is then an unreviewed draft.
  • Figures such as “six weeks of audit preparation instead of four days” on our pages are model calculations, not measured customer results.

Auditor access

We agree read access for your audit with your client. It is set up through the client’s own user management:

  • Your client’s administrators invite you by email with the “Auditor” role. It reads compliance results, evidence, documents and the audit log, and changes nothing. The invitation link is valid for seven days.
  • You export the audit log and the Compliance Scanner reports yourself. The chain check stays with the administrators; your client shows you its result.
  • There is no automatic expiry: access ends when your client revokes it. Agree the end date together.

Discuss audit support

Are you preparing an audit at a client that uses Agentic360, or would you like to walk through the audit pack on an example? We will show you its structure and the verification steps in a demo.

Discuss audit support