DORA Audit at an ICT Service Provider
The internal audit function of an international telecommunications provider had ADVISORI review whether its contractual DORA obligations towards more than 2,000 regulated customers are embedded in its own processes.
- 2,000+customers with contractual requirements in audit scope
- 2business units audited
- 4requirement dimensions in the audit programme
- 20PDperson-days over a period of 3 months
At a glance
- Assignment
- Supporting Internal Audit in planning, conducting and debriefing an audit in the area of “DORA readiness”.
- Audit subject
- Degree of implementation of contractual DORA obligations (in particular Art. 30) in two business units of an international telecommunications provider.
- Result
- A documented maturity level, deficiencies made visible, and pragmatic recommendations, above all on steering subcontractors.
Regulated customers pass their DORA obligations on by contract
The telecommunications provider’s customers include regulated companies such as banks and insurers. They impose contractual requirements that stem from DORA. The provider has to know these requirements and reflect them in its own processes.
Internal Audit wanted to know whether the requirements of these regulated customers are already embedded in the internal control processes. The audit covered the degree of implementation of contractual DORA obligations in two business units.
Three audit questions on the state of implementation
The objective was to audit how far the contractual requirements of DORA-regulated customers have been implemented. This led to three questions on which the audit programme is built.
- Audit question 1
Are the requirements known?
Are the contractual requirements of more than 2,000 customers known and systematically recorded?
- Audit question 2
Are internal processes sufficient?
Do internal processes meet the requirements, for example in business continuity management measures?
- Audit question 3
Are subcontractors steered?
Are the company’s subcontractors steered effectively?
Six steps from audit programme to audit report
Define audit objective and scope
Delimiting and agreeing the audit objective and scope, then drawing up the audit programme.
Categorise the requirements
Structuring the requirements into dimensions: subcontractor steering, business continuity management, audit rights, and certificates and assurance.
Conduct interviews
Interviews with the contacts in the respective business functions.
Collect and assess evidence
Recording and assessing the evidence against the audit questions.
Prepare the audit report
Assessing deficiencies and developing recommendations to raise the maturity level.
Present the results
Presenting the report and debriefing the audit.
| Subcontractor steeringFocus | Steering of the subcontractors used. |
|---|---|
| Business continuity management | BCM measures contractually assured to customers. |
| Audit rights | Inspection and audit rights of regulated customers. |
| Certificates and assurance | Evidence the provider uses to demonstrate that requirements are met. |
What the audit delivered for the company
Awareness in business functions and management
The customers’ DORA requirements are present in the business functions and in management.
Detailed maturity level of implementation
The state of implementation is recorded in detail, with a focus on steering subcontractors.
Pragmatic recommendations
Concrete measures to raise the maturity level, for example adequate resourcing of the provider-steering function.
Conclusion
The audit made existing deficiencies visible and produced pragmatic solutions. It contributed significantly to problem awareness within the business functions.
Talk to the team behind this project


Philip Güntsch
Philip Güntsch bringt umfassende Expertise in der Leitung komplexer IT-Projekte mit C-Level-Sponsoren (CISO, CRO, CIO, COO) in regulierten Branchen mit. Sein Fachwissen erstreckt sich auf operative IT-Resilienz, IT-Transformation, Third Party Risk Management und operatives Risikomanagement im Kontext regulatorischer Anforderungen wie DORA und VAIT. Er verfügt über langjährige Erfahrung in der Führung von Projektteams (3 bis >50 Personen) und der Anwendung seiner Expertise bei Gap-Analysen, der Umsetzung von Mitigationsmaßnahmen und der vertraglichen Anpassung von ICT-Drittparteien. Er profitiert von seinem Fachwissen in der Entwicklung geopolitischer Impact-Assessments, dem Aufbau von Nearshore Resilience Services und der Durchführung von über ITSCM- und BCM-Projekten.
- Informationssicherheit
- Information Security
- IT-Resilienz
- IT-Transformation
- Third Party Risk Management
- Risikomanagement
- Regulatorik
- DORA
- VAIT
- Gap-Analyse
- Mitigationsmaßnahmen
- Impact Assessment
- Nearshore
- ITSCM
- BCM