NIS2 starts with knowing what you run.
Get the checklist of the 10 ANSSI ReCyF objectives covered by Uncia. No spreadsheets, no 6-month project.
Prefer to see Uncia in action? Schedule a 30-min demo →
Deployed on your premises; hosted in France on request
-
Your IT system, automatically mapped
Uncia connects to your clouds, virtualisation, CMDB and firewalls to rebuild the application and flow map. Updated with every collection.
-
10 NIS2 obligations covered
The ANSSI ReCyF framework is built in. Gaps are detected with every collection and the audit report is exportable in one click.
-
An incident, its impact in a few clicks
When an incident hits, you identify the affected applications and flows in a few clicks: what you need to notify the regulator within the 24h / 72h window.
The regulatory stake
What the NIS2 directive asks for
-
Sectors in scope
18
Annexes I and II of the directive, generally from 50 employees or €10M revenue.
-
Incident notification deadlines
24 h / 72 h
Early warning within 24 hours, notification within 72 hours (Article 23).
-
Minimum fine ceiling member states must set
€10M
Or 2% of worldwide turnover for an essential entity (Article 34).
Source: Directive (EU) 2022/2555, EUR-Lex, accessed October 29, 2026. Figures checked October 29, 2026.
Technical proof
The 10 ReCyF objectives Uncia covers
Synthesis of the ANSSI Cybersecurity Reference Framework objectives directly addressed by the platform.
- No. 01
IT system inventory
List activities, services and supporting IT systems.
Uncia: Auto inventory from your tools.
- No. 02
Governance and ISP
Run a compliance gap analysis, track an action plan.
Uncia: Compliance dashboard, exportable plan.
- No. 03
Ecosystem control
Trace third parties and their access.
Uncia: Map of third parties and their flows.
- No. 05
IT system mastery
Components, owners, dependencies.
Uncia: Application map by criticality.
- No. 07
Architecture security
Segmentation, zoning, defence in depth.
Uncia: Auto-documented zoning, gaps detected.
- No. 12
Incident response
Notify the regulator within 24h / 72h.
Uncia: Impact view: affected applications and flows.
- No. 13
Business continuity
Critical IT systems, dependencies, tested recovery.
Uncia: Dependency tree, impact scenarios.
- No. 16
Risk-based approach
Risk analysis per critical IT system.
Uncia: Per-asset criticality, feeds EBIOS RM.
- No. 17
Security audit
Regular audits, recommendations tracked.
Uncia: Structured, sourced reports, updated with every collection.
- No. 20
Security monitoring
Centralise security events.
Uncia: Unified view of assets and their vulnerabilities.
Source: France's Cybersecurity Reference Framework (ReCyF), published by ANSSI.
To go further: IT mapping and sourced reports for NIS2, DORA, ISO 27001.
Frequently asked questions
Everything a CISO wants to know about NIS2
What is the NIS2 directive and who is concerned?
NIS2 is Directive (EU) 2022/2555 on cybersecurity. It covers eighteen sectors listed in its Annexes I and II (energy, transport, health, digital infrastructure and more), generally from 50 employees or €10M in revenue. Each member state transposes it into its own law, on its own timetable. Obligations span governance, risk management, IT system security and incident reporting.
What are the NIS2 incident reporting deadlines?
Three milestones: early warning within 24h of detection, incident notification within 72h with an initial impact assessment, final report within 1 month. Without an up-to-date IT system map these deadlines are nearly impossible to meet manually.
What is the financial risk of NIS2 non-compliance?
The directive requires member states to set fines for essential entities with a maximum of at least €10M or 2% of worldwide turnover, whichever is higher, and at least €7M or 1.4% for important entities (Article 34). The actual amounts are set by national law. The directive also holds management bodies accountable.
Ready to face a NIS2 audit with confidence?
30 min to see Uncia cover your 10 critical obligations.