A week of stolen patient records, and the three-way trade-off behind every breach

The three jobs

Strip away the acronyms and every security decision comes down to three goals. Keep the data secret, so only the right people see it. Keep it correct, so no one can quietly change it. Keep it reachable, so the people who need it can get to it. Secrecy, correctness, reachability. Almost every attack in the news is an attack on one of the three.

A data breach steals secrecy. Ransomware scrambles files and takes away reachability. A supply-chain attack, where someone slips bad code into software everyone trusts, ruins correctness. Different names, same three targets.

They pull against each other

Here is the catch that most people miss: you cannot have all three at their best at once. They trade off.

Lock a system down with tight access checks and extra passwords, and you protect secrecy - but you also make it slower and harder to reach in a hurry. Keep spare copies of everything so nothing is ever lost, and you protect reachability. But now the secret data sits in more places, each one a fresh door to guard. Run strict checks on every change to protect correctness, and everything gets slower. Push hard on any one goal and you spend from the other two.

So a defender is never really choosing “how secure.” They are choosing which kind of secure - and against what.

What you are protecting decides the winner

That choice is not free-floating. It follows what the data is for.

A bank cares most about correctness. A slow transfer is annoying; a leaked balance is bad; but a balance that is silently wrong is a disaster. A spy agency cares most about secrecy - it would rather lose access to a file than let the wrong person read it. A hospital cares most about reachability, because a patient record locked away during an emergency can cost a life. Same three dials. Different settings, for good reasons.

The leg you leave leaner is where the break-in lands

Now look at this week. Health care leaks more patient data than any other sector, and the reason sits right in that trade-off. A hospital pours its money and design into staying up. The secrecy of its records gets the thinner budget - and secrecy is exactly the leg that broke.

Madera hospital, 150,000 people. Brown Health, 311,000. A billing firm, 3.8 million. Amgen, patient data pulled from its cloud. Not because anyone was careless, but because the goal these places guard hardest is not the one the attackers went for. The attacker gets to pick the leg. They aim at the one you left leaner - the ransomware crew at your reachability, the breach at your secrecy, the poisoned code at your correctness.

You are inside this, not above it

You are a node in this, not a spectator. Your medical records sit inside a system built to stay running, not built to keep you secret - and that setting was chosen before you ever walked in. You feel the leak; you never sat at the table where the dials were set.

And you turn the same dials yourself. Every time you skip a second login check because it is slower, you trade a little secrecy for a little reachability. That is the exact swap the Snowflake victims made - the one that let a single stolen password reach a hundred million people’s records. There is no setting that wins on all three. The defender who believes they have locked down everything has usually just not yet been tested on the one they quietly let go.