Skip to content

Compliance guide

The compliance role is built for whoever keeps your regulatory frameworks current: uploading evidence, closing controls, and walking into an audit with nothing missing.

Your day-to-day

Your main screen is the evidence library (/evidence). When you upload a document — a signed policy, a certificate, a pentest report — you can link it to the controls it covers across every active framework (ENS, ISO 27001, DORA, NIS2, and the rest of /compliance). One well-linked piece of evidence can close several controls at once, thanks to the cross-framework mapping.

Expiry reminders

You get a reminder when a piece of evidence is about to expire, with enough lead time to renew it before it becomes an audit gap. Renewing replaces the old evidence with the new one without losing the history of which controls it was linked to.

What a piece of evidence carries

Title, type, framework, control, description and, if you wish, a reference link. You can upload a file (PDF, PNG, JPG or ZIP) of up to 50 MiB or record just a link. Also state until which day it is valid: it must be a future date. When you renew, the new evidence states which one it replaces.

One piece of evidence, several frameworks

In the compliance section, the Crosswalk screen shows which controls of one framework correspond to those of another, for example between the ENS and NIS2 article 21. The equivalences go through a spine of canonical HodeiShield controls: they are our own mapping, not an official correspondence between standards.

What you can write, and what you can't

You can upload, renew, and delete evidence, and generate the evidence pack for an auditor. Outside of that, your access is read-only: you don't manage users, licenses, credentials, or integrations — that stays with the tenant administrator. Inside GDPR, DORA, policies, and the rest of the compliance domain you can see everything, but write access stays with the administrator until your organization decides to extend it.