cm/controlmapping
Sources
DORA · Chapter II: ICT risk management
Art.9(4)(e)

Protection and prevention

frameworkDORA (Regulation (EU) 2022/2554) sectionChapter II: ICT risk management csf 2.0— topics— frameworks0 2 0 11
Official textimplement documented policies, procedures and controls for ICT change management, including changes to software, hardware, firmware components, systems or security parameters, that are based on a risk assessment approach and are an integral part of the financial entity’s overall change management process, in order to ensure that all changes to ICT systems are recorded, tested, assessed, approved, implemented and verified in a controlled manner;Regulation (EU) 2022/2554 (DORA), Official Journal of the European Union. © European Union, https://eur-lex.europa.eu (reuse authorised with acknowledgement; only the Official Journal text is authentic)

Wrong or missing mapping? Report it

Equivalents of Art.9(4)(e) in other frameworks
FrameworkRequirementTitleLinkSource / reason
NIST CSF 2.0—No requirementNo mapping in our dataNo mapping in our data.
ISO 27001A.8.32Change managementEditorialControlMapping editorial: All three require documented, risk-based change management in which changes are recorded, tested, approved and verified.
CIS v8.1—No requirementNo mapping in our dataNo mapping in our data (most CIS links are editorial: CIS's published crosswalk covers 49 of 153 safeguards).
SOC 2—No requirementNo mapping in our dataNo mapping in our data (SOC 2 links are editorial only).
PCI DSS—No requirementNo mapping in our dataNo mapping in our data.
CMMC—No requirementNo mapping in our dataNo mapping in our data.
800-53—No requirementNo mapping in our dataNo mapping in our data.
HIPAA—No requirementNo mapping in our dataNo mapping in our data.
GDPR—No requirementNo mapping in our dataNo mapping in our data (only GDPR's security articles are mapped, editorially).
NIS26.4Change management, repairs and maintenanceEditorialControlMapping editorial: All three require documented, risk-based change management in which changes are recorded, tested, approved and verified.
Essential Eight—No requirementNo mapping in our dataNo mapping in our data (Essential Eight links are editorial only).
CPS 234—No requirementNo mapping in our dataNo mapping in our data (CPS 234 is principles-based and its links are editorial).
Cyber Essentials—No requirementNo mapping in our dataNo mapping in our data (Cyber Essentials covers five technical controls only).

Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · Loosely related only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.