Your SBOM Won’t Cover Crypto Risk. Here’s Why CBOM Is the CISO’s Next Test

Your SBOM Won’t Cover Crypto Risk. Here’s Why CBOM Is the CISO’s Next Test

Why SBOM then, and why CBOM now?

The Software Bill of Materials (SBOM) entered mainstream security practice and government mandates in 2021, after the SolarWinds breach showed how malicious code could be slipped into trusted software updates. The Log4j vulnerability followed soon after, affecting hundreds of millions of devices worldwide.

Now a new term is surfacing among India’s security community in the post-quantum cryptography (PQC) conversation: the Cryptographic Bill of Materials (CBOM).

The urgency is real. Adversaries are already harvesting encrypted data today to decrypt it once quantum computers mature, and regulators are tightening rules on cryptographic visibility. Without knowing where legacy encryption hides, organisations cannot patch exposed APIs, prevent sudden certificate outages, or plan a PQC transition before classical encryption breaks.

Why CBOM? The regulatory shift

In July 2025, CERT-In released Version 2.0 of its technical guidelines. It moved beyond software transparency to explicitly include CBOMs alongside Quantum, AI and Hardware BOMs. Government, public-sector and essential-services organisations, and the software export and services ecosystem that supports them, must now integrate CBOMs into procurement, development and vulnerability management.

On paper, this looks like a routine compliance update. In practice, it is a major accountability shift for Indian CISOs.

The timelines are tight. India’s Quantum Mission Task Force has set a 2029 migration target for critical sectors such as banking, telecom and power, and 2033 for the rest of the economy.

Dr. Rajkumar Upadhyay, CEO of C-DOT and Chairman of the task force, told CISONow: “Organizations have to know their cryptographic inventories because systems have been built over time. You need to discover your CBOM and conduct a vulnerability assessment to see which systems are most exposed.” He added that organisations “need not struggle because such discovery and assessment tools are available from us and others.”

What a CBOM actually does and Why it Matters?

A CBOM is a structured, machine-readable inventory of every cryptographic asset in an enterprise. It maps algorithms, key lengths, digital certificates, protocols and dependencies across code, cloud and hardware.

Its value goes well beyond quantum readiness. A functional CBOM:

  • Exposes hidden vulnerabilities: It flags weak ciphers, expired certificates and hardcoded keys before attackers or outages exploit them.
  • Measures crypto-agility: It shows whether an algorithm is hardcoded into legacy software or can be swapped at the configuration layer without rewriting applications.
  • Enforces vendor accountability: It gives security teams auditable proof of what third-party software runs under the hood, turning compliance from guesswork into measurable risk management.

Reality check: what the US GAO audit found

To see what happens when enterprises underestimate cryptographic discovery, look at the US Government Accountability Office (GAO) report released in October 2026, Quantum Computing: Federal Actions Needed to Prepare for Emerging Cyber Threat.

Despite years of federal mandates, 22 of 24 major US agencies had only partially inventoried systems using vulnerable cryptography. Only one had finished.

The root causes are a warning for Indian CISOs:

  • Process vacuum: 23 agencies had no documented process to keep inventories current as systems changed.
  • Manual blind spots: 19 did not use automated discovery tools to verify cryptographic assets.
  • Classification errors: 18 reported severe cryptographic skill shortages. Several flagged quantum-safe symmetric algorithms such as AES while missing the real threat to public-key cryptography such as RSA and ECC.

If well-funded federal agencies stumble on static spreadsheets and manual guesswork, Indian enterprises running complex hybrid-cloud and legacy banking estates will hit the same wall unless they learn from these traps early.

Why Your SBOM Isn’t Enough

A common misconception is that an existing SBOM programme covers cryptographic risk. It does not.

An SBOM lists the libraries and packages an application uses. A CBOM shows what is inside them: which algorithms are active, how keys are configured and where certificates live. Knowing you run a given version of OpenSSL tells you little if developers hardcoded a deprecated RSA-2048 key exchange into a customer-facing API.

This is why standards such as OWASP CycloneDX, and emerging minimum-element models such as CATALOGA, are gaining traction. Researcher Basil Hess noted in his 2026 work on CycloneDX standardisation that enterprises struggle with inconsistent algorithm naming and configuration-driven cryptography.

A useful CBOM must do more than list algorithms. It must capture runtime context, business criticality, and whether weak encryption can be replaced without breaking the application.

The CBOM checklist for Indian enterprises

CERT-In places responsibility at both ends of the supply chain. Suppliers must provide complete CBOMs. Consumer organisations must maintain internal inventories, validate vendor claims and feed them into vulnerability workflows. Avoiding the GAO’s traps takes three shifts:

  1. Never take a vendor’s CBOM on faith. With CERT-In, SEBI and the RBI tightening supply-chain oversight, a vendor’s inventory shows only how software was built, not how it runs in your environment. Use independent automated scanning across source code, IaC and live TLS endpoints.
  2. Automate for drift, not one-time audits. Static inventories go stale as developers deploy microservices and certificates rotate daily. Generate CBOMs continuously in CI/CD pipelines and runtime environments to catch “shadow cryptography” the moment it reaches production.
  3. Anchor migration in business criticality, not panic. NIST IR 8547 sets deprecation timelines for vulnerable public-key standards, and attackers are running “harvest-now, decrypt-later” campaigns against long-lived data. Map your CBOM against your asset registry and direct PQC budgets to high-value assets first.

The bottom line

A CBOM won’t make you quantum-safe overnight, but it ends wilful blindness. As CERT-In’s guidelines become baseline expectations across banking, telecom and critical infrastructure, “we didn’t know that algorithm was there” will no longer satisfy boards or regulators.

The quantum threat is still maturing, but the cryptographic visibility crisis is already here. Indian CISOs who automate and verify their CBOMs today will be ready for PQC migration, and they will have proof that they control their digital trust.

 

Senior Associate Editor - APAC (CISONow)
Senior Associate Editor at  | Editorial | Bilaspur, Chhattisgarh | prajeet@observenow.co.in | + posts

Nair is a seasoned cybersecurity journalist with over a decade of experience covering cybersecurity and OT developments in the US and the Asia-Pacific region. As an editor, he has interviewed key decision-makers, including CISOs, CIOs, regulators and law enforcement leaders. Before joining ObserveNow, Nair held editorial roles at Information Security Media Group, News Corp owned TechCircle, IDG, The Times Group and The New Indian Express. He is currently based in Bilaspur, India.

Share:

Author

Prajeet Nair

Nair is a seasoned cybersecurity journalist with over a decade of experience covering cybersecurity and OT developments in the US and the Asia-Pacific region. As an editor, he has interviewed key decision-makers, including CISOs, CIOs, regulators and law enforcement leaders. Before joining ObserveNow, Nair held editorial roles at Information Security Media Group, News Corp owned TechCircle, IDG, The Times Group and The New Indian Express. He is currently based in Bilaspur, India.

Chat with CISONow.in