DORA and NIS2 · For regulated firms and the technology providers they rely on
Keep the services running. EA keeps the evidence current.
EA takes the work DORA or NIS2 asks of you. In scope, that’s the information and communication technology (ICT) risk framework, the register of information and the yearly review. As a provider, it’s the evidence behind each customer’s resilience terms. EA drafts from your own records, and your Head of Technology Risk approves.
Supplying a regulated firm? See the provider’s path.
Try EA free. No card needed.
Organisations that run work on EA
The work
Resilience lives in the services. The proof lives everywhere else.
The register’s facts sit in contracts
Each row of the register of information is one contract for ICT services: the supplier, the function it supports and where the data sits. Those facts are in contracts that procurement, legal and the business each keep in their own place.
The review comes round regardless
The framework is reviewed at least once a year and again after a major incident, and under DORA the register goes to your competent authority early each year. The evidence for both sits with teams who are busy running the services in between.
As an ICT provider
Each bank, its own terms
Each bank’s contract asks for tested continuity, a workable exit plan and prompt notice of incidents, each in its own wording.
Getting it done means a review your management body can approve on its evidence, and a register that matches the contracts behind it.
What EA does
This year’s review, built from this year’s evidence.What your contracts promise, evidenced before anyone asks.
Follow a financial firm’s yearly review of its ICT risk framework through EA. For a NIS2 entity, the steps are the same, with the cybersecurity risk-management measures in the framework’s place.
A regulated customer’s contract holds you to resilience terms. EA keeps the evidence for each one current, across your customers.
01 / 05
- EA
Reads last year’s approved framework, the incident log, the change log and new contracts since, and lists what each policy and service needs this year, with its owner. Knowledge Library
Your teamThe Head of Technology Risk confirms the scope and the date the management body meets.
- EA
Drafts a register entry for each new or changed contract (provider, service, function supported, data location) from the contract itself, and marks the fields a contract leaves open, such as the subcontractor behind a messaging service. Autofill Workspaces
Your teamContract owners confirm their entries; the business decides which functions are critical or important.
- EA
Matches each policy to this year’s records and flags those out of date, such as a payments continuity test last run in 2024. It sends one request to each owner and follows up. EA Agent
Your teamThe Head of Payments Technology reruns the continuity test, and each service owner files this year’s records for their own service.
- EA
Writes up what changed, what was tested and what was found, with each finding’s owner and remediation date, every statement beside its source. EA Agent
Your teamService owners correct the findings that concern them.
- EA
Fills the register in your own template, which can be the competent authority’s spreadsheet template if that’s the form you keep it in, and assembles it with the review report and the updated policies for the management body. Approvals
Your teamThe Head of Technology Risk approves, the management body approves the framework, and your team sends the register when the competent authority collects it.
01 / 04
- EA
Reads your customer contracts and lists each resilience commitment (notice of incidents, continuity testing, exit support, audit access) with the customers it applies to and its owner. EA Agent
Your teamLegal confirms the list.
- EA
Finds the record behind each commitment, from the latest continuity test to the incident notification procedure, and marks “Needs evidence” where none exists, such as an exit plan nobody has written down. Knowledge Library
Your teamThe Head of Operations supplies what’s missing.
- EA
Drafts the exit plan from your data export runbook and the exit schedules in your contracts, and updates the subcontractor list from procurement’s records. EA Agent
Your teamThe Head of Engineering corrects the detail.
- EA
Brings the approved evidence together as one pack, kept current as tests and plans are renewed. Approvals
Your teamThe Head of Technology Risk approves, and you share the pack with a customer by a secure link when its audit rights call for it.
One register entry, from contract clause to approval: we’ll show you in the demo.
Book a demoThrough the year
The register follows each contract you sign.
A new contract
When a contract is signed, EA drafts its register entry from the contract for the contract owner to confirm, so the register is already current on 31 December, the date it is reported as at.
Before the register goes in
Your competent authority sets its own date for the register, before its 31 March deadline to the European supervisors. A reminder your administrator sets in EA asks each contract owner with an entry still open to confirm it ahead of that date.
After a major incident
EA lists the policies, plans and tests the incident touched, so the review that follows starts from them.
The next yearly review
Next year’s review opens on this year’s approved framework and register, with each owner’s part waiting for them to confirm.
- Arrangement
- Cloud hosting, core banking
- Function supported
- Critical, confirmed by the business
- Contract clause
- Hosting agreement, schedule 3
- Data location
- Ireland
- Subcontractor
- Data centre operator, named in schedule 5
- Approved by
- Head of Technology Risk, Tuesday 09:35
- Contract renewal
- April 2028 Current
As an ICT provider
One evidence pack behind each customer’s due diligence.
Each regulated customer also sends its own due diligence questionnaire and asks for the facts its register needs. The evidence pack you’ve already approved is the source for those answers, so each customer hears the same thing.
EA’s own security
EA will be a row in your register too.
We ran our own ISO 27001 certification on EA: read how it ran on the ISO 27001 page. The facts you’ll record about us:
- Hosted your way
EA’s cloud in a region you choose, hybrid options or on-premises. Data never used to train the models EA runs on.
- Access
Single sign-on, which you can enforce, and an access list for each workspace.
- Support access
EA staff see your data only in a time-limited window you open.
- Testing
An independent firm runs a penetration test on EA every year.
- Security contact
EA’s security team is at security@eaglobal.ai.
In the demo, see who can open your register, and how each entity’s register stays in its own workspace.
Book a demoFAQ
Questions from teams with a framework to keep.
An entry for each contract under which an ICT provider serves your firm: the service, the functions it supports, the subcontractors behind it and where the data is held. You keep it current as contracts change, and your competent authority can ask for it.
Your competent authority, or for NIS2 the national authority that supervises you, which can ask for the register and the review report. If you’re the provider, each customer checks under the audit rights in its contract. EA prepares what they look at, and your team sends it.
EA fills each field from the contract or record it cites. If a contract says nothing about where data is stored, the field stays “Needs evidence” and the contract owner is asked, and no entry counts until your Head of Technology Risk approves it.
Only the people you add to the register’s workspace. The register names each provider you rely on, so keep that workspace to the few who need it; an auditor sees it only by a link you can revoke.
The terms differ more than the work. Financial firms work to DORA, and essential and important entities in NIS2’s sectors work to their national rules, but both ask for a framework the management body approves, evidence that it works and a hold on your suppliers. As a provider, the rules usually reach you through customers’ contracts, unless you’re a managed service or cloud provider within NIS2’s scope yourself.
EA can draft the review that follows a major incident from your incident records, and carry its lessons into the yearly review. The initial notifications, on the regulator’s clock, stay with your incident team.
The drafting and the upkeep. Your advisers interpret the rules and shape the framework; EA drafts the documents, gathers each year’s evidence and keeps the register current after the programme ends.
Yes. A register already in a spreadsheet, last year’s review or a shelf of policies is enough to begin, and our Customer Success team helps with exports from other platforms. Plans differ by the number of autofills, the workspaces you need and the size of your knowledge library; see the pricing page.
Your next framework review, without pulling teams off the services.
The yearly review, to your Head of Technology Risk.
Related frameworks, and the sectors these rules reach.
Related solutions
- Vendor security assessmentsFor providers, customers’ questionnaires draw on the evidence pack approved here.Security and IT
- ISO 27001Certified controls supply much of the framework’s evidence, already approved for the audit.Security and IT
- NIST CSFFirms that profile against the Cybersecurity Framework (CSF) rate their outcomes from the same test reports and policies.Security and IT
By industry
Banking and building societiesEach entity in the group keeps its own register, and EA drafts each from the same approved evidence.
InsurancePolicy administration and claims often run on outside providers, each a row in the register.
Energy and utilitiesOperators within NIS2 keep the same framework and supplier records for their national authority.

