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 / Communications team

Communications team: its risk register

Says why the site is down without saying more than is known.

Kind role · Assigned here 2 · In its register 2 · the briefing for a media and communications team

The register

Assigned here, or arriving through a part of this stakeholder. The part played is the one recorded for whoever holds the assignment.

RiskRatingKindPart playedControls
R04 Services lost to precautionary shutdowns20 criticalOperationaltreaterISO/IEC 27001 A.5.29, ISO/IEC 27001 A.5.30, NIS2 Art.21(2)(c), DORA Art.11 +2
R04-2 Councils and police offline without saying why15 highReputationaltreaterCyber Essentials SUM, NIST CSF 2.0 RS.CO-03, ISO/IEC 27001 A.5.24

Where its risks sit

Likelihood / impact1 Minor2 Moderate3 Significant4 Major5 Severe
5 Happening5 10 15 R04-220 R0425
4 Likely4 8 12 16 20
3 Possible3 6 9 12 15
2 Unlikely2 4 6 8 10
1 Rare1 2 3 4 5

Who it shares risks with

Governments and public services (1), People who need a service that went offline (1), Agencies and CERTs (1), Board and executives (1), Local councils (1), UK NCSC (1)

The standards its register touches

ISO/IEC 27001 (3), NIST CSF 2.0 (2), NIS2 (1), DORA (1), NIST SP 800-53 (1), Cyber Essentials (1)