Auditor Access and Evidence Bundle
Auditors, assessors and insurers need to see evidence without being given a regular account. OrbisID has an Auditor user: read-only, limited to evidence, and ending automatically on a date you choose. An auditor, or you, can also download a signed evidence bundle whose contents cannot be altered without detection.
Auditor access and the evidence bundle are available in Pro and Enterprise. See Licensing.
Inviting an auditor
An Administrator creates the auditor under Administration > Access & Security > User Management:
- Choose Add User and set the role to Auditor (read-only, time-limited).
- Choose the day the access ends. It must be in the future and at most a year away. The access ends at the end of that day.
- Create the user with a password, or tick the option to email them a link to set their own.
Auditors count towards your user limit while they are active. An auditor cannot be changed into another role, and no other user can be changed into an auditor, so create a new user instead.
What an auditor can see
An auditor can only read:
- Control Monitoring: status, evidence and history
- Findings and the remediation dashboard
- Access reviews and their completion reports
- Attestation records
- KRIs, their trends, snapshots and exceptions
- Reports, the PAM Gap Analysis and the cyber insurance evidence pack
- The evidence bundle and its public signing key
An auditor cannot see or change anything else: no credentials, systems, accounts, identities, users, settings, audit logs or API keys, and no action that creates, edits or deletes anything. Everything not on the list above is refused, including any feature added in future, until it is deliberately made available to auditors. The auditor's menu shows only the evidence pages.
Ending access
- It expires. From the end of the chosen day the auditor cannot sign in, and a session already open stops working. An hourly job then marks the user inactive and records the expiry in the audit log.
- You revoke it. Deactivate the user under Administration > Access & Security > User Management. Their sessions end at once.
- You extend it. Edit the user and choose a later day. If the user has already been deactivated, activate them again.
Creating an auditor, signing in, deactivating and expiry are all recorded in the audit log, and so is every evidence bundle download.
The signed evidence bundle
Reports > Evidence Bundle > Download bundle produces a ZIP containing:
| Folder | Contents |
|---|---|
control-status/ | Status of every monitored control for every framework (CSV and JSON), and the last 90 days of evaluations |
insurance/ | The cyber insurance evidence pack, PDF and CSV |
gap-analysis/ | The latest completed gap analysis, PDF |
findings/ | Findings and remediation, CSV |
attestations/ | Attestation history, attested accounts and answers, CSV |
access-reviews/ | A summary of every access review, and each review's decisions (CSV and PDF) |
| root | manifest.json, manifest.sig, public-key.pem and VERIFY.md |
manifest.json lists the SHA-256 hash of every other file. manifest.sig is an Ed25519 signature of the manifest. If any file is changed, added or removed after export, verification fails. VERIFY.md in the bundle gives the exact commands, using OpenSSL and standard tools.
Signing key
A signing key is created the first time a bundle is downloaded. The private key is stored encrypted on the server and is never exported. The page shows the fingerprint of the public key. Give the fingerprint to your auditor by another route, for example in the engagement email, and ask them to compare it with the fingerprint of public-key.pem in the bundle. A bundle carries its own public key, so without that comparison the signature proves the contents were not changed, but not that this instance produced them.
An Administrator can rotate the key. The old key is retired and its private half erased; its public half is kept, so the fingerprint on an older bundle can still be matched to a key your instance used. After a rotation, tell your auditors the new fingerprint.
What a signature does and does not show
It shows that the bundle is exactly what the server exported. It does not show that the data on the server was correct, and someone with access to both the database and the server's encryption key could sign a forged bundle.
Who can do what
| Action | Role |
|---|---|
| Create, edit and deactivate auditors | Administrator |
| Download the evidence bundle, see the signing key | Analyst and above, and auditors |
| Rotate the signing key | Administrator |