Access Official Technical PDF

Share Summary:LinkedInEmail

Cyber resiliency engineering gives industrial organizations a way to design and manage systems with the expectation that cyber defenses may be breached. For automation engineers, system integrators and plant leaders, the goal is not simply to prevent every incident. It is to help systems anticipate, withstand, recover from and adapt to adverse conditions while sustaining essential operations where possible.

This perspective matters because industrial systems depend on interconnected cyber resources, including control, communication and information technologies. A cyber event can affect more than a single device or application: consequences may reach system operations, business processes and the organization’s wider mission. A systems engineering approach brings those dependencies and consequences into decisions made across the system life cycle.

What cyber resiliency means for industrial systems

Cyber resiliency is the ability of a system that uses or depends on cyber resources to anticipate, withstand, recover from and adapt to adversity. That adversity can include cyber-attacks, compromises, faults, failures and human errors. The approach assumes that an adversary may get past existing defenses or remain undetected in a system for an extended period.

This assumption distinguishes cyber resiliency from a strategy focused exclusively on keeping attackers out. Prevention remains important, but engineering decisions also consider how a system behaves when protections fail. Depending on stakeholder needs and risk tolerance, the system may need to preserve mission-essential functions in a degraded state, recover functionality after disruption or adapt to changed conditions.

Resilience also depends on more than software. Hardware, networks, data, people, processes and facilities can all affect whether an operation can continue. A resilient software design, for example, cannot by itself compensate for unavailable personnel, fragile communications or an inaccessible production facility. Assessment therefore needs to consider the system and its operating context as a whole.

Cyber resiliency engineering across the system life cycle

NIST’s systems security engineering approach treats cyber resiliency as part of structured life-cycle work, rather than a measure added only after a system is built. Teams can consider it when defining stakeholder needs and system requirements, developing architecture and design, implementing and integrating components, verifying and validating the system, and planning operation, maintenance and disposal.

Applying the approach throughout these stages helps connect protection needs to engineering decisions. It also creates traceability and evidence that can support risk-informed choices and trade-offs. For industrial organizations, that means cyber resiliency can be considered during development of a new system, an upgrade or the repurposing of an existing one.

The guidance is intended to be tailored, not applied as a fixed recipe. Organizations can select and adapt relevant concepts to their technical, operational and threat environments. The processes can be used with different development methods, including waterfall, spiral or agile, and at different points in a system’s life cycle. The appropriate scope depends on stakeholder and mission needs, organizational capability, and cost, schedule and performance considerations.

How to select and prioritize resiliency measures

A useful starting point is to establish the context for the system and the consequences of disruption. Teams can then identify which cyber resiliency outcomes matter most and assess possible engineering alternatives against the organization’s risk management strategy. This avoids treating every system or threat as if it had identical requirements.

In practice, analysis can consider:

  • Stakeholder protection needs: Identify the assets and functions that need protection and the consequences stakeholders regard as unacceptable.
  • System characteristics: Account for the system’s purpose, architecture, operating environment and relationships with other systems.
  • Risk and threats: Consider relevant adversary capabilities and the possibility of faults, failures or errors that may produce similar operational effects.
  • Interactions between measures: Examine potential conflicts and synergies among selected resiliency constructs, as well as their relationship to other engineering disciplines and existing investments.
  • Evidence for decisions: Compare alternatives and document the reasoning behind recommendations so decision-makers can understand the associated trade-offs.

This is an analytical process, not a checklist exercise. A measure that supports one objective may have implications for another, and its value depends on where and how it is applied. The engineering team’s task is to assess options in context and recommend an approach aligned with protection needs and accepted risk.

Why an engineering approach supports better decisions

Integrating cyber resiliency with systems engineering helps organizations connect security requirements to system functions, architecture and operations. It also makes risk management a shared concern across technical and organizational perspectives: teams may need to consider project risk, operational risk, enterprise cyber risk and requirements arising from policies or regulations.

For industrial automation, this provides a structured way to ask practical questions: Which functions must remain available? What kinds of disruption are relevant to this system? Where could a design change reduce exposure or support recovery? What evidence is needed to compare options? The answers should come from the system’s purpose, environment and stakeholder priorities—not from assuming that one set of controls fits every facility.

Use the current NIST publication

The 2019 edition of NIST Special Publication 800-160, Volume 2, described in the supplied material, was withdrawn on December 9, 2021. NIST states that it was superseded in its entirety by SP 800-160, Volume 2, Revision 1. Organizations consulting the framework should use the current revision and verify publication status before relying on older copies.

Conclusion: design for disruption, not only prevention

Cyber resiliency engineering expands industrial cybersecurity planning beyond the perimeter of prevention. By integrating protection needs, risk analysis and resiliency considerations into system life-cycle decisions, organizations can evaluate how systems should respond when adverse conditions occur. The practical priority is to tailor engineering work to essential functions, operating context and stakeholder risk tolerance—and to support decisions with clear analysis and evidence.

Access Official Technical PDF

About The Author