TL;DR: Nearly 800 assets and more than 100 accounts were found with PHP instances, Oneleet's case work shows, highlighting how much surface can sit outside audit reporting. Asset discovery has to stay continuous if exposed systems are to be owned, patched, and verified before new vulnerabilities turn them into liabilities.
Editorial analysis by NHI Mgmt Group, based on content published by Oneleet: “PHP2Shell Showed What SOC 2 Was Never Built to Do”.
Key questions
Q: Why do hidden internet-facing assets create such a large risk after a new CVE?
A: Because the patching process cannot start until the asset is found and owned.
Q: How do security teams know if continuous compliance is actually working?
A: Look for shorter time-to-detect on control drift, fewer undocumented exceptions, and access review results that lead to measurable revocation.
Q: What breaks when SOC 2 evidence is treated as real-time security?
A: The main failure is timing.
Practitioner guidance
- Map external attack surface to the asset inventory Compare internet-facing discovery from ASM and dependency scanning against the asset register so hidden PHP instances are not left outside remediation workflows.
- Assign ownership for every critical exposed asset Name a business owner and a technical owner for servers that can be reached from the internet, including legacy PHP hosts and forgotten deployments.
- Verify patch status outside the audit window Check that critical fixes are actually installed on exposed systems rather than assuming a policy, ticket, or scanner result means the issue is closed.
Bottom line: PHP2Shell is a reminder that audit success and operational security are not the same thing when asset discovery is incomplete.
Glossary terms: Audit-window security gap, Shadow IT, Attack Surface Management, Vulnerability Disclosure (Open Source)
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Audit-ready is not security-ready: SOC 2 can prove that a control existed at a point in time, but it cannot guarantee that the same control still protects the environment after disclosure. That distinction matters whenever discovery, inventory, and remediation are decoupled from the audit cycle. Practitioners should treat the report as evidence of governance, not evidence of current safety.
A question worth separating out:
Q: Should organisations rely on SOC 2 alone or pair it with continuous security monitoring?
A: They should pair them. SOC 2 remains useful for governance and evidence, but continuous monitoring is what finds shadow IT, validates exposure, and confirms that critical patches actually landed. Without both, teams can pass an audit while staying vulnerable in production.
👉 Read our full editorial: PHP2Shell exposed the limits of audit-only compliance