A year searchable, on storage you own.
Retention defaults to 365 days and is configurable; older events can tier to your own object storage and stay searchable. Storage and retention
What ASD's Information Security Manual asks of your security logs in the September 2026 release: a central facility, protected and encrypted logs, timely analysis, threat hunting and 12 months of searchable retention. And how a SIEM you run in your own environment covers each control.
Earlier releases published these controls as the Guidelines for system monitoring. In the September 2026 ISM they sit in the Security monitoring section of the Guidelines for security assurance, with three new controls added this year.
ISM-1983 to ISM-1989 were added in December 2024, including 12-month searchable retention.
cyber.gov.au · ISM Dec 2024 changes ↗Security monitoring policy replaced event logging policy (ISM-0580). New ISM-2116 (threat intelligence) and ISM-2117 (AI models). ISM-1984 now says ASD-approved cryptography.
cyber.gov.au · ISM June 2026 changes ↗New ISM-2153: threat hunting at least every three months. This is the current release as of November 2026.
cyber.gov.au · ISM Sep 2026 changes ↗Each line: the control text from the September 2026 ISM, what it means in practice, and where nano fits.
September 2026 ISM, Guidelines for security assurance, Security monitoring. Every control below applies to NC, OS, P, S and TS systems.
| Ref | What the ISM 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 | "Event logs sent to a centralised event logging facility are sent as soon as possible after they occur." cyber.gov.au · ISM Sep 2026 | Forward continuously, not in nightly batches. | Agents and pull connectors forward events continuously to HTTP, HEC and OTLP/HTTP ingest endpoints. |
| ISM-1984 | Event logs sent to the centralized facility "are encrypted in transit using Australian Signals Directorate (ASD)-approved cryptography". cyber.gov.au · ISM Sep 2026 | Encrypt log transport, with cryptography ASD approves. (The June 2026 release added the ASD-approved wording.) | Ingest endpoints sit 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. |
| Ref | What the ISM says | In plain English | How nano helps |
|---|---|---|---|
| ISM-0585 | For each event logged, "the date and time of the event, the relevant user or process, the relevant filename, the event description, and the information technology equipment involved are captured". cyber.gov.au · ISM Sep 2026 | Each event needs the who, what, when and where. | Parsers extract these into named fields you can search and alert on. Whether a source records them is up to its own logging configuration. |
| ISM-1959 | "To the extent possible, event logs are captured and stored in a consistent and structured format." cyber.gov.au · ISM Sep 2026 | Structured, consistently named fields rather than raw text blobs. | Every onboarded source is parsed into a common, structured schema, so one query works across sources. |
| Ref | What the ISM says | In plain English | How nano helps |
|---|---|---|---|
| ISM-0120 | "Cyber security personnel have access to sufficient tools to facilitate the detection of cyber security events and the identification of cyber security incidents." cyber.gov.au · ISM Sep 2026 | Your team needs real tooling, not log files on each server. | Search, detection rules, alerts, cases, notebooks and dashboards in one platform. |
| ISM-2116 | "Cyber threat intelligence services are used to support the detection of cyber security events and the identification of cyber security incidents." (New, June 2026.) cyber.gov.au · ISM Sep 2026 | Feed threat intelligence into detection. | Default feeds (IPinfo Lite, ThreatFox, Tor exit nodes) tag matching events in your install, and you can add threat-intelligence lookups of your choice. |
| ISM-2117 | "Suitable AI models are used to augment the detection of cyber security events and the identification of cyber security incidents." (New, June 2026.) cyber.gov.au · ISM Sep 2026 | Use AI to help analysts, with a model suitable for your data. | pivt AI is off by default. When on, it investigates and helps tune detections using a model endpoint you configure, including one you host yourself, connecting directly, never via nano. |
| ISM-1986 · 1906 · 1907 · 0109 | Event logs from critical servers, internet-facing servers (E8 ML2, ML3), non-internet-facing servers (E8 ML3) and workstations (E8 ML3) "are analysed in a timely manner to detect cyber security events". cyber.gov.au · ISM Sep 2026 | Look at server and workstation logs promptly, starting with critical and internet-facing servers. | Detection rules run on events as they arrive. Licensing is per GB/day with no per-endpoint fee, so adding workstations changes volume, not the pricing model. |
| ISM-1987 · 1960 · 1961 | Event logs from security products, internet-facing network devices and non-internet-facing network devices are analyzed in a timely manner to detect cyber security events. cyber.gov.au · ISM Sep 2026 | EDR, firewall, proxy and switch logs count too. | Collect from security products and network devices over syslog, HTTP or pull connectors, and run the same detections across them. |
| ISM-1228 | "Cyber security events are analysed in a timely manner to identify cyber security incidents." (E8 ML2, ML3.) cyber.gov.au · ISM Sep 2026 | Decide promptly which events are incidents. | Related alerts group into cases, with risk-based alerting rolling weak signals into one alert for triage. |
| 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. |
| Ref | What the ISM says | In plain English | How nano helps |
|---|---|---|---|
| ISM-1988 | "Event logs are retained in a searchable manner for at least 12 months." cyber.gov.au · ISM Sep 2026 | At least a year, and searchable, not just archived. | Event retention defaults to 365 days and is configurable. Older data can tier to S3-compatible object storage you own. For a 12-month rule, set at least 366 days so a full year is always kept. |
| ISM-1989 | Event logs are retained as per the minimum retention requirements for classes of records set out in the National Archives of Australia's AFDA Express Version 2. cyber.gov.au · ISM Sep 2026 | Some records must be kept longer; the records authority says how long. | Licensed per GB/day of ingest, not by how long you keep data, so longer retention costs storage you own rather than license. |
The ISM marks which controls belong to each Essential Eight maturity level. In the security monitoring section, five do.
| Control | What it asks | Essential Eight |
|---|---|---|
| ISM-1815 | Event logs protected from unauthorized modification and deletion | ML2, ML3 |
| ISM-1906 | Internet-facing server logs analyzed in a timely manner | ML2, ML3 |
| ISM-1228 | Cyber security events analyzed in a timely manner to identify incidents | ML2, ML3 |
| ISM-1907 | Non-internet-facing server logs analyzed in a timely manner | ML3 |
| ISM-0109 | Workstation logs analyzed in a timely manner | ML3 |
The Essential Eight's own central logging requirements (application control, privileged access, MFA, PowerShell and command-line events) are covered on the Essential Eight logging page.
The ISM asks you to protect event logs from unauthorized access. A log store you run yourself keeps that protection in your hands, and keeps the logs inside the system your assessor reviews.
Your data center, your account in an Australian cloud region, or an air-gapped network
Never receives your logs.
Retention defaults to 365 days and is configurable; older events can tier to your own object storage and stay searchable. Storage and retention
AI is off by default. When on, pivt calls the model endpoint you configure directly, including one you host yourself, so "suitable" can mean suitable for your classification. AI settings
Enrichment feeds tag events as they arrive, and retro-hunt runs new indicators against stored history. Enrichments · Retro-hunt · Audit log
The Information Security Manual (ISM) is the Australian Signals Directorate's (ASD) cyber security framework: a set of principles and controls, each with an ID such as ISM-1405, that organizations select and tailor to protect their systems. It is organized as guidelines on topics such as security assurance, system hardening and networking. The current release, as of November 2026, is the September 2026 ISM, first published on 7 September 2026.
Non-corporate Commonwealth entities must, through the Protective Security Policy Framework: PSPF Release 2026 requires them to apply the ISM's cyber security principles during all stages of a system's lifecycle, and to apply its controls and guidelines on a risk-based approach. Other organizations use the ISM as guidance, or because a contract, a customer or an assessment (such as IRAP) asks for it.
Each control has an ID (for example ISM-1988), a revision number, the month it was last updated, the classifications it applies to (NC non-classified, OS OFFICIAL: Sensitive, P PROTECTED, S SECRET, TS TOP SECRET) and, where relevant, the Essential Eight maturity levels it maps to. For example, ISM-1815, protecting event logs from unauthorized modification and deletion, maps to Essential Eight ML2 and ML3.
In the September 2026 ISM they are in the Security monitoring section of the Guidelines for security assurance: a security monitoring policy (ISM-0580); a centralized event logging facility (ISM-1405); prompt, encrypted forwarding (ISM-1983, ISM-1984); protection from unauthorized access, modification and deletion (ISM-1985, ISM-1815); an accurate time source (ISM-0988); event details and structure (ISM-0585, ISM-1959); timely analysis of logs from servers, workstations, security products and network devices (ISM-1986, ISM-1906, ISM-1907, ISM-0109, ISM-1987, ISM-1960, ISM-1961, ISM-1228); tools, threat intelligence and AI for detection (ISM-0120, ISM-2116, ISM-2117); threat hunting (ISM-2153); and retention (ISM-1988, ISM-1989).
At least 12 months, in a searchable manner (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, including figures of seven years and 18 months that many guides still quote; those are not in the current ISM.
It requires a centralized event logging facility (ISM-1405) and says this may be achieved using a security information and event management (SIEM) platform, a security orchestration, automation and response (SOAR) platform, or both. So a SIEM is the ISM's own example, not the only way. The facility then has to meet the other controls: prompt and encrypted forwarding, protection of logs, timely analysis and 12-month searchable retention.
The June 2026 release renamed the event logging policy to a security monitoring policy (ISM-0580), required ASD-approved cryptography for logs in transit (ISM-1984), and added controls for using cyber threat intelligence (ISM-2116) and suitable AI models (ISM-2117) to support detection. The September 2026 release added threat hunting informed by current threat intelligence at least every three months (ISM-2153).
No. ISM compliance is a property of a whole system and how it is run, not of a product, and nano is not IRAP-assessed or otherwise certified. It runs inside your environment and helps you implement the security monitoring controls; your assessor tests whether your system meets them.
Last reviewed 13 November 2026. Regulations and guidance change, so read the current version at the source.
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.