Comparison
SOC 2 vs Essential Eight
SOC 2 (Trust Services Criteria) · ASD Essential Eight · data 2026-10-27
Requirement-level comparison of SOC 2 (Trust Services Criteria) and ASD Essential Eight, in both directions, derived from published crosswalks and ControlMapping's curated topics.
Of 126 ASD Essential Eight requirements, 57 map to something in SOC 2, 69 are only loosely related, and 0 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.
Check these: only loosely related (a shared CSF outcome, not a mapping) (69)
| Essential Eight | Requirement | Match | SOC 2 | Evidence |
|---|---|---|---|---|
| Patch applications · 6 | ||||
| ISM-0304 | ML3 Applications other than office productivity suites, web browsers and their extensions… | CC7.1 | 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… | CC7.1 | 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… | CC7.1 | 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… | CC7.1 | 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… | CC7.1 | 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 | CC7.1 | 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 | CC7.1 | 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… | CC7.1 | 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… | CC7.1 | 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… | CC7.1 | 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 | CC7.1 | 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… | CC7.1 | 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 | CC7.1 | 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… | CC7.1 | 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… | CC7.1 | 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… | CC7.1 | 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 | CC6.1CC6.6 | 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… | CC6.1CC6.6 | 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… | CC6.1CC6.6 | 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… | CC6.1CC6.6 | 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… | CC6.1CC6.6 | 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 | CC6.1CC6.6 | 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… | CC6.1CC6.6 | 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… | CC6.1CC6.6 | 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… | CC6.1CC6.6 | 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 | CC6.1CC6.2CC6.3+2 | 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 | CC6.1CC6.2CC6.3+2 | 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… | CC6.1CC6.2CC6.3+2 | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1686 | ML3 Credential Guard functionality is enabled | CC6.1CC6.2CC6.3+2 | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1687 | ML2, ML3 Privileged operating environments are not virtualised within unprivileged operating… | CC6.1CC6.2CC6.3+2 | 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 | CC6.1CC6.2CC6.3+2 | 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… | CC6.1CC6.2CC6.3+2 | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1861 | ML3 Local Security Authority protection functionality is enabled | CC6.1CC6.2CC6.3+2 | 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… | CC6.1CC6.2CC6.3+2 | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1897 | ML3 Remote Credential Guard functionality is enabled | CC6.1CC6.2CC6.3+2 | Only shares CSF PR.AA-05: related, not a mapping | |
| ISM-1898 | ML3 Secure Admin Workstations are used in the performance of administrative activities | CC6.1CC6.2CC6.3+2 | Only shares CSF PR.AA-05: related, not a mapping | |
| Application control · 5 | ||||
| ISM-1582 | ML2, ML3 Application control rulesets are validated at least annually | CC6.8 | Only shares CSF PR.PS-05: related, not a mapping | |
| ISM-1656 | ML3 Application control is implemented on non-internet-facing servers | CC6.8 | Only shares CSF PR.PS-05: related, not a mapping | |
| ISM-1658 | ML3 Application control restricts the execution of drivers to an organisation-approved set | CC6.8 | Only shares CSF PR.PS-05: related, not a mapping | |
| ISM-1659 | ML3 Microsoft’s vulnerable driver blocklist is implemented | CC6.8 | Only shares CSF PR.PS-05: related, not a mapping | |
| ISM-1871 | ML2, ML3 Application control is applied to all locations other than user profiles and temporary… | CC6.8 | Only shares CSF PR.PS-05: related, not a mapping | |
| Restrict Microsoft Office macros · 10 | ||||
| ISM-1487 | ML3 Only privileged human users responsible for checking that Microsoft Office macros are… | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| ISM-1489 | ML1, ML2, ML3 Microsoft Office macro security settings cannot be changed by human users | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| ISM-1671 | ML1, ML2, ML3 Microsoft Office macros are disabled for human users that do not have a demonstrated… | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| ISM-1672 | ML1, ML2, ML3 Microsoft Office macro antivirus scanning is enabled | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| ISM-1673 | ML2, ML3 Microsoft Office macros are blocked from making Win32 API calls | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| ISM-1674 | ML3 Only Microsoft Office macros running from within a sandboxed environment, a Trusted… | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| ISM-1675 | ML3 Microsoft Office macros digitally signed by an untrusted publisher cannot be enabled… | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| ISM-1676 | ML3 Microsoft Office’s list of trusted publishers is validated at least annually | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| ISM-1890 | ML3 Microsoft Office macros are checked to ensure they are free of malicious code before… | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| ISM-1891 | ML3 Microsoft Office macros digitally signed by signatures other than V3 signatures cannot… | CC5.2CC6.7CC6.8+2 | Only shares CSF PR.PS-01, PR.PS-05: related, not a mapping | |
| User application hardening · 13 | ||||
| ISM-1485 | ML1, ML2, ML3 Web browsers do not process web advertisements from the internet | CC5.2CC6.7CC7.1+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 | CC5.2CC6.7CC7.1+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… | CC5.2CC6.7CC7.1+1 | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1622 | ML3 PowerShell is configured to use Constrained Language Mode | CC5.2CC6.7CC7.1+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 | CC5.2CC6.7CC7.1+1 | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1667 | ML2, ML3 Microsoft Office is blocked from creating child processes | CC5.2CC6.7CC7.1+1 | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1668 | ML2, ML3 Microsoft Office is blocked from creating executable content | CC5.2CC6.7CC7.1+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 | CC5.2CC6.7CC7.1+1 | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1670 | ML2, ML3 PDF applications are blocked from creating child processes | CC5.2CC6.7CC7.1+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 | CC5.2CC6.7CC7.1+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 | CC5.2CC6.7CC7.1+1 | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1889 | ML2, ML3 Command line process creation events are centrally logged | CC5.2CC6.7CC7.1+1 | Only shares CSF PR.PS-01: related, not a mapping | |
| ISM-1896 | ML3 Memory integrity functionality is enabled | CC5.2CC6.7CC7.1+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… | A1.2 | 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… | A1.2 | 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… | A1.2 | 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 | A1.2 | Only shares CSF PR.DS-11, RC.RP-03: related, not a mapping | |
| ISM-1813 | ML3 Unprivileged user accounts cannot access their own backups | A1.2 | Only shares CSF PR.DS-11, RC.RP-03: related, not a mapping | |
Mapped (57)
| Essential Eight | Requirement | Match | SOC 2 | 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 | CC7.1 | Same topic: Patch Management (editorial pick) |
| ISM-1693 | ML2, ML3 Patches, updates or other vendor mitigations for vulnerabilities in applications other… | Editorial | CC7.1 | 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 | CC7.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 | CC7.1 | Same topic: Vulnerability Mgmt (editorial pick) |
| ISM-1704 | ML1, ML2, ML3 Office productivity suites, web browsers and their extensions, email clients, PDF… | Editorial | CC7.1 | 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 | CC7.1 | 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 | CC6.1CC7.1 | 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 | CC7.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 | CC7.1 | 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 | CC7.1 | 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 | CC7.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 | CC7.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 | CC7.1 | 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 | CC6.1 | Same topic: Multi-Factor Auth (editorial pick) |
| ISM-1173 | ML2, ML3 Multi-factor authentication is used to authenticate privileged human users of systems | Editorial | CC6.1 | Same topic: Multi-Factor Auth (editorial pick) |
| ISM-1401 | ML1, ML2, ML3 Multi-factor authentication uses either: something people have and something people… | Editorial | CC6.1 | 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 | CC6.1 | 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 | CC6.1 | Same topic: Multi-Factor Auth (editorial pick) |
| ISM-1683 | ML2, ML3 Successful and unsuccessful multi-factor authentication events are centrally logged | Editorial | CC7.2 | Same topic: Logging & Audit (editorial pick) |
| ISM-1872 | ML2, ML3 Multi-factor authentication used for authenticating human users of online services is… | Editorial | CC6.1 | 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 | CC6.3 | Same topic: Privileged Access (editorial pick) |
| ISM-1175 | ML1, ML2, ML3 Privileged user accounts (excluding those explicitly authorised to access online… | Editorial | CC6.3 | Same topic: Privileged Access (editorial pick) |
| ISM-1380 | ML1, ML2, ML3 Privileged human users use separate privileged and unprivileged operating environments | Editorial | CC6.3 | Same topic: Privileged Access (editorial pick) |
| ISM-1387 | ML2, ML3 Administrative activities are conducted through jump servers | Editorial | CC6.3 | 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 | CC6.3 | Same topic: Privileged Access (editorial pick) |
| ISM-1508 | ML3 Privileged access to systems and their resources is limited to only what is required… | Editorial | CC6.3 | Same topic: Privileged Access (editorial pick) |
| ISM-1509 | ML2, ML3 Privileged access events are centrally logged | Editorial | CC7.2 | Same topic: Logging & Audit (editorial pick) |
| ISM-1647 | ML2, ML3 Privileged access to systems and their resources are disabled after 12 months unless… | Editorial | CC6.3 | 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 | CC6.3 | Same topic: Privileged Access (editorial pick) |
| Application control · 6 | ||||
| ISM-0843 | ML1, ML2, ML3 Application control is implemented on workstations | Editorial | CC6.8 | Same topic: Endpoint Protection (editorial pick) |
| ISM-1490 | ML2, ML3 Application control is implemented on internet-facing servers | Editorial | CC6.8 | Same topic: Endpoint Protection (editorial pick) |
| ISM-1544 | ML2, ML3 Microsoft’s recommended application blocklist is implemented | Editorial | CC6.8 | Same topic: Endpoint Protection (editorial pick) |
| ISM-1657 | ML1, ML2, ML3 Application control restricts the execution of executables, libraries, scripts… | Editorial | CC6.8 | Same topic: Endpoint Protection (editorial pick) |
| ISM-1660 | ML2, ML3 Allowed and blocked application control events are centrally logged | Editorial | CC7.2 | Same topic: Logging & Audit (editorial pick) |
| ISM-1870 | ML1, ML2, ML3 Application control is applied to user profiles and temporary folders used by operating… | Editorial | CC6.8 | Same topic: Endpoint Protection (editorial pick) |
| Restrict Microsoft Office macros · 1 | ||||
| ISM-1488 | ML1, ML2, ML3 Microsoft Office macros in files originating from the internet are blocked | Editorial | CC6.8 | Same topic: Endpoint Protection, Email Security (editorial pick) |
| User application hardening · 7 | ||||
| ISM-1412 | ML2, ML3 Web browsers are hardened using ASD and vendor hardening guidance, with the most… | Editorial | CC5.2CC7.1 | Same topic: Secure Config (editorial pick) |
| ISM-1585 | ML1, ML2, ML3 Web browser security settings cannot be changed by human users | Editorial | CC5.2CC7.1 | Same topic: Secure Config (editorial pick) |
| ISM-1621 | ML3 Windows PowerShell 2.0 is disabled or removed | Editorial | CC5.2CC7.1 | Same topic: Secure Config (editorial pick) |
| ISM-1623 | ML2, ML3 PowerShell module logging, script block logging and transcription events are centrally… | Editorial | CC7.2 | Same topic: Logging & Audit (editorial pick) |
| ISM-1654 | ML1, ML2, ML3 Internet Explorer 11 is disabled or removed | Editorial | CC5.2CC7.1 | Same topic: Secure Config (editorial pick) |
| ISM-1859 | ML2, ML3 Office productivity suites are hardened using ASD and vendor hardening guidance, with… | Editorial | CC5.2CC7.1 | Same topic: Secure Config (editorial pick) |
| ISM-1860 | ML2, ML3 PDF applications are hardened using ASD and vendor hardening guidance, with the most… | Editorial | CC5.2CC7.1 | Same topic: Secure Config (editorial pick) |
| Regular backups · 6 | ||||
| ISM-1511 | ML1, ML2, ML3 Backups of data, applications and settings are performed and retained in accordance… | Editorial | A1.2 | 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 | A1.2A1.3 | Same topic: Backup & Recovery, Disaster Recovery (editorial pick) |
| ISM-1707 | ML2, ML3 Privileged user accounts (excluding backup administrator accounts) are prevented from… | Editorial | A1.2 | 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 | A1.2 | 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 | A1.2 | Same topic: Backup & Recovery (editorial pick) |
| ISM-1814 | ML1, ML2, ML3 Unprivileged user accounts are prevented from modifying and deleting backups | Editorial | A1.2 | 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 | CC7.2 | Same topic: Cont. Monitoring (editorial pick) |
| ISM-0123 | ML2, ML3 Cyber security incidents are reported to the chief information security officer, or one… | Editorial | CC2.3 | 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 | CC2.3 | Same topic: Reporting (editorial pick) |
| ISM-1228 | ML2, ML3 Cyber security events are analysed in a timely manner to identify cyber security incidents | Editorial | CC7.2CC7.3 | Same topic: Anomaly Detection, SIEM / SOC (editorial pick) |
| ISM-1815 | ML2, ML3 Event logs are protected from unauthorised modification and deletion | Editorial | CC7.2 | Same topic: Logging & Audit (editorial pick) |
| ISM-1819 | ML2, ML3 Following the identification of a cyber security incident, the cyber security incident… | Editorial | CC7.3CC7.4 | 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 | CC7.2CC7.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 | CC7.2 | Same topic: Cont. Monitoring (editorial pick) |
Of 61 SOC 2 (Trust Services Criteria) requirements, 11 map to something in Essential Eight, 9 are only loosely related, and 41 have no mapping in our data.
AICPA's SOC 2 mappings aren't openly licensed, so every SOC 2 link here is ControlMapping editorial: criteria we haven't mapped can't match. Processing-integrity (PI) criteria and most privacy (P) criteria have no equivalent in security frameworks.
Likely new work: SOC 2 requirements with no mapping to Essential Eight (41)
| SOC 2 | Requirement | Match | Essential Eight | Evidence |
|---|---|---|---|---|
| C1 Confidentiality · 1 | ||||
| C1.1 | Identifying and protecting confidential information | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC1 Control environment · 5 | ||||
| CC1.1 | Commitment to integrity and ethical values | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC1.2 | Board independence and oversight of internal control | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC1.3 | Structures, reporting lines, authorities and responsibilities | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC1.4 | Commitment to attracting, developing and retaining competent people | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC1.5 | Accountability for internal control responsibilities | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC2 Communication and information · 2 | ||||
| CC2.1 | Quality information to support internal control | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC2.2 | Internal communication of objectives and responsibilities | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC3 Risk assessment · 4 | ||||
| CC3.1 | Objectives specified clearly enough to identify risks | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC3.2 | Risk identification and analysis | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC3.3 | Considering the potential for fraud | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC3.4 | Identifying and assessing significant changes | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC4 Monitoring activities · 2 | ||||
| CC4.1 | Ongoing and/or separate evaluations of controls | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC4.2 | Communicating and remediating control deficiencies | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC5 Control activities · 2 | ||||
| CC5.1 | Control activities that mitigate risks | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC5.3 | Control activities deployed through policies and procedures | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC6 Logical and physical access · 1 | ||||
| CC6.4 | Physical access restrictions | No mapping in our data | — | No mapping to Essential Eight in our data. |
| CC8 Change management · 1 | ||||
| CC8.1 | Change management for infrastructure, data and software | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P Privacy · 18 | ||||
| P1.1 | Privacy notice | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P2.1 | Choice and consent | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P3.1 | Collection limited to privacy objectives | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P3.2 | Explicit consent where required | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P4.1 | Use limited to privacy objectives | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P4.2 | Retention of personal information | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P4.3 | Disposal of personal information | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P5.1 | Data subject access | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P5.2 | Correction of personal information | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P6.1 | Disclosure to third parties with consent | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P6.2 | Record of authorized disclosures | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P6.3 | Record of unauthorized disclosures | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P6.4 | Privacy commitments from third parties | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P6.5 | Notification by third parties of unauthorized disclosures | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P6.6 | Breach notification to affected individuals | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P6.7 | Accounting of disclosures to data subjects | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P7.1 | Quality of personal information | No mapping in our data | — | No mapping to Essential Eight in our data. |
| P8.1 | Handling privacy inquiries, complaints and disputes | No mapping in our data | — | No mapping to Essential Eight in our data. |
| PI1 Processing integrity · 5 | ||||
| PI1.1 | Information about processing objectives | No mapping in our data | — | No mapping to Essential Eight in our data. |
| PI1.2 | Controls over system inputs | No mapping in our data | — | No mapping to Essential Eight in our data. |
| PI1.3 | Controls over system processing | No mapping in our data | — | No mapping to Essential Eight in our data. |
| PI1.4 | Controls over system outputs | No mapping in our data | — | No mapping to Essential Eight in our data. |
| PI1.5 | Storing inputs, items in processing and outputs | 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) (9)
| SOC 2 | Requirement | Match | Essential Eight | Evidence |
|---|---|---|---|---|
| A1 Availability · 1 | ||||
| A1.1 | Capacity management to meet availability commitments | ISM-1515 | Only shares CSF PR.IR-03: related, not a mapping | |
| C1 Confidentiality · 1 | ||||
| C1.2 | Disposing of confidential information | ISM-1488 | Only shares CSF PR.DS-02: related, not a mapping | |
| CC6 Logical and physical access · 4 | ||||
| CC6.2 | User registration, authorization and removal | ISM-0445ISM-1175ISM-1380+5 | Only shares CSF PR.AA-05: related, not a mapping | |
| CC6.5 | Protection of data when assets are disposed of | ISM-1488 | Only shares CSF PR.DS-02: related, not a mapping | |
| CC6.6 | Protection against threats from outside system boundaries | ISM-0109ISM-0445ISM-0974+5 | Only shares CSF DE.CM-01, PR.AA-05, PR.AA-03: related, not a mapping | |
| CC6.7 | Restricting transmission, movement and removal of information | ISM-1488ISM-0445ISM-1175+5 | Only shares CSF PR.DS-02, PR.PS-01, PR.AA-05: related, not a mapping | |
| CC7 System operations · 1 | ||||
| CC7.5 | Recovering from identified security incidents | ISM-1515 | Only shares CSF RC.RP-02, RC.RP-05: related, not a mapping | |
| CC9 Risk mitigation · 2 | ||||
| CC9.1 | Mitigating risks from business disruptions | ISM-1515 | Only shares CSF PR.IR-03: related, not a mapping | |
| CC9.2 | Managing vendor and business partner risk | ISM-1412ISM-1485ISM-1486+5 | Only shares CSF PR.PS-01: related, not a mapping | |
Mapped (11)
| SOC 2 | Requirement | Match | Essential Eight | Evidence |
|---|---|---|---|---|
| A1 Availability · 2 | ||||
| A1.2 | Environmental protections, backups and recovery infrastructure | Editorial | ISM-1511ISM-1515ISM-1707+3 | Same topic: Backup & Recovery, Disaster Recovery (editorial pick) |
| A1.3 | Testing recovery plan procedures | Editorial | ISM-1515 | Same topic: Disaster Recovery (editorial pick) |
| CC2 Communication and information · 1 | ||||
| CC2.3 | Communication with external parties | Editorial | ISM-0123ISM-0140 | Same topic: Reporting (editorial pick) |
| CC5 Control activities · 1 | ||||
| CC5.2 | General controls over technology | Editorial | ISM-1412ISM-1585ISM-1621+3 | Same topic: Secure Config (editorial pick) |
| CC6 Logical and physical access · 3 | ||||
| CC6.1 | Logical access security over information assets | Editorial | ISM-0974ISM-1173ISM-1401+4 | Same topic: Multi-Factor Auth (editorial pick) |
| CC6.3 | Role-based access, least privilege and segregation of duties | Editorial | ISM-0445ISM-1175ISM-1380+5 | Same topic: Privileged Access (editorial pick) |
| CC6.8 | Preventing or detecting unauthorized or malicious software | Editorial | ISM-0843ISM-1488ISM-1490+3 | Same topic: Endpoint Protection, Email Security (editorial pick) |
| CC7 System operations · 4 | ||||
| CC7.1 | Detecting configuration changes and new vulnerabilities | Editorial | ISM-1412ISM-1501ISM-1585+16 | Same topic: Secure Config, Patch Management (editorial pick) |
| CC7.2 | Monitoring system components for anomalies | Editorial | ISM-0109ISM-1228ISM-1509+6 | Same topic: Cont. Monitoring, Anomaly Detection, Logging & Audit (editorial pick) |
| CC7.3 | Evaluating security events to determine if they are incidents | Editorial | ISM-1228ISM-1819ISM-1906 | Same topic: SIEM / SOC, Incident Response (editorial pick) |
| CC7.4 | Responding to identified security incidents | Editorial | ISM-1819 | Same topic: Incident Response (editorial pick) |
By topic
Both cover (16):
Asset ManagementVulnerability MgmtMulti-Factor AuthBackup & RecoveryPrivileged AccessEndpoint ProtectionPatch ManagementSecure ConfigEmail SecurityCont. MonitoringLogging & AuditAnomaly DetectionSIEM / SOCIncident ResponseReportingDisaster Recovery
Only SOC 2 (30):
Governance PolicyAwareness & TrainingRisk ManagementSupply Chain RiskRoles & ResponsibilitiesComplianceRisk AssessmentBusiness EnvironmentData ClassificationAccess ControlEncryptionData ProtectionFirewall / Net SegSecure DevelopmentWeb SecurityZero TrustMobile SecurityCloud SecurityWAFDLPIntrusion DetectionForensicsCommunicationMitigationRecovery PlanningBusiness ContinuityLessons LearnedComms & RestoreVendor 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.