The fix existed. The warning went out. Nobody applied it.
Not because it was hidden. Because it belonged to everyone, which meant it belonged to no one.
In March 2017, a critical flaw appeared in the software Equifax ran.
Their own security team emailed staff, instructing them to install the patch within 48 hours. A scan was meant to confirm the fix had landed.
The scan missed it. And in a company that size, closing the loop was everyone's job, which quietly made it no one's.
By the time anyone noticed, attackers had spent over two months inside the network. 147 million records were gone. A congressional report later called the breach entirely preventable.
In 1968, after the murder of Kitty Genovese, psychologists John Darley and Bibb Latané described the bystander effect. The more people who witness a problem, the less likely any single one acts, because each assumes someone else will.
Here is the part that should worry every leader. On a street, the effect is weak. Because everyone can see that no one else is moving, someone eventually steps in. In real-world public incidents, a bystander helps about nine times out of ten.
Inside an organisation, it runs the other way. Nobody can see that everyone else is also doing nothing. The problem sits in a CC line, a shared inbox, a "someone should look at this". Ponemon found 60% of breaches traced to a known flaw with a patch that existed but was never applied.
The danger is rarely that the problem is hidden. It is that the problem is visible to a dozen people and owned by none of them.
A risk everyone can see and no one owns is not being managed. It is simply waiting.
So here's the question worth sitting with:
Who, by name, owns the problem your team has been circling for weeks?
If you can't answer that in one sentence, that's the work. Tell me what you'd do about it.
