Standards and compliance
A single ISMS for your company. Adopt standards on top of it, implement each control once and give the auditor the Statement of Applicability and the audit package.
In SofIA Governance your company has a single information security management system (ISMS). Its controls use ISO/IEC 27001 as the backbone, plus the management system requirements (clauses 4 to 10) and specific controls for what ISO doesn't cover (for example, data subject rights or reporting to ANCI).
Each standard your company decides to comply with (ISO 27001, ISO 22301, NIST CSF, Law 21.663 or Law 21.719) is adopted on top of that ISMS. Its requirements are met by the ISMS controls that cover them: a control is implemented once and counts for every standard that requires it, with the same evidence and the same KPIs.
You'll find everything in Standards → Adopted standards, Standards → Cross-standard coverage, ISMS → ISMS controls and ISMS → Statement of Applicability.
How each requirement is met
Each requirement of a standard is linked to one or more ISMS controls with a coverage type:
Coverage | What it means | Requirement status |
|---|---|---|
Equivalent | Meeting the control meets the requirement | The control's status (if there are several, the worst) |
Partial | The control contributes, but the standard asks for something more (for example, that the owner be the DPO, or a legal deadline) | The worse of the control and the standard-specific part |
Related | Informational only: the control relates to the requirement, but doesn't meet it | Doesn't change it |
No control | The requirement is handled only in that standard | Its own answer |
So when a control moves to Compliant, every standard that requires it goes up at the same time.
How you work
You define the ISMS: its scope, its owner and its status. See ISMS details and scope.
You adopt a standard with a wizard that shows upfront how much of it your ISMS already covers. See Adopt a standard.
You implement the ISMS controls: status, maturity, implementation, owner, KPIs and evidence. See ISMS controls.
You complete each standard's specific part where coverage is partial or there's no control, and follow its roadmap. See Work on an adopted standard.
You prepare for the audit with the Statement of Applicability and the Generate the audit package.
Who can do what
Role | What they can do |
|---|---|
Administrator | Everything, including Delete an adopted standard |
Editor | Edit the ISMS, adopt standards, assess controls and requirements, record measurements, apply assessments, generate and reschedule the roadmap, analyze documents and review their proposals, migrate to a new revision and generate audit packages |
Read only | View everything, check coverage, export the Statement of Applicability and download audit packages and analyzed documents; the buttons to create or change appear disabled |
Auditor | Same as Read only; if their access is limited to certain standards, they only see those adopted standards. They don't change anything in this section; they record findings and results in Internal audit |