Failing badly
Failing badly and failing well are key concepts in systems security and network security describing how a system reacts to failure. These terms have been popularized by Bruce Schneier, a renowned cryptographer and security consultant.[1]
Failing badly
A system that fails badly results in a catastrophic outcome when failure occurs. Examples include:
- Databases protected only by a password. Once breached, all data can be accessed.
- Fracture critical structures that depend on a single component, whose failure can cause a chain reaction collapse.
- Security checks focused solely on identity, allowing suicide attackers to pass.
- Internet access through a single service provider. If the provider's network fails, all connectivity is lost.
- Systems relying on a single person. If this person is absent, the system halts.
- Brittle materials, such as over-reinforced concrete, which fail suddenly under overload.
- Storing data in one central place. The data is lost forever if that place is damaged.
Failing well
A system that fails well contains or compartmentalizes its failure. Examples include:
- Compartmentalized hulls in watercraft to prevent entire vessel flooding.
- Databases limiting data downloads to reduce compromised data.
- Structurally redundant buildings designed to resist loads beyond normal expectations.
- Computer systems that restart or proceed to a stopped state upon invalid operations.
- Access control systems that lock when power is cut.[2]
- Concrete structures showing fractures before breaking, giving early warning.
- Armored cockpit doors on airplanes to confine potential hijackers.[1]
- Multihoming for internet connectivity to ensure redundancy.
- Star or mesh networks that continue operating despite node or connection failures.
- Ductile materials failing gradually under overload, giving warning before ultimate failure.
- Making a backup copy of important data and storing it separately for recovery.
Designing systems to fail well is considered a more effective use of limited security funds compared to attempting to eliminate all potential errors.[3]
See also
- Fail-safe
- Fault tolerance
- Fail-deadly
- Resilience (network)
- Resilience (engineering and construction)
References
- ↑ 1.0 1.1 Homeland Insecurity Archived 2011-09-28 at the Wayback Machine, Atlantic Monthly, September 2002
- ↑ Eric Vanderburg (February 18, 2013). "Fail Secure – The right way to fail". PC Security World. Archived from the original on October 27, 2014. Retrieved November 11, 2014. Unknown parameter
|url-status=ignored (help) - ↑ Failing Well with Information Security Archived 2008-10-14 at the Wayback Machine - Young, William; Apogee Ltd Consulting, 2003
This article "Failing badly" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Failing badly. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
