Essential Eight · Australia

Essential Eight event logging, and the move to ASD Essentials.

What the Essential Eight maturity model and the ISM ask of your event logs, what ASD's new Essentials series means for them, and how a SIEM you run in your own environment covers each requirement, without your logs ever reaching nano.

Buy nano
Talk to sales
ASD Essentials

The Essential Eight is evolving. Logging isn't going away.

On 15 October 2026 ASD launched the ASD Essentials, which it describes as an evolution of the Essential Eight. Both frameworks run side by side for now, and ASD's advice is to keep meeting your current obligations.

  1. 27 Nov 2023 In effect

    Current Essential Eight model

    The November 2023 maturity model is the version in force, with event logging centralized from ML2.

    cyber.gov.au · E8 maturity model ↗
  2. 15 Oct 2026 In effect

    ASD Essentials launched

    ASD launched the Essentials series, starting with Essentials for enterprise IT, OT and cloud.

    cyber.gov.au · ASD Essentials ↗
  3. Now Transition

    Both frameworks maintained

    ASD maintains the Essential Eight and the Essentials side by side during the transition. Keep meeting current obligations.

    cyber.gov.au · ASD Essentials ↗
  4. Not yet published No date

    Essential Eight retirement

    As of November 2026, ASD has not published a retirement date for the Essential Eight.

    cyber.gov.au · ASD Essentials ↗
Essential Eight maturity model

Where event logging sits on the maturity ladder.

Event logging appears in four of the eight strategies, and only from Maturity Level Two. Patching, Office macro settings and backups carry no logging requirements at any level.

  1. ML1

    No event-logging requirements

    • Maturity Level One sets no central logging or log analysis requirements.
    • Logging starts at Maturity Level Two.
  2. ML2 PSPF baseline

    Centrally logged, protected, analyzed

    • Application control, privileged access, MFA, PowerShell and command-line events centrally logged
    • Event logs protected from unauthorized modification and deletion
    • Internet-facing server logs analyzed in a timely manner
    • Incidents reported to the CISO and to ASD as soon as possible
  3. ML3

    Analysis everywhere

    • Everything at ML2
    • Plus: event logs from non-internet-facing servers analyzed in a timely manner
    • Plus: event logs from workstations analyzed in a timely manner
Summarized from the Essential Eight maturity model, November 2023. The model has the full requirement text.
What the rule requires

The Essential Eight and ISM logging checklist.

Each line: what ASD says, what it means in practice, and where nano fits.

Essential Eight maturity model: event logging at ML2 and ML3

From the November 2023 maturity model. Logging appears under four strategies: application control, restrict administrative privileges, multi-factor authentication and user application hardening.

Ref What ASD says In plain English How nano helps
ML2 · App control "Allowed and blocked application control events are centrally logged." cyber.gov.au · E8 maturity model Every allow and block decision from AppLocker, WDAC or your application control tool goes to one central place.
Collect the Windows Event Log (Security, Sysmon, PowerShell, Defender and other channels) with Vector agents and an aggregator on your network, then search and alert on it in one place.
ML2 · Admin privileges "Privileged access events are centrally logged." "Privileged user account and security group management events are centrally logged." cyber.gov.au · E8 maturity model Admin sign-ins and changes to privileged accounts and groups must be logged centrally.
Windows Security events plus identity sources such as Entra ID and Okta land in the same store, so admin activity can be searched and detected on across all of them.
ML2 · MFA "Successful and unsuccessful multi-factor authentication events are centrally logged." cyber.gov.au · E8 maturity model Keep both the passes and the failures, centrally.
Pull connectors for identity providers bring sign-in and MFA events in, both successes and failures.
ML2 · App hardening "PowerShell module logging, script block logging and transcription events are centrally logged." "Command line process creation events are centrally logged." cyber.gov.au · E8 maturity model Turn on PowerShell logging and command-line auditing, and ship the events centrally.
The Windows agent configuration collects PowerShell and Sysmon process-creation events, so command lines are searchable alongside everything else.
ML2 "Event logs are protected from unauthorised modification and deletion." cyber.gov.au · E8 maturity model Ordinary admins, and attackers with their accounts, must not be able to edit or delete the logs.
Logs sit on infrastructure you control, behind nano's role-based access control; retention and settings changes are written to the platform audit log.
ML2 "Event logs from internet-facing servers are analysed in a timely manner to detect cyber security events." "Cyber security events are analysed in a timely manner to identify cyber security incidents." cyber.gov.au · E8 maturity model Someone, or something, has to look at internet-facing server logs promptly and decide what is an incident.
Detection rules run on events as they arrive and raise alerts; related alerts group into cases for triage.
ML2 Cyber security incidents are reported to the CISO, or a delegate, and to ASD "as soon as possible after they occur or are discovered". cyber.gov.au · E8 maturity model Incidents go up the chain and to ASD quickly.
Cases keep the alerts, evidence, timeline and notes your CISO report and your report to ASD draw on. nano does not report to ASD for you.
ML3 "Event logs from non-internet-facing servers are analysed in a timely manner…" "Event logs from workstations are analysed in a timely manner…" cyber.gov.au · E8 maturity model At ML3, timely analysis extends to internal servers and every workstation.
Licensed per GB/day of ingest, with no per-endpoint fee, so adding workstation and internal-server logs changes volume, not the pricing model.

ISM: Security monitoring

Control text from the September 2026 ISM, Guidelines for security assurance, Security monitoring. The E8 maturity levels map to these controls (for example ISM-1815 sits at ML2 and ML3).

Ref What ASD says In plain English How nano helps
ISM-0580 "A security monitoring policy is developed, implemented and maintained." cyber.gov.au · ISM Sep 2026 Write down what you log, with which facilities, how you monitor it and how long you keep it. (Until June 2026 this was an "event logging policy".)
The onboarded log sources, detection rules and retention settings in nano give the policy concrete things to point to.
ISM-1405 "A centralised event logging facility is implemented." The ISM adds that this "may be achieved by using a security information and event management (SIEM) platform, a security orchestration, automation and response (SOAR) platform, or both". cyber.gov.au · ISM Sep 2026 One central place for security logs. The ISM names a SIEM as one way to do it.
nano is a SIEM with cases and playbooks that you run in your own environment.
ISM-1983 · 1984 Event logs are sent to the centralized facility "as soon as possible after they occur" and "are encrypted in transit using Australian Signals Directorate (ASD)-approved cryptography". cyber.gov.au · ISM Sep 2026 Ship logs promptly, encrypted with cryptography ASD approves.
Agents and pull connectors forward events continuously to HTTP, HEC and OTLP/HTTP ingest endpoints behind TLS that you configure. Choosing ASD-approved protocols and cipher suites is part of your configuration.
ISM-1985 · 1815 "Event logs are protected from unauthorised access." "Event logs are protected from unauthorised modification and deletion." (ISM-1815: Essential Eight ML2, ML3.) cyber.gov.au · ISM Sep 2026 Control who can read logs, and who can change or delete them.
Role-based access control, source visibility rules for sensitive sources, and a platform audit log of administrative changes.
ISM-0988 "An accurate and consistent time source is used for event logging." cyber.gov.au · ISM Sep 2026 Keep clocks synchronized so events from different systems line up.
Events keep their original timestamps in consistent time fields; keep NTP running on your hosts and log sources.
ISM-2116 · 2117 "Cyber threat intelligence services are used to support the detection of cyber security events and the identification of cyber security incidents." "Suitable AI models are used to augment the detection of cyber security events and the identification of cyber security incidents." (Both new, June 2026.) cyber.gov.au · ISM Sep 2026 Feed threat intelligence into detection, and use AI to help analysts with a model suitable for your data.
Default feeds (IPinfo Lite, ThreatFox, Tor exit nodes) tag matching events in your install. pivt AI is off by default; when on, it uses a model endpoint you configure, including one you host yourself, connecting directly, never via nano.
ISM-2153 "Threat hunting activities, informed by current strategic and sector-specific cyber threat intelligence, are conducted at least every three months." (New, September 2026.) cyber.gov.au · ISM Sep 2026 Hunt at least quarterly, using current threat intelligence.
Search and notebooks for hypothesis-led hunts, and retro-hunt to run new indicators against stored history.
ISM-1988 · 1989 "Event logs are retained in a searchable manner for at least 12 months", and as per the minimum retention requirements for classes of records in the National Archives of Australia's AFDA Express Version 2. cyber.gov.au · ISM Sep 2026 At least a year, searchable, and longer where the records authority says so.
Event retention defaults to 365 days and is configurable. Older data can tier to S3-compatible object storage you own and stays searchable. For a 12-month rule, set at least 366 days so a full year is always kept.
Why where your logs live matters

Inside your boundary, not ours.

Event logs describe your privileged accounts, your servers and your incidents. With nano they stay in an environment you control, so the protections and assessments you already rely on apply to them.

Your environment

Your data center, your account in an Australian cloud region, or an air-gapped network

01 · Sources
  • AppLocker / WDAC
  • Entra ID
  • PowerShell
  • Sysmon
  • servers
  • firewall
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano runs inside your environment. Log data is never sent to nano.
Your assessment boundary

Runs inside your IRAP-assessed environment.

nano is not IRAP-assessed and doesn't need to host your logs. It is software you deploy inside an environment you control, including one you have had assessed, so your logs stay within that boundary.

Protection · ML2

Protected from modification and deletion.

The event store sits on your infrastructure, behind your network controls and nano's role-based access. Administrative changes are written to the platform audit log.

Retention · ISM-1988

A year searchable, on storage you own.

The license is priced per GB/day of ingest, not by how long you keep data. Keep 12 months or more searchable and tier older events to your own object storage. Storage and retention

PSPF and who must comply

Mandatory for some, the benchmark for many.

The Essential Eight is guidance from ASD. The Protective Security Policy Framework (PSPF) is what makes it mandatory for Commonwealth entities.

PSPF · Commonwealth

Non-corporate Commonwealth entities: ML2.

The PSPF directs non-corporate Commonwealth entities to implement the Essential Eight; PSPF Release 2026 sets each strategy at Maturity Level Two. ASD's maturity model FAQ explains how ML3 controls in the ISM apply to their systems.

ASD Essentials · audience

Critical infrastructure and large organizations.

ASD aims the new Essentials at "Commonwealth entities, critical infrastructure owners and operators, and large organisations". Expect the same audience to be asked for logging evidence.

Everyone else

Guidance, contracts and regulators.

Outside the Commonwealth, ASD publishes the Essential Eight as guidance. Whether you must meet it, and at which level, depends on your contracts, your sector and your regulators. Check before you choose a target level.

Planning collection? See on-premise Windows and Linux collection in the docs, and pricing for the per-GB/day license.

FAQ

Questions we get asked.

What is the Essential Eight?

The Essential Eight is the Australian Signals Directorate's (ASD) set of eight mitigation strategies: patch applications, patch operating systems, multi-factor authentication, restrict administrative privileges, application control, restrict Microsoft Office macros, user application hardening and regular backups. The Essential Eight maturity model, last updated in November 2023, sets requirements for each strategy at Maturity Levels One to Three.

Is the Essential Eight being replaced by ASD Essentials?

ASD launched the ASD Essentials on 15 October 2026 as an evolution of the Essential Eight, starting with Essentials for enterprise IT, OT and cloud. ASD maintains both frameworks during the transition and says organizations should keep meeting their current regulatory obligations until regulators communicate changes. As of November 2026, ASD had not published a retirement date for the Essential Eight. The enterprise IT chapter keeps detection, analysis and response to cyber security events as a core area.

Is the Essential Eight mandatory?

For non-corporate Commonwealth entities, yes: the Protective Security Policy Framework (PSPF) directs non-corporate Commonwealth entities to implement the Essential Eight, and PSPF Release 2026 sets the target at Maturity Level Two. For other organizations ASD publishes it as guidance; whether you must meet it depends on your contracts, your sector and your regulators.

What are the Essential Eight maturity levels?

The maturity model defines Maturity Levels One, Two and Three. Each level adds requirements to every strategy and targets more capable adversaries. Organizations pick a target level based on their risk. Event logging requirements start at Maturity Level Two.

What event logging does Essential Eight ML2 and ML3 require?

At Maturity Level Two: central logging of allowed and blocked application control events, privileged access events, privileged account and security group management events, successful and unsuccessful MFA events, PowerShell module, script block and transcription events, and command line process creation events. Event logs must be protected from unauthorized modification and deletion, internet-facing server logs analyzed in a timely manner, and incidents reported to the CISO and to ASD as soon as possible. Maturity Level Three adds timely analysis of event logs from non-internet-facing servers and workstations. Maturity Level One has no event logging requirements.

What does an Essential Eight assessment check?

An assessment checks whether each requirement for the target maturity level is in place and working, using evidence rather than policy statements. For event logging, that means showing the required events reach a central store, that the logs cannot be changed or deleted by unauthorized users, and that someone analyzes them in a timely manner and acts on what they find.

Can you get Essential Eight certified?

No. ASD does not certify organizations or products against the Essential Eight. Organizations are assessed, by themselves or by a third party, against a target maturity level. A product sold as "Essential Eight certified" is making a claim ASD does not support.

Can a SIEM provide Essential Eight logging evidence without sending logs offshore?

Yes, if the SIEM runs in your environment. nano is software you install in your own data center, your account in an Australian cloud region, or an air-gapped network, so event logs are collected, stored and analyzed there and never reach nano. nano, LLC is a US company, but it never holds your log data.

How long must event logs be kept under the ISM?

The September 2026 ISM, the current release as of November 2026, says event logs are retained in a searchable manner for at least 12 months (ISM-1988), and for any longer period the National Archives of Australia's AFDA Express Version 2 sets for the class of records (ISM-1989). Older ISM releases used different retention controls, so check the current release.

Is nano IRAP-assessed?

No. nano is not IRAP-assessed and holds no ISO 27001 or SOC 2 certification. It runs inside your own environment, for example one you have had IRAP-assessed, and helps you centralize, protect, analyze and retain the event logs the Essential Eight and the ISM ask for.

What does a connected install send to nano?

A daily license check-in (deployment ID, install ID, version and license token) and one number per completed day: the total GB ingested. It also polls nano hourly for content and enrichment feeds: the log-source catalog, detection rules, SOAR content and the default IPinfo Lite, ThreatFox and Tor exit node feeds, which are on by default and can be turned off. No log content is sent. Air-gapped mode stops all of this; an offline license on its own does not. AI is off by default; when on, it connects directly to your own model endpoint, never via nano.

Primary sources

Read the rules yourself.

Start with nano.

From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.

Buy nano
Talk to sales