ASD Essentials vs ISO 27001, NIST CSF and SOC 2
Skip to content

ASD Essentials vs ISO 27001, NIST CSF and SOC 2

ASD Essentials, ISO 27001, NIST CSF 2.0 and SOC 2 each answer a different question, so a result under one cannot stand in for a result under another.

Compare the Frameworks Side by Side

ASD Essentials rates how effective security actions are within specific domains. ISO/IEC 27001 supports certification of a management system. NIST CSF 2.0 organises cyber security outcomes, and SOC 2 produces a CPA attestation report.

The Essential Eight belongs in the comparison too, because it is the framework Australian regulatory and government requirements still name. This guide sets out how the frameworks differ, where they overlap and how existing evidence can support more than one assessment while each result keeps its own meaning.

Compared side by side, the frameworks differ most in what each one assesses and what its result shows. An organisation may use several of them, but a certificate, a maturity assessment, an attestation report and an action effectiveness rating are different kinds of result.

FrameworkPublished byWhat it isWhat the result shows
ASD EssentialsAustralian Signals Directorate, October 15, 2026Principles, actions and domains. No ASD certification scheme.Whether an action achieves its intended outcome in each applicable domain. ASD’s assessment process guide focuses on whether the intended security outcome is being achieved rather than on the controls themselves.
Essential EightAustralian Signals Directorate, maturity model last updated November 2023Mitigation strategies assessed against maturity levels. No ASD certification scheme for organisations.A maturity level for implementation of the mitigation strategies.
ISO/IEC 27001ISO and IEC, adopted in Australia as AS ISO/IEC 27001An information security management system standard.A third-party certification body’s judgement of the management system against the standard.
NIST CSF 2.0US National Institute of Standards and Technology, February 26, 2024Cyber security outcomes grouped under Govern, Identify, Protect, Detect, Respond and Recover.The organisation’s position against those outcomes.
SOC 2AICPAA CPA attestation examination of controls against the Trust Services Criteria.A CPA’s attestation report on those controls.

ASD Essentials and the Essential Eight both come from ASD, but they are assessed differently. The Essential Eight measures maturity against mitigation strategies. ASD Essentials looks at how effective each action is for the assets and functions within each applicable domain.

Neither has an ASD certification scheme for organisations. ASD’s Essential Eight assessment course certifies individuals only.

ISO/IEC 27001 and SOC 2 both give independent assurance, through different processes. NIST CSF 2.0 gives a structure for assessing and communicating cyber security outcomes. It produces no directly equivalent certification or attestation result.

ASD Essentials draws its principles from ASD’s Information Security Manual (ISM). Relevant controls and evidence can be reused across frameworks, but each resulting assessment keeps its own meaning.

ASD Essentials vs ISO 27001

ISO/IEC 27001 gives assurance over an organisation’s information security management system. ASD Essentials measures how effective security actions are within the domains assessed. An ISO 27001 program can supply useful supporting records, but an ISO certificate does not produce an ASD Essentials rating.

Australian government assurance draws a similar line. Section 14.3 of PSPF Release 2026 recognises ISO/IEC 27001 and similar standards as useful, but says they are not suitable for use as an alternative authorisation to operate pathway. Commonwealth entities relying on such standards must explain the deviation in their annual security report.

ASD’s assessment evidence guide does not cross-reference ISO/IEC 27001. The assessment process guide still permits controls from other frameworks to be mapped against ASD Essentials actions as “a starting point”. The assessor must still determine whether the action achieves its intended security outcome.

GOV-03 is an example. Its action IT.GOV-03.1 calls for an approved risk management methodology and plan. In our reading, an organisation’s ISO 27001 risk management processes, risk register and treatment plans may already contain relevant material.

The useful evidence is the approved methodology, its use in practice and the records it produces. The certificate shows something different: that a certification body assessed the management system against ISO/IEC 27001 within its stated scope.

A security manager can keep ISO 27001 certification and draw on the same underlying records for an ASD Essentials assessment. Each record is checked against the applicable action and domain. No result is converted from one framework into the other.

ASD Essentials and NIST CSF

NIST CSF 2.0 is the closest structural match to ASD Essentials among the frameworks compared here. Both organise cyber security around outcomes, and ASD Essentials uses ISM principle prefixes that correspond closely to the NIST CSF functions.

The NIST CSF 2.0 functions are Govern, Identify, Protect, Detect, Respond and Recover. ASD Essentials for enterprise IT uses GOV, IDE, PRO, DET and RES for govern, identify, protect, detect and respond.

Recovery has no separate principle family in enterprise IT, although the OT chapter adds a REC principle. Backup and restoration testing appear under protect principles instead. ASD’s enterprise IT assessment evidence guide links restoration testing action IT.PRO-10.3 to NIST CSF 2.0 subcategories RC.RP-03, RC.RP-04 and RC.RP-05.

ASD gives NIST CSF 2.0 references for every enterprise IT action in its evidence guide. An organisation already using NIST CSF can follow those references to existing assessment results, control tests and operational records.

The mapping shows where evidence may exist. A NIST CSF profile describes an organisation’s position against CSF outcomes. The ASD Essentials assessment must still determine how effectively the relevant action operates in each applicable domain.

An organisation using both frameworks can keep its NIST CSF profile and trace the supporting evidence to ASD’s action-level indicators. The same record may support both assessments without making the ratings equivalent.

Essential 8 vs SOC 2

The Essential Eight and SOC 2 assess different aspects of cyber security assurance. An Essential Eight assessment measures how far ASD’s mitigation strategies are implemented, against maturity levels. SOC 2 is a CPA attestation examination of controls against the AICPA Trust Services Criteria.

SOC 2 is a US attestation report. It is neither an ASD framework nor an Australian regulatory assessment method, and it is absent from the PSPF, the SOCI risk management program rules and ASD’s assessment evidence guide. A SOC 2 report does not, by itself, satisfy any of those named obligations.

Where SOC 2 can still contribute is supplier assurance under ASD Essentials. GOV-11 Supplier cyber security assurance asks organisations to select suppliers following a proportionate cyber supply chain risk assessment and retain appropriate assurance evidence to support the decision. Its second action calls for current assurance that suppliers continue to meet their cyber security commitments.

In our reading, a supplier’s SOC 2 report may contribute to this evidence. The organisation should check which system the report covers, the reporting period, any exceptions and whether the findings affect the service it consumes. A report scoped to a different product from the one the organisation buys, for example, adds little.

Contract terms, supplier questionnaires and other relevant assessment material may be needed alongside the report. The aim is appropriate assurance about the supplier. A file note that a SOC 2 report exists falls short of that.

For cloud services, the ASD Essentials cloud chapter also identifies an IRAP assessment scoped to the service consumed as a potential source of provider assurance.

ASD says separate guidance on assessing suppliers will follow. The Governance and culture guide examines GOV-11 in more detail.

Other Referenced Cyber Security Frameworks

ASD’s enterprise IT assessment evidence guide also references NIST SP 800-171r3 and AESCSF v2. An organisation that already assesses against either framework can use the mappings to find records relevant to ASD Essentials.

NIST SP 800-171r3

Titled Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations. The mapping is likely to matter most to organisations handling that class of US government information.

AESCSF v2

AEMO’s Australian Energy Sector Cyber Security Framework. The SOCI risk management program rules accept AESCSF as one of the available frameworks.

The enterprise IT evidence guide cross-references AESCSF v2 under every action. Energy sector organisations can use existing AESCSF assessments to locate relevant security evidence, with no need to rebuild their records from the beginning.

The reuse is of evidence only, and the ratings stay separate. An AESCSF assessment result may point to useful records, but an ASD Essentials assessor must still evaluate the corresponding action against the applicable domain.

Use ASD's Framework Cross-References

ASD’s framework cross-references sit at action level in the enterprise IT assessment evidence guide. Each action includes “Potential evidence sources” showing where supporting evidence of that action’s effectiveness may exist when an organisation already follows another framework.

The guide references:

ISM

ASD’s Information Security Manual, version 2026.09.4, excluding Essential Eight controls.

Essential Eight

The Essential Eight as of October 2, 2024, referenced by ISM control number.

NIST CSF 2.0

Cybersecurity Framework subcategories.

NIST SP 800-171r3

Requirements for protecting controlled unclassified information.

AESCSF v2

Australian Energy Sector Cyber Security Framework practices.

The table shows the possible evidence sources ASD identifies for specific enterprise IT actions.

ASD Essentials actionNIST CSF 2.0NIST SP 800-171r3AESCSF v2
IT.PRO-13.4 Phishing-resistant MFAPR.AA-01, PR.AA-02, PR.AA-03, PR.AA-0503.05.03, 03.05.04, 03.01.12ACCESS-1h, ACCESS-1i, ACCESS-2g
IT.GOV-11.1 Supplier selection and assuranceGV.SC-01, GV.SC-03, GV.SC-05, GV.SC-07, GV.SC-0603.17.01, 03.17.02, 03.17.03, 03.16.03THIRD-PARTIES-2a, THIRD-PARTIES-2b, THIRD-PARTIES-2d, THIRD-PARTIES-2j
IT.DET-03.1 Timely triage of alertsDE.AE-02, DE.AE-04, DE.AE-08, RS.MA-0103.06.01, 03.06.02, 03.14.06RESPONSE-1b, RESPONSE-2a, RESPONSE-2d

These references are a starting point for locating evidence. They do not show that the referenced framework requires exactly the same control, or that an assessment result can be transferred directly. ASD explicitly says the list is not intended to define the controls required for an action.

For example, an organisation may already hold authentication configuration records and control test results for NIST CSF subcategories PR.AA-01, PR.AA-02, PR.AA-03 and PR.AA-05. Those records may help assess phishing-resistant MFA action IT.PRO-13.4.

The assessor must still decide whether the relevant action is effective for the assets and functions in the domain being assessed. A control that works effectively in one domain does not automatically prove effectiveness in another.

As of late 2026, these detailed framework cross-references cover enterprise IT only. ASD has not published equivalent assessment evidence guides for the cloud or OT chapters.

Check Current Australian Requirements

Current Australian cyber security obligations still name existing frameworks, including the Essential Eight, ISO/IEC 27001 and other recognised approaches. ASD Essentials is mandatory for no one yet, and no regulator has referenced it.

An organisation should keep meeting the frameworks, versions and maturity levels its obligations name.

ObligationApplies toFrameworks named
PSPF Release 2026, sections 14.2 and 14.3Non-corporate Commonwealth entitiesEssential Eight at Maturity Level Two; ISO/IEC 27001 is useful but no alternative authorisation to operate pathway.
SOCI CIRMP rulesResponsible entities for assets covered by the CIRMP rulesISO/IEC 27001, the Essential Eight, NIST, C2M2, AESCSF or an equivalent, with versions and levels raised for the enhanced asset classes since June 2026. The critical infrastructure guide lists them.
DISPDISP membersThe full Essential Eight at Maturity Level Two.
NSW Cyber Security Policy 2026-2027NSW departments, agencies and statutory authoritiesEssential Eight Maturity Level One controls as mandatory requirements.

SOC 2 is named in none of these requirements.

Some of these obligations accept a choice of framework and others fix the result. The SOCI CIRMP rules offer a choice among recognised frameworks, while the PSPF, DISP and the NSW policy set specific Essential Eight expectations.

A customer or contract may separately ask for ISO 27001 certification or a SOC 2 report. Those requests do not replace the framework specified by an Australian regulator.

A register of obligations is a useful starting point. It records the applicable framework, version, required level and reporting expectations for each obligation. An entry for a DISP member, for example, would name the full Essential Eight at Maturity Level Two. Security teams can then prepare evidence for each obligation without treating different forms of assurance as interchangeable.

The government guide covers the Commonwealth and state requirements in more detail.

Evidence to Reuse From Existing Frameworks

Existing ISO 27001, SOC 2, NIST and Essential Eight records can support an ASD Essentials assessment when they show the relevant security outcome. ASD’s assessment process guide tells assessors to identify and use relevant existing evidence before generating new evidence, and names configuration baselines, assessment reports, control test results, audit findings and risk registers.

Evidence collection starts with the records an organisation already keeps. The collection methods are common practice rather than ASD requirements.

EvidenceHow to get itWhat it should show
Framework obligations registerList the framework, version and level that each regulator, contract and customer names, with the reporting terms each one expects.Which result each audience needs, so a certificate, attestation or maturity level is reported in its own terms rather than converted into an ASD Essentials rating.
ISO 27001 Statement of ApplicabilityExport the current version from the information security management system, with its approval date and the certificate scope it relates to.Which controls the management system applies and why, as a starting point for an organisation-specific mapping. It does not show that any action is effective in a domain, and ASD’s evidence guide gives no ISO 27001 references.
ISO 27001 risk register and treatment plansExport the register with risk owners, treatment plans, implementation status and the date of the last review.Material for GOV-03: an approved methodology in use and a current register with documented and implemented treatment plans (IT.GOV-03.1.FE-1, FE-2). It says little about technical actions.
ISO 27001 certificate and audit reportKeep the certificate with its scope statement and the certification body’s latest audit report.A management system certified for a stated scope. Check that the scope includes the domain’s assets. The certificate gives no ASD Essentials rating.
Supplier SOC 2 reportRequest the report from the supplier, often under a nondisclosure agreement, and record its period, the system it describes and any exceptions noted.Current assurance, reviewed for findings that affect the organisation (IT.GOV-11.2.FE-1). It shows the supplier’s controls only, and appears in neither the PSPF nor ASD’s evidence guide.
Control test resultsExport internal control tests and audit samples with the test date, sample, method and result, from the governance tool or audit working papers.How a control operated when tested. Results count where they are current, cover the domain’s assets and test the outcome the action describes.
NIST CSF 2.0 profileExport the current profile with subcategory results and the assessment date, then use ASD’s CSF references for each action to find matching records.Where evidence may sit, such as RC.RP-03 to RC.RP-05 for restoration testing action IT.PRO-10.3. A profile shows position against CSF outcomes. It does not show an action’s effectiveness in a domain.
NIST SP 800-171r3 or AESCSF assessmentExport requirement or practice results with their evidence references, and trace them through the matching IDs in ASD’s evidence guide.Records from frameworks that ASD lists as possible evidence sources for enterprise IT actions, a list ASD says is not intended to define the controls required.
Essential Eight assessment reportKeep the report with its scope, sampled systems, assessment dates and maturity result for each strategy.Where and how far a control is deployed. ASD’s transition guide says to reuse it where it remains current and relevant, and that deployment alone does not demonstrate effectiveness.

Collecting these records once cuts duplicate assessment work and still leaves each framework with the evidence it needs.

How strong a record is depends on the outcome being assessed. An ISO 27001 risk register can show that a risk management process exists and is being used. A supplier SOC 2 report can inform a supplier assurance decision. A configuration export or control test may give direct evidence that a particular technical action operates as intended.

ASD’s assessment process guide asks assessors to seek the highest quality evidence reasonably practicable, ranging from evidence that directly proves the outcome to evidence that demonstrates none.

In common practice, a dated assessment report or system export is generally stronger evidence than a screenshot alone. A screenshot can still support an assessment when it clearly shows the system, scope and date.

Evidence also has to reflect how the environment operates now. An ISO certificate or SOC 2 report issued before significant system or process changes may need backing from more recent configuration records, tests or operational evidence. A report whose period ended before a move to a new identity provider is a typical case.

One well-kept set of records can support several assurance activities. Each assessment must still explain what those records show, which assets they cover and where further verification is needed.

Multi-Framework Evidence With ThreatDefence

ThreatDefence supports cybersecurity monitoring, investigation and evidence collection that can contribute to multiple assurance activities.

ThreatDefence runs a 24x7 SOC with its team based in Australia and a 3 min average response under guaranteed SLAs. Threat hunting and an incident response retainer are included in the standard service.

Response actions remain within the authority approved by each customer. Case records can be exported for an assessor or at the end of a contract. Australian customers’ data and AI processing stay in Australia.

ThreatDefence does not certify organisations. The assessor determines ASD Essentials ratings.

ThreatDefence holds ISO 27001 and PCI DSS certification and a SOC 2 report, providing examples of supplier assurance material relevant to GOV-11.

The free ASD Essentials Navigator maps every principle and action by chapter and priority phase, and turns your ratings into a board summary. Readers new to the framework can start with the five-minute ASD Essentials explainer, which walks through principles, actions, domains, priority phases and ratings.

Compliance report in the ThreatDefence portal with the share of controls passing, control families by status, and the priority fix for the period

Talk to Our Experts

See how ThreatDefence automates security monitoring, compliance and cyber risk management in one platform.

    I'm an MSP, MSSP, or reseller

    By submitting this form, you accept the terms in our privacy policy.

    Frequently Asked Questions

    Can ISO 27001 replace ASD Essentials for government?

    No. PSPF Release 2026 still requires Essential Eight Maturity Level Two for non-corporate Commonwealth entities and does not reference ASD Essentials. Section 14.3 considers ISO/IEC 27001 useful but does not accept it as an alternative authorisation to operate pathway.

    An entity relying on ISO 27001 or similar standards must explain the deviation in its annual security report. ISO certification can add supporting assurance. It does not replace the framework named in the PSPF.

    Does ASD map ASD Essentials to NIST CSF?

    Yes. ASD’s assessment evidence guide for enterprise IT includes NIST CSF 2.0 references for every action. It also references the ISM, the Essential Eight, NIST SP 800-171r3 and AESCSF v2.

    These mappings help organisations find relevant evidence they may already hold. They do not set equivalent control requirements or prove that an ASD Essentials action is effective. The assessor must evaluate the supporting evidence within the applicable domain.

    Is a SOC 2 report relevant in Australia?

    Yes. A SOC 2 report can give useful assurance about a supplier’s controls, although it does not itself satisfy requirements in the PSPF, SOCI CIRMP rules or ASD’s assessment evidence guide.

    ASD’s evidence guide does not list SOC 2, but a supplier’s report may contribute to the assurance evidence kept under GOV-11. The organisation should review the report’s scope, period and exceptions, and consider whether the findings are relevant to the service it consumes.

    Is the Essential Eight the same as ISO 27001?

    No. The Essential Eight contains ASD mitigation strategies assessed against maturity levels associated with increasing adversary tradecraft. ISO/IEC 27001 is an information security management system standard assessed by third-party certification bodies.

    ASD operates no certification scheme for organisations under the Essential Eight or ASD Essentials. Australian requirements also treat the frameworks differently. The SOCI CIRMP rules accept either approach within their framework options, while the PSPF specifically names Essential Eight Maturity Level Two.

    Does ISO 27001 evidence count towards ASD Essentials?

    Yes, where the evidence is relevant to an ASD Essentials action and shows the required outcome. ASD’s evidence guide does not cross-reference ISO 27001, so each organisation has to build its own mapping.

    ASD’s assessment process guide treats controls mapped from other frameworks as “a starting point”. Such a mapping may find that an ISO 27001 risk management program already holds records relevant to GOV-03’s approved risk management methodology and plan. A certificate alone cannot establish an ASD Essentials rating.

    How does NIST CSF 2.0 compare with ASD Essentials?

    NIST CSF 2.0 and ASD Essentials share a similar outcomes-based structure. NIST CSF 2.0, published February 26, 2024, groups cyber security outcomes under Govern, Identify, Protect, Detect, Respond and Recover.

    ASD Essentials enterprise IT uses GOV, IDE, PRO, DET and RES, while only the OT chapter adds a REC principle. Backup and restoration testing appear under protect principles. ASD maps restoration testing action IT.PRO-10.3 to NIST CSF subcategories RC.RP-03, RC.RP-04 and RC.RP-05.

    What is the difference between the Essential Eight and SOC 2?

    The Essential Eight assesses implementation of ASD mitigation strategies against defined maturity levels. SOC 2 is an AICPA attestation examination in which a CPA reports on controls against the Trust Services Criteria.

    The results serve different assurance purposes and cannot be converted into one another. The PSPF, DISP and NSW Cyber Security Policy name the Essential Eight. SOC 2 appears in none of the PSPF, SOCI CIRMP rules or ASD’s assessment evidence guide, although it may support supplier assurance.

    Do we need more than one security framework?

    Often, yes. Australian obligations, customer requirements and supplier assurance needs can call for different forms of evidence. Non-corporate Commonwealth entities work to Essential Eight Maturity Level Two under the PSPF, responsible entities under the SOCI CIRMP rules select an accepted framework, and DISP members need the full Essential Eight at Maturity Level Two.

    Customers may separately request ISO 27001 certification or SOC 2 reports. An obligations register and shared evidence collection can support these requirements without duplicating records or treating their assessment results as equivalent.

    Where does the AESCSF fit with ASD Essentials?

    AESCSF is AEMO’s Australian Energy Sector Cyber Security Framework and is one of the frameworks accepted under the SOCI CIRMP rules. Those rules identify the 2020-21 Framework Core at Security Profile 1 for baseline requirements and the 2023 Framework Core at Security Profile 2 for enhanced requirements.

    ASD’s enterprise IT assessment evidence guide references AESCSF v2 under every action. Energy operators can use those references to trace existing AESCSF assessment records to ASD Essentials actions, while assessing effectiveness separately.