Glossary
Canonical definitions for Runtime Stability concepts.
Each term below has a precise, citable definition. These are not marketing descriptions. They are technical terms with formal publication backing.
Runtime Stability
A technology framework for structurally maintaining seven Protection Attributes when a computer system faces cyberattacks, failures, or anomalies during execution.
Runtime Stability integrates three protection layers — Traditional Security, Runtime Security, and Runtime Immunity — into a unified evaluation model.
Full definition →Runtime Immunity
A technical system that structurally nullifies the preconditions or outcomes of an attack, maintaining Protection Attributes without halting the system.
Runtime Immunity operates independently of detection. It does not require identifying the attack to neutralize its outcome.
Full definition →Runtime Security
A technical system that detects attacks and unauthorized activities in real time during execution, maintaining the system's Controllability.
Runtime Security is Layer 2 in the Runtime Stability framework. It contributes to Safety, Availability, and Controllability through detection and dynamic response.
Full definition →Inexploitability
The condition in which an attack succeeds structurally but produces no exploitable outcome for the attacker.
Inexploitability is the seventh Protection Attribute in the Runtime Stability Framework — and the most distinctive. No existing security framework has formally defined this concept as a measurable system property.
RS Level (Runtime Stability Level)
A formal evaluation metric combining Security Level (SL) and Immunity Level (IL) to measure a system's runtime protection maturity.
RS = SL + IL. RS ranges from 0 to 6. Detection-based security alone reaches RS-2. RS-5 and RS-6 require Runtime Immunity.
See RS Level matrix →