SPARTA's usefulness relies on community engagement and collaboration. Below you will find several ways to contribute to SPARTA. If you don't see an option that suits your specific need, you can always email us directly at

All contributions and feedback to SPARTA are appreciated. If we find the contribution fills a gap, corrects an error, or improves existing content then we will work with you to make the necessary edits, listing you as a contributor if desired.

Before submitting any content, please consider whether SPARTA is the right place for it- does the concept/technique/idea primarily apply to the unique elements of a space system? Alternatively, TTPs geared towards traditional enterprise information technology, mobile devices, or industrial control systems (ICS) should be sent to MITRE for consideration within their existing matrices.

Contributing to SPARTA

Techniques and Sub-Techniques

We appreciate your help to let us know about what new techniques and technique variations are being performed by threat actors. Additionally, since SPARTA also attempts to document the “art of the possible” new techniques can be sent in that have been performed in the lab setting as well. You can start by emailing us the technique name, a brief description, and references or knowledge about how it is being used. Please take a close look at what we already have on our site, paying attention to the level of abstraction of techniques and sub-techniques. Since we are working on adding new technique details constantly, we will deconflict what you send with what we’re working on. We will provide feedback and work with you to get the content added. When documenting the TTPs, attempt to communicate countermeasures with your request if known.

Data Sources

We’re always looking for partners who would be interested in sharing relevant data from logs that show how adversaries are using SPARTA techniques beyond what appears in threat reporting. This is one of the largest hurdles with understanding attacks on space-based assets as many platforms lack the functionality to even detect these behaviors. As a result, the majority of current SPARTA TTPs are hypothetical or a result of simulation/in-lab testing vice observed events.


SPARTA not only attempts to document the TTPs that can affect the spacecraft via cyber means, but it also attempts to identify countermeasures for the TTPs. Feel free to submit new countermeasures to existing TTPs or when new techniques/sub-techniques are submitted consider submitted countermeasures as well. When countermeasures are submitted, please submit any NIST revision 5 control mapping if known.

Use Cases

It is helpful for us to hear about how you’re using SPARTA in your organization. We appreciate any information you can share with us about your specific use case or application of SPARTA, and particularly any success stories you have had as a result.

Content Errors on the Website

If you find errors or typos on the site related to content, please let us know by sending an email to with the subject "Content Error."

Please provide the url where you found the error and a short description of the error.

External Contributors

Special thanks to the following non-Aerospace Corporation individuals or organizations who have contributed to SPARTA content development and peer reviews:

  • Gregory Falco
  • Nick Tsamis
  • Mario Zuniga
  • Francesco Traini, Università Politecnica delle Marche
  • Antonios Atlasis
  • Ignacio Aguilar Sanchez
  • Tim Dafoe
  • Wayne Henry
  • Andres Coronado
  • Timothy O'Neill
  • Florent Rizzo, CyberInflight's Market Intelligence Team
  • Matthias Popoff, CyberInflight's Market Intelligence Team
  • Héloise Do Nascimento Cardoso, CyberInflight's Market Intelligence Team
  • Jens Freymuth, RACCOON Team_Chair of Aerospace Technology_TU-Berlin
  • Mohamed Abdelgawad, RACCOON Team_Chair of Aerospace Technology_TU-Berlian
  • Philipp Wüstenberg, RACCOON Team_Chair of Aerospace Technology_TU-Berlin