Concept and mechanism
Banking infrastructure supports outcomes with deadlines, data, and accountable owners. A custody service may require applications, databases, external files, calendars, and people authorized to validate exceptions. Technical inventory is necessary but does not alone describe this chain. Building the map from the expected outcome helps identify shared dependencies and places where failure prevents operation. Record each connection’s owner, the period when it is needed, and evidence of operation. Basel Committee resilience principles support identifying critical operations and their interdependencies; this lesson’s examples are fictional applications of those concepts.
Guided application
Before estimating the project, clarify scope, critical periods, data classification, and acceptance criteria. High availability without a measure leaves different teams working toward different outcomes. A monitoring view should distinguish available components, completed flow, and validated result. If a portal responds but positions are stale, service may remain degraded. Also record the nature of references used: legislation, supervisory expectations, and good practices are distinct categories. The July 2025 ECB cloud guide clarifies expectations without creating new legal obligations. The institution’s responsible function validates concrete applicability against current documents.
Example: at 06:40 a position file is missing. Mapping connects provider, receipt, validation, and NAV calculation, allowing communication of the deadline-blocking stage.
Common pitfalls
Machine inventory treated as complete mapping; HTTP 200 treated as current data; vague requirement treated as approved architecture.
Related topics: Identity, connectivity, and protection · Resilience and data recovery · Operations, batch, and observability
Connect service, dependency, owner, and evidence before choosing a solution.
Reference: Principles for operational resilience · DR banking infrastructure professional assessment2026.10