All techniques
REC-0009
ST0001Reconnaissance

Gather Mission Information

Description

Adversaries compile a CONOPS-level portrait of the mission to predict priorities, constraints, and operational rhythms. They harvest stated needs, goals, and performance measures; enumerate key elements/instruments and their duty cycles; and extract mode logic, operational constraints (pointing, keep-outs, contamination, thermal/power margins), and contingency concepts. They mine the scientific and engineering basis, papers, algorithms, calibration methods, to anticipate data value, processing chains, and where integrity or availability attacks would have maximal effect. They correlate physical and support environments (ground networks, cloud pipelines, data distribution partners, user communities) and public schedules (campaigns, calibrations, maneuvers) to identify periods of elevated workload or reduced margin. The aim is not merely understanding but timing: choosing moments when authentication might be relaxed, monitoring is saturated, or rapid-response authority is invoked.

Mappings

EU regulation articles

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

    Mission CONOPS, mode logic, and operational constraints are operator-controlled artifacts; while some elements are public, internal documents (algorithms, calibration methods, contingency CONOPS) are within 80(3)'s confidentiality categorization scope.

ENISA controls

  • Information classification governs the protective marking of CONOPS, payload concept, and ground-architecture documentation that REC-0009 compiles.

Cross-reference controls

SPARTA countermeasures

Cite as SafeMode Space, REC-0009 (SPARTA v3.2).

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