HomeEditor’s PicksIs Space Cybersecurity Becoming a Standalone Commercial Market?

Is Space Cybersecurity Becoming a Standalone Commercial Market?

Space cybersecurity services cover command authentication, data encryption, access controls, embedded software, laboratory testing, and ground systems.

French satellite manufacturer U-Space signed a long-term contract with CYSEC in February 2025 to incorporate security software into its small-satellite platforms. The agreement is a concrete example of space cybersecurity being purchased as a specialized product within spacecraft manufacturing. The customer buys software that protects communications between a satellite and its ground systems, integrating another company’s security technology into the platform it sells.

The U-Space agreement covers CYSEC’s ARCA SATLINK software across platforms produced at the manufacturer’s Toulouse factory. The product implements a space communications security protocol on the ground and aboard spacecraft. Its functions cover telemetry, which reports spacecraft condition, telecommands, which direct spacecraft actions, and payload data links carrying mission information. This arrangement places a specialist supplier inside a manufacturer’s production process, with the satellite manufacturer serving as the route to mission customers.

The Products Being Purchased

Space cybersecurity includes several connected markets. Some suppliers provide software embedded in spacecraft or ground systems. Others sell engineering services, authorized security assessments, or protection for organizations using satellite connectivity. The purchasing organization changes with the product: a spacecraft builder incorporates security into a platform, an operator manages access to its mission, and an enterprise protects data traveling through a satellite network.

These transactions have different commercial units. Embedded software belongs to a spacecraft configuration and its integration process. A laboratory assessment has a defined target, testing period, and report. Operational security software manages permissions and information exchange during service delivery. Treating all three as a single generic security subscription would obscure what the customer actually receives.

Thuraya, for example, lists CYSEC’s ARCA SATCOM among its encryption solutions. The offering applies encryption to satellite data communications for network users. Its position in the service chain differs from software protecting a spacecraft’s command interface: the buyer is concerned with information transmitted through connectivity, and the communications provider can introduce the security product to that customer.

A company purchasing satellite connectivity may use the link for corporate files, operational messages, or remote-site communications. Encryption converts readable information into a form that authorized recipients can recover using the appropriate cryptographic material. This provides a security function attached to the customer’s data path. It can be purchased alongside connectivity even when the customer neither owns nor operates the satellite.

Protecting Commands and Mission Data

The Space Data Link Security Protocol, published by the Consultative Committee for Space Data Systems, defines mechanisms for authentication and confidentiality at the communications link layer. Authentication checks whether received information has the required valid cryptographic protection. Confidentiality prevents someone without the appropriate key from reading protected content. The protocol also supports protections against replaying previously transmitted information.

Those functions address different questions in a satellite system. A command may direct a change in spacecraft behavior, making its origin and integrity operationally relevant. Mission data may contain images or other information intended for particular customers. A security implementation can protect both command traffic and data traffic, with the selected services reflected in its configuration.

The commercial work includes connecting the protocol to the actual onboard computer, communications equipment, and ground software. The same standard can be implemented on different platforms, but each installation interacts with that platform’s interfaces and operating procedures. A specialist’s product combines reusable software with the engineering needed to make it operate within a particular mission system.

NASA’s ground systems reference describes security across flight hardware, payloads, ground infrastructure, and supporting services. It identifies authenticated command paths, software verification, access controls, and operating records as parts of this work. Its treatment connects cybersecurity with mission engineering: permissions determine who can act, and verification determines which software and commands the system accepts.

For a service provider, these are identifiable integration activities. A ground operations account has a user and an assigned role; a software update has a version and an authorization process; a command has a source and an intended destination. Security software and engineering services operate on these concrete elements of the mission. Their commercial purpose is tied to the customer’s spacecraft and operating environment.

Software for Intermittent Networks

SpiderOak’s OrbitSecure product description emphasizes access controls that travel with protected data and commands. The company describes certificate-based authentication, management of cryptographic keys, and the ability to add or remove participating devices. Its software supports role-based access in environments where a continuous connection to centralized infrastructure is unavailable.

That operating condition matters for spacecraft communications. A satellite may exchange information during a ground contact and continue operating between contacts. A distributed mission may also involve separate organizations and communications providers. Security decisions then concern the identity and permissions of participants as well as the network carrying their messages. The software’s assigned function is to preserve those distinctions during information exchange.

In July 2024, SpiderOak announced an International Space Station demonstration conducted through Axiom Space. The company reported validation testing on July 1 of an OrbitSecure module rewritten in Rust, a programming language designed with memory safety features. This followed an earlier station demonstration in 2023. The reported milestone concerned software operation in orbit, establishing a specific application of the product on space-based computing infrastructure.

This form of delivery allows cybersecurity companies to participate without supplying an entire spacecraft. The security module becomes part of another organization’s system, and the partner provides the mission or computing environment. The commercial relationship centers on software integration and the information that software protects. That is a distinct supplier role within the broader space economy.

Testing as a Separate Service

An assessment business sells a different deliverable: evidence about the behavior of a defined system under authorized testing. ESA’s SAThical project account describes a service developed by Hungary’s Sys-Control that covers spacecraft firmware, communications links, and ground systems. Testing uses engineering models, laboratory equipment, and representative environments approved by the customer.

ESA reported that the project’s Kick-Start activity finished in October 2026. Work included a representative laboratory environment using a FlatSat engineering model and a bounded assessment of satellite bootloader firmware. A FlatSat places spacecraft components in an accessible ground arrangement for engineering work. The project identified its next commercial step as a first paid laboratory Proof Test, followed by a proposed customer-led proof of concept.

The assessment’s scope gives this business its product boundary. The customer authorizes a particular target and receives findings associated with the tested configuration. The deliverable can identify which software version, interfaces, and operating conditions were examined. A subsequent change to that configuration creates a different engineering question and can support a separate testing engagement.

This model places specialist knowledge alongside physical test infrastructure. Spacecraft firmware handles commands and hardware interfaces; a radio link carries traffic using mission-specific settings; a ground system connects people and software to command authority. An assessment provider can examine the interactions among those components within an agreed laboratory scope. The purchased output is an engineering record that the customer can use in its development and acceptance process.

Shared Frameworks Support Specialized Work

The Aerospace Corporation’s SPARTA framework organizes space cyber threats into a shared vocabulary of tactics and techniques. Its published material connects adversary behavior with protective measures and mission analysis. A common vocabulary lets spacecraft engineers and security specialists refer to the same kinds of activity when discussing a system or planning an assessment.

Public frameworks and commercial services occupy complementary positions. The framework describes categories and relationships; the service applies them to a customer’s actual equipment, software, permissions, and records. Much of the paid work lies in translating general descriptions into a specific mission configuration. The result can be an implemented control, a test finding, or an operating procedure associated with an identifiable system.

The National Institute of Standards and Technology addresses the terrestrial side in its report on satellite command and control. Published in December 2022, the report applies the Cybersecurity Framework to the ground segment, including control of spacecraft platforms and payloads. It establishes that the relevant security environment includes the computers and organizations directing a mission from Earth.

This expands the set of possible customers beyond spacecraft manufacturers. Mission-control providers operate software and accounts with access to spacecraft. Ground-station companies handle communications infrastructure. Payload operators manage instruments and customer information. Each participates in a mission with particular responsibilities, and security products can address the interfaces through which those responsibilities are exercised.

New Space Economy’s examination of the space cybersecurity incident record similarly distinguishes spacecraft, ground infrastructure, terminals, and organizational information systems. That distinction is useful commercially because the owner of the affected function is often the organization purchasing its protection. A terminal service and a spacecraft command system involve different equipment, operating teams, and procurement decisions.

A Market Within Connected Space Systems

NIST’s work on hybrid satellite networks describes space systems assembled from independently owned and operated segments. Hosted payloads, ground infrastructure services, and virtualized operations centers are examples. In these arrangements, a mission uses capabilities supplied by several organizations, creating explicit interfaces between their systems.

Those interfaces explain why a separate security supplier can have a defined place in the transaction. A manufacturer can integrate a specialist’s communications protection; an operator can procure an assessment of its ground environment; a connectivity provider can offer encryption to an end customer. The security company supplies a component or service that fits a purchasing decision already present in mission development and operation.

The European Union Agency for Cybersecurity’s 2025 space threat report treats commercial satellite security across development, deployment, operations, and decommissioning. That lifecycle corresponds to different kinds of work. Design integrates controls into a system, deployment establishes the operating configuration, and operations manages access and changes over time. Security spending can occur at more than one stage of the same mission.

The documented commercial pattern is already specific: U-Space purchases embedded protection for satellite platforms, Thuraya presents encryption within its connectivity offerings, and specialist firms develop mission software and laboratory assessment services. Space cybersecurity has identifiable suppliers, products, and purchasing organizations. In the U-Space agreement, that specialization is incorporated directly into satellite production, making security software part of the equipment delivered to mission customers.

YOU MIGHT LIKE

WEEKLY NEWSLETTER

Subscribe to our weekly newsletter. Sent every Monday morning. Quickly scan summaries of all articles published in the previous week.

Most Popular

Featured

FAST FACTS