The problem
Behind what is declared, real control remains unknown. Management’s expectations, the applicable requirements and the security in place are described by different people, in different documents, and rarely compared.
For organisations subject to NIS2
NIS2 makes management accountable: it approves the risk-management measures and oversees their implementation (Article 20). The assessment checks, measure by measure, the gap between what Article 21 requires of you and your operational reality, and gives management a roadmap it can defend before the supervisory authority.
The objective
Everyone starts from the same picture of where you stand, from the executive committee to the auditors, and management knows what it decided and why: the target, the order of priorities, the deadline and the budget envelope as an order of magnitude.
How it is measured
- At the start, the sponsor signs measurable success criteria, in the expectations framing note.
- During the work, each gap is rated by business impact and by risk, and a maturity score by domain sets the baseline.
- At closing, management decides the priorities in a workshop, and the sponsor and compliance approve the deliverables.
- Afterwards, the signed criteria are checked against reality at the Orchestrate step: if they are not met, a gap is reopened.
What we do: Orient
“Set the course from reality and its gaps.”
Four steps, in this order: write down what management expects, gather the applicable requirements in a single register, establish the operational reality as declared, then measure the gaps and have the sponsor decide on them.
Key deliverables
| Deliverable |
Who it is for |
| Orientation report: executive summary, the priorities decided, findings and reservations, presented to the sponsor |
Management, executive committee |
| Unified register of applicable requirements, one requirement per line, linked to all its frameworks |
Compliance, CISO |
| Maturity score by domain and prioritised action plan |
CISO, CIO |
| Detailed gap matrix, each finding marked “declared, to be proven” |
Compliance, auditors |
What Trusted Assessment does not do
It is not an audit: no technical verification happens at this stage. The diagnosis rests on what is declared, which is proven later on the real systems, at the Orchestrate step of the O³ method.
The O³ method and the proof loop in detail