Q-Cyber Magazine
When the telecom path includes a satellite
CERT-In's February 2026 space and SatCom framework treats satellite links, ground stations and user terminals as a reported, segment-controlled estate; terrestrial operators who depend on those links should adopt the same discipline.

A growing share of telecommunications traffic, backhaul and remote coverage now travels, at some point, through space. The security model cannot stop at the terrestrial edge. CERT-In's February 2026 framework was written for that overlap.
Four segments, not a single "satellite risk"
The official text is organised by segment because a failure in any one of them can undermine the others. The spacecraft, the ground station, the link and the user terminal each need authentication, encryption, access control, intrusion detection and secure firmware practice. For a telecom operator, the practical translation is this: a managed satellite service is not a black box. The operator should know who runs the ground station, how firmware is updated, how commands are authenticated, and how an incident on that path will be reported within six hours. Those facts belong in the same operational file as a terrestrial point of presence: a named owner, a current contact, and a tested path to CERT-In, rather than a service description that ends at the satellite provider's logo.
The framework's threat list also explains why availability belongs in the same conversation as confidentiality. Jamming and spoofing are service-affecting events. A network that uses satellite backhaul for remote or backup coverage needs a rehearsed terrestrial fallback, and a rule that an unexpected signal is not treated as authoritative.
Exhibit 1
How a terrestrial operator should read the 2026 SatCom framework
| Framework element | Implication for a telecom estate that uses satellite capacity |
|---|---|
| Stakeholders named | The satellite provider, ground-station operator and terminal vendor are in scope; the terrestrial operator should name them in its own inventory |
| Segments | Space, ground, link and terminal each need controls; a service-level agreement should not hide the ground station |
| Illustrated threats | Plan for jamming, spoofing, unauthorised commands, ground-station compromise and firmware manipulation, not only for data leakage |
| Reporting and logs | Six-hour notice to CERT-In and 180-day logs, consistent with the 2022 directions |
| Supply chain | Provenance, firmware-tamper testing, secure updates, and bills of materials as CERT-In already requires in this framework |
| Terrestrial catalogue | Where ground or customer-premises equipment is also telecom equipment, map it to any applicable NCCS ITSAR |
Source: CERT-In, Cyber Security Framework and Guidelines for Space including Satellite Communication, February 2026; CERT-In Directions, 28 April 2022; NCCS notified ITSAR list.
Implications
- Put satellite providers and ground stations in the network inventory, with points of contact and a reporting path.
- Demand firmware and provenance conditions in SatCom contracts, in line with section 5.8 of the framework.
- Rehearse jamming and spoofing as availability incidents, with an authenticated-source rule and a fallback bearer.
- Align ground and terminal equipment with notified ITSARs where they apply.
What this means for telecom
Satellite capacity is now part of many terrestrial networks. The February 2026 framework gives operators a public way to treat that capacity as a controlled, reported segment, rather than as an unmanaged extension of the wide-area network.


