Apply SPARTA countermeasures to protect your space systems
SPARTA (Space Attack Research and Tactic Analysis) is a free, unclassified framework from The Aerospace Corporation that catalogues how spacecraft can be compromised through cyber and counterspace attacks.
- Full name
- Space Attack Research and Tactic Analysis
- Published by
- The Aerospace Corporation
- Type
- Voluntary threat and countermeasure framework
- Structure
- 9 tactics, techniques and sub-techniques, and 90 countermeasures
Is SPARTA right for your organisation?
It organises adversary behaviour into tactics and techniques, in a style similar to MITRE ATT&CK, and links each technique to numbered countermeasures (CM0001 onwards). Teams use it to threat-model missions and choose defences across the space, ground and supply chain segments.
SPARTA is voluntary, so no law requires it, but it is widely used by satellite operators, spacecraft and component manufacturers, ground station providers and space mission integrators. It is most useful during mission design and threat modelling, when answering customer or government security questions about a space system, and when building a defence-in-depth programme for operations.
Adopting it is voluntary, though customers and auditors often expect it.
How OneClickComply helps with SPARTA
SPARTA is supported in OneClickComply today. The enterprise-side countermeasures, such as development environment security, vulnerability scanning, configuration management, least privilege, data backup and continuous monitoring, map to controls you may already run for ISO 27001 or SOC 2, so evidence collected once can count towards both. Our in-house audit team and virtual CISO can help you scope which countermeasures apply to your mission.
Requirements covered
A matrix of 9 attack tactics, from Reconnaissance to Impact, with techniques and sub-techniques mapped to 90 numbered countermeasures (CM0001 to CM0090), which are also mapped to NIST SP 800-53 and ISO 27001 controls.
Manual SPARTA compliance vs OneClickComply
Doing it manually
- Reading through 90 countermeasures to work out which apply to your mission
- Tracking SPARTA, NIST SP 800-53 and ISO 27001 mappings in separate spreadsheets
- Collecting screenshots from ground and development systems to prove controls work
- Finding out about access or configuration drift only at the next review
- Answering customer security questionnaires about your space system from scratch
With OneClickComply
- Scoping support from auditors and a virtual CISO who help you focus on relevant countermeasures
- One set of controls mapped across frameworks, so evidence counts towards each one
- Evidence pulled automatically from connected tools and logged for review
- Continuous monitoring that alerts you as soon as a control drifts
- Security questionnaire automation and a trust centre to share your posture
Everything you need for SPARTA
SPARTA countermeasures mapped to controls you may already run for ISO 27001 and SOC 2
Automated evidence for enterprise countermeasures from 13,000+ integrations
OneClickFix for supported misconfigurations in your cloud, identity and device tools
AutoComplete policies covering development security, access control and backups
Continuous monitoring with alerts when ground and enterprise controls drift
Risk register and vendor risk management for space supply chain threats
Three steps to SPARTA compliance
Connect and scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against SPARTA and shows which controls pass and which fail.
Fix and generate
OneClickFix fixes supported misconfigurations automatically, and AutoComplete drafts SPARTA policies from your real environment.
Monitor and evidence
Continuous monitoring flags drift as it happens, and our in-house audit team is on hand when you need expert guidance.
See how far your current setup is from SPARTA.
SPARTA (Space Attack Research and Tactic Analysis) requirements
All 90 SPARTA countermeasures (CM0001 to CM0090), which mitigate the techniques across SPARTA's 9 attack tactics.
| Reference | Requirement |
|---|---|
| CM0001 | Protect Sensitive Information |
| CM0002 | COMSEC |
| CM0003 | TEMPEST |
| CM0004 | Development Environment Security |
| CM0005 | Ground-based Countermeasures |
| CM0006 | Cloaking Safe-mode |
| CM0007 | Software Version Numbers |
| CM0008 | Security Testing Results |
| CM0009 | Threat Intelligence Program |
| CM0010 | Update Software |
| CM0011 | Vulnerability Scanning |
| CM0012 | Software Bill of Materials |
| CM0013 | Dependency Confusion |
| CM0014 | Secure Boot |
| CM0015 | Software Source Control |
| CM0016 | CWE List |
| CM0017 | Coding Standard |
| CM0018 | Dynamic Testing |
| CM0019 | Static Analysis |
| CM0020 | Threat Modeling |
Always check the official text of SPARTA for the exact wording.
SPARTA questions, answered
Can't find what you need? Our in-house auditors can talk you through SPARTA on a 30-minute call.
What is SPARTA?
SPARTA, short for Space Attack Research and Tactic Analysis, is a free framework published by The Aerospace Corporation that describes how spacecraft can be attacked through cyber and counterspace means. It sets out adversary tactics, techniques and sub-techniques in a matrix similar to MITRE ATT&CK, and links them to numbered countermeasures that help designers and operators protect space missions.
Who created SPARTA?
SPARTA was created and is maintained by The Aerospace Corporation, a US nonprofit that operates a federally funded research and development centre supporting the space enterprise. It publishes the framework on sparta.aerospace.org and updates it with new techniques, countermeasures and mappings drawn from academic, government and industry research into space system threats.
Is SPARTA mandatory?
No. SPARTA is a voluntary framework, not a law or regulation, so there are no penalties for not using it. However, space customers, primes and government programmes may reference it when asking suppliers how they assess and mitigate cyber threats, so following it can help you answer security reviews and show a structured approach to space cybersecurity.
How is SPARTA different from MITRE ATT&CK?
SPARTA follows the same tactics and techniques model as MITRE ATT&CK but focuses on spacecraft and space missions. It covers threats that ATT&CK does not, such as attacks on the space segment, radio frequency links and on-board software, and adds counterspace techniques. It also provides its own countermeasure catalogue designed for space systems.
What are SPARTA countermeasures?
SPARTA countermeasures are numbered defensive measures, from CM0001 to CM0090, that mitigate the techniques in the SPARTA matrix. They range from enterprise practices such as vulnerability scanning, configuration management and least privilege to space-specific measures such as secure boot, cyber-safe mode, on-board intrusion detection and resilient position, navigation and timing. Each is mapped to NIST SP 800-53 controls.
How does SPARTA relate to ISO 27001 and NIST SP 800-53?
SPARTA countermeasures are mapped to NIST SP 800-53 controls, and The Aerospace Corporation has also published mappings to ISO 27001 controls. This means many enterprise and ground segment countermeasures overlap with an existing ISO 27001 or NIST programme, so organisations can reuse controls and evidence rather than building separate processes for space cybersecurity.
How do you implement SPARTA?
Start by threat modelling your mission against the SPARTA matrix to identify the techniques relevant to your spacecraft, ground segment and supply chain. Then select countermeasures for those techniques, prioritise them by risk, assign owners and gather evidence that they work. Revisit the analysis as your mission design, threat intelligence and the framework itself change.
Does OneClickComply support SPARTA?
Yes. SPARTA is supported in OneClickComply today. Because its enterprise countermeasures overlap with ISO 27001 and SOC 2 controls, evidence collected in OneClickComply can count towards them. Our in-house audit team and virtual CISO can help you decide which countermeasures apply to your mission. OneClickComply does not certify SPARTA compliance, as SPARTA is a framework rather than a certification scheme.
Related frameworks
- Cybersecurity Capability Maturity Model (C2M2)Framework · United States
- NIST Cybersecurity Framework 2.0Framework · United States
- Trusted Internet Connections (TIC) 3.0Framework · United States
- NIST SP 800-218 Secure Software Development Framework (SSDF)Framework · United States
- IRS Publication 1075Guidance · United States
- NIST SP 800-82 Rev. 3 High OT OverlayGuidance · United States
- FBI CJIS Security Policy v6.0Standard · United States
- NIST SP 800-161 Rev. 1Guidance · United States
Start working towards SPARTA
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.