Why this environment matters
Security for satellite ground control workstations starts with the system's role: it creates and sends commands to satellites while receiving telemetry and mission data. A key concern is that stolen credentials or malicious command software can disrupt a spacecraft, alter its orbit or expose mission information. NØNOS offers a potential architecture based on signed capsules, explicit capabilities and strong isolation.
The security challenge
The threat model should assume that one component will eventually fail or be exploited. In this case, stolen credentials or malicious command software can disrupt a spacecraft, alter its orbit or expose mission information. Public-sector systems hold authoritative records and powers that affect identity, liberty, property, emergency response and national security. Endpoint compromise can therefore create consequences far beyond data loss. The aim is to prevent that single failure from automatically gaining the keys, devices, records and network paths of the whole platform.
How the capsule model could help
A candidate NØNOS architecture would separate command generation, approval, cryptographic signing and transmission, requiring attestation at each privileged stage. The design would prioritise purpose-bound data access and attestation for privileged actions, supported by controlled removable media and disposable trusted sessions. Each capsule would carry a declared policy for files, networks, devices and secrets, and unknown or altered software would not receive the same authority as an approved component.
Deployment requirements
Government deployment would require formal accreditation, identity and records integration, accessibility testing, procurement assurance and controls appropriate to the information classification and public function.
Current public-beta limitations, hardware support and application availability must be assessed before any pilot. Neither this use case nor an industry source establishes NONOS certification or a current customer deployment.
Who could buy or integrate it?
- Satellite operators procuring mission-control software and terminal estates
- Ground-system suppliers integrating command approval and telemetry platforms
- Government space programmes commissioning controlled operations infrastructure
Industry examples: Kratos, GMV. These are research prospects, not represented as NONOS customers, partners or endorsers.