Q-Cyber Magazine

Telecom · 19 March 2026 · 3 min read

Telecom supply-chain assurance: Name the equipment, name the software

Indian operators can now combine NCCS's notified ITSAR catalogue with the 2026 SBOM minimum elements, co-authored by CERT-In, to make equipment and software provenance a contract condition rather than a vendor narrative.

Abstract graphic of concentric signal rings in Knowlcom blue

A telecommunications network is a long composition of other people's hardware, firmware and software. If that composition is unnamed, then so is the operator's exposure when a component, a dependency or a signing key fails.

Two inventories, one contract

The ITSAR catalogue is an equipment-class inventory: radio units, distributed and central units, the RIC, routers, switches, customer-premises equipment, subscriber databases, and cryptographic-control standards, each with a document number and a release date. The SBOM is a software inventory: producer, name, version, dependencies, hashes, licence, and a signed author. A modern telecom node needs both. A radio that has been assessed against ITSAR303042601, but whose software composition is unknown, is only half described. A software list that ignores firmware and hardware origin has the opposite gap. The useful test, at acceptance and at each upgrade, is whether an independent reviewer can name the ITSAR, open a signed SBOM, and see how a firmware update would be authenticated. If any of those three artefacts is missing, the composition of the node is still a narrative, not a record.

CERT-In's space-sector language is a useful template even for operators who never touch a satellite. Vet vendors, verify provenance, test firmware, mandate secure updates, and keep the relevant bill of materials. Those sentences can be pasted, with little loss, into a terrestrial radio or core contract.

Exhibit 1

A two-layer supply-chain ask for a telecom procurement

LayerWhat to requirePublic reference
Equipment className the applicable notified ITSAR and the evidence of assessment against itNCCS notified ITSAR list, including ITSAR303042601 and ITSAR303102601 (8 January 2026) for 5G Open RAN
Software and firmware compositionA signed SBOM meeting the 2026 minimum elements, updated at each material change, with unknowns statedCISA and partners, 29 July 2026, co-authored by CERT-In
Provenance and updatesHardware origin, firmware-tamper testing, and a signed, secure update channelCERT-In space and SatCom framework, February 2026, section 5.8
Broader BOM classesWhere AI or hardware-specific inventories are relevant, use CERT-In's AIBOM or HBOM guidance rather than stretching a single listSame CERT-In framework, citing CERT-In technical guidelines on SBOM, QBOM, CBOM, AIBOM and HBOM

Source: NCCS notified ITSAR list; CISA 2026 SBOM minimum elements; CERT-In space framework, February 2026.

Implications

  1. Map the network bill of materials to ITSARs and record any class that has no notified document.
  2. Require signed SBOMs at delivery and at each upgrade, not as a one-time annex.
  3. Put firmware provenance and update channels in the same schedule as software.
  4. Use CERT-In's wider BOM guidance where AI or hardware inventories are needed.

What this means for telecom

Supply-chain assurance is no longer short of public documents. Operators who name ITSARs and SBOMs in the next tender will be able to test vendors against a baseline. Those who accept a narrative in place of an inventory will be reconstructing that inventory later, under time pressure.

Sources

  1. NCCS, Notified ITSARs
  2. 2026 Minimum Elements for a Software Bill of Materials
  3. CERT-In space framework, February 2026, section 5.8