safemode.space
← All techniques
RD-0002.03
ST0002Resource Development
sub-technique

3rd-Party Spacecraft

Parent: RD-0002

Description

By compromising another operator’s spacecraft, or a hosted payload, an adversary can gain proximity, sensing, and relay capabilities that are costly to build from scratch and difficult to attribute. With control of an on-orbit asset, the actor may conduct local spectrum measurement and traffic analysis, attempt selective interference or spoofing at short range, or probe crosslinks and gateways where payload networks bridge to buses. In rideshare or hosted-payload contexts, weak segmentation and shared ground paths can provide insight into neighboring missions. More aggressive scenarios include remote proximity operations (RPO) to achieve advantageous geometry; however, physical grappling, docking, or exposure of debug/test interfaces is highly specialized and rare, with significant safety, legal, and tracking implications. Realistic attacker goals emphasize adjacency for RF leverage, covert relay, or data theft rather than mechanical capture.

Mappings

EU regulation articles

  • eu-space-actArt. 91(3)
    addresses
    moderate
    direct

    91(3)'s pre-defined-agreements-with-third-party-entities clause (for hosted-payload contexts) governs how operators coordinate with the third-party spacecraft owner during compromise scenarios affecting proximity assets.

  • eu-space-actArt. 92(1)
    addresses
    moderate
    direct

    When the third-party spacecraft is the operator's hosted-payload host or rideshare neighbor, 92(1)'s supply-chain governance covers the contractual relationship that affects access to neighboring assets.

  • nis2Art. 21(2)(d)
    addresses
    moderate
    direct

    When a hosted-payload bus operator or rideshare host is in the entity's supplier graph, Art. 21(2)(d)'s supplier-relationship security obligation governs the trust framework around weak segmentation and shared ground paths the technique exploits.

  • nis2Art. 21(3)
    addresses
    moderate
    direct

    Cross-organisation segmentation and key-management practices at the third-party operator are the supplier-specific vulnerabilities Art. 21(3) requires the entity to consider when its mission rides shared infrastructure.

  • nis2-implAnnex 5.1.1
    addresses
    moderate
    derived

    Compromise of a third-party operator's spacecraft acting as proxy or relay engages the entity's supply-chain policy when the entity uses that operator's services or shares a bus/payload; the policy bounds what the entity accepts from the host operator.

ENISA controls

  • ENISA-STL-2025-03-sD.20-i04
    addresses
    high

    Third-party risk management explicitly covers other operators whose spacecraft share infrastructure with the host mission.

  • ENISA-STL-2025-03-sD.28-i01
    addresses
    moderate

    Supplier security management on co-hosted spacecraft providers establishes the audit and standards baseline that limits compromise propagation.

Cross-reference controls

SPARTA countermeasures

Cite as SafeMode Space, RD-0002.03 (SPARTA v3.2).

Built 2026-07-25 from 216 techniques, 334 regulation articles, 125 ENISA controls, 2,610 framework controls, and 90 countermeasures.