Cyber resiliency engineering starts from a practical premise: security controls matter, but organizations cannot assume every intrusion will be prevented. For industrial automation environments, where control systems support essential operations, the engineering challenge is to prepare systems to withstand disruption and continue critical functions—even if operating capability is degraded.
NIST Special Publication 800-160, Volume 2, presents cyber resiliency as a systems engineering concern that can be integrated with risk management and life cycle processes. Its draft was withdrawn in November 2019 and superseded by the final November 2019 publication. The approach is relevant to organizations developing, upgrading, acquiring, or operating systems that depend on cyber resources.
What cyber resiliency means for industrial systems
Cyber resiliency is the ability to anticipate, withstand, recover from, and adapt to adverse conditions, stresses, attacks, or compromises affecting systems that use or depend on cyber resources. This extends beyond preventing unauthorized access. It asks whether a system can still deliver its mission-essential functions when safeguards fail, a component malfunctions, or an adversary remains inside the environment.
In a plant, cyber resources may be part of the systems used to monitor and control operations, as well as the supporting systems on which those functions depend. A cyber incident can therefore have consequences at several levels: within a system, across an operational or business process, and for the organization’s ability to meet its objectives. Resiliency planning connects those levels instead of treating cybersecurity as an isolated IT activity.
The approach assumes that sophisticated adversaries may breach defenses and establish a presence that goes undetected. That assumption shifts planning from “How do we keep every attack out?” to questions such as: Which functions must continue? What level of degraded operation is acceptable? How will the organization recognize and respond to compromise? What must be restored first?
Cyber resiliency engineering across the system life cycle
Resiliency is most useful when it is considered as part of engineering and operational decisions—not added as a separate exercise after a system is deployed. NIST’s framework is intended to work alongside systems security engineering and risk management. It can be applied to new systems, upgrades, and repurposed or already-operating systems, at different stages of the life cycle.
This makes the approach applicable to different development methods and organizational contexts. Teams can tailor the activities to their system, operating environment, stakeholder needs, and available resources. The goal is not to apply every possible measure everywhere. It is to make risk-informed choices that balance protection needs with cost, schedule, and performance.
Connect protection needs to operational priorities
Start by identifying the missions, business functions, and assets that matter most, along with the consequences of their loss or disruption. For an industrial organization, this means involving both technical and operational stakeholders: engineering, operations, maintenance, security, and those accountable for business continuity. Their input helps clarify which capabilities are essential and what forms of degraded operation may be tolerable.
These priorities inform system requirements and design decisions. They also help teams distinguish between a security measure that is generally desirable and one that addresses a defined operational risk. A traceable link between stakeholder needs, requirements, design choices, and risk decisions makes trade-offs easier to explain and revisit.
Use a framework, not a fixed recipe
NIST describes a set of related cyber resiliency constructs: goals, objectives, techniques, implementation approaches, and design principles. Together, these provide a way to frame desired outcomes, consider ways to achieve them, and incorporate the relevant choices into system design and analysis.
Organizations can select and adapt the constructs that fit their circumstances. The selection should reflect the type of system, the organization’s risk management strategy, the threats and operating environment, and any existing investments or requirements. Teams should also consider potential conflicts and synergies among design choices, as well as where in the system architecture a measure would be applied.
Make analysis part of the decision process
Cyber resiliency engineering is not simply a list of controls to implement. It is a structured analysis process that helps organizations compare options and make decisions based on context. A practical sequence is to:
- Understand the context: Define the system, its operating environment, stakeholder needs, and the risks that could affect essential functions.
- Establish a baseline: Record the system’s existing resiliency measures and the assumptions behind its current design or operation.
- Analyze the system: Examine how system elements and dependencies contribute to mission or business functions, and where compromise, failure, or disruption could have consequences.
- Compare alternatives: Assess relevant design or operational options against protection needs, risk, and practical constraints.
- Develop recommendations: Document the preferred choices and the reasoning and evidence that support them.
This sequence can support both engineering projects and reviews of installed systems. It also creates a basis for revisiting decisions as system requirements, operational needs, or the threat environment change.
Practical implications for industrial decision-makers
For plant managers and operations leaders, the central question is how to sustain essential work through disruption—not whether every component can operate normally in every circumstance. For engineers and integrators, that question becomes a set of system requirements and design trade-offs. For security and risk leaders, it provides a way to connect technical protections to organizational consequences.
Applying the approach does not require treating every asset as equally critical or adopting every available resiliency measure. It requires a clear understanding of priorities, a deliberate selection of relevant engineering constructs, and evidence that supports risk-informed decisions. Those activities can be integrated into system development, upgrades, and ongoing risk management.
Conclusion
Cyber resiliency engineering complements prevention-focused cybersecurity by planning for the possibility that attacks, faults, or failures will affect system operation. For industrial organizations, its practical value lies in linking stakeholder protection needs to system requirements, architecture, analysis, and life cycle decisions. By prioritizing essential functions and tailoring measures to the operating context, teams can make more deliberate choices about how systems withstand disruption, recover, and adapt.