1. INTRODUCTION
2. RELATED WORKS
2.1. Literature Review
2.2. Comparative Analysis of Framework
3. SPACE CYBER THREAT MODELING AND RISK ASSESSMENT WITH SPARTA
3.1. Design Principles of Multi-tierd TARA
3.2. Quantitative Baseline for Overlay and Tailoring
3.3. Proof-of-concept with Best Practice
4. CONCLUSION
1. INTRODUCTION
As the cybersecurity paradigm undergoes fundamental transformation within the New Space era, driven by rapid advancements in space technology, major space security agencies are conducting comprehensive reviews of potential vulnerabilities across the space cyber domain. In particular, following the mid-to-long-term evolution of space cybersecurity strategies outlined in Space Policy Directive-5 (SPD-5) [1], nations such as the United States and those in the EU are standardizing cybersecurity guidelines and regulations. These initiatives seek to protect all segments of the space ecosystem, including ground, space, link, and supply chain domains. Moreover, these nations are optimizing total lifecycle security management for mission-critical space infrastructure by implementing targeted security enhancements that prioritize resilience-oriented strategies giving the advantage to defenders.
To strategically implement Defense-in-Depth (DiD) and Secure-to-Build (S2bD) principles in s pace cybersecurity, frameworks such as SPARTA [2] and SPACE-SHIELD (Space Attacks and Countermeasures Engineering Shield) [3] have been developed. These frameworks, built on MITRE ATT&CK [4] and MITRE D3FEND [5], integrate space-specific TTPs (Tactics, Techniques, and Procedures) and security controls tailored for the space domain.
However, current advancements in space cybersecurity focus primarily on countering exploits targeting low-Earth orbit (LEO) CubeSat protocols and data. Vulnerability analyses of Ground Control Stations (GCS) and third-party supply chains remain limited, primarily identifying potential attack surfaces rather than offering comprehensive mitigation strategies. Furthermore, existing defense approaches rely heavily on traditional security measures such as network segment ation, access and device control, end-to-end encryption (E2EE), and public key authentication, as specified by CCSDS (Consultative Committee for Space Data Systems) [6]. While these methods provide foundational security, they fail to adequately address the growing sophistication of cyber threats in the New Space environment [7].
Without comprehensive total lifecycle security management to counter increasing latent vulnerabilities, space infrastructure will face significant risks from state-sponsored cyber threats. To effectively neutralize the defender-inferior spatiotemporal asymmetry, space threat modeling must adopt Model-Based Systems Engineering (MBSE) methodologies. This approach should be tailored to support Independent Verification & Validation (IV&V) [8] within Space-DevSecOps (Development, Security, and Operations) processes.
Accordingly, this study proposes a Multi-Tiered Space Cyber TARA (Threat Analysis and Risk Assessment) framework integrating Knowledge Management (KM) [9], Cyber Threat Susceptibility Assessment (CTSA) [10], and Cyber Risk Remediation Assessment (CRRA) [11]. This app roach quantifies Security Risk (SR) based on the impact of each threat and Security Mitigation (SM) based on the effectiveness of countermeasures. Additionally, sensitivity analysis is performed on cyber engagement scenarios within the space supply chain, providing a compliance-based Proof-of-Concept (PoC) to validate the proposed method.
The remainder of this paper is organized as follows: Section 2 reviews the state-of-the-art in space cybersecurity, focusing on existing space TTP-based frameworks and their comparative analysis. Section 3 presents a custom TARA-based threat modeling approach, assessing the effectiveness of cyber attack and defense strategies using space supply chain scenarios. Finally, Section 4 discusses insights from the PoC and concludes the study.
2. RELATED WORKS
This section examines the current state of space cybersecurity across different countries while analyzing precedents of TTP-based space-specific cybersecurity frameworks that provided foundational insights for this study.
2.1. Literature Review
This section initially analyzes developments in the United States, which has emerged as a first- mover in the space cybersecurity domain. In response to the Call-to-Action (CTA) under SPD-5, NIST, in collaboration with MITRE, established cybersecurity standards to ensure S2bD and DiD within the space cyber domain. These standards include NISTIR 8270 [12], NISTIR 8323 [13], NISTIR 8401 [14], and NISTIR 8441 [15], each of which addresses specific security aspects. For example, NISTIR 8270 ensures the secure operation of commercial satellite platforms through collaboration with private vendors. NISTIR 8323 aims to identify cyber risk factors in PNT (Positioning, Navigation, and Timing) infrastructure. NISTIR 8401 establishes detailed security requirements and countermeasures for ground stations a nd end users. NISTIR 8441 proposes a dedicated security framework and profiling mechanisms for hybrid constellation satellites that provide deep-space internet services. Additionally, NASA, leveraging MITRE ATT&CK, developed the BPG (Best Practice Guide) [16] to operational ize space security controls and established NASA-STD-1006A [17], a guideline for space system security requirements and resilience profiling. To manage DevSecOps for emerging New-Space platforms, NASA internally established the C-SCRM (Cybersecurity Supply Chain Risk Management) agency and contributed to the creation of Space-ISAC (Information Sharing and Analysis Center) [18]. This initiative facilitates the inter national sharing of space Cyber Threat Intelligence (CTI) and IoC using STIX (Structured Threat Information Expression) [19] and TAXII (Trusted Automated Exchange of Intelligence Information) [20]. Furthermore, Aerospace Corporation is actively operating MoonLighter [21] in orb it, a practical CubeSat integrated with Hack-a-Sat [22], to enhance space cyberrange capabilities and specialize in space CTI. The corporation has also, in collaboration with MITRE and NASA, further formalized SPARTA, a TTP-based space cybersecurity framework, and Space C-SoC (Cybersecurity Operations Center), an IoC-driven space cybersecurity monitoring platform.
Subsequently, this section analyzes developments in the EU and the UK, which have establish ed themselves as independent fast-followers in the space cybersecurity domain. The ESA initiated multiple space cybersecurity projects under ARTES-4S [23]: Space Cyber Range [24]: A research initiative focused on constructing a space cybersecurity training environment and automating satellite penetration testing. 4SSTB [25]: A project dedicated to automating satellite security management. CCSDS SDLS (Space Data Link Security) [26]: A protocol designed to enhance secure satellite communications. INT-UQKD [27] and Caramuel [28]: Projects aimed at developing quantum cryptographic architectures for ground stations. Furthermore, through collaboration with NASA, ESA published the Bulk Security [29] and Bundle Protocol [30] standards to enhance GovSATCOM [31] security for IRIS2 [32]. Additionally, under the CASSINI [33] project, ESA contributed to the establishment of EU Space-ISAC [34] within EUSPA. Notably, prior to Aerospace Corporation’s SPARTA, ESA had already proposed SPACE-SHIELD, a MITRE ATT&CK-based space cybersecurity framework, structuring it for use in EU Space C-SoC. To evaluate draft security solutions and detailed algorithms, ESA initially operated the low-orbit CubeSat OPS-SAT [35], later expanding its scope with CyberCube [36]. Concurrently, the UK, led by UKSA and NCSC, developed the CAF (Cyber Assessment Framework) [37] and CST (Cybersecurity Toolkit) [38] to establish key cybersecurity management, risk assessment, and incident response guidelines for its national space cyber domain. Similarly, Germany, through BSI, developed the IT-Grundschutz Profile for Space Infrastructures [39] and TR-03184 [40], security standards aimed at ensuring S2bD in space cybersecurity. These collective initiatives have contributed to the refinement of the EU’s comprehensive space cyber risk management framework.
Furthermore, this section examines initiatives in Japan, which represents a dependent fast-follower in the space cybersecurity domain. METI standardized the Cybersecurity Guidelines for Commercial Space Systems [41] through dedicated efforts of an internal working group. This profiling standard was designed to preemptively neutralize potential malicious state actors’ compromise kill chains targeting the commercial space supply chain. Moreover, JAXA, in collaboration with the Cabinet Office, strategically developed the Space Security Initiative [42] to bench mark the NIST CSF [43], RMF [44], C-SCRM [45], and CMMC [46]. This initiative has substantively enhanced space cybersecurity cooperation between Japan and the United States.
Building upon these international precedents, the research and development maturity of space cybersecurity for each major country is systematically summarized in Table 1 according to specific attributes. In Table 1, the scoring scale is defined as follows. No Action: Indicates that no officially reported precedent exists. Identifying: Denotes that related work is in progress, but no official results have been produced yet.
TABLE 1.
Taxonomy of research and development rating of space cybersecurity by major countries
Developing: Signifies that foundational work has been conducted, yielding preliminary results. In Progress: Represents an ongoing effort where initial results have been produced, followed by further refinements. Achieved: Indicates that a clearly differentiated technological development has been successfully completed. Leader: Refers to a country that demonstrates extensive implementation and widely recognized practices in space cybersecurity.
2.2. Comparative Analysis of Framework
This section examines SPARTA and SPACE-SHIELD, which represent exemplary space cybersecurity frameworks. For ISACs and C-SoCs, SPARTA serves as a catalog archive that normalizes specialized TTPs and countermeasures for each major segment within the space cyber domain. Specifically, SPARTA supports S2bD by tailoring security requirements and security controls from the design phase of subcomponents. Furthermore, it ensures DiD by utilizing functional decomposition methods and Notional Risk Score (NRS)-based risk matrices, which abstract operational layers. Notably, SPARTA exhibits robust structural network correlations with other frameworks, including SPACE-SHIELD, MITRE ATT&CK, and MITRE D3FEND. It also maintains complex system relationships with governance standards such as NIST CSF, RMF, NASA BFG, CCSDS, and ISO/IEC 27001 [47]. Consequently, SPARTA facilitates developers, operators, and sub-parties in the supply chain in identifying potential space cyber threats and enables the rapid optimization of countermeasures for each threat. Therefore, SPARTA is quantitatively evaluated as the most advanced standard for space CTIs and IoCs, while also being qualitatively recognized for its comprehensive coverage of space TTPs and countermeasures.
In parallel, SPACE-SHIELD represents the first dedicated operational space cybersecurity framework that was specialized as a subdomain of MITRE ATT&CK to precisely define threats, vulnerabilities, TTPs, and kill chains within the EU space cyber domain. SPACE-SHIELD was architecturally designed to be applicable to ARTES-4S, CyberCube, and EU Space-ISAC, with its record data structured accordingly. Although its content update frequency is comparatively lower than SPARTA, it is documented to achieve broader adoption for independent C-SoC development.
Ultimately, the comparative analysis of each framework is comprehensively summarized in Table 2. Based on this classification, when evaluating the damage ripple effect for each threat and validating the mitigation response effectiveness for each countermeasure within this study, and particularly when concretizing the Multi-tiered Space Cyber TARA, the analysis confirmed that SPARTA’s record data constitutes the most suitable foundation.
TABLE 2.
Taxonomy of space & legacy TTP-based cybersecurity framework
3. SPACE CYBER THREAT MODELING AND RISK ASSESSMENT WITH SPARTA
This section formalizes key procedures within the proposed Multi-tiered Space Cyber TARA and specifies its novel metrics for cyber engagement effectiveness analysis, including the risk matrix and defense coverage, using both baseline layers and detailed pseudo-code. Furthermore, by conceptualizing segment-specific space system architectures and engagement scenarios within the supply chain as best practices, this study empirically demonstrates the qualitative and quantitative applicability of the proposed method.
3.1. Design Principles of Multi-tierd TARA
Initially, based on the TTPs and security controls in SPARTA, this section concretizes TARA- based threat modeling, which systematically performs cyber threat assessment and maps optimal countermeasures for secure IV&V in the space cyber domain. In this context, threat modeling constitutes a quantitative analysis method that identifies potential vulnerabilities from the design lifecycle of key test units, such as complex digital infrastructure, software components, and service applications. It then optimizes countermeasures to internalize both perimeter and n on-perimeter defenses, incorporating the degree of CIA (Confidentiality, Integrity, and Availability). This advanced threat modeling structure is abstracted into a five-step process, as shown in Fig. 1.
Based on the criticality and severity of key test units, this threat modeling concept is structured as a hierarchical TARA approach, which serves as an MBSE-based mechanism to ensure IV&V. The TARA framework represents a custom threat modeling strategy developed by MIT RE, designed to identify cyber threats throughout the critical system acquisition lifecycle and strategically select optimized defense measures. Within this framework, it contributes to DevSecOps by analyzing the effectiveness of cyber engagements and optimizing security controls using baselines. As shown in Fig. 2, TARA is divided into three distinct phases: Define and Model—the preprocessing step, where threats and vulnerabilities are structured. Analyze and Assess—the quantitative verification step, where risk levels and potential impacts are evaluated. Mitigate and Operate—the decision- making optimization step, where optimal defense measures are selected and operationalized. The primary objective of TARA is to preemptively identify vulnerable points and potential attack surfaces within an adaptive acquisition process, ensuring that all defensive actions are implemented before an attack occurs. Moreover, it guarantees the functional safety and operational resilience of protected space platforms, thereby maintaining service reliability. Additionally, TARA determines the baseline solution for qualitative security profiles and quantitative damage/mitigation metrics of key test units. It also optimizes Standard Operating Procedures (SOPs) by applying overlay and tailoring schemes.
Accordingly, the main diagram of the proposed Multi-tiered Space Cyber TARA, which incorporates both the threat modeling structure and TARA procedures, is structured into three key sequences, as illustrated in Fig. 3. First, KM serves as the preprocessing step, organizing and cataloging space cyber threats and countermeasures to establish a knowledge archive for effectiveness analysis. Specifically, KM is responsible for normalizing combat data within the space cyber ecosystem into a structured TARA-compatible knowledge set. To achieve this, KM integrates the structural and technical total lifecycle system management steps of operational space systems. Furthermore, it abstracts TTP-based kill chains and the chain of compromises using the pivot concept, thereby embedding hierarchical correlations across different catalogs.
Subsequently, CTSA constitutes the stage that evaluates attack vectors, vulnerabilities, and weaknesses that could precipitate adverse impacts. It defines the degree of cyber risk and quantifies the damage ripple effect. In CTSA, which pertains to threat analysis, potential attack surfaces and candidate vulnerable points are identified based on a data flow diagram. Risk assessment is then conducted by referencing cataloged compromising information, which enables the standardization of both a two-dimensional impact-likelihood-based risk matrix and the Notional SR and Notional SM.
Finally, CRRA represents the stage that derives and validates the optimal countermeasures and security profiles for mitigation. It establishes categorization results, formulates defense baselines, and quantifies the mitigation response level. In CRRA, which focuses on the mapping of defense measures, candidates are optimized by structuring the Pareto front of trade-offs based on prioritization. Moreover, regression analysis is performed to minimize residual risk to realize S2bD and DiD within the space ecosystem.
3.2. Quantitative Baseline for Overlay and Tailoring
Subsequently, the Multi-tiered Space Cyber TARA and its subprocedures (KM, CTSA, and CRRA) are integrated with TSN to tailor and overlay the augmented SR for evaluating the damage ripple effect of each threat and the defined SM for validating the mitigation response of each countermeasure. During this phase, by utilizing CTSA within TARA, the impact-based propagation scope for each threat and the likelihood-based attack type are configured. Similarly, by applying CRRA within TARA, the impact-based response scope and likelihood-based defense measures for each countermeasure are constructed. Consequently, the TSN-based refined TARA analysis procedures are delineated in Fig. 4.
Initially, in KM, the Categorization of Asset and Implementation of Metrics phase is structured into several sub-processes based on capability assessment to systematically evaluate space as sets and their potential risks. Criticality Analysis: Classifies potential security failures and accident levels for each space asset, then determines the priority of countermeasure implementation for each entity. Space Risk and Threat Assessment: Identifies attack surfaces within the space cyber ecosystem and analyzes threat types associated with each potential risk. Space Vulnerability Assessment: Identifies detailed kill chains and compromise sequences for each threat and analyzes the types of damages that may occur. Resulting Consequence of Space Cybersecurity Loss: Enhances the SR score by supplementing the NRS with impact considerations. Resulting Probability of Space Cybersecurity Loss: Refines the SR score by incorporating likelihood considerations based on NRS. Each of these sub-processes is systematically structured and concretized within the KM-based categorization framework. Subsequently, in CTSA, the Risk Assessment phase initially determines TTPs and threat-specific SR based on an impact-likelihood-based risk matrix, while referencing the criticality of protected assets through an initial verification flow. Ultimately, in CRRA, the Selection of Countermeasure and Mitigation Tailoring phase is subdivided into multiple sub-processes: Identification of Countermeasure: Defines SM by mapping applicable countermeasures and security profile elements for each threat. It then quantifies the degree of mitigation response using the SM. Decision, Optimization, and Tailoring: Implements a defensive decision-making model based on the identified mitigation response. It further reduces residual risk by optimizing security strategies according to the system and architecture structure. These sub- processes comprehensively structure the countermeasure selection and risk mitigation process within CRRA.
Within the TSN-based process, the SR, which is inherited from SPARTA’s NRS as a baseline for threat assessment, is structured to interoperate seamlessly with the threat modeling procedures. As shown in Algorithm 1, SR is decomposed into atomic templates, including Identify & Configure, Populate, and Select, ensuring optimal integration within the modeling workflow.
Algorithm 1.
Pseudo code of space risk (SR) metric for threat quantification
As illustrated in Fig. 5, the threshold for attack efficiency per threat is determined based on consequence attributes, which are associated with an arbitrary space asset’s mission, CIA, reputation, and regulatory impact. Conversely, the threshold for attack type per threat is calculated based on probability attributes, which are linked to the space asset’s ability, attention, opportunity, and scope. Through this process, the risk assessment domain within SR is systematically established.
Subsequently, the NRS metric, inherited by SR from SPARTA, was originally proposed only as a baseline for qualitatively recommending countermeasures and controls that are closely linked to each technique. Consequently, relying solely on SR may introduce bias-induced errors. Moreover, there is a lack of evaluation regarding the mitigation response generated by mapped countermeasures. To address these limitations, SM is introduced as a novel baseline, divided into SM1 and SM2, as shown in Fig. 6. This is achieved by leveraging MITRE Engenuity’s mitigation efficiency factor and SPARTA’s defense coverage factor. Unlike conventional matrix axis shifts that define the degree of mitigation response, SM is conceptualized to directly attenuate the cascading impact of cyber threats. The threshold for mitigation efficiency for each countermeasure is based on impact attributes correlated with reduction degrees, classified as low, medium, high, and critical. Correspondingly, the threshold for defense type for each countermeasure is based on likelihood attributes, considering the effect on both attackers and arbitrary space assets when applying defense mechanisms. These attributes are categorized into: Detect & Prevent, Neutralize & Eliminate, Limit & Stop, Resilience & Recover. Through this process, the security verification domain within SM is systematically structured.
Consequently, SM1 is established as the first baseline, which is directly correlated with the impact- likelihood layer, as defined in Table 3. It serves as an essential metric for defense effectiveness analysis of each countermeasure.
TABLE 3.
Baseline of SM1 with risk matrix
Conversely, SM2 is structured as the second baseline, as outlined in Table 4. It is directly related to operational segments and defensive coverage, based on the SPARTA navigator. SM2 is selectively applied when a comprehensive analysis is required, considering the sequential interconnectivity of aggressive kill chains and the hierarchical multi-redundancy of cybersecurity solutions.
TABLE 4.
Baseline of SM2 with defense coverage
Subsequently, SM, which is conceptualized for validating mitigation responses within the TSN-based process, is globally interoperable with detailed TARA procedures, as shown in Algorithm 2. It is structured into atomic templates, including: Prepare, Decide, Calculate, and Mitigate. This methodology further ensures seamless integration within alternative custom TARA frameworks.
Algorithm 2.
Pseudo code of space mitigation (SM) metric for countermeasure quantification
3.3. Proof-of-concept with Best Practice
To empirically validate the efficacy and novelty of the proposed Multi-tiered Space Cyber TARA, SR, and SM, a comprehensive validation of best practice is conducted, focusing on the software supply chain within the space system architecture. As depicted in Fig. 7, the space cyber ecosystem subject to cybersecurity assessment in this study is structured as a data flow diagram and is systematically normalized into three primary segments: Space Segment, Link Segment, and Ground Segment. In the Space Segment, two key platforms are categorized: Operational Platform: Centrally controls mission-oriented propulsion and maneuvering in space. Pay load Platform: Executes sub-party missions, such as weather observation, by utilizing RF antennas and CCSDS protocol-based telemetry and telecommand to communicate with ground stations. In the Ground Segment, multiple sub- segments are hierarchically structured: Operational Ground Sub-Segment: Remotely manages TT&C (Telemetry, Tracking, and Command) Systems and GNSS (Global Navigation Satellite Systems) for segmented GCS. Launch Ground Sub-Segment: Controls space asset launch and maneuvering. Space Supply Chain Segment: Manages logistics and security aspects of the space supply chain. User Ground Sub-Segment: Implements access and device control within the space ecosystem via VPN (Virtual Private Network).
Through this best practice, the applicability of Multi-tiered Space Cyber TARA to space system architectures is comprehensively demonstrated.
Given that the space supply chain segment encompasses numerous sub-party organizations and development vendors with comparatively weaker security postures, it represents the most vulnerable attack surface. Therefore, the supply chain segment is designated as the initial attack vector, predicated on the assumption that malicious state actors could exploit it to propagate space cyber warfare in a cascading manner.
Based on this assumption, as illustrated in Fig. 8, an adversarial kill chain case is conceptualized, focusing on social engineering attacks and backdoor concealment activities.
3.3.1. Definition of APT
・Prepares malware that establishes a reverse connection based on external constraint conditions.
・Conducts social-engineering attacks (e.g., spear phishing and water ing hole attacks) targeting employees of SMEs (Small and Medium-Sized Enterprises) with relatively weaker security management.
・Injects malware into spacecraft software under development.
・After development completion, the malware remains persistently concealed within the operational spacecraft software.
・During PNT communications with the GCS, the geofencing trigger is exploited to establish RCE (Remote Code Execution).
・Achieves T-DDoS (Telemetry-centric Distributed Denial-of-Service) via a reverse shell based on C2 (Command and Control).
3.3.2. Identification of Attack Surfaces
・Human and physical layers of commercial vendors with relatively lower security (No DiD).
・Unverified security assessment and defense validation procedures for software subcomponents and subsystems (No S2bD).
・Absence of security controls established through total life-cycle system management (No Space-DevSecOps).
・Non-redundant authorization/authentication mechanisms.
・Unprotected operational zones of internal units, lacking sandboxing mechanisms.
3.3.3. Normalization of Kill Chain Sequences
・Conducts social-engineering attacks to obtain legitimate internal access within a vulnerable commercial vendor.
・Exploits the compromised access to inject a C2 backdoor into the space system software during development.
・Before transportation, conceals execution to evade vulnerability analysis and inspection. Additionally, fragments and distributes malicious code in memory to bypass anomaly detection mechanisms.
・Disrupts communication services by triggering automatic RCE through PNT geofencing.
・Introduces persistent issues in the GCS, preventing realtime TC execution and payload operations.
Additionally, as shown in Fig. 8, the initial SR for each threat is derived by embedding the correlations among referenced space cybersecurity frameworks within the Multi-tiered Space Cyber TARA. These results are systematically summarized in Table 5. Moreover, to adaptively defend against this adversarial kill chain case, a defensive chain case is formulated, as illustrated in Fig. 9. This defensive approach is structured based on the competitive engagement concept of the C-SoC, which continuously monitors the status of space infrastructure.
TABLE 5.
List of initial SR for space cyber warfare scenario
3.3.4. Determination of Countermeasures
・Implement secure TDD (Test-Driven Development) for hardware components and embedded software within space systems (Yes DiD).
・Adopt specialized space cybersecurity profiles and leverage TTP-based CTI and IoCs (Yes S2bD).
・Establish hierarchical access control policies and multi-layered device control principles (Yes Space- DevSecOps).
・Standardize asset management and mission control mechanisms through SBO
・M (Software Bill of Materials) while simultaneously structuring POA&M (Plan of Action & Milestones) governance within the SOPs.
As illustrated in Fig. 9, the SM1 list for reducing the initial SR is determined based on impact and likelihood layers, as summarized in Table 6. Through this approach, the quantitative assessment for IV&V demonstrates that all kill chain activities of adversaries targeting the space supply chain can be significantly mitigated. Notably, by focusing on preemptive counter measures against weaponization tactics—particularly those in the reconnaissance and initial access stages, which occur before the exploit and execution stages—the analysis explicitly demon strates that the continuity of an advanced space attack can be proactively disrupted.
TABLE 6.
List of calculated mandatory SM1 with SPARTA
However, mitigation measures based solely on SM1 fail to comprehensively capture the correlations assigned to specific countermeasures and CTI catalogs, nor do they adequately reflect the latent sequential dependencies within TTPs and IoCs in adversarial kill chains. To address these limitations, the SM2 list is derived based on location layers and defense coverage layers, as summarized in Table 7. SM2 is then integrated with SM1, as shown in Table 8, for integrated application. Through this approach, the analysis demonstrates that risk assessment procedures can be operationalized more effectively from a management perspective, leveraging the SPARTA navigator. Furthermore, in the space cyber domain, this framework enables more granular quantitative security evaluation by layering and interlinking perimeter and non-perimeter defense solutions, ensuring enhanced multi-dimensional risk mitigation with multi-redundancy.
TABLE 7.
List of mitigated SR with SM1
TABLE 8.
List of calculated optional SM2 with SPARTA
4. CONCLUSION
This study has introduced the Multi-tiered Space Cyber TARA, incorporating SR and SM metrics, to extend the IV&V applicability of established space cybersecurity frameworks including SPARTA and SPACE-SHIELD. The framework systematically evaluated the damage ripple effect and validated mitigation responses based on the competitive dynamics of supply chain actors. Security controls, intelligence, and IoCs were analyzed, demonstrating the proposed method as a quantitative MBSE-based risk assessment toolkit for secure space IV&V. Moreover, its interoperability with SPARTA, MITRE ATT&CK, and NIST CSF was qualitatively validated through MNB-based overlay and tailoring mechanisms.
Nevertheless, a key limitation of this study is that the conceptualized Multi-tiered Space Cyber TARA primarily references atomic records derived from SPARTA, MITRE ATT&CK TTPs, and their countermeasures. Its applicability to other space cybersecurity frameworks, such as S PACE- SHIELD, remains limited to mediating SPARTA-related elements. To minimize discrepancies in threat representations across frameworks, direct normalization of SPACE-SHIELD into an archival format is imperative.
Additionally, SM1’s likelihood assessment relies upon MITRE’s Cyber Risk Remediation Asses sment (CRRA), while SM2’s defense coverage depends on SPARTA’s navigator component.
To enhance the generalizability of Space Mitigation (SM), diversification of referenced assessment artifacts is essential. Moreover, in the Proof-of-Concept (PoC), the space system architecture and supply chain scenarios were abstracted into a generalized model to control the analysis scope. This abstraction encompassed subordinate platforms, infrastructure, peripherals, auxiliary modules, and unit components. Nevertheless, as these assumptions may not fully align with the specific policies, doctrines, and SOPs of space agencies and security organizations, addressing this heterogeneity is imperative for broader applicability.
To address these limitations, future work will expand the PoC scope to space cyber-electronic warfare (S-CEW) and constellation satellite best practices. The research will also integrate additional framework components, including SPACE- SHIELD, MITRE ENGAGE, and MITRE EMB3D. Building on these foundations, the development of Space-PTaaS solutions for S2bD and Space- eMASS appliances for DiD is anticipated.











