The Spacecraft Hackers Handbook A Practical Guide to Breaking Space Systems (Andrzej Olchawa, Milenko Starcik) (z-library.sk, 1lib.sk, z-lib.sk)

【One-Line Pitch】 A hands-on field manual for anyone who wants to understand how spacecraft actually get compromised—not by crashing them, but by attacking flight software, mission control, and the communication links in between. Best suited to security researchers, aerospace engineers, and students comfortable reading Python, Java, and C. 【Book Arc】 - **Opening (~0%–20%)**: Frames spacecraft cybersecurity as a discipline distinct from "making satellites fall out of the sky," establishing the threat model—data exposure, communications disruption, onboard manipulation, and mission-operations takeover—and setting up the lab environment (Docker plus a virtualization platform, no radio hardware required). - **Early (~20%–40%)**: Grounds readers in mission control software, working with Yamcs and OpenC3 COSMOS to understand how operators command and monitor spacecraft, which is the surface attackers would target first. - **Middle (~40%–65%)**: Moves into flight software proper—NASA's F′ framework and the core Flight System (cFS)—where readers explore onboard code and begin hunting for vulnerabilities in the software that actually runs in space. - **Late (~65%–85%)**: Shifts to communications, analyzing CCSDS spacecraft protocols and extending into SATCOM terminals and GNSS attack scenarios, connecting ground and space segments through their links. - **Ending (~85%–100%)**: Turns exploitation into practice—reproducing real space cyberattacks in a safe environment, then discovering, validating, and responsibly disclosing new vulnerabilities. 【Key Takeaways】 - **Spacecraft hacking is about control, not destruction** (Opening): the realistic threat is data theft, comms disruption, and mission-operations takeover—reframing what "hacking a satellite" means and why it matters. - **Mission control software is the practical entry point** (Early): Yamcs and OpenC3 COSMOS are treated as working targets, giving readers a realistic operator-side attack surface to study. - **Flight software is auditable code** (Middle): NASA's F′ and cFS are explored as real codebases, so vulnerability hunting becomes a source-reading exercise rather than abstract theory. - **Protocols are where ground meets space** (Late): CCSDS analysis anchors the communications segment, with SATCOM terminals and GNSS attacks showing how links become attack vectors. - **Labs make the abstract concrete** (throughout): hands-on exercises and working exploits let readers reproduce actual space cyberattacks safely instead of only reading about them. - **Responsible disclosure is part of the skill set** (Ending): the book closes the loop from finding a bug to validating and reporting it—treating ethics as a technical competency, not an afterthought. - **Low barrier to entry** (Opening): standard OS, Docker, and basic Python/Java/C literacy suffice; no specialized radio or satellite hardware is needed. 【Reading Tips】 - Set up the Docker and virtualization lab before reading the middle chapters—the flight-software and protocol sections assume a working environment. - Skim the opening threat-model framing if you already know space systems, but deep-read the mission control and flight software chapters; that's where the transferable skills live. - Treat the CCSDS and SATCOM/GNSS material as the hardest stretch—protocol details reward slow, reference-in-hand reading. - Do the labs rather than reading them passively; the exploitation and disclosure chapters only pay off if you've reproduced the attacks yourself. - Keep Python, Java, and C references nearby; the book assumes you can read source, not that you're fluent in every language. 【Coverage Limits】 This guide is synthesized from the book's front matter and descriptive material; the excerpts do not cover specific chapter titles, lab walkthroughs, or technical detail, so chapter-level guidance is inferred from the stated structure rather than verified against the text.