DORA Article 8 is the part of the EU Digital Operational Resilience Act that requires financial entities to identify, classify, and document ICT-supported business functions, assets, roles, responsibilities, and interdependencies. It also expects inventories to stay current and to reflect major changes so operational resilience can be assessed and managed properly.
Expanded Definition
DORA Article 8 sits within the EU Digital Operational Resilience Act and turns resilience from a general policy goal into a documentation obligation. It requires financial entities to maintain a clear, current view of ICT-supported business functions, supporting assets, and the roles and responsibilities that keep those functions operating. The practical boundary is important: Article 8 is not a generic asset-management note and it is not limited to servers or applications. It is about tracing how ICT underpins business delivery, where the dependencies sit, and what changes when those dependencies shift.
The article is best read as a governance and evidence requirement. A compliant inventory must stay usable over time, which means it has to reflect mergers, platform migrations, outsourcing changes, and major control updates. That matters because resilience assessments depend on whether the organisation can see the chain from business function to ICT dependency to accountable owner. The European Insurance and Occupational Pensions Authority describes DORA as a resilience framework for the financial sector, and that framing is helpful here because Article 8 supports operational resilience rather than standalone configuration hygiene. DORA — Digital Operational Resilience Act
A common misunderstanding is to treat the inventory as a one-time cataloguing exercise. Article 8 is stricter than that: the value lies in keeping the view current enough that management can reason about impact, concentration, and recovery before a disruption exposes the gaps.
Examples and Use Cases
In practice, Article 8 shows up wherever a financial entity has to explain how technology supports business delivery and who owns the risk around it. It is especially visible when organisations are preparing resilience reviews, onboarding providers, or validating whether a major change alters the operational picture.
- A bank maps payment processing to the applications, network services, and third-party platforms that support settlement and reconciliation.
- An insurer documents underwriting workflows, the data feeds they depend on, and the internal teams responsible for maintaining those dependencies.
- A trading venue updates its inventory after a platform migration so the resilience view still reflects the current production architecture.
- A payment firm tracks outsourced hosting and managed services alongside internal assets so it can see where control boundaries sit.
- A financial group uses the inventory to compare business criticality across functions and identify where one ICT failure could affect multiple services.
The main tradeoff is granularity. Too little detail makes the inventory unusable for resilience assessment, while too much detail creates a record that cannot be maintained. Article 8 works best when the inventory is detailed enough to support decision-making but still aligned to the business questions resilience teams actually ask.
Security Implications
When Article 8 is weak, the organisation loses visibility into what depends on what, and that turns resilience into guesswork. The immediate security problem is not just missing documentation; it is misjudging blast radius. If a business service relies on a shared platform, a third-party tool, or a hidden operational dependency, the entity may underestimate how many functions are affected by a fault, patch delay, configuration error, or provider outage.
That gap creates governance failure as well as operational failure. Without a current inventory, responsibility becomes blurred, major changes go unreflected, and resilience testing can miss the very dependencies that matter most. A practitioner should treat stale dependency mapping as an observable warning sign because it often correlates with inconsistent ownership, weak change discipline, and poor recovery assumptions. In the context of DORA, that is a serious issue because operational resilience depends on being able to identify critical dependencies before they become incidents.
The broader consequence is reduced confidence in impact assessment. If leadership cannot see which business functions are exposed to the same underlying ICT dependency, it cannot prioritise remediation, test meaningful failure scenarios, or make credible resilience decisions.
Domain and Governance Relevance
DORA Article 8 matters because it connects operational resilience to accountable governance. The article forces financial entities to describe not only the technology estate, but also the business functions and responsibilities that sit on top of it. That makes it a control for understanding systemic exposure, not just technical inventory quality.
Where non-human identities, service accounts, or automated processes are part of the dependency chain, Article 8 becomes more than an asset register exercise. Those machine-supported pathways can carry critical operational authority, so the inventory has to reflect them accurately enough to show where business function, access path, and recovery responsibility intersect. In other words, the control does not become an NHI control, but it does become materially more useful when the organisation can see which automated components are tied to which business services and who can restore them.
For financial entities, the governance lesson is straightforward: keep the mapping between business service, ICT dependency, and owner current enough that resilience decisions are based on the real operating model, not an outdated diagram.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8 and NIST CSF 2.0 set the technical controls, while DORA and NIS2 define the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| DORA | Article 8 — Identification and Classification of ICT-Supported Business Functions | Directly governs the inventory and dependency-mapping duty discussed here. |
| Recommendation — Maintain a current inventory of ICT-supported business functions, assets, roles, and interdependencies. | ||
| NIS2 | 21(2)(d) — Supply Chain Security | Applies where outsourced and interdependent ICT services affect operational resilience. |
| Recommendation — Map third-party dependencies that can disrupt critical services and update them after material change. | ||
| CIS Controls v8 | 1 — Inventory and Control of Enterprise Assets | Supports the asset visibility needed to keep ICT dependency records usable. |
| 2 — Inventory and Control of Software Assets | Covers the software layer that often underpins ICT-supported functions. | |
| Recommendation — Inventory assets consistently so business-function dependency maps stay accurate and actionable. Track software dependencies so changes do not break the business-function view. | ||
| NIST CSF 2.0 | ID.AM-1 — Physical Devices and Systems Inventoried | Maps to the visibility foundation needed for operational resilience assessment. |
| ID.AM-2 — Software Platforms and Applications Inventoried | Addresses application-level dependencies central to Article 8 mapping. | |
| Recommendation — Identify and maintain the assets that support each critical business function. Keep application inventories current so dependency assessments reflect the live environment. | ||
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 9, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
