Institutions
Build and share an evidence pack
Choose the systems and dates, sign the pack with a cover note, and share it with an examiner key.
How-to video coming soon
- For
- Compliance leads
- You need
- The Compliance lead’s or the CISO’s role.
- Result
- A signed pack, and a share record when you share it.
Steps
Open the Evidence pack builder. Every system in the regime profile is in by default.
To leave a system out, untick it and give a reason on the Evidence pack builder. The pack’s manifest lists every exclusion, and the examiner sees it.
On the Evidence pack builder, set From and To as YYYY-MM-DD, who it is for, and the purpose. A cover note is optional; the examiner reads it first.
Choose Review and sign the pack on the Evidence pack builder, confirm what it covers, and sign with your identity provider.
On the built pack, choose Download both forms or Share with the examiner key.
Send the examiner the pack’s chain head and the pack key hash yourself, by your own route, such as your letter to the supervisor. The built pack shows both.
Good to know
- The Compliance lead or the CISO builds and signs a pack.
- A pack holds the records in the GovernanceOS schema, the same records as flat JSON and CSV with an embedded dictionary, evidence hashes and timestamps, the chain segment and its anchors, the exclusions, the signature and the verifier version.
- The cover note is part of the signed manifest, so it cannot change after you sign.
- The verifier ties a pack to your institution only through a value that reached the examiner outside GovernanceOS. The pack key hash stays the same for every pack the key signs.
Where in the product
These open the prototype, on fictional institutions. People are shown as roles.