Two different questions
A vulnerability assessment asks whether a system has a weakness and under what conditions it can be reached. An incident investigation asks whether suspicious activity occurred, what systems or data may be involved, and what actions are needed to contain and recover. The evidence and people required are different.
The PHP project published fixes for two critical vulnerabilities in October 2026, and CISA’s KEV catalogue records known exploitation. Those facts raise the importance of checking a deployment. They do not prove that a particular organisation was attacked or that a particular system was breached. PHP project security advisory: critical remote code execution vulnerabilities, 21 October 2026
When a vulnerability check is the right starting point
If the concern is that the application may run an affected package, but there are no known signs of suspicious activity, begin by identifying the PHP setup, provider package, deployment mode and applicable fix. A scoped assessment can validate whether the relevant condition applies, document reachable exposure and prioritise remediation. Do not describe that result as a forensic clearance.
When to escalate as a suspected incident
If monitoring, a provider or a staff member identifies unexplained system changes, processes, accounts, access, outbound connections or other indicators, contact the incident lead. If the business has no incident lead, contact the hosting or IT provider and ask for qualified incident-response help. These examples are prompts for escalation, not proof that PHP2Shell caused the activity. Record who observed what and when.
Preserve evidence and coordinate decisions
Incident response should be coordinated with the people responsible for security, infrastructure, the application, legal/compliance and business operations as appropriate. Preserve relevant logs and evidence in line with the organisation’s process and specialist guidance. Containment actions can affect evidence and service availability, so decisions should be made by the incident lead with the technical owners. NIST’s current incident-response guidance frames response as part of ongoing cybersecurity risk management. NIST SP 800-61 Rev. 3
Applicable notification duties depend on the organisation, jurisdiction and incident facts. In India, CERT-In reporting requirements may apply to specified cyber incidents; assess the current directions with the responsible compliance owner rather than assuming that a vulnerability alert itself triggers a report. CERT-In directions under section 70B
Patching is necessary, but it is not a forensic conclusion
Apply the relevant security fix through the vendor’s process and verify that the production runtime is updated. If compromise is suspected, also determine whether historical evidence needs review and whether credentials, keys or connected systems require action. A routine scan or retest checks selected technical conditions; it does not establish that no earlier access occurred.
Choose the right engagement
The proposed Bravewall PHP Application Security Check covers a scoped assessment, prioritised reporting, remediation guidance and a retest of agreed fixes. It is intended for organisations of any size that operate PHP applications and is designed for vulnerability validation. Suspected compromise requires a separate incident-response owner, authorisation, evidence-handling process and scope; this service page does not promise that response capability.

