01

Why suppliers feel DORA

Financial entities must manage ICT risk and information about supplier arrangements. Services supporting critical or important functions can receive more detailed assessment and terms.

This does not automatically place every small provider under direct supervision, but customer contracts and controls may still apply.

02

Describe the service clearly

Document scope, data, service and processing locations, subcontractors, dependencies, service levels and contacts. Material changes should not surprise the customer.

  • service and supported processes;
  • administrative access controls;
  • data and delivery locations;
  • subcontractors and chains;
  • monitoring and incident cooperation;
  • data return or deletion and exit support.

03

Turn clauses into operations

Incident notification needs a scope, channel and responsible people. Audit rights need secure evidence-sharing. Recovery targets require architecture and regular tests.

The largest risk is signing a standard annex without checking whether teams can fulfil every commitment. Give each clause an owner and procedure.

04

Prepare a supplier evidence pack

Collect architecture and data-flow descriptions, access controls, backup tests, incident process, subcontractor list, continuity and exit arrangements.

Be specific and proportionate. If a control is being built, provide an owner and target date rather than claiming it already exists.

SOURCES

Verified source material

Information was checked on the publication date. Legal obligations should always be assessed for the specific organisation and use case.

  1. EBA — Digital Operational Resilience Act
  2. Komisja Europejska — akty wykonawcze DORA