Does DORA require an SBOM? What financial entities and suppliers need
By SBOMBox SBOM experts · · 4 min readShort answer: the Digital Operational Resilience Act (DORA, Regulation (EU) 2022/2554) does not use the word SBOM. But since 17 January 2025 it has required financial entities to identify and document their ICT assets and dependencies, and its technical standards require them to track the third-party and open-source libraries in the software that supports critical functions. An SBOM is the most direct way to do both, so banks, insurers and investment firms increasingly require one from their software suppliers by contract.
Who DORA applies to
- Financial entities in the EU: banks, payment and e-money institutions, investment firms, insurers and reinsurers, crypto-asset service providers, trading venues, fund managers and others listed in Article 2.
- ICT third-party service providers, indirectly through contracts with those entities. Providers designated as critical are also overseen directly by the European Supervisory Authorities.
- Software vendors selling to financial entities: not regulated by DORA itself, but bound by the contractual terms DORA requires (Article 30).
Where SBOMs come in
| Provision | What it requires | How an SBOM helps |
|---|---|---|
| DORA Article 8 (identification) | Identify, classify and document ICT assets and their interdependencies, including those supporting critical or important functions | A per-release component inventory, with dependency relationships |
| Delegated Regulation (EU) 2024/1774, Article 10 (vulnerability and patch management) | Track third-party libraries, including open-source libraries, used by ICT services supporting critical or important functions, and monitor their versions and updates | SBOMs matched continuously against vulnerability feeds |
| DORA Article 28 (register of information) | Keep a register of all contractual arrangements with ICT third-party providers | Supplier SBOMs linked to each contract and product version |
| DORA Article 30 (key contractual provisions) | Contracts must cover security, access, audit and incident assistance | SBOM and VEX delivery written into the contract |
Check the exact article wording in the Official Journal before you rely on it; summaries of DORA's technical standards differ on article numbers.
If you are a financial entity
- Ask each provider of software supporting a critical or important function for an SBOM per release, in CycloneDX or SPDX. Our guide to getting SBOMs from suppliers has contract wording.
- Check the SBOMs for quality, not just existence. The free SBOM checker scores them against CISA, BSI and NTIA rulesets.
- Monitor them continuously and record your assessment of each vulnerability with VEX, so you can show supervisors why something was or was not patched.
- Store them with the register of information, so you can answer 'which of our services use this library?' during an incident.
If you sell software to financial entities
- Expect questionnaires and contract clauses asking for an SBOM per release, vulnerability notification timelines and VEX. See how to answer an SBOM questionnaire.
- Generate the SBOM from the artifact you ship, in CI, every release, and meet the 2026 minimum elements.
- If your software is also a product sold in the EU, the Cyber Resilience Act requires an SBOM in its own right from 11 December 2027.
DORA, NIS2 and the CRA
DORA is the sector-specific rule for finance and takes precedence over NIS2 for the entities it covers. NIS2 covers other critical sectors; see NIS2 and SBOMs. The CRA regulates the products themselves. A software vendor can face all three: DORA and NIS2 through its customers' contracts, and the CRA directly. One SBOM programme built to the strictest of them serves all three; see SBOM regulations by country.
Frequently asked questions
Does DORA require an SBOM?
Not by name. DORA requires financial entities to document ICT assets and dependencies, and its technical standards require tracking of third-party and open-source libraries. An SBOM is the most practical way to meet both, so many financial entities require one from suppliers.
When did DORA start to apply?
DORA has applied since 17 January 2025.
Does DORA apply to software vendors?
Not directly, unless the vendor is designated a critical ICT third-party provider. In practice vendors are bound through the contractual terms DORA requires financial entities to include.
What is the difference between DORA and NIS2?
DORA is the EU's sector-specific operational resilience law for financial entities. NIS2 sets cybersecurity duties for other critical sectors. Where both could apply, DORA takes precedence for financial entities.
This is general information, not legal advice. Confirm how the rules apply to your products with counsel.