DORA
DORA Chapter II: ICT Risk Management

DORA DORA-Art.8: Identification

Financial entities shall identify, classify and adequately document all ICT-supported business functions, roles and responsibilities, the information assets and ICT assets supporting them, and their interdependencies, and identify all sources of ICT risk on a continuous basis.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 68 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

SOC 2 · 7 controls

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-C1.2 C1.2 Disposing of confidential information
  • SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC3.3 CC3.3 Considering fraud risk (COSO principle 8)
  • SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

NIST SP 800-161 Rev 1 · 6 controls

FedRAMP High · 5 controls

  • CM-12 Information Location (CM-12)
  • CM-8 System Component Inventory
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • RA-2 Security Categorization
  • RA-9 Criticality Analysis (RA-9)

FedRAMP Moderate · 5 controls

  • CM-12 Information Location (CM-12)
  • CM-8 System Component Inventory
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • RA-2 Security Categorization
  • RA-9 Criticality Analysis (RA-9)
  • NIST-CSF-GV.OC-05 Outcomes, capabilities, and services that the organization depends on are understood and communicated
  • NIST-CSF-ID.AM-01 Inventories of hardware managed by the organization are maintained
  • NIST-CSF-ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained
  • NIST-CSF-ID.AM-05 Assets are prioritized based on classification, criticality, resources, and impact on the mission
  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
  • CPS230-11 Identification, Assessment and Management of Operational Risk
  • CPS230-P25 Information and Technology Capability and Asset Health
  • CPS230-P26 Assessment of Business and Strategic Decisions on the Risk Profile
  • CPS230-P27 Comprehensive Assessment of the Operational Risk Profile

C5 (Germany) · 4 controls

CIS Controls v8 · 4 controls

  • CIS-1.1 Establish and Maintain Detailed Enterprise Asset Inventory
  • CIS-2.1 Establish and Maintain a Software Inventory
  • CIS-3.2 Establish and Maintain a Data Inventory
  • CIS-3.7 Establish and Maintain a Data Classification Scheme

ISO 27001:2022 · 4 controls

  • 5.12 Classification of information
  • 5.2 Information security roles and responsibilities
  • 5.9 Inventory of information and other associated assets
  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 4 controls

  • 5.12 Classification of information
  • 5.2 Information security roles and responsibilities
  • 5.9 Inventory of information and other associated assets
  • 8.8 Management of technical vulnerabilities

NIST SP 800-53 Rev 5 · 4 controls

  • CFTC-SS-17 Enterprise Technology Risk Assessment
  • CFTC-SS-29 Recovery Plan Accounts for Essential Service Providers
  • CFTC-SS-4 Systems Operations Category

NIS2 Directive · 2 controls

  • Art.21.2.a Policies on risk analysis and on information system security
  • Art.21.2.i Human resources security, access control policies and asset management
  • EBA-GL-3.3.2 Identification of functions, processes and assets

GDPR · 1 control

ISO 10005:2005 · 1 control

  • 5.14 Identification and traceability

ISO 22301:2019 · 1 control

  • 8.3.2 Identification of strategies and solutions

ISO 9001:2015 · 1 control

  • 8.5.2 Identification and traceability

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in DORA Chapter II: ICT Risk Management

You are reading one control. How much of DORA have you already done?

DORA DORA-Art.8 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of DORA your existing evidence covers. Hold NIS2 Directive and 17 of 26 DORA controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIS2 Directive pair alone.

Query this from an agent

The graph holds this control, the 68 it maps to, and the evidence behind each claim, over MCP and REST.