NIS2 services: what a proper compliance engagement includes
Published:
Short answer: a NIS2 service is not a policy document. It starts with whether and how you are in scope, continues with a gap analysis against the requirements, implements technical and organisational measures and ends with procedures that are followed in practice. If a quote mentions only "policies", ask what else is included.
The steps of an engagement
- Scope check: sector, size, and whether you are an essential or important entity.
- Gap analysis: what you already do and what is missing against the measures of Joint Ministerial Decision 1689/2025.
- Risk assessment and a treatment plan with priorities and timeline.
- Policies and procedures, together with their implementation: MFA, backup, vulnerability management, access control.
- An incident reporting procedure, with the deadlines set by the legislation.
- Supplier management: who has access to your systems and what you require from them.
- Training for management and staff, and ongoing monitoring.
Responsibility for compliance stays with the entity’s management, so the consultant should guide you and leave you with procedures you can keep up yourself.
ITHACA starts with a scope check and gap analysis, implements the measures and supports your business afterwards with ongoing monitoring.
Frequently asked questions
Who is responsible for compliance?
The entity’s management. The consultant helps but does not take over the responsibility.
Where do I start?
With the scope check and a gap analysis. Ask for these first, before any policy.