NIS2 readiness means knowing whether your SaaS business falls under the law, operating the required controls, and proving they work. Selling into Europe alone doesn’t establish scope, but European customers can still demand security evidence before signing.
For your leadership team, the immediate issue is clear ownership. An unanswered security questionnaire or uncertain recovery capability can delay revenue while leaving material risk unresolved.
Start by separating your legal obligations from your customers’ contractual requirements.
Key Takeaways
- Your service category, size, and jurisdiction determine direct NIS2 obligations.
- Significant incidents require an early warning within 24 hours and an incident notification within 72 hours of awareness.
- Article 21 requires working risk management measures, supported by evidence.
- Management remains accountable even when a supplier or fractional executive supports delivery.
Establish Whether Your SaaS Business Is in Scope

Assess your service, size, and jurisdiction
The NIS2 Directive’s scope rules generally cover medium-sized and larger entities in listed sectors. Employee and financial tests matter, including linked-enterprise calculations. Some entities fall within scope regardless of size.
Your SaaS service may qualify as cloud computing. Managed services and managed security services are also covered categories. However, the SaaS label alone doesn’t settle the question.
NIS2 operates through national law. Your scope assessment should identify the responsible legal entity, applicable jurisdiction, registration duties, reporting authority, and relevant NIS2 requirements. Covered non-EU providers offering services in the EU may need an EU representative.
Distinguish sector lists from entity classification
Annex I covers energy, transport, banking, financial market infrastructure, healthcare, drinking water, wastewater, digital infrastructure, public administration, and space. It also includes business-to-business ICT service management.
Annex II covers postal and courier services, waste management, chemical production and distribution, food production and processing, and manufacturing categories including medical equipment. Digital providers include online marketplaces, search engines, and social-networking platforms.
NIS2 distinguishes essential and important entities based on sector, size, designation, and specific provisions. Placement in Annex I or II alone doesn’t determine classification.
Even outside direct scope, you may face customer security requirements because regulated buyers must manage supplier risk. That commercial exposure belongs in your expansion plan.
Give Management a Defined Oversight Role
Approve the controls and the resources
Article 20 requires management bodies to approve cybersecurity risk management measures and oversee implementation. Management members must also undertake training.
Senior executives can face personal liability for inadequate oversight under national implementing law. For essential entities, enforcement can include temporary suspension of relevant management functions under specified conditions.
Your governance record should show approved priorities, funding, accepted risks, and remediation decisions. Meeting minutes should explain decisions rather than merely record that cybersecurity appeared on the agenda.
Assign delivery without surrendering accountability
Name an executive sponsor and a control owner for each material obligation. Define who can authorize containment, customer communication, and regulatory notification.
A fractional CTO can coordinate the technology roadmap. A fractional CISO can lead security governance and evidence management. Neither appointment removes management’s obligations.
Use board-ready cyber risk reporting to show business exposure, overdue actions, and decisions required. ENISA’s NIS2 roles and skills guidance can help translate obligations into operational responsibilities.
Turn Article 21 Into a Checkable Control Register
Article 21 sets out the required risk management measures. Your register should connect each measure to an owner, affected systems, evidence, and a review date.
Use these evidence examples to make the requirements testable.
| Article 21 measure | Evidence your team should maintain |
|---|---|
| Risk analysis and information systems security | Approved risk assessment, security policies, and remediation owners |
| Incident handling | Response plan, escalation contacts, and completed exercise records |
| Business continuity and crisis management | Backup records, restore results, recovery objectives, and crisis procedures |
| Supply chain security | Critical-provider assessments and contractual security commitments |
| Secure acquisition, development, and maintenance | Security reviews, vulnerability handling, patch records, and disclosure procedures |
| Effectiveness assessment | Control tests, findings, and documented corrective actions |
| Cyber hygiene and training | Training records and evidence that basic protections operate |
| Cryptography and encryption | Encryption standards and key-management responsibilities |
| Personnel security, access control, and asset management | Systems inventory, access reviews, and joiner/leaver records |
| Authentication and secure communications | Appropriate MFA, protected communications, and emergency communication arrangements |
The takeaway is traceable evidence: a policy alone doesn’t demonstrate that a control operates.
Regularly testing controls, especially incident response and restoration, supports cyber resilience across prevention, response, and recovery. Records help verify test results, but documentation alone doesn’t show that controls work.
Use ENISA’s technical implementation guidance for implementation detail relevant to covered digital entities. Also account for the applicable EU implementing regulation and national requirements.
Prepare Incident Reporting Before the Clock Starts

Separate the early warning from the incident notification
For a significant incident, submit an early warning without undue delay, and within 24 hours of becoming aware. Indicate whether malicious or unlawful activity is suspected and whether cross-border effects are possible.
The incident notification follows without undue delay, within 72 hours of awareness. It updates the warning and provides an initial assessment of severity and impact, plus available indicators of compromise.
A significant incident involves severe operational disruption or financial loss, or considerable material or non-material harm to others. Additional criteria apply to covered digital providers.
Prepare the full reporting workflow
Assign responsibility for recording the awareness time, assessing significance, and contacting the competent authority or CSIRT. Don’t wait for a complete forensic investigation.
A final report generally follows within one month of the incident notification. It covers the incident, likely cause, mitigation, and cross-border impact. Ongoing incidents require progress reporting and a later final report.
Your executive incident response checklist should cover evidence preservation, legal escalation, and customer notices. Prepare secure internal communication channels for use if normal systems fail, and use end-to-end encryption where appropriate.
Treat Suppliers as Operating Dependencies
Supply chain weaknesses give attackers a route into your business. Vendor risk management needs to cover more than onboarding questionnaires.
Rank providers by operational impact, data access, and replacement difficulty. Include hosting, identity, source-code repositories, payment services, support tools, and material subcontractors. Mapping dependencies and single points of failure shows which outages could interrupt service and supports operational resilience.
For critical suppliers, review security controls, privileged access, recovery capability, and concentration risk. Contracts should address incident notification, recovery commitments, subcontractor changes, evidence rights, termination, and data return or deletion.
A supplier’s notification deadline must leave your team enough time to assess significance and meet its own reporting obligations.
Reassess critical providers after material changes. Test your vendor incident response plan, including an identity-provider outage or compromised software dependency.
Finally, include vendor offboarding. Remove accounts, tokens, integrations, and retained data. Use third-party risk reporting for the board to show dependencies that could interrupt customer delivery.
Measure NIS2 Readiness With Evidence
Microsoft’s summary of IDC research reports that only 14% of organizations were fully ready and 77% were partially ready. IDC categorized 17% as “capable” and 33% as “equipped.”
The survey covered about 2,000 organizations across more than 20 European markets. Over 90% of affected organizations knew about the directive. Awareness clearly exceeded demonstrated readiness.
Use those findings as context, not a compliance benchmark for your company.
For internal tracking, score each control: zero for absent, one for documented, two for implemented, and three for tested. This is a management scale, not an official NIS2 rating.
Report the evidence date, owner, business consequence, and next action beside each score. Never let an average hide a failed restore test or an unstaffed incident-reporting process.
Build a Practical 90-Day Readiness Roadmap
Discover the gaps and integrate the evidence
During days 1 through 30, settle scope, map critical assets and dependencies, and complete a cybersecurity risk assessment.
Compare Article 21 obligations with existing ISO 27001 controls. Record gaps in coverage, operation, and evidence. This gap analysis moves you beyond having tools toward demonstrating capability.
During days 31 through 60, integrate priority logs into your SIEM and close high-risk access gaps. In Microsoft environments, Defender and Sentinel can support detection. Compliance monitoring, security posture management, and Conditional Access policies support evidence and control enforcement.
Test the operating model and brief executives
During days 61 through 90, refine playbooks, run tabletop drills, test restores, and commission scoped red-team testing where justified. Finish with an executive briefing on remaining exposure and funding decisions.
A 24×7 MDR (managed detection and response) service can support four readiness capabilities: always-on visibility, rapid incident response, audit-ready reporting, and threat hunting. It doesn’t replace governance obligations.
Extend unresolved work into a funded 12-month technology roadmap. For each action, name the owner, deadline, evidence required, and business risk reduced.
Frequently Asked Questions About SaaS NIS2 Readiness
Does ISO 27001 certification establish NIS2 compliance?
No. ISO 27001 provides a useful management system and control evidence. You still need to address NIS2 scope, management duties, incident reporting, and applicable national requirements. Certification doesn’t replace testing whether your recovery and response arrangements work.
Can customer requirements apply when your SaaS company is outside scope?
Yes. Regulated customers can impose contractual security obligations on suppliers. Your customer security questionnaires, notification commitments, and recovery evidence may therefore affect enterprise sales even without direct NIS2 obligations.
Make the Next Leadership Decision Clear
NIS2 readiness should give you clear ownership of cyber risk and evidence that your business can respond under pressure. Start with scope, then fund the gaps that threaten customer delivery or reporting obligations.
If responsibility remains scattered, Get an Executive Technology Clarity Check. Your next leadership conversation should end with named owners and a practical priority, rather than another unresolved compliance discussion.