Operational resilience starts with knowing what each business service depends on. That knowledge usually sits across a CMDB, a vendor register, contract files and incident tooling. Affectli brings it into one ontology, so concentration risk and incident impact can be read directly from the model.

  1. Your systems stay where they are. Nothing is replaced.
  2. Affectli connects to each of them, where they run.
  3. Every reading is checked on its way in.
  4. One live register of services, systems and the providers behind them.
Third-party risk

ICT third-party register and concentration risk

Which critical functions depend on which providers, and where several rest on one.

FunctionICT ProviderContractDependency
Incidents

Major ICT incident classification and reporting timeline

Incident, affected services and classification recorded as they happen, so the report is built from the record.

IncidentAffected ServiceClassificationReport
Resilience

Operational resilience mapping

Important business services traced to the systems, teams and suppliers they rely on.

Business ServiceSystemTeamSupplier
Server racks with status lights in a data centre aisle
Object · Business Service Degraded
BS-CARDS
Card payments
Impact tolerance2 h
Systems7 · 1 degraded
ICT providers4 · 2 critical
ConcentrationPRV-031 · 3 functions
Open incidentINC-0389 · classifying
Context

DORA, Regulation (EU) 2022/2554, has applied to EU financial entities since 17 January 2025. It covers ICT risk management, incident reporting, resilience testing, third-party risk and the register of information. Banking and financial market infrastructure are also sectors under the CER Directive (EU) 2022/2557 and NIS2 Annex I.

Affectli can hold the service, provider and incident records this work draws on. Each entity remains responsible for its own compliance.

Sources: Regulation (EU) 2022/2554 · Directive (EU) 2022/2557 · NIS2 Directive, Annex I
Next step

Show us where your systems disagree.

Tell us your industry, the decision that matters most and the systems involved. Our team will show how one ontology brings them together.