FEATURED INCIDENT · OCTOBER 2026

PHP2Shell. 72 hours to decide.

A critical PHP vulnerability. An incomplete inventory. A CEO who wants zero downtime. The better decision still has a price.

5 decisions · 7–9 minutes · No login · No live exploits
THE BIG RED BUTTON · CONTROL ROOMSIMULATED TELEMETRY

Enable emergency PHP exposure controls

Toggle the control. Watch what disappears, what remains, and what costs the business.

SECURITY ON · CONTROL ACTIVE

Interim restrictions reduce some attack paths while patching proceeds.

Suspicious execution alerts
37

Investigate: alerts are not confirmed compromise

Blocked requests under review
12

Some may be legitimate customer traffic

Known public assets covered
96%

Remaining inventory is unverified

Planned patch maintenance
4h

Downtime and regression testing still required

Cost of keeping this control ON

WAF and restrictions are not equivalent to patching; verify the fixed runtime.

Illustrative numbers only. Alerts are not confirmed incidents. Green means a control is active, not that your organization is safe.

THE DECISION LAB
—recorded site visits
—recorded scenario completions
5interactive scenarios

Counts reflect recorded sessions and completions only when the live counter is connected; never fabricated.

MAKE THE CALL

Five incident rooms. No perfect answers.

Choose a scenario, switch a control and experience the consequences.

All decisions →
THE SECURITYOFF PRINCIPLE

Security ON is not the end of the story.

Controls reduce exposure. They also introduce downtime, costs, friction, exceptions and governance obligations. Our scenarios make both sides visible.

How the lab works →