Breach Blast Radius

mental-model

A breach is only the starting point; its real damage depends on where the exposed credential can travel. Reusing a password turns otherwise separate accounts into one shared security boundary.

The account you care about least may be the one that unlocks everything else. A lightly protected app becomes consequential when its password also fits your important accounts.

E1

The password carries the breach

Attackers do not need the first compromised service to matter. They need its leaked credentials to work somewhere that does. password-reuse creates that bridge: one breach supplies a username-password pair, and credential-stuffing tests the pair against unrelated services. What looked like several independent accounts was actually a single security boundary. The blast radius is therefore determined less by the breached app’s importance than by the credential connections leading away from it.

E1

Where it shows up

The disposable account that was not disposable

Using the same password on an “easier,” less important account lets a breach percolate into later attacks. The weak service is merely the entry point; the consequential failure occurs when shared credentials carry access toward primary accounts. This is blast-radius expressed through identity rather than infrastructure.

E1

Exposure does not guarantee propagation

This model concerns damage caused by credential overlap. A breached service can still expose data or enable other attacks even when its password is unique, but the specific path described here breaks when the stolen credential cannot authenticate anywhere else.

E1

Cut the highest-value connection

Tomorrow, choose your most important account and replace any password it shares with another service. Start with email or whichever account controls recovery for the rest: separating that credential removes a direct route from a minor breach to a major one.

E1

Episodes that teach this