Abstract
Currently, perimeter-based approaches are the mainstay of cybersecurity. While this paradigm is necessary, there is mounting evidence of its insufficiency with respect to sophisticated and coordinated attacks. In contrast to perimeter-based security, mission-centric cybersecurity provides awareness of how attacks can influence mission success and therefore focuses resources for mitigating vulnerabilities and protecting critical assets. This is strategic as opposed to tactical perimeter-based cybersecurity. We propose MISSION AWARE, which assists in the identification of parts of a system that destabilize the overall mission of the system if compromised. MISSION AWARE starts with a structured elicitation process that leads to hazards analysis. It employs hierarchical modeling methods to capture mission requirements, admissible functional behaviors, and system architectures. It then generates evidence—attacks applicable to elements that directly correlate with mission success. Finally, MISSION AWARE traces evidence back to mission requirements to determine the evidence with the highest impact relative to mission objectives.
Introduction
Traditional cybersecurity for Cyber-Physical Systems (CPS)—such as power grids, autonomous vehicles, and industrial controls—often relies on "perimeter-based" defenses. These methods utilize firewalls, encryption, and compliance checklists to harden system boundaries. However, such approaches are frequently "mission-blind," treating all vulnerabilities with equal weight regardless of their actual impact on the system's core purpose.
Furthermore, security is often treated as an afterthought in the development lifecycle. Research indicates that 70-80% of decisions affecting a system's safety and security are made during the initial concept phase. MISSION AWARE addresses this gap by providing tools for early-stage "what-if" security analysis using the same systems engineering language (such as SysML) used to design the system's functions.
The MISSION AWARE Methodology
The MISSION AWARE approach integrates systems theory, model-based engineering, and graph theory into a unified workflow designed to shift focus from protecting the perimeter to protecting the mission.
Hierarchical Modeling
At the core of the methodology is a hierarchical modeling framework. The system is modeled across three distinct domains to ensure traceability:
- Mission: High-level objectives and unacceptable losses.
- Behavioral: The functions required to achieve those objectives.
- Architectural: The physical and logical components (hardware and software) that implement those functions.
This structure creates a traceable path from a physical component to a high-level mission goal, allowing engineers to understand the mission-level consequences of a technical compromise.
The MISSION AWARE Workflow
The complete workflow consists of several integrated steps that bridge the gap between stakeholder needs and technical vulnerabilities:
- Stakeholder Elicitation: Analysts interview mission owners to define "unacceptable losses" and mission goals.
- Systems-Theoretic Analysis (STPA-Sec): Using the STAMP framework, the team identifies hazardous control actions that could lead to mission failure.
- Graph Metamodels: SysML models are converted into mathematical graphs, enabling algorithms to identify "attack chains" and "impact traces."
- Evidence Mapping: The methodology automatically queries public vulnerability repositories (CVE, CWE, CAPEC) to map relevant threats to specific architectural components.
Key Insights
- Security as a Control Problem: MISSION AWARE treats security like a safety problem. It asks: "What constraints must we enforce on system behavior to ensure the mission succeeds, even if an adversary is present?"
- Filtering Noise: By utilizing architectural and operational context, the framework filters out irrelevant vulnerabilities from public databases, allowing analysts to focus on the small subset of threats that truly jeopardize the mission.
- Thinking in Graphs: While defenders often think in lists (checklists, inventories), attackers think in graphs (lateral movement, dependencies). MISSION AWARE forces defenders to adopt this graph-based perspective.
Case Study: Military UAV
The authors evaluated the methodology using a military UAV reconnaissance mission. The analysis successfully identified mission-critical subsystems—specifically the GPS, XBee radio, and camera. By tracing vulnerabilities to mission impact, the tool demonstrated that a vulnerability in the radio module was significantly more critical than one in the camera, as the former could lead to a total loss of the vehicle, whereas the latter only impacted imagery quality.
Conclusion and Future Work
MISSION AWARE provides a strategic framework for prioritizing cybersecurity efforts based on mission impact rather than just technical severity. While the current evidence-based portion relies on public databases of known threats, future work aims to incorporate "cause-agnostic" analysis. This would simulate functional loss regardless of the cause (e.g., cyberattack vs. hardware failure), moving the field toward a broader "resilience engineering" paradigm where systems are designed to survive any disruption.
Summary updated