Taking advantage of rapid recovery features at the system level is part of what secure design principle?
-
Design for survivability
-
Design for secure failure
-
Design for controllability
-
Design for redundancy
Design for survivability means systems can quickly recover and continue operating despite attacks or failures. This principle emphasizes rapid recovery features at the system level, ensuring essential services are maintained. Secure failure (B) focuses on failing safely, controllability (C) on maintaining control, and redundancy (D) on backup components.
'Design for survivability' is the secure design principle focused on ensuring a system can continue operating (or degrade gracefully and recover quickly) under attack or failure conditions, which includes leveraging rapid recovery features at the system level. 'Design for secure failure' is about failing safely/closed rather than about recovery speed. 'Design for controllability' concerns the ability to monitor and manage system behavior, not recovery. 'Design for redundancy' isn't a standard named principle here — redundancy is a technique used in service of survivability, not the principle itself.