Comparison
Essential Eight vs DORA
ASD Essential Eight · DORA (Regulation (EU) 2022/2554) · data 2026-10-27
Requirement-level comparison of ASD Essential Eight and DORA (Regulation (EU) 2022/2554), in both directions, derived from published crosswalks and ControlMapping's curated topics.
Of 22 DORA (Regulation (EU) 2022/2554) requirements, 11 map to something in Essential Eight, 2 are only loosely related, and 9 have no mapping in our data.
DORA here means the articles that bind financial entities, mapped editorially at paragraph level. The technical standards that add detail, such as Delegated Regulation (EU) 2024/1774, are not mapped, so technical topics they cover show no link.
Likely new work: DORA requirements with no mapping to Essential Eight (9)
| DORA | Requirement | Match | Essential Eight | Evidence |
|---|---|---|---|---|
| Chapter II: ICT risk management · 6 | ||||
| Art.5 | Governance and organisation | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Art.6 | ICT risk management framework | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Art.7 | ICT systems, protocols and tools | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Art.13 | Learning and evolving | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Art.14 | Communication | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Art.16 | Simplified ICT risk management framework | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Chapter IV: Resilience testing · 1 | ||||
| Art.24 | General requirements for the performance of digital operational resilience testing | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Chapter V: ICT third-party risk · 1 | ||||
| Art.29 | Preliminary assessment of ICT concentration risk at entity level | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Chapter VI: Information sharing · 1 | ||||
| Art.45 | Information-sharing arrangements on cyber threat information and intelligence | No mapping in our data | — | No mapping to Essential Eight in our data. |
Check these: only loosely related (a shared CSF outcome, not a mapping) (2)
| DORA | Requirement | Match | Essential Eight | Evidence |
|---|---|---|---|---|
| Chapter V: ICT third-party risk · 2 | ||||
| Art.28 | General principles | ISM-1412ISM-1485ISM-1486+5 | Only shares CSF PR.PS-01: related, not a mapping | |
| Art.30 | Key contractual provisions | ISM-1412ISM-1485ISM-1486+5 | Only shares CSF PR.PS-01: related, not a mapping | |
Mapped (11)
| DORA | Requirement | Match | Essential Eight | Evidence |
|---|---|---|---|---|
| Chapter II: ICT risk management · 5 | ||||
| Art.8 | Identification | Editorial | ISM-1807ISM-1698ISM-1699+3 | Same topic: Asset Management, Vulnerability Mgmt (editorial pick) |
| Art.9 | Protection and prevention | Editorial | ISM-0109ISM-1906ISM-1907+21 | Same topic: Cont. Monitoring (editorial pick) |
| Art.10 | Detection | Editorial | ISM-1228 | Same topic: Anomaly Detection (editorial pick) |
| Art.11 | Response and recovery | Editorial | ISM-1819 | Same topic: Incident Response (editorial pick) |
| Art.12 | Backup policies and procedures, restoration and recovery procedures and methods | Editorial | ISM-1511ISM-1515ISM-1707+3 | Same topic: Backup & Recovery (editorial pick) |
| Chapter III: ICT-related incidents · 3 | ||||
| Art.17 | ICT-related incident management process | Editorial | ISM-1819 | Same topic: Incident Response (editorial pick) |
| Art.18 | Classification of ICT-related incidents and cyber threats | Editorial | ISM-0123ISM-0140ISM-1819 | Same topic: Reporting, Incident Response (editorial pick) |
| Art.19 | Reporting of major ICT-related incidents and voluntary notification of significant cyber threats | Editorial | ISM-0123ISM-0140 | Same topic: Reporting (editorial pick) |
| Chapter IV: Resilience testing · 3 | ||||
| Art.25 | Testing of ICT tools and systems | Editorial | ISM-1698ISM-1699ISM-1701+3 | Same topic: Vulnerability Mgmt (editorial pick) |
| Art.26 | Advanced testing of ICT tools, systems and processes based on TLPT | Editorial | ISM-1698ISM-1699ISM-1701+3 | Same topic: Vulnerability Mgmt (editorial pick) |
| Art.27 | Requirements for testers for the carrying out of TLPT | Editorial | ISM-1698ISM-1699ISM-1701+3 | Same topic: Vulnerability Mgmt (editorial pick) |
Of 126 ASD Essential Eight requirements, 45 map to something in DORA, 76 are only loosely related, and 5 have no mapping in our data.
Essential Eight here means the ISM controls ASD tags for Maturity Levels One to Three; each row shows its levels (ML1–ML3). ASD publishes no crosswalk to other frameworks, so every match is ControlMapping editorial.
Likely new work: Essential Eight requirements with no mapping to DORA (5)
| Essential Eight | Requirement | Match | DORA | Evidence |
|---|---|---|---|---|
| Application control · 5 | ||||
| ISM-1582 | ML2, ML3 Application control rulesets are validated at least annually | No mapping in our data | — | No mapping to DORA in our data. |
| ISM-1656 | ML3 Application control is implemented on non-internet-facing servers | No mapping in our data | — | No mapping to DORA in our data. |
| ISM-1658 | ML3 Application control restricts the execution of drivers to an organisation-approved set | No mapping in our data | — | No mapping to DORA in our data. |
| ISM-1659 | ML3 Microsoft’s vulnerable driver blocklist is implemented | No mapping in our data | — | No mapping to DORA in our data. |
| ISM-1871 | ML2, ML3 Application control is applied to all locations other than user profiles and temporary… | No mapping in our data | — | No mapping to DORA in our data. |
Check these: only loosely related (a shared CSF outcome, not a mapping) (76)
| Essential Eight | Requirement | Match | DORA | Evidence |
|---|---|---|---|---|
| Patch applications · 6 | ||||
| ISM-0304 | ML3 Applications other than office productivity suites, web browsers and their extensions… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1690 | ML1, ML2, ML3 Patches, updates or other vendor mitigations for vulnerabilities in online services are applied within two weeks of… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1692 | ML3 Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF applications, and security products are applied within 48… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1700 | ML2, ML3 A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in applications other than office… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1901 | ML3 Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF applications, and security products are applied within two weeks of release when… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1905 | ML1, ML2, ML3 Online services that are no longer supported by vendors are removed | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| Patch operating systems · 10 | ||||
| ISM-1407 | ML3 The latest release, or the previous release, of operating systems are used | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1694 | ML1, ML2, ML3 Patches, updates or other vendor mitigations for vulnerabilities in operating systems of internet-facing servers and internet-facing network devices are applied within two weeks… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1696 | ML3 Patches, updates or other vendor mitigations for vulnerabilities in operating systems of workstations, non-internet-facing servers and non-internet-facing network devices are applied within 48 hours of… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1697 | ML3 Patches, updates or other vendor mitigations for vulnerabilities in drivers are applied within one month of release… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1703 | ML3 A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in drivers | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1879 | ML3 Patches, updates or other vendor mitigations for vulnerabilities in drivers are applied within 48 hours of release… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1900 | ML3 A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in firmware | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1902 | ML3 Patches, updates or other vendor mitigations for vulnerabilities in operating systems of workstations, non-internet-facing servers and non-internet-facing network devices are applied within one month of… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1903 | ML3 Patches, updates or other vendor mitigations for vulnerabilities in firmware are applied within 48 hours of release… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| ISM-1904 | ML3 Patches, updates or other vendor mitigations for vulnerabilities in firmware are applied within one month of release… | Art.8(2)Art.9(4)(f)Art.25(1)+2 | Only shares CSF ID.RA-01, PR.PS-02: related, not a mapping | |
| Multi-factor authentication · 9 | ||||
| ISM-1505 | ML3 Multi-factor authentication is used to authenticate human users of data repositories | Art.9(4)(d) | Only shares CSF PR.AA-03: related, not a mapping | |
| ISM-1680 | ML1, ML2, ML3 Multi-factor authentication (where available) is used to authenticate human users to… | Art.9(4)(d) | Only shares CSF PR.AA-03: related, not a mapping | |
| ISM-1681 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate customers to online customer… | Art.9(4)(d) | Only shares CSF PR.AA-03: related, not a mapping | |
| ISM-1682 | ML2, ML3 Multi-factor authentication used for authenticating human users of systems is… | Art.9(4)(d) | Only shares CSF PR.AA-03: related, not a mapping | |
| ISM-1873 | ML2 Multi-factor authentication used for authenticating customers of online customer services provides a… | Art.9(4)(d) | Only shares CSF PR.AA-03: related, not a mapping | |
| ISM-1874 | ML3 Multi-factor authentication used for authenticating customers of online customer services is phishing-resistant | Art.9(4)(d) | Only shares CSF PR.AA-03: related, not a mapping | |
| ISM-1892 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate human users to their organisation’s online customer services that… | Art.9(4)(d) | Only shares CSF PR.AA-03: related, not a mapping | |
| ISM-1893 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate human users to third-party online customer services that process… | Art.9(4)(d) | Only shares CSF PR.AA-03: related, not a mapping | |
| ISM-1894 | ML3 Multi-factor authentication used for authenticating human users of data repositories is… | Art.9(4)(d) | Only shares CSF PR.AA-03: related, not a mapping | |
| Restrict administrative privileges · 11 | ||||
| ISM-1649 | ML3 Just-in-time administration is used for the administration of systems and their resources | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1650 | ML2, ML3 Privileged user account and security group management events are centrally logged | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1685 | ML2, ML3 Credentials for break glass accounts, local administrator accounts and service accounts… | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1686 | ML3 Credential Guard functionality is enabled | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1687 | ML2, ML3 Privileged operating environments are not virtualised within unprivileged operating… | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1688 | ML1, ML2, ML3 Unprivileged user accounts cannot be used to log on to privileged operating environments | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1689 | ML1, ML2, ML3 Privileged user accounts (excluding local administrator accounts) cannot be used to log… | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1861 | ML3 Local Security Authority protection functionality is enabled | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1883 | ML1, ML2, ML3 Privileged user accounts explicitly authorised to access online services are strictly… | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1897 | ML3 Remote Credential Guard functionality is enabled | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1898 | ML3 Secure Admin Workstations are used in the performance of administrative activities | Art.9(4)(c) | Only shares CSF PR.AA-05: related, not a mapping | |
| Application control · 5 | ||||
| ISM-0843 | ML1, ML2, ML3 Application control is implemented on workstations | Art.9(1)Art.10(1)Art.10(3) | Only shares CSF DE.CM-09: related, not a mapping | |
| ISM-1490 | ML2, ML3 Application control is implemented on internet-facing servers | Art.9(1)Art.10(1)Art.10(3) | Only shares CSF DE.CM-09: related, not a mapping | |
| ISM-1544 | ML2, ML3 Microsoft’s recommended application blocklist is implemented | Art.9(1)Art.10(1)Art.10(3) | Only shares CSF DE.CM-09: related, not a mapping | |
| ISM-1657 | ML1, ML2, ML3 Application control restricts the execution of executables, libraries, scripts… | Art.9(1)Art.10(1)Art.10(3) | Only shares CSF DE.CM-09: related, not a mapping | |
| ISM-1870 | ML1, ML2, ML3 Application control is applied to user profiles and temporary folders used by operating… | Art.9(1)Art.10(1)Art.10(3) | Only shares CSF DE.CM-09: related, not a mapping | |
| Restrict Microsoft Office macros · 11 | ||||
| ISM-1487 | ML3 Only privileged human users responsible for checking that Microsoft Office macros are… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1488 | ML1, ML2, ML3 Microsoft Office macros in files originating from the internet are blocked | Art.9(1)Art.9(2)Art.9(3)(a)+5 | Only shares CSF DE.CM-09, PR.DS-02: related, not a mapping | |
| ISM-1489 | ML1, ML2, ML3 Microsoft Office macro security settings cannot be changed by human users | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1671 | ML1, ML2, ML3 Microsoft Office macros are disabled for human users that do not have a demonstrated… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1672 | ML1, ML2, ML3 Microsoft Office macro antivirus scanning is enabled | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1673 | ML2, ML3 Microsoft Office macros are blocked from making Win32 API calls | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1674 | ML3 Only Microsoft Office macros running from within a sandboxed environment, a Trusted… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1675 | ML3 Microsoft Office macros digitally signed by an untrusted publisher cannot be enabled… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1676 | ML3 Microsoft Office’s list of trusted publishers is validated at least annually | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1890 | ML3 Microsoft Office macros are checked to ensure they are free of malicious code before… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1891 | ML3 Microsoft Office macros digitally signed by signatures other than V3 signatures cannot… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| User application hardening · 19 | ||||
| ISM-1412 | ML2, ML3 Web browsers are hardened using ASD and vendor hardening guidance, with the most… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1485 | ML1, ML2, ML3 Web browsers do not process web advertisements from the internet | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1486 | ML1, ML2, ML3 Web browsers do not process Java from the internet | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1542 | ML2, ML3 Microsoft Office is configured to prevent activation of Object Linking and Embedding… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1585 | ML1, ML2, ML3 Web browser security settings cannot be changed by human users | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1621 | ML3 Windows PowerShell 2.0 is disabled or removed | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1622 | ML3 PowerShell is configured to use Constrained Language Mode | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1654 | ML1, ML2, ML3 Internet Explorer 11 is disabled or removed | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1655 | ML3 .NET Framework 3.5 (includes .NET 2.0 and 3.0) is disabled or removed | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1667 | ML2, ML3 Microsoft Office is blocked from creating child processes | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1668 | ML2, ML3 Microsoft Office is blocked from creating executable content | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1669 | ML2, ML3 Microsoft Office is blocked from injecting code into other processes | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1670 | ML2, ML3 PDF applications are blocked from creating child processes | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1823 | ML2, ML3 Office productivity suite security settings cannot be changed by human users | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1824 | ML2, ML3 PDF application security settings cannot be changed by human users | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1859 | ML2, ML3 Office productivity suites are hardened using ASD and vendor hardening guidance, with… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1860 | ML2, ML3 PDF applications are hardened using ASD and vendor hardening guidance, with the most… | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1889 | ML2, ML3 Command line process creation events are centrally logged | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1896 | ML3 Memory integrity functionality is enabled | Art.28(8)Art.30(2) | Only shares CSF PR.PS-01: related, not a mapping | |
| Regular backups · 5 | ||||
| ISM-1705 | ML2, ML3 Privileged user accounts (excluding backup administrator accounts) cannot access… | Art.12(1)Art.12(2)Art.12(3) | Only shares CSF PR.DS-11, RC.RP-03: related, not a mapping | |
| ISM-1706 | ML3 Privileged user accounts (excluding backup administrator accounts) cannot access their… | Art.12(1)Art.12(2)Art.12(3) | Only shares CSF PR.DS-11, RC.RP-03: related, not a mapping | |
| ISM-1708 | ML3 Backup administrator accounts are prevented from modifying and deleting backups during… | Art.12(1)Art.12(2)Art.12(3) | Only shares CSF PR.DS-11, RC.RP-03: related, not a mapping | |
| ISM-1812 | ML1, ML2, ML3 Unprivileged user accounts cannot access backups belonging to other user accounts | Art.12(1)Art.12(2)Art.12(3) | Only shares CSF PR.DS-11, RC.RP-03: related, not a mapping | |
| ISM-1813 | ML3 Unprivileged user accounts cannot access their own backups | Art.12(1)Art.12(2)Art.12(3) | Only shares CSF PR.DS-11, RC.RP-03: related, not a mapping | |
Mapped (45)
| Essential Eight | Requirement | Match | DORA | Evidence |
|---|---|---|---|---|
| Patch applications · 6 | ||||
| ISM-1691 | ML1, ML2 Patches, updates or other vendor mitigations for vulnerabilities in office productivity suites, web browsers and their extensions, email clients, PDF applications, and security products are applied within two weeks of release | Editorial | Art.9(4)(f) | Same topic: Patch Management (editorial pick) |
| ISM-1693 | ML2, ML3 Patches, updates or other vendor mitigations for vulnerabilities in applications other… | Editorial | Art.9(4)(f) | Same topic: Patch Management (editorial pick) |
| ISM-1698 | ML1, ML2, ML3 A vulnerability scanner is used at least daily to identify missing patches or updates for vulnerabilities in online… | Editorial | Art.8(2)Art.25(1)Art.26(1)+1 | Same topic: Vulnerability Mgmt (editorial pick) |
| ISM-1699 | ML1, ML2, ML3 A vulnerability scanner is used at least weekly to identify missing patches or updates… | Editorial | Art.8(2)Art.25(1)Art.26(1)+1 | Same topic: Vulnerability Mgmt (editorial pick) |
| ISM-1704 | ML1, ML2, ML3 Office productivity suites, web browsers and their extensions, email clients, PDF… | Editorial | Art.9(4)(f) | Same topic: Patch Management (editorial pick) |
| ISM-1876 | ML1, ML2, ML3 Patches, updates or other vendor mitigations for vulnerabilities in online services are applied within 48 hours of… | Editorial | Art.9(4)(f) | Same topic: Patch Management (editorial pick) |
| Patch applications & Patch operating systems · 2 | ||||
| ISM-1807 | ML1, ML2, ML3 An automated method of asset discovery is used at least fortnightly to support the… | Editorial | Art.8(1)Art.8(2)Art.8(4)+4 | Same topic: Asset Management, Vulnerability Mgmt (editorial pick) |
| ISM-1808 | ML1, ML2, ML3 A vulnerability scanner with an up-to-date vulnerability database is used for… | Editorial | Art.8(2)Art.25(1)Art.26(1)+1 | Same topic: Vulnerability Mgmt (editorial pick) |
| Patch operating systems · 5 | ||||
| ISM-1501 | ML1, ML2, ML3 Operating systems that are no longer supported by vendors are replaced | Editorial | Art.9(4)(f) | Same topic: Patch Management (editorial pick) |
| ISM-1695 | ML1, ML2 Patches, updates or other vendor mitigations for vulnerabilities in operating systems of workstations, non-internet-facing servers and non-internet-facing network devices are applied within one month of release | Editorial | Art.9(4)(f) | Same topic: Patch Management (editorial pick) |
| ISM-1701 | ML1, ML2, ML3 A vulnerability scanner is used at least daily to identify missing patches or updates for vulnerabilities in… | Editorial | Art.8(2)Art.25(1)Art.26(1)+1 | Same topic: Vulnerability Mgmt (editorial pick) |
| ISM-1702 | ML1, ML2, ML3 A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in operating systems of… | Editorial | Art.8(2)Art.25(1)Art.26(1)+1 | Same topic: Vulnerability Mgmt (editorial pick) |
| ISM-1877 | ML1, ML2, ML3 Patches, updates or other vendor mitigations for vulnerabilities in operating systems of internet-facing servers and internet-facing network devices are applied within 48 hours… | Editorial | Art.9(4)(f) | Same topic: Patch Management (editorial pick) |
| Multi-factor authentication · 7 | ||||
| ISM-0974 | ML2, ML3 Multi-factor authentication is used to authenticate unprivileged human users of systems | Editorial | Art.9(4)(d) | Same topic: Multi-Factor Auth (editorial pick) |
| ISM-1173 | ML2, ML3 Multi-factor authentication is used to authenticate privileged human users of systems | Editorial | Art.9(4)(d) | Same topic: Multi-Factor Auth (editorial pick) |
| ISM-1401 | ML1, ML2, ML3 Multi-factor authentication uses either: something people have and something people… | Editorial | Art.9(4)(d) | Same topic: Multi-Factor Auth (editorial pick) |
| ISM-1504 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate human users to their organisation’s online services that process… | Editorial | Art.9(4)(d) | Same topic: Multi-Factor Auth (editorial pick) |
| ISM-1679 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate human users to third-party online services that process, store or… | Editorial | Art.9(4)(d) | Same topic: Multi-Factor Auth (editorial pick) |
| ISM-1683 | ML2, ML3 Successful and unsuccessful multi-factor authentication events are centrally logged | Editorial | Art.10(3) | Same topic: Logging & Audit (editorial pick) |
| ISM-1872 | ML2, ML3 Multi-factor authentication used for authenticating human users of online services is… | Editorial | Art.9(4)(d) | Same topic: Multi-Factor Auth (editorial pick) |
| Restrict administrative privileges · 9 | ||||
| ISM-0445 | ML1, ML2, ML3 Privileged human users are assigned a dedicated privileged user account to be used… | Editorial | Art.9(4)(c) | Same topic: Privileged Access (editorial pick) |
| ISM-1175 | ML1, ML2, ML3 Privileged user accounts (excluding those explicitly authorised to access online… | Editorial | Art.9(4)(c) | Same topic: Privileged Access (editorial pick) |
| ISM-1380 | ML1, ML2, ML3 Privileged human users use separate privileged and unprivileged operating environments | Editorial | Art.9(4)(c) | Same topic: Privileged Access (editorial pick) |
| ISM-1387 | ML2, ML3 Administrative activities are conducted through jump servers | Editorial | Art.9(4)(c) | Same topic: Privileged Access (editorial pick) |
| ISM-1507 | ML1, ML2, ML3 Requests for privileged access to systems and their resources are validated when first… | Editorial | Art.9(4)(c) | Same topic: Privileged Access (editorial pick) |
| ISM-1508 | ML3 Privileged access to systems and their resources is limited to only what is required… | Editorial | Art.9(4)(c) | Same topic: Privileged Access (editorial pick) |
| ISM-1509 | ML2, ML3 Privileged access events are centrally logged | Editorial | Art.10(3) | Same topic: Logging & Audit (editorial pick) |
| ISM-1647 | ML2, ML3 Privileged access to systems and their resources are disabled after 12 months unless… | Editorial | Art.9(4)(c) | Same topic: Privileged Access (editorial pick) |
| ISM-1648 | ML2, ML3 Privileged access to systems and their resources are disabled after 45 days of inactivity | Editorial | Art.9(4)(c) | Same topic: Privileged Access (editorial pick) |
| Application control · 1 | ||||
| ISM-1660 | ML2, ML3 Allowed and blocked application control events are centrally logged | Editorial | Art.10(3) | Same topic: Logging & Audit (editorial pick) |
| User application hardening · 1 | ||||
| ISM-1623 | ML2, ML3 PowerShell module logging, script block logging and transcription events are centrally… | Editorial | Art.10(3) | Same topic: Logging & Audit (editorial pick) |
| Regular backups · 6 | ||||
| ISM-1511 | ML1, ML2, ML3 Backups of data, applications and settings are performed and retained in accordance… | Editorial | Art.12(1)Art.12(2)Art.12(3) | Same topic: Backup & Recovery (editorial pick) |
| ISM-1515 | ML1, ML2, ML3 Restoration of data, applications and settings from backups to a common point in time… | Editorial | Art.11(6)Art.12(1)Art.12(2)+2 | Same topic: Disaster Recovery, Backup & Recovery (editorial pick) |
| ISM-1707 | ML2, ML3 Privileged user accounts (excluding backup administrator accounts) are prevented from… | Editorial | Art.12(1)Art.12(2)Art.12(3) | Same topic: Backup & Recovery (editorial pick) |
| ISM-1810 | ML1, ML2, ML3 Backups of data, applications and settings are synchronised to enable restoration to a… | Editorial | Art.12(1)Art.12(2)Art.12(3) | Same topic: Backup & Recovery (editorial pick) |
| ISM-1811 | ML1, ML2, ML3 Backups of data, applications and settings are retained in a secure and resilient manner | Editorial | Art.12(1)Art.12(2)Art.12(3) | Same topic: Backup & Recovery (editorial pick) |
| ISM-1814 | ML1, ML2, ML3 Unprivileged user accounts are prevented from modifying and deleting backups | Editorial | Art.12(1)Art.12(2)Art.12(3) | Same topic: Backup & Recovery (editorial pick) |
| Logging and incident response (all strategies) · 8 | ||||
| ISM-0109 | ML3 Event logs from workstations are analysed in a timely manner to detect cyber security… | Editorial | Art.9(1)Art.10(3) | Same topic: Cont. Monitoring (editorial pick) |
| ISM-0123 | ML2, ML3 Cyber security incidents are reported to the chief information security officer, or one… | Editorial | Art.18(1)Art.19(1)Art.19(3)+1 | Same topic: Reporting (editorial pick) |
| ISM-0140 | ML2, ML3 Cyber security incidents are reported to ASD as soon as possible after they occur or… | Editorial | Art.18(1)Art.19(1)Art.19(3)+1 | Same topic: Reporting (editorial pick) |
| ISM-1228 | ML2, ML3 Cyber security events are analysed in a timely manner to identify cyber security incidents | Editorial | Art.10(1)Art.10(2)Art.10(3) | Same topic: Anomaly Detection, SIEM / SOC (editorial pick) |
| ISM-1815 | ML2, ML3 Event logs are protected from unauthorised modification and deletion | Editorial | Art.10(3) | Same topic: Logging & Audit (editorial pick) |
| ISM-1819 | ML2, ML3 Following the identification of a cyber security incident, the cyber security incident… | Editorial | Art.11(2)(b)Art.17(1)Art.17(3)+1 | Same topic: Incident Response (editorial pick) |
| ISM-1906 | ML2, ML3 Event logs from internet-facing servers are analysed in a timely manner to detect cyber… | Editorial | Art.9(1)Art.10(2)Art.10(3) | Same topic: Cont. Monitoring, SIEM / SOC (editorial pick) |
| ISM-1907 | ML3 Event logs from non-internet-facing servers are analysed in a timely manner to detect… | Editorial | Art.9(1)Art.10(3) | Same topic: Cont. Monitoring (editorial pick) |
By topic
Both cover (13):
Asset ManagementVulnerability MgmtMulti-Factor AuthBackup & RecoveryPrivileged AccessPatch ManagementCont. MonitoringLogging & AuditAnomaly DetectionSIEM / SOCIncident ResponseReportingDisaster Recovery
Only Essential Eight (3):
Only DORA (26):
Governance PolicyAwareness & TrainingRisk ManagementSupply Chain RiskRoles & ResponsibilitiesComplianceRisk AssessmentBusiness EnvironmentData ClassificationThreat IntelligenceAccess ControlEncryptionData ProtectionFirewall / Net SegCloud SecurityIntrusion DetectionForensicsCommunicationMitigationRecovery PlanningBusiness ContinuityLessons LearnedComms & RestoreInsider ThreatVendor Risk MgmtPhysical Security
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · 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. Mapped = curated together in a ControlMapping topic, or linked directly. Crosswalks don't prove compliance. Methodology · Download the data · Report a mistake.