> For the complete documentation index, see [llms.txt](https://www.headlesslaw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.headlesslaw.com/dora/level-3/q-and-a/eba.md).

# EBA

EBA — Digital Operational Resilience Act (DORA) (23 instruments).

EBA under Digital Operational Resilience Act (DORA), ordered by official identifier.

* [EBA Q\&A 2024\_7047 — Q\&A — Critical Services Affected \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7047-critical-services-affected.md)
* [EBA Q\&A 2024\_7050 — Q\&A — Duplicate ICT Incident Reporting \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7050-duplicate-ict-incident-reporting.md)
* [EBA Q\&A 2024\_7096 — Q\&A — Exemption for Non-EU ICT Intra-group Service Providers \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7096-exemption-for-non-eu-ict-intra-group-service-providers.md)
* [EBA Q\&A 2024\_7098 — Q\&A — Scope of Register of Information for Contractual Arrangements \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7098-scope-of-register-of-information-for-contractual-arrangement.md)
* [EBA Q\&A 2024\_7178 — Q\&A — Elaboration on the meaning of a separated and dedicated network for ICT asset administration \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7178-elaboration-on-the-meaning-of-a-separated-and-dedicated-netw.md)
* [EBA Q\&A 2024\_7277 — Q\&A — Template specific instructions: field B\_01.02.0050 (Hierarchy of the financial entity within the group) \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7277-template-specific-instructions-field-b-01-02-0050-hierarchy.md)
* [EBA Q\&A 2024\_7278 — Q\&A — Template specific instructions: field B\_01.02.0060 \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7278-template-specific-instructions-field-b-01-02-0060-lei-of-the.md)
* [EBA Q\&A 2024\_7279 — Q\&A — Template specific instructions: field B\_02.02.0130 (Country of the governing law of the contractual arrangement) \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7279-template-specific-instructions-field-b-02-02-0130-country-of.md)
* [EBA Q\&A 2024\_7281 — Q\&A — Template specific instructions: field B\_02.02.0160 (Location of management of the data) \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7281-template-specific-instructions-field-b-02-02-0160-location-o.md)
* [EBA Q\&A 2024\_7282 — Q\&A — Template specific instructions: field B\_04.01.0040 (Identification code of the branch) \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7282-template-specific-instructions-field-b-04-01-0040-identifica.md)
* [EBA Q\&A 2024\_7283 — Q\&A — Template specific instructions: field B\_05.01.0020 \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7283-template-specific-instructions-field-b-05-01-0020-type-of-co.md)
* [EBA Q\&A 2024\_7284 — Q\&A — Template specific instructions: field B\_05.02.0060 (Identification code of the recipient of sub-contracted ICT services) \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7284-template-specific-instructions-field-b-05-02-0060-identifica.md)
* [EBA Q\&A 2024\_7285 — Q\&A — Template specific instructions: primary keys \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7285-template-specific-instructions-primary-keys.md)
* [EBA Q\&A 2024\_7290 — Q\&A — Definition and scope of ICT services \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2024-7290-definition-and-scope-of-ict-services.md)
* [EBA Q\&A 2025\_7297 — Q\&A — Scope of the regulation described in Article 6 \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2025-7297-the-scope-of-the-regulation-described-in-article-6-mismatche.md)
* [EBA Q\&A 2025\_7309 — Q\&A — ANNUAL REPORT ON NEW ARRANGEMENTS ON THE USE OF ICT SERVICES \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2025-7309-annual-report-on-new-arrangements-on-the-use-of-ict-services.md)
* [EBA Q\&A 2025\_7313 — Q\&A — Part 2: Template specific instructions to template B\_06.01 \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2025-7313-part-2-template-specific-instructions-to-template-b-06-01.md)
* [EBA Q\&A 2025\_7387 — Q\&A — How to fill the refPeriod field of the parameters.csv file \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2025-7387-how-to-fill-the-refperiod-field-of-the-parameters-csv-file-f.md)
* [EBA Q\&A 2025\_7388 — Q\&A — Obligation to maintain a register of information for FEs exempt under article 16 \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2025-7388-obligation-to-maintain-a-register-of-information-for-fes-exe.md)
* [EBA Q\&A 2025\_7439 — Q\&A — Staff costs \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2025-7439-staff-costs.md)
* [EBA Q\&A 2025\_7466 — Q\&A — Public Authorities Exemption \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2025-7466-public-authorities-exemption.md)
* [EBA Q\&A 2025\_7539 — Q\&A — Types of 'telephone services' included under the definition of 'ICT services' \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2025-7539-types-of-telephone-services-included-under-the-definition-of.md)
* [EBA Q\&A 2025\_7613 — Q\&A — Classification of phishing-attacks as a reportable major ICT-related incident \[Final Q\&A\]](/dora/level-3/q-and-a/eba/eba-qa-2025-7613-classification-of-phishing-attacks-as-a-reportable-major-ict.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.headlesslaw.com/dora/level-3/q-and-a/eba.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.