Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?
Stakeholders / Everyone with PHP in the path / Agencies and CERTs / EU and member-state CERTs
EU and member-state CERTs: its risk register
CERT-EU, CERT-FR, NCSC-NL, CERT.LV, ACN, BACS and the CSIRTs that receive incident reports under NIS2 and the Cyber Resilience Act.
Kind group · Assigned here 5 · In its register 5
The register
Assigned here, or arriving through a part of this stakeholder. The part played is the one recorded for whoever holds the assignment.
| Risk | Rating | Kind | Part played | Controls |
|---|---|---|---|---|
| R04-1 National government services offline | 20 critical | Operational | informer | NIS2 Art.21(2)(c), ISO/IEC 27001 A.5.29, NIST CSF 2.0 RC.RP-01 |
| R01-6 Products that embed PHP stay vulnerable while their suppliers investigate | 16 high | Supply chain | informer | Cyber Resilience Act Art.13, Cyber Resilience Act AnnexI.II, OWASP Top 10s A03:2025, NIS2 Art.21(2)(d) +4 |
| R06 A compromise becomes a reportable breach | 15 high | Compliance | regulator | GDPR Art.32, GDPR Art.33, GDPR Art.34, NIS2 Art.23 +2 |
| R06-2 Essential and financial entities miss their reporting clocks | 12 high | Compliance | regulator | NIS2 Art.23, NIS2 Art.20, DORA Art.19, DORA Art.10 +1 |
| R06-3 Manufacturers under the Cyber Resilience Act owe a 24-hour report | 12 high | Compliance | regulator | Cyber Resilience Act Art.14, Cyber Resilience Act Art.13, Cyber Resilience Act Art.24, Cyber Resilience Act AnnexI.II |
Where its risks sit
The standards its register touches
Cyber Resilience Act (4), NIS2 (4), DORA (3), GDPR (3), ISO/IEC 27001 (2), NIST CSF 2.0 (2), OWASP Top 10s (1), SOC 2 (1), NIST SP 800-53 (1)