Introduction — The Age of "Locks That Don't Hold"

There is a premise that has become conventional wisdom in cybersecurity:

"No matter how strong the lock, it will eventually be picked."

This isn't pessimism. It's the hard-won conclusion of decades of experience across the global security community. So when we accept that the lock will be broken — what should we be preparing for? Two very different approaches are now competing for the answer.

Chapter 1: Cyber Resilience — "The Ability to Get Back Up After Being Hit"

NIST defines Cyber Resilience as "the ability to anticipate, withstand, recover from, and adapt to adverse conditions, stresses, attacks, or compromises on systems that include cyber resources."

Three forces are driving Cyber Resilience into the mainstream: attacks are accelerating, regulators have moved (EU CRA), and the global cyber insurance market reached $20.6 billion in 2025.

Chapter 2: The Cyber Resilience Act — When "Secure by Design" Becomes Law

In December 2024, the EU Cyber Resilience Act entered into force. Full compliance is required by December 2027. Non-compliance penalties reach up to €15 million or 2.5% of global annual revenue. Any company that manufactures, imports, or distributes digital products in the EU must comply — regardless of headquarters location.

Chapter 3: "But Some Machines Can't Stop" — The Case for Runtime Stability

To "get back up," you have to go down first. What about things that can't go down?

Commercial aircraft. Surgical robots. Autonomous vehicles. For these systems, halting is not a failure mode — it is the failure itself. Runtime Stability engineers systems to maintain control under attack, continue operating without halting, and structurally render the attack's outcome meaningless.

Chapter 4: Seven Shields — What Runtime Stability Protects

Runtime Stability defines seven protection attributes: Safety, Reliability, Availability, Controllability, Confidentiality, Data Integrity, and Inexploitability — the condition where an attack "succeeds" but its outcome is worthless to the attacker.

Chapter 5: Not Enemies — Allies on Different Fronts

Cyber Resilience and Runtime Stability are not rivals. They guard different domains. Cyber Resilience protects the organization. Runtime Stability protects the running system.

Chapter 6: Why This Matters Now

The world of "systems that can't stop" is expanding. Organizations that can answer both questions — how quickly can it get back up, and does it have a structure that keeps it from going down — are the ones that will endure.

References
  • NIST SP 800-160 Vol. 2 Rev. 1 — Developing Cyber-Resilient Systems
  • EU Regulation (EU) 2024/2847 — Cyber Resilience Act
  • Runtime Stability Definition v3.2 — Superasystem