What EU Rules Ask of Your Software Supplier
DORA, NIS2, the AI Act, the Cyber Resilience Act and GDPR put duties on the regulated buyer, the manufacturer, the AI provider or deployer, or the controller, and each one reaches a software supplier through a contract term, an audit right or a reporting clock. This guide reads the Official Journal texts and turns them into questions for any vendor, including StepTo, a 15-20 engineer nearshore team in Belgrade.
Reviewed by Igor Gazivoda, Founder & CEO of StepTo · Updated
Which EU rules reach a software supplier?
Six rules matter most. DORA, NIS2, the Cyber Resilience Act, GDPR and the AI Act put duties on the regulated buyer, the manufacturer, the AI provider or deployer, or the controller, and each one reaches a software supplier through a contract term, an audit right or a reporting clock. eIDAS adds a wallet timeline that lands in your product. StepTo is a 15-20 engineer nearshore team in Belgrade, and it makes no compliance or certification claim on this page: the table shows what the law asks you to put to any supplier.
Read on 2026-11-20 from the Official Journal texts. For the AI Act the consolidated version of 27 July 2026 is used. The other five are the texts as first published, so check EUR-Lex for later amendments before you rely on a date. This is a reading aid, not legal advice.
| Rule | Who it binds | What it asks about a supplier | Dates in the Official Journal |
|---|---|---|---|
| DORARegulation (EU) 2022/2554 | Financial entities, the regulated buyer. Chapter V, Section II adds an oversight framework for critical ICT third-party service providers (Article 31). | Article 28: a register of information on every ICT contract, due diligence before contracting, termination rights and exit strategies for critical or important functions. Article 30: the contract content, in writing. | Applies from 17 January 2025 (Article 64). |
| NIS2Directive (EU) 2022/2555 | Essential and important entities (Article 21(1)). It is a directive, so the duties you meet are in the national law of the Member State that applies to you. | Article 21(2)(d): supply chain security, including relationships with direct suppliers. Article 21(2)(e): vulnerability handling and disclosure. Article 21(3): take each supplier's vulnerabilities and secure development procedures into account. Article 23: reporting clocks of 24 hours and 72 hours that bind the entity. | Member States apply their transposing measures from 18 October 2024 (Article 41). |
| AI ActRegulation (EU) 2024/1689 | Providers and deployers of AI systems. Article 25(4) covers the written agreement between the provider of a high-risk system and a third party supplying tools, services or components used in it. | Article 50: tell people they are interacting with an AI system, mark synthetic audio, image, video or text in a machine-readable format, disclose deep fakes. Article 4: measures to support AI literacy of staff. Article 25(4): the written agreement above. | General application 2 August 2026. High-risk systems under Annex III from 2 December 2027 and under Annex I from 2 August 2028 (Article 113). Providers of generative systems placed on the market before 2 August 2026 must meet Article 50(2) by 2 December 2026 (Article 111(4)). |
| Cyber Resilience ActRegulation (EU) 2024/2847 | Manufacturers of products with digital elements, which can be you when you ship software. | Article 13(5): due diligence on third-party components, including open source. Article 13(6): report a vulnerability in a component to whoever maintains it. Article 14: for actively exploited vulnerabilities, an early warning within 24 hours, a notification within 72 hours and a final report no later than 14 days after a corrective or mitigating measure is available; for severe incidents, the same 24 and 72 hour clocks and a final report within one month of the incident notification. | Chapter IV (Articles 35 to 51) from 11 June 2026, Article 14 from 11 September 2026, the rest from 11 December 2027 (Article 71). |
| GDPRRegulation (EU) 2016/679 | Controllers, who may only use processors that give sufficient guarantees (Article 28(1)). | Article 28(2): no other processor without written authorisation. Article 28(3): a binding contract covering documented instructions, confidentiality, Article 32 measures, assistance, deletion or return at your choice, and information and audits. Article 28(4): the same duties passed to any sub-processor. | Applies from 25 May 2018 (Article 99). |
| eIDASRegulation (EU) 2024/1183 | Member States, which provide European Digital Identity Wallets, and private relying parties that must use strong user authentication (Article 5f(2)), except micro and small enterprises. | Article 5a(1): each Member State provides at least one wallet. Article 5f(2): those private relying parties also accept wallets, only on the voluntary request of the user. | Relative to the implementing acts: within 24 months (wallets) and no later than 36 months (acceptance) of their entry into force (Articles 5a(1) and 5f(2)). The first implementing acts, Implementing Regulation (EU) 2024/2977, were published on 4 December 2024 and entered into force on 24 December 2024, so the 24-month wallet date falls at the end of 2026 and the 36-month acceptance date on 24 December 2027. |
What should you ask a supplier under each rule?
Put these in writing before you sign, and tick an answer only when it is in the proposal or the contract. They are questions to ask any vendor. The vendor scorecard turns twelve general checks into a score, and the software RFP template carries your answers into a brief.
DORA: questions for the supplier
- Which functions and ICT services does the contract describe, and may the supplier subcontract any of them, under what conditions? (Article 30(2)(a))
- In which regions or countries are services provided and data processed, and will you be told in advance of a change? (Article 30(2)(b))
- How are your data returned in an easily accessible format on insolvency, discontinuation or termination? (Article 30(2)(d))
- What help does the supplier give in an ICT incident, at no extra cost or at a cost fixed in advance? (Article 30(2)(f))
- What termination rights and minimum notice periods apply? (Article 30(2)(h))
- For critical or important functions: what audit and access rights, and what transition period lets you move to another provider or in-house? (Article 30(3)(e) and (f))
Article 3 defines ICT services as digital and data services provided through ICT systems on an ongoing basis. Whether a given development engagement falls under that definition is a question for your counsel, not this page.
NIS2: questions for the supplier
- What does the supplier do to secure its own supply chain, and what evidence of secure development procedures can it show? (Article 21(2)(d) and 21(3))
- How does it handle and disclose vulnerabilities in what it builds for you? (Article 21(2)(e))
- How quickly will it tell you about an incident that touches your systems? Your early warning is due within 24 hours of becoming aware and your incident notification within 72 hours (Article 23(4)), so the supplier's notice has to reach you sooner than that.
- Does the contract say who notifies whom, and in what form, before an incident happens?
AI Act: questions for the supplier
- Does the work add an AI system that talks to people or generates synthetic audio, image, video or text? If so, who builds the disclosure and the machine-readable marking that Article 50 asks for?
- Who is the provider and who is the deployer for each AI system under the Act, and is that written down?
- If the system is high-risk, is there the written agreement Article 25(4) describes between its provider and whoever supplies tools or components?
- Who supports the AI literacy of the people who operate AI systems on your behalf? (Article 4)
The 2024 text set 2 August 2026 for most high-risk obligations. Regulation (EU) 2026/1744 of 8 July 2026 moved them, which is why this page quotes the consolidated version.
Cyber Resilience Act: questions for the supplier
- Which third-party components, including open source, go into the product, and how does the supplier check them? (Article 13(5))
- If a vulnerability turns up in a component, who reports it to the maintainer and who fixes it? (Article 13(6))
- If an actively exploited vulnerability is found, how fast does the supplier tell you, given that your early warning is due within 24 hours (Article 14(2)(a))?
- What support period does the contract assume? Article 13(8) sets at least five years, or the expected use time where that is shorter.
GDPR: questions for the supplier
- Does the processor contract cover each item Article 28(3) lists, in writing (Article 28(9))?
- Which sub-processors will touch the data, and how are you told of a change? (Article 28(2) and (4))
- At the end of the work, are personal data deleted or returned at your choice? (Article 28(3)(g))
- What information does the supplier give so you can show compliance and run an audit? (Article 28(3)(h))
Article 28(3) describes what the buyer's processor contract must contain. It is a duty on the controller's paperwork, and this page does not say who signs it.
eIDAS: questions for the supplier
- If your product authenticates users, who builds and tests the wallet integration, and which dates does the contract assume (the wallet date at the end of 2026 and 24 December 2027 for acceptance)?
- Does the supplier's estimate separate the wallet work from your existing login work?
What does StepTo state, and what does it not?
StepTo makes no DORA, NIS2, AI Act, Cyber Resilience Act or GDPR compliance claim, and no certification claim, on this page. StepTo's published offers are staff augmentation, dedicated teams and projects, not regulatory consulting.
What StepTo does state is short: NDA and IP assignment terms are signed before any work begins. Questions on certifications and personal-data handling are topics StepTo answers on the discovery call, and the pre-answered due diligence sheet lists them next to the answers we do publish. How the work is run is on the engineering practices page.
StepTo's rate card is $25-85/hr, and the pricing page shows it by seniority. A procurement file can start from published numbers instead of a quote. For the model itself, see staff augmentation, or the fintech software development page if you are building for a regulated firm.
Where do larger suppliers win on regulation?
A buyer whose procurement requires a certified supplier, or regulatory consulting from the vendor itself, should shortlist firms that publish both. Each statement below is taken from the company's own site as of 2026-11-20.
- Endava reports SOC 2 Type II, several ISO certificates and TISAX on its certifications page as of 2026-11-20. On certification a regulated buyer filters on first, Endava simply wins. Its DORA glossary page reads "Before enforcement starts ... must comply with DORA by January 17, 2025" as of 2026-11-20. Article 64 gives the same 17 January 2025 date; the regulation has applied since then.
- Sigma Software lists a DORA compliance consulting page and a Cyber Resilience Act compliance services page in its services sitemap as of 2026-11-20. We did not read either page.
- Future Processing reports ISO 27001 and ISO 9001 on its about-us page and mentions NIS2, DORA and the AI Act on its how-we-deliver page as of 2026-11-20.
StepTo is a 15-20 engineer team and does not compete on scale, certificates or consulting. It competes on a published rate card. For how it works as a nearshore team, see the nearshore development page and the outsourcing glossary.
Where can you read more on each rule?
The StepTo blog has an engineering-side article for most of the rules above.
- DORA ICT Risk and Your Development Partner
Our article on DORA's third-party rules and what they mean for a software development contract and exit plan.
- NIS2 Supply Chain: Your Dev Partner In Scope
Our article on Article 21(2)(d) and how supply chain duties reach a software supplier as contract clauses.
- AI Act Article 50: What Applies Now
Our article on the transparency obligations as an engineering task, and the high-risk deferral.
- EU Cyber Resilience Act: The 24-Hour Clock
Our article on the Article 14 reporting duty and why outsourcing does not transfer it.
- Outsourced Developers and Production Data Access
Our article on GDPR, processors and whether an outsourced team should touch production data at all.
- EUDI Wallet: What Engineering Teams Must Build
Our article on the digital identity wallet timeline and the parts of your data model it breaks.
What do buyers ask StepTo about EU regulation?
Is StepTo DORA, NIS2 or AI Act compliant?
StepTo makes no compliance or certification claim on this page. DORA, NIS2, the AI Act, the Cyber Resilience Act and GDPR put duties on the regulated buyer, the AI provider or deployer, the product manufacturer or the controller, and the Official Journal texts read for this page show what each asks you to put to a supplier. A buyer whose procurement requires a certified supplier should choose one that holds the certificate.
What does StepTo sign before work starts?
NDA and IP assignment terms are signed before any work begins. Questions on certifications and personal-data handling are topics StepTo answers on the discovery call, and the pre-answered due diligence sheet on stepto.net lists them.
What commercial terms does StepTo publish?
StepTo's rate card is $25-85/hr. A dedicated team of three starts from $13,500 per month, billed monthly. Replacement is free within the first 30 days, and the terms are a 3-month minimum, then 30 days notice to scale down. Read them against the contract elements your counsel lists.
Does StepTo offer regulatory compliance consulting?
StepTo's published offers are staff augmentation, dedicated teams and projects, not regulatory consulting. If you need a vendor that delivers DORA or Cyber Resilience Act consulting, larger firms such as Sigma Software list those services, and this page names where they win.
Who is StepTo and where is it based?
StepTo is a 15-20 engineer nearshore team based in Belgrade, Serbia, on CET, founded in 2020. Name the countries where work is done and data is processed in your contract, which DORA Article 30(2)(b) lists for regulated buyers.
Send us your supplier questions
Bring the questions above to a first call. Messages sent through the contact form are answered within one business day.
Or reach us directly
Office hours
Sent on a weekend: we reply on the next business day.
Contracting party: StepTo d.o.o. Company details are on the Imprint page.
Send us a message
StepTo's Belgrade team replies within one business day.
It starts with a 15-minute intro call. If there is a fit, a 60-minute discovery call follows. Engineers can typically start within one to two weeks of first contact; a full team usually takes two to four weeks.
