Comparison
GDPR vs Essential Eight
GDPR · ASD Essential Eight · data 2026-10-27
Requirement-level comparison of GDPR and ASD Essential Eight, in both directions, derived from published crosswalks and ControlMapping's curated topics.
Of 126 ASD Essential Eight requirements, 15 map to something in GDPR, 82 are only loosely related, and 29 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 GDPR (29)
| Essential Eight | Requirement | Match | GDPR | Evidence |
|---|---|---|---|---|
| Multi-factor authentication · 16 | ||||
| ISM-0974 | ML2, ML3 Multi-factor authentication is used to authenticate unprivileged human users of systems | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1173 | ML2, ML3 Multi-factor authentication is used to authenticate privileged human users of systems | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1401 | ML1, ML2, ML3 Multi-factor authentication uses either: something people have and something people… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1504 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate human users to their organisation’s online services that process… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1505 | ML3 Multi-factor authentication is used to authenticate human users of data repositories | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1679 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate human users to third-party online services that process, store or… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1680 | ML1, ML2, ML3 Multi-factor authentication (where available) is used to authenticate human users to… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1681 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate customers to online customer… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1682 | ML2, ML3 Multi-factor authentication used for authenticating human users of systems is… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1683 | ML2, ML3 Successful and unsuccessful multi-factor authentication events are centrally logged | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1872 | ML2, ML3 Multi-factor authentication used for authenticating human users of online services is… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1873 | ML2 Multi-factor authentication used for authenticating customers of online customer services provides a… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1874 | ML3 Multi-factor authentication used for authenticating customers of online customer services is phishing-resistant | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1892 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate human users to their organisation’s online customer services that… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1893 | ML1, ML2, ML3 Multi-factor authentication is used to authenticate human users to third-party online customer services that process… | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1894 | ML3 Multi-factor authentication used for authenticating human users of data repositories is… | No mapping in our data | — | No mapping to GDPR in our data. |
| Application control · 11 | ||||
| ISM-0843 | ML1, ML2, ML3 Application control is implemented on workstations | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1490 | ML2, ML3 Application control is implemented on internet-facing servers | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1544 | ML2, ML3 Microsoft’s recommended application blocklist is implemented | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1582 | ML2, ML3 Application control rulesets are validated at least annually | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1656 | ML3 Application control is implemented on non-internet-facing servers | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1657 | ML1, ML2, ML3 Application control restricts the execution of executables, libraries, scripts… | No mapping in our data | — | No mapping to GDPR 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 GDPR in our data. |
| ISM-1659 | ML3 Microsoft’s vulnerable driver blocklist is implemented | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1660 | ML2, ML3 Allowed and blocked application control events are centrally logged | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1870 | ML1, ML2, ML3 Application control is applied to user profiles and temporary folders used by operating… | No mapping in our data | — | No mapping to GDPR 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 GDPR in our data. |
| Logging and incident response (all strategies) · 2 | ||||
| ISM-1228 | ML2, ML3 Cyber security events are analysed in a timely manner to identify cyber security incidents | No mapping in our data | — | No mapping to GDPR in our data. |
| ISM-1815 | ML2, ML3 Event logs are protected from unauthorised modification and deletion | No mapping in our data | — | No mapping to GDPR in our data. |
Check these: only loosely related (a shared CSF outcome, not a mapping) (82)
| Essential Eight | Requirement | Match | GDPR | Evidence |
|---|---|---|---|---|
| Patch applications · 10 | ||||
| ISM-0304 | ML3 Applications other than office productivity suites, web browsers and their extensions… | Art.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| 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 | Art.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| ISM-1693 | ML2, ML3 Patches, updates or other vendor mitigations for vulnerabilities in applications other… | Art.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| ISM-1704 | ML1, ML2, ML3 Office productivity suites, web browsers and their extensions, email clients, PDF… | Art.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| ISM-1876 | ML1, ML2, ML3 Patches, updates or other vendor mitigations for vulnerabilities in online services are applied within 48 hours of… | Art.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| ISM-1905 | ML1, ML2, ML3 Online services that are no longer supported by vendors are removed | Art.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| Patch operating systems · 13 | ||||
| ISM-1407 | ML3 The latest release, or the previous release, of operating systems are used | Art.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| ISM-1501 | ML1, ML2, ML3 Operating systems that are no longer supported by vendors are replaced | Art.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| 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 | Art.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| 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… | Art.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: 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.32(1)(d) | Only shares CSF ID.RA-01: related, not a mapping | |
| Restrict administrative privileges · 20 | ||||
| ISM-0445 | ML1, ML2, ML3 Privileged human users are assigned a dedicated privileged user account to be used… | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1175 | ML1, ML2, ML3 Privileged user accounts (excluding those explicitly authorised to access online… | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1380 | ML1, ML2, ML3 Privileged human users use separate privileged and unprivileged operating environments | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1387 | ML2, ML3 Administrative activities are conducted through jump servers | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1507 | ML1, ML2, ML3 Requests for privileged access to systems and their resources are validated when first… | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1508 | ML3 Privileged access to systems and their resources is limited to only what is required… | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1509 | ML2, ML3 Privileged access events are centrally logged | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1647 | ML2, ML3 Privileged access to systems and their resources are disabled after 12 months unless… | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1648 | ML2, ML3 Privileged access to systems and their resources are disabled after 45 days of inactivity | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1649 | ML3 Just-in-time administration is used for the administration of systems and their resources | Art.25(2)Art.32(1)(b) | 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.25(2)Art.32(1)(b) | 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.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1686 | ML3 Credential Guard functionality is enabled | Art.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1687 | ML2, ML3 Privileged operating environments are not virtualised within unprivileged operating… | Art.25(2)Art.32(1)(b) | 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.25(2)Art.32(1)(b) | 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.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1861 | ML3 Local Security Authority protection functionality is enabled | Art.25(2)Art.32(1)(b) | 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.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1897 | ML3 Remote Credential Guard functionality is enabled | Art.25(2)Art.32(1)(b) | 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.25(2)Art.32(1)(b) | Only shares CSF PR.AA-05: 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(1) | 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.5(1)(e)Art.5(1)(f)Art.28(1)+3 | Only shares CSF PR.DS-02, PR.PS-01: related, not a mapping | |
| ISM-1489 | ML1, ML2, ML3 Microsoft Office macro security settings cannot be changed by human users | Art.28(1) | 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(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1672 | ML1, ML2, ML3 Microsoft Office macro antivirus scanning is enabled | Art.28(1) | 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(1) | 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(1) | 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(1) | 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(1) | 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(1) | 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(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| User application hardening · 20 | ||||
| ISM-1412 | ML2, ML3 Web browsers are hardened using ASD and vendor hardening guidance, with the most… | Art.28(1) | 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(1) | 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(1) | 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(1) | 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(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1621 | ML3 Windows PowerShell 2.0 is disabled or removed | Art.28(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1622 | ML3 PowerShell is configured to use Constrained Language Mode | Art.28(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1623 | ML2, ML3 PowerShell module logging, script block logging and transcription events are centrally… | Art.28(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1654 | ML1, ML2, ML3 Internet Explorer 11 is disabled or removed | Art.28(1) | 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(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1667 | ML2, ML3 Microsoft Office is blocked from creating child processes | Art.28(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1668 | ML2, ML3 Microsoft Office is blocked from creating executable content | Art.28(1) | 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(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1670 | ML2, ML3 PDF applications are blocked from creating child processes | Art.28(1) | 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(1) | 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(1) | 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(1) | 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(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1889 | ML2, ML3 Command line process creation events are centrally logged | Art.28(1) | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1896 | ML3 Memory integrity functionality is enabled | Art.28(1) | 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.32(1)(c) | 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.32(1)(c) | 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.32(1)(c) | 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.32(1)(c) | 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.32(1)(c) | Only shares CSF PR.DS-11, RC.RP-03: related, not a mapping | |
| Logging and incident response (all strategies) · 3 | ||||
| ISM-0109 | ML3 Event logs from workstations are analysed in a timely manner to detect cyber security… | Art.29Art.32(4) | Only shares CSF DE.CM-03: related, not a mapping | |
| ISM-1906 | ML2, ML3 Event logs from internet-facing servers are analysed in a timely manner to detect cyber… | Art.29Art.32(4) | Only shares CSF DE.CM-03: related, not a mapping | |
| ISM-1907 | ML3 Event logs from non-internet-facing servers are analysed in a timely manner to detect… | Art.29Art.32(4) | Only shares CSF DE.CM-03: related, not a mapping | |
Mapped (15)
| Essential Eight | Requirement | Match | GDPR | Evidence |
|---|---|---|---|---|
| Patch applications · 2 | ||||
| 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.32(1)(d) | 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.32(1)(d) | Same topic: Vulnerability Mgmt (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.30(1)Art.32(1)(d) | 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.32(1)(d) | Same topic: Vulnerability Mgmt (editorial pick) |
| Patch operating systems · 2 | ||||
| ISM-1701 | ML1, ML2, ML3 A vulnerability scanner is used at least daily to identify missing patches or updates for vulnerabilities in… | Editorial | Art.32(1)(d) | 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.32(1)(d) | Same topic: Vulnerability Mgmt (editorial pick) |
| Regular backups · 6 | ||||
| ISM-1511 | ML1, ML2, ML3 Backups of data, applications and settings are performed and retained in accordance… | Editorial | Art.32(1)(c) | 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.32(1)(c) | Same topic: Backup & Recovery, Disaster Recovery (editorial pick) |
| ISM-1707 | ML2, ML3 Privileged user accounts (excluding backup administrator accounts) are prevented from… | Editorial | Art.32(1)(c) | 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.32(1)(c) | 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.32(1)(c) | Same topic: Backup & Recovery (editorial pick) |
| ISM-1814 | ML1, ML2, ML3 Unprivileged user accounts are prevented from modifying and deleting backups | Editorial | Art.32(1)(c) | Same topic: Backup & Recovery (editorial pick) |
| Logging and incident response (all strategies) · 3 | ||||
| ISM-0123 | ML2, ML3 Cyber security incidents are reported to the chief information security officer, or one… | Editorial | Art.33(1)Art.34(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.33(1)Art.34(1) | Same topic: Reporting (editorial pick) |
| ISM-1819 | ML2, ML3 Following the identification of a cyber security incident, the cyber security incident… | Editorial | Art.33(1)Art.33(5) | Same topic: Incident Response (editorial pick) |
Of 13 GDPR requirements, 4 map to something in Essential Eight, 4 are only loosely related, and 5 have no mapping in our data.
GDPR is a privacy law: only its security-related articles are mapped here, and all mappings are editorial.
Likely new work: GDPR requirements with no mapping to Essential Eight (5)
| GDPR | Requirement | Match | Essential Eight | Evidence |
|---|---|---|---|---|
| Requirements · 5 | ||||
| Art.24 | Responsibility of the controller | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Art.35 | Data protection impact assessment | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Art.37 | Designation of the data protection officer | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Art.38 | Position of the data protection officer | No mapping in our data | — | No mapping to Essential Eight in our data. |
| Art.39 | Tasks of the data protection officer | 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) (4)
| GDPR | Requirement | Match | Essential Eight | Evidence |
|---|---|---|---|---|
| Requirements · 4 | ||||
| Art.5 | Principles relating to processing of personal data | ISM-1488 | Only shares CSF PR.DS-02: related, not a mapping | |
| Art.25 | Data protection by design and by default | ISM-0445ISM-1175ISM-1380+5 | Only shares CSF PR.AA-05: related, not a mapping | |
| Art.28 | Processor | ISM-1412ISM-1485ISM-1486+5 | Only shares CSF PR.PS-01: related, not a mapping | |
| Art.29 | Processing under the authority of the controller or processor | ISM-0109ISM-1906ISM-1907 | Only shares CSF DE.CM-03: related, not a mapping | |
Mapped (4)
| GDPR | Requirement | Match | Essential Eight | Evidence |
|---|---|---|---|---|
| Requirements · 4 | ||||
| Art.30 | Records of processing activities | Editorial | ISM-1807 | Same topic: Asset Management (editorial pick) |
| Art.32 | Security of processing | Editorial | ISM-1511ISM-1707ISM-1810+8 | Same topic: Backup & Recovery (editorial pick) |
| Art.33 | Notification of a personal data breach to the supervisory authority | Editorial | ISM-0123ISM-0140ISM-1819 | Same topic: Reporting, Incident Response (editorial pick) |
| Art.34 | Communication of a personal data breach to the data subject | Editorial | ISM-0123ISM-0140 | Same topic: Reporting (editorial pick) |
By topic
Both cover (6):
Only GDPR (17):
Governance PolicyAwareness & TrainingRisk ManagementSupply Chain RiskRoles & ResponsibilitiesComplianceRisk AssessmentAccess ControlEncryptionData ProtectionSecure DevelopmentCloud SecurityRecovery PlanningBusiness ContinuityComms & RestoreInsider ThreatVendor Risk Mgmt
Only Essential Eight (10):
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.