Join the crewMy track

Classes / Systems class / Systems Department

Systems Track: Spacecraft Links and Flight Software Basics · Rank 5 coursework · Module 2 of 3 · about 40 min

Cybersecurity for satellite operations

Satellite operations depend on computers across the ground, communication links and spacecraft. We assess weaknesses in all three. Ground networks and operator accounts can expose a mission to ordinary IT risks; protecting only the space link leaves those dependencies out.

NIST wrote an introduction aimed at commercial satellite operators (NIST IR 8270). It applies the NIST Cybersecurity Framework to the space segment, ground segment and links, organized around identify, protect, detect, respond and recover.

Basic controls do a lot: authenticate and encrypt commands, keep ground networks segmented, limit who can send commands, log everything, and patch the ground software. Plan in advance what operators do if they see commands they did not send.

We study operating habits such as individual logins, controlled use of removable media and prompt reporting of unusual activity under the organization's procedures. Security is shared across the operation, not left to one specialist team. The course gives us no authority to change real access controls.

We keep the framework's date visible: IR 8270 was published in 2023, while CSF 2.0 added Govern to Identify, Protect, Detect, Respond and Recover. These are concurrent functions, not a checklist that finishes security forever. Governance includes responsibility and policy; controls and incident evidence must still work in the actual ground, link and spacecraft environment. The introductory satellite report is not a compliance certificate for a particular operation.

Worked example, fictional tabletop: an encrypted ground connection carries an unexpected command request. Encryption protects confidentiality but does not establish that the requester has permission for that action. We distinguish authenticated identity, authorized scope and an audit record. Shared credentials make attribution weaker. A successful login alone is insufficient evidence that an unusual command is legitimate, and an unexplained request is escalated through the organization's response procedure rather than tested on a live system.

Practice, on paper: we map identity controls, logs, response ownership and restoration checks to a fictional incident. We explain why a backup is not a complete recovery demonstration without checking restoration and intended operation. Our self-check separates prevention, detection and response evidence. We do not probe mission networks, inspect credentials or change access controls as part of this exercise.

Sources

Module quiz

10 questions, 8 correct to pass. You'll see what you missed and why, and you can retake it.

Next: Cornerstone reading: Attention Is All You Need →