DIR-05 · Stakeholder reporting and transparency
Catalogue · Direct & Oversee
The organisation reports on technology performance, risk and compliance to its stakeholders, including regulators, in an accurate and timely way.
Typical activities
- Define which stakeholders receive which reports and how often
- Produce a regular management report covering performance, risk, incidents and compliance
- Meet regulatory reporting obligations with named owners and tracked deadlines
Evidence an assessor would expect
- Reporting calendar with owners
- Issued board or regulator reports
- Log of regulatory submissions and deadlines
Capability scale
- 0 · Absent
- The practice is not performed, or happens so rarely that it produces no recognisable outcome.
- 1 · Initial
- The practice is performed informally and its results depend on the people involved.
- 2 · Repeatable
- The practice is planned, assigned and tracked, with basic records kept.
- 3 · Defined
- The practice follows a documented, organisation-wide approach with clear roles and measurable outputs.
- 4 · Measured
- The practice is managed with quantitative targets and its performance is monitored and reported.
- 5 · Optimising
- The practice is continuously improved using performance data, external comparison and automation.
Regulatory requirements
- supporting DORA Art. 5 · Governance and organisation
- supporting DORA Art. 11 · Response and recovery
- supporting DORA Art. 14 · Communication
- supporting DORA Art. 19 · Reporting of major ICT-related incidents
- supporting DORA Art. 28 · ICT third-party risk: general principles
- supporting NIS 2 Art. 23 · Reporting obligations
Cross-references
- COBIT® 2019 EDM05
- ISO/IEC 38500 Principle 6 · Human behaviour
Identifiers only, for orientation. Consult the original publications for their content.