We're preparing to patch internet-facing PHP systems, but our internal estate includes older versions and applications without clear engineering owners. How would you organize the rollout and assess what needs attention first?
How should we handle a PHP2Shell patch rollout across external and internal systems?
Answers
Start with an inventory that connects each PHP installation to a host, application, exposure level, version, and owner. Check what is actually running, not just what a scanner reports as installed. Then compare it with the advisory's affected configurations before deciding which systems need the patch.
Handle affected internet-facing systems first, then work through internal systems by exposure and risk. Internal does not automatically mean unreachable, but it may change the urgency. Track verification separately from patch deployment so a completed change doesn't get mistaken for a confirmed fix.
Reply to this answer
For the old PHP 5 and 7 applications, the hard part may be ownership rather than the patch itself. Find someone who can make a decision about each app, even if the original engineering team is gone. They need to decide whether to upgrade, restrict access, replace it, or retire it.
Don't assume a current patch is available for an unsupported version. Check the vendor's guidance and document any temporary restrictions along with who owns the longer-term fix.
Reply to this answer
Set up the coverage before the release, not just the warning. Agree who is available to deploy, who can approve changes, who validates them, and when the incident team gets involved. If the release falls outside someone's working hours, arrange on-call coverage rather than assuming they'll stay online.
Reply to this answer
Make the security and operations handoff concrete. Security can identify potentially affected systems and explain the risk, while the teams managing the services check configuration and carry out changes. A version alert is a starting point, not proof that a particular host is exploitable.
There can be disagreement about how practical an exploit is. Use the advisory and your own exposure assessment to set priorities rather than treating either a scary label or a dismissal as the whole answer.
Reply to this answer
Add your answer
Answers are reviewed before publication.
5n+bramblewidget_864:
That ownership list is useful beyond this incident too. An application with nobody able to approve or test a change will keep slowing down future fixes.