Australia and New Zealand

External attack surface management (EASM) in Australia

Attack surface management in Australia starts with policy that names the internet-facing estate directly. PSPF Requirement 0211 asks Commonwealth entities for continuous visibility of internet-facing systems, the Essential Eight expects automated asset discovery, and the enhanced SOCI rules add critical system inventories. EASMLens gives security and risk leaders that outside-in view without installing anything.

Serving organisations in Sydney, Melbourne, Canberra, Brisbane, Perth, Adelaide.

What the rules in Australia expect

PSPF Requirement 0211: the technology asset stocktake

PSPF Release 2026 carries Requirement 0211, effective for all non-corporate Commonwealth entities from 1 July 2025. It requires a Technology Asset Stocktake and a Technology Security Risk Management Plan that identify and manage the entity’s internet-facing systems and services, with continuous visibility and monitoring of the technology estate as the stated outcome. The requirement absorbed the earlier Direction 002-2024.

How fast that inventory needs to work was shown in February 2026. PSPF Direction 001-2026, signed on 26 February, gave entities until 28 February to inventory their Cisco SD-WAN systems, patch them and report back. Two days leaves no time to start looking.

The Essential Eight, still the November 2023 model

The Essential Eight Maturity Model remains the version last updated in November 2023. From Maturity Level One it expects an automated method of asset discovery at least fortnightly, daily vulnerability scanning of online services and internet-facing servers and network devices, and patches for internet-facing systems within 48 hours when a vulnerability is critical or a working exploit exists.

ASD opened consultation on a successor "Essentials" series in June 2026, closing on 12 July 2026. That was a consultation, not a replacement, and the Essential Eight remains current. Commonwealth entities must reach Maturity Level Two under PSPF Requirements 0099 to 0106. ASD’s own posture report found 22 per cent of entities achieved it in 2025.

SOCI and the Enhanced CIRMP Rules 2026

The Enhanced CIRMP Rules commenced on 10 June 2026 for nine asset classes, including electricity, gas, water, liquid fuel, freight and domain name systems. They require responsible entities to identify and maintain an inventory of critical systems and their connections (section 8C), minimise the risk of late patching and unsupported technology (section 8A), map major suppliers (section 10A) and adopt one of five named frameworks, such as ISO/IEC 27001:2023 or the Essential Eight at Maturity Level Two.

Grace periods apply: patching and legacy technology duties from 10 June 2027, and the inventory, supply chain and framework duties from 10 June 2028. The annual CIRMP report is due 90 days after the end of the financial year and must be approved by the board.

APRA CPS 234 and CPS 230

CPS 234 requires APRA-regulated entities to classify all information assets, including those managed by third parties, and to test controls at a frequency that matches how quickly threats and assets change. Material incidents must be notified within 72 hours. CPS 230, in force since 1 July 2025, adds a register of material service providers and expects entities to monitor the health of their information assets.

Both standards assume the entity knows which systems face the internet, including systems a supplier runs on its behalf. That is where most inventories are weakest.

What ASD sees from the outside

ASD’s edge device guidance reports 17.9 million Australian devices visible on the public internet, 212,000 of them edge devices, and notes that edge devices often sit outside enterprise asset management. ASD’s Annual Cyber Threat Report 2024 to 2025 counted more than 120 incidents involving edge devices. ASD already watches the Commonwealth’s internet-facing systems and email posture from the outside through its CHIPs programme. EASMLens gives any organisation the same outside-in view of its own estate.

What each rule asks for, and what EASMLens shows you

RuleWhat it asks forWhat EASMLens shows you
PSPF 0211Stocktake of internet-facing systems with continuous visibilityA continuously refreshed inventory of domains, subdomains, IPs, certificates and cloud-hosted services attributed to you
Essential Eight ML1+Automated asset discovery at least fortnightly; daily scanning of internet-facing systemsDiscovery every 12 hours by default, with new assets flagged for your scanning and patching programme
Enhanced CIRMP s8A, s8CCritical system inventory; manage patching and unsupported technology riskExposed services with known CVEs and end-of-life software, evidenced over time
CPS 234 para 20Classify all information assets, including third-party managedInternet-facing assets run by suppliers under your brand and domains
Email posture (ASD CHIPs checks)DMARC at quarantine or reject, STARTTLS and valid TLSSPF, DKIM, DMARC, MTA-STS, TLS-RPT and DNSSEC graded for every domain

Reporting clocks

  • SOCI responsible entities

    12 hours (significant impact) or 72 hours (relevant impact) to ASD’s ACSC

  • APRA-regulated entities (CPS 234)

    72 hours for a material incident; 10 business days for a material control weakness

  • APRA-regulated entities (CPS 230)

    24 hours if a critical operation is disrupted beyond tolerance

  • Ransomware payments (Cyber Security Act 2024)

    72 hours after the payment, to ASD

  • Notifiable Data Breaches (Privacy Act)

    Assess within 30 days, then notify the OAIC and individuals as soon as practicable

Questions for the board

  1. 1Could we produce, today, a list of every internet-facing system we own, including supplier-run services, as PSPF 0211 and the Cisco SD-WAN direction would demand?
  2. 2If we are in one of the nine enhanced SOCI classes, which framework have we chosen under section 8A, and is our critical system inventory on track for June 2028?
  3. 3For APRA entities: does our material service provider register show what each provider exposes to the internet on our behalf?

How EASMLens supports these obligations

  • Agentless discovery of domains, subdomains, IP ranges, certificates and cloud services, refreshed every 12 hours by default
  • Exposure intelligence: known CVEs, end-of-life software and risky services visible on your internet-facing assets
  • Email domain security grading across SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DNSSEC and more
  • Change detection and alerts, so a new exposure surfaces in hours rather than at the next audit
  • Evidence exports for CIRMP annual reports, Essential Eight assessments and board packs

EASMLens discovers your attack surface from DNS, certificate transparency, internet-wide scan datasets and public records, then runs non-destructive checks against the assets in your scope. It never attempts exploitation. It provides discovery, monitoring and evidence. It does not certify an organisation against any framework, and no product can.

Frequently asked questions

Does EASMLens make us compliant with PSPF 0211 or the Essential Eight?
No tool makes an organisation compliant on its own. EASMLens produces the continuously updated internet-facing inventory and exposure evidence that 0211 and the Essential Eight discovery controls call for. Your patching, hardening and governance still do the rest.
Is the Essential Eight being replaced?
Yes. ASD published the ASD Essentials series on 15 October 2026 as its successor. The Essential Eight stays in place until ASD and regulators set transition dates, so existing obligations still apply. Boundary services, the domain for internet-facing systems, is in priority phase 1. See ASD Essentials and your internet-facing systems.
Does EASMLens scan our systems?
Yes, lightly. EASMLens discovers your estate passively from DNS, certificate transparency and internet-wide datasets, then runs non-destructive active checks, such as service detection and web server checks, against the assets in your scope. It never attempts to exploit a vulnerability, and it is not a penetration test.
Can data stay in Australia?
Tell us your residency requirement and we will confirm in writing what we can commit to, rather than answering in general terms.

More in Australia and New Zealand