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 / Platform engineers and developers
Platform engineers and developers: its risk register
Find every PHP runtime, upgrade it, rebuild the images and prove it is done.
Kind role · Assigned here 4 · In its register 4 · the briefing for a php or platform engineer
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 |
|---|---|---|---|---|
| R09 Not knowing where PHP runs | 16 high | Operational | treater | NIST CSF 2.0 ID.AM-02, NIST SP 800-53 CM-8, CIS Controls 16.4, DORA Art.8 +2 |
| R01-1 Default Apache mod_php installations exploited before application code runs | 15 high | Security | treater | ISO/IEC 27001 A.8.8, CIS Controls 7.4, Cyber Essentials SUM, PCI DSS 6.3.3 |
| R01-4 The fix is incomplete, or a third flaw follows | 15 high | Security | bearer | NIST SSDF RV.3, NIST SSDF PW.8, ISO/IEC 27001 A.8.29, ISO/IEC 29147 and 30111 30111:handling |
| R06-3 Manufacturers under the Cyber Resilience Act owe a 24-hour report | 12 high | Compliance | treater | 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), ISO/IEC 27001 (3), CIS Controls (2), NIST SSDF (2), Cyber Essentials (1), PCI DSS (1), ISO/IEC 29147 and 30111 (1), NIST CSF 2.0 (1), NIST SP 800-53 (1), DORA (1)