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 / Organisations running PHP / Inside any one organisation / Board and executives
Board and executives: its risk register
Accountable under NIS2 Article 20 and DORA; decides whether to take a service offline.
Kind role · Assigned here 5 · In its register 5 · the briefing for a board member or executive
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 Services lost to precautionary shutdowns | 20 critical | Operational | owner | ISO/IEC 27001 A.5.29, ISO/IEC 27001 A.5.30, NIS2 Art.21(2)(c), DORA Art.11 +2 |
| R06 A compromise becomes a reportable breach | 15 high | Compliance | owner | GDPR Art.32, GDPR Art.33, GDPR Art.34, NIS2 Art.23 +2 |
| R03-3 Exploited in the wild without anyone being able to show it | 12 high | Governance | owner | CISA KEV and BOD 22-01 KEV-entry, NIST CSF 2.0 ID.RA-02, NIST CSF 2.0 GV.RR-01 |
| R04-3 The agencies' advice disagrees | 12 high | Governance | owner | ISO/IEC 27001 A.5.5, NIST CSF 2.0 GV.RR-01, NIS2 Art.20 |
| R07 Decisions made on numbers that measure something else | 12 high | Governance | owner | NIST CSF 2.0 GV.RM-01, ISO/IEC 27001 6.1.2, OWASP Top 10s LLM09:2025 |
Where its risks sit
The standards its register touches
NIST CSF 2.0 (4), ISO/IEC 27001 (4), NIS2 (3), GDPR (3), DORA (2), CISA KEV and BOD 22-01 (1), NIST SP 800-53 (1), Cyber Resilience Act (1), OWASP Top 10s (1)