SBOM analysis from Sumrite, so you know what is really inside your software.
Most of the code you ship or buy was written by someone else. Sumrite builds or checks your software bill of materials, finds the components that put you at risk, proves which vulnerabilities are actually exploitable, and hands you SBOM and VEX evidence that regulators, auditors and enterprise buyers accept.
SPDX and CycloneDXMachine-readable SBOMs that meet the CISA 2026 minimum elements and the CERT-In field list.
Exploitable, not just listedEach vulnerable component is triaged with reachability, CISA KEV and EPSS, then confirmed by a pentester where it matters.
Evidence for every frameworkFindings mapped to CERT-In, SEBI CSCRF, RBI, the EU Cyber Resilience Act, FDA 524B and PCI DSS.
SBOM analysis is the review of a software bill of materials, the machine-readable list of every open-source and third-party component inside an application, container or device. Sumrite generates the SBOM where you do not have one, checks it for missing or wrong components, matches every component against known vulnerabilities and licences, works out which vulnerabilities are actually reachable and exploitable, and delivers a validated SBOM, VEX statements and a prioritised fix plan, with a retest included.
What Sumrite’s SBOM analysis covers
Area
What Sumrite checks
SBOM generation
Builds SPDX or CycloneDX SBOMs from source repositories, build pipelines, container images and compiled binaries, including firmware for IoT and embedded products
Completeness and quality
Compares the SBOM with the real build to find missing transitive dependencies, vendored code, statically linked libraries and wrong versions
Minimum elements
Checks every field against the CISA 2026 minimum elements and the CERT-In SBOM guidelines, including supplier, version, unique identifiers, hashes and licences
Vulnerability matching
Matches components to CVEs and advisories from NVD, OSV and GitHub, then enriches each match with CISA KEV and EPSS
Reachability and exploitability
Confirms whether vulnerable code is loaded and reachable, and tests high-risk cases in a running environment
VEX statements
Issues CycloneDX VEX or OpenVEX records stating which vulnerabilities affect the product and which do not, with the reason
Licence risk
Flags copyleft, unknown and conflicting licences that create legal or commercial exposure
Component health
End-of-life, unmaintained and suspicious packages, typosquats and components pulled from untrusted sources
Supplier SBOM review
Reviews SBOMs received from vendors before you buy or renew, for banks, insurers and regulated buyers
Who needs SBOM analysis
Banks, NBFCs and SEBI-regulated entities
SEBI CSCRF requires SBOMs for core and critical software, and RBI points regulated entities to the CERT-In SBOM guidelines. Sumrite collects, checks and maps them for your audit.
Scope the products and releases. Applications, containers, firmware or supplier software, the releases in scope and the frameworks you need evidence for.
Collect or generate SBOMs. Existing SBOMs are taken as supplied; missing ones are generated from source, build output, images or binaries in SPDX or CycloneDX.
Validate quality. Schema checks, minimum-element checks and a comparison with the real build to catch missing or wrong components.
Analyse risk. Vulnerabilities, licences, end-of-life and untrusted components, enriched with CISA KEV and EPSS.
Confirm exploitability. Reachability analysis and hands-on testing by a Sumrite pentester for the components that matter most.
Report, issue VEX and retest. A prioritised fix plan, VEX statements and a regenerated SBOM after fixes, with a retest of the fixed components.
What you receive
A validated SBOM per product and release, in SPDX or CycloneDX, ready to share with buyers or regulators
VEX statements for every known vulnerability, showing which are exploitable and which are not, with reasons
A risk report ranked by real exploitability: component, version, CVE, KEV and EPSS status, reachability, fix version and effort
A licence and component health summary covering copyleft, unknown licences, end-of-life and unmaintained packages
Mapping to CERT-In SBOM guidelines, SEBI CSCRF, RBI, the EU Cyber Resilience Act, FDA 524B, PCI DSS 4.0 requirement 6.3.2, NCA ECC and SAMA third-party controls
A pipeline recipe to keep SBOMs current on every release, and a retest with an updated SBOM after fixes
SBOM requirements Sumrite maps your evidence to
Regulator or law
What it asks for
CERT-In (India)
Technical Guidelines on SBOM, QBOM and CBOM, AIBOM and HBOM, version 2.0 of July 2025, with minimum data fields for each SBOM
SEBI CSCRF (India)
SBOMs for core and critical software used by regulated entities, including in-house, third-party, legacy and SaaS applications
RBI (India)
Regulated entities advised to adopt the CERT-In SBOM guidelines
EU Cyber Resilience Act
Annex I Part II requires manufacturers to identify and document components, including an SBOM covering at least top-level dependencies, from 11 December 2027
FDA section 524B (US)
An SBOM in every premarket submission for a cyber device
CISA 2026 minimum elements
The baseline fields and practices for any SBOM, adding component hash, licence, tool name and generation context
NCA ECC and SAMA CSF (Saudi Arabia)
Asset inventory, trusted software sources, vulnerability management and third-party controls, which an SBOM evidences directly
Frequently asked questions
What is SBOM analysis?
SBOM analysis is the review of a software bill of materials to check that it is complete and accurate, find vulnerable, unlicensed or end-of-life components, and decide which vulnerabilities are actually exploitable. The output is a validated SBOM, VEX statements and a prioritised fix plan.
Does Sumrite generate the SBOM or only review it?
Both. Sumrite reviews SBOMs you already have or receive from suppliers, and generates SPDX or CycloneDX SBOMs from source code, build pipelines, container images and compiled binaries, including firmware, where none exist.
Which SBOM formats do you support?
SPDX and CycloneDX, the two formats named by CISA, CERT-In and the FDA. VEX is delivered as CycloneDX VEX or OpenVEX.
How is SBOM analysis different from a vulnerability scan?
A scanner reports every CVE it can match, which is usually hundreds of results. SBOM analysis checks the inventory itself, then uses reachability, CISA KEV, EPSS and manual testing to separate the few exploitable vulnerabilities from the noise, and records the decision in VEX.
Can you analyse firmware or software without source code?
Yes. Binary composition analysis identifies libraries compiled into firmware, installers and closed-source applications. Sumrite does IoT, embedded firmware and hardware security testing in-house.
Does an SBOM analysis help with SEBI CSCRF and CERT-In audits?
Yes. The report maps your SBOMs to the CERT-In minimum data fields and the SEBI CSCRF SBOM requirement, and shows how components are tracked and remediated, which is what auditors check.
Is a retest included?
Yes. After fixes Sumrite regenerates the SBOM, re-runs the analysis on the fixed components and updates the report and VEX.