NIS2
Evidence readiness for NIS2 — scoped, fresh and explicit about limitations.
The directive emphasizes incident handling, continuity, recovery and assessment of control effectiveness. AegiFlow records technical evidence for those conversations; it does not certify compliance or replace legal advice.
GoTe now
GoTe nowGoTePrivate beta · operator-assisted
- Traffic
- Checking current route
- Protection
- Unknown
- Runtime
- Unknown
- Scope
- Not verifiable
- Traffic proof until
- Not verifiable
Current state is shown only after a fresh, schema-validated snapshot is loaded.
Open status evidence01
What NIS2 expects, and what AegiFlow records
A practical mapping between the directive's technical measures and the operational evidence the platform keeps.
| NIS2 measure (Art. 21) | AegiFlow evidence |
|---|---|
| Incident handling | Correlated cases with one accountable timeline: signals, decisions, actions and outcomes, retained for audit. |
| Business continuity and crisis management | Signed static bundles record approved public content. Independent activation is still a required production gate. |
| Backup management and disaster recovery | Technical drill receipts exist; their current count and freshness come from the validated snapshot. Login, checkout and apex recovery are not yet demonstrated and remain explicit limitations. |
| Supply-chain security | A signed, read-only software inventory matched against public advisories with exact package versions. |
| Effectiveness assessment | Delivery stage and runtime health are independent. A failed or expired check becomes Degraded, Stale or Unknown rather than reusing a previous green state. |
AegiFlow provides operational evidence, not legal advice. The compliance determination and reporting duties remain with your organization and its advisors.
Bring your web services under evidence.
Start without changing traffic and build the operational record NIS2 conversations ask for.