Launch Facility
Parent: RD-0001
Description
In practice, adversaries are far more likely to purchase launch services (rideshare slots, hosted-payload opportunities) than to “acquire a launch facility.” Nevertheless, understanding and exploiting launch infrastructure, pads, integration cells, range networks, and control centers, could support resource development (e.g., positioning an asset, staging equipment near range telemetry). The realistic objective is influence over access to orbit, schedule, or integration touchpoints rather than ownership of a pad. Shell entities might book benign-sounding rides, insert dual-use payloads, or seek special handling that relaxes controls.
Mappings
Cross-reference controls
Acquiring or leasing a launch facility (range services, integration cleanrooms, TT&C support) is operational-infrastructure procurement; T1583 'Acquire Infrastructure' covers this at cross-framework level.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Referenced in: sparta-data
Mapped by SPARTA, not curated by SafeMode Space.
Launch facility access (rideshare slots, hosted-payload opportunities, range network influence) falls within T1583's general infrastructure-acquisition scope; SPACE-SHIELD has no launch-facility-specific sub-technique.
SPARTA countermeasures
Mapped by SPARTA, not curated by SafeMode Space.
Cite as SafeMode Space, RD-0001.04 (SPARTA v3.2).