A Russian satellite’s reported maneuvers near the orbital path of ICEYE X36 have renewed a practical question about commercial satellite protection: how governments and operators coordinate when a privately operated spacecraft supports military users. In an October 15 CSIS commentary, Clayton Swope and Chantal Li argue that the United States and European partners should establish a coordinated response to potential hostile activity involving Cosmos 2612.
Their analysis concerns a possible threat, not a confirmed attack. Its significance lies in the relationship between orbital behavior and the services delivered on Earth. A commercial imaging satellite can remain privately operated while providing information used by a government during conflict. Protecting that service involves tracking spacecraft, maintaining operations, and establishing responsibilities before an incident interrupts delivery.
The underlying orbital analysis, published by ISR University on October 14, describes a sequence beginning September 30. Cosmos 2612 reportedly raised its orbit, adjusted its inclination on October 7, and descended on October 12 to approximately 555 kilometers, close to ICEYE X36’s altitude. The analysis attributes observations to commercial tracking providers.
That sequence matters because altitude and orbital-plane alignment affect how spacecraft move relative to one another. The reported climb changed the rate at which Cosmos 2612’s orbital plane rotated around Earth. Its later descent brought the two planes into closer alignment. Once spacecraft occupy similar orbital planes, adjusting their separation along the orbit can require less propulsion than correcting a substantial difference between planes.
The report placed Cosmos 2612 about 475 kilometers behind X36 on October 13. That is a dated observation, not a current separation measurement. It interpreted the maneuvers as preparation for possible proximity operations but did not establish the Russian spacecraft’s payload or intended action. This distinction separates observable movement from an assessment of what that movement could enable.
ICEYE’s role in Ukraine illustrates why commercial infrastructure attracts government attention. Under an agreement announced in August 2022, the company provided Ukraine with use of one satellite’s capabilities over the region and access to imagery from its wider constellation. ICEYE retained responsibility for operating the designated satellite. That earlier agreement establishes the service relationship; it does not identify X36 as the spacecraft designated in 2022.
Synthetic aperture radar produces images from transmitted radio signals and their returning echoes. Unlike an optical camera dependent on illumination, radar can collect observations at night and through cloud cover. This makes commercial radar imagery useful for monitoring areas where lighting and weather restrict optical observations. The government customer receives an information service without having to build, launch, and operate every component itself.
Commercial satellite protection consequently involves more than preventing physical destruction. A maneuver can affect an observation schedule even if the spacecraft remains functional. ESA’s explanation of collision-avoidance costs describes the staff time, propellant consumption, and interrupted data collection associated with changing an orbit. Those are general operational effects, not measured losses attributed to the reported Cosmos 2612 encounter.
For an imaging customer, the immediate consequence could be a missed opportunity to observe a location at the required time. For the operator, responding involves assessing the available tracking information and the effects of possible maneuvers on the mission. The distinction between safeguarding a spacecraft and preserving its output helps explain the commercial significance of monitoring unusual orbital behavior.
New Space Economy’s coverage of the earlier encounter discusses the operational responsibilities raised by reported Russian approaches to an ICEYE satellite in May. The October analysis adds a different concern: the reported effort to establish sustained orbital alignment. Treating the episodes separately avoids confusing an earlier close pass with the later maneuver sequence.
NATO’s Commercial Space Strategy provides an existing framework for several parts of this problem. Endorsed in February 2025, it seeks continued commercial service availability during peace, crisis, and conflict. It proposes arrangements with groups of providers, greater participation in exercises, and faster exchange of space-domain-awareness information between military, civilian, and commercial organizations.
For operators and public customers, those proposals identify work that can be done before an emergency. Contact arrangements, compatible information formats, and practiced reporting procedures can shorten the path from detecting unusual behavior to assessing its effect on a contracted service. The value comes from making information usable across organizational boundaries.
The strategy also calls for examining financial and contractual measures that could reduce commercial partners’ exposure to risk. Its discussion of deterrence and defense places potential responses before the North Atlantic Council for approval. These provisions describe a process for cooperation and decision-making, rather than a predetermined response to the specific activity around ICEYE X36.
Independent research connects those policy provisions to lessons from Ukraine. A RAND study of wartime space services, by Andrew Radin and colleagues, recommends formal contracts that address service provision under hostile interference. It also recommends clearer expectations about the commercial and government information that partners could receive during a conflict. The research was largely completed in July 2024, so it supplies historical context rather than evidence about the October 2026 maneuvers.
RAND’s findings support a practical division of responsibilities. Operators need defined service obligations and procedures for communicating disruptions. Government customers need to understand which services remain available under different circumstances and how alternative providers could help. Exercises can test these arrangements before an actual disruption forces decisions under time pressure. The study also emphasizes cybersecurity, since service continuity depends on ground infrastructure and data access as well as spacecraft.
Swope and Li’s central policy argument is that allied governments should clarify how they would respond to hostile activity near commercial satellites. Their recommendation addresses the political dimension of a system that already depends on private operators, tracking companies, and government users working together. For commercial satellite protection, the operational objective is specific: shared observations must reach decision-makers promptly, responsibilities must be established, and customers must retain access to the information their missions require.
Useful Books Available on Amazon
