Protect event logs
The log store sits on infrastructure you control. Inside nano, roles and source visibility limit who can see and change what, and nano itself has no standing access to your install. Platform audit log
For agencies, the NZISM sets the logging rules and Cloud First keeps anything above RESTRICTED out of public cloud. nano is a SIEM you run yourself: in a New Zealand cloud region, on your own servers, or air-gapped. Your logs stay there, and none of your log data ever reaches nano.
What each asks of your security logs, and where a SIEM you run yourself fits, as of November 2026.
| Rule | Who it binds | What it asks of logs | How running nano yourself helps |
|---|---|---|---|
| NZISM, section 16.6 Event Monitoring, Logging and Auditinggcsb.govt.nz · NZISM 16.6 ↗ | New Zealand government agencies | Event logs MUST be protected from modification, unauthorized access, and whole or partial loss within the retention period. They MUST be archived and retained for a period the agency determines, and agencies SHOULD retain DNS, proxy and event logs for at least 12 months. | One log store on infrastructure your agency controls, with role-based access inside nano and an audit log of administrative actions. Retention is a setting you choose, so 12 months or more costs you storage, not license. |
| Cloud First policydigital.govt.nz · Cloud First ↗digital.govt.nz · jurisdictional risk ↗ | Public service agencies | Agencies must only store data classified RESTRICTED or below in a public cloud service, whether it is hosted onshore or offshore. Over time, RESTRICTED information is to be hosted in New Zealand where a suitable onshore service exists. | Run nano in your own account in a New Zealand cloud region for RESTRICTED and below. Above RESTRICTED, run it on your own servers or air-gapped, where a SaaS SIEM cannot go. |
| Privacy Act 2020, Principle 5 and notifiable privacy breachesprivacy.org.nz · IPP 5 ↗privacy.org.nz · notifiable breaches ↗ | All agencies, public and private | Personal information must be protected by security safeguards that are reasonable in the circumstances against loss and against access, use, modification or disclosure that is not authorized. A breach that has caused or is likely to cause serious harm must be notified to the Privacy Commissioner as soon as practicable; the Commissioner says ideally within 72 hours of becoming aware of it. | Security logs carry personal information such as user names and IP addresses. With nano they stay in your environment and never go to a SIEM vendor, and cases hold the evidence and timeline you report from. |
Three of the event logging controls agencies ask about most, and where nano fits each one.
The log store sits on infrastructure you control. Inside nano, roles and source visibility limit who can see and change what, and nano itself has no standing access to your install. Platform audit log
Retention defaults to 365 days and is yours to change. Older events can tier to your own object storage, so archived logs stay searchable in the same place. For a 12-month rule, set at least 366 days so a full year is always kept. Storage and retention
Every install starts with zero log sources. You add DNS, proxy, firewall, identity and endpoint sources from the catalog, and detections run across all of them as events arrive.
You install nano with Docker Compose or with Helm on Kubernetes, on infrastructure you control. Sources send logs to it over your network; it parses, stores, searches and runs detections on them there.
Your New Zealand cloud account, your data center, or an air-gapped network
Never receives your logs.
You pay the provider directly, and your existing cloud controls apply to the log store.
Run on your own servers, single node or multi-node with high availability, or on Kubernetes with Helm. Logs and backups stay on storage you own, for the retention period your agency sets.
Included with every license, if your environment requires it: a signed image bundle, content and enrichment packs you import by hand, on-premises AI and an offline license you renew by hand. Air-gapped deployment
A connected install makes a few outbound HTTPS connections to nano. Here is each one, and what you can turn off.
| Exchange | What it contains | Direction | Can you turn it off? |
|---|---|---|---|
| License check-in, daily | Deployment ID, install ID, version, a nonce and the license token | To nano | Required when connected. Air-gapped installs use an offline license. |
| Usage, once per day | One number per completed UTC day: total GB ingested | To nano | Sent with the check-in when connected. |
| Content and enrichment feeds, hourly | Log-source catalog, detection rules and SOAR content; IPinfo Lite, ThreatFox and Tor exit node feeds. The poll carries no install data; nano sees the source IP. | Download | Yes. The default feeds are on by default and can be turned off. |
| Images and releases | nano container images at install and upgrade; on Kubernetes, a registry credential refreshed about every 20 minutes | Download | The Kubernetes credential refresh can be disabled. |
nano is licensed per GB/day of ingest, not per endpoint or per year of retention. You run, and pay for, the infrastructure in your own account or data center.
US$149/month at 5 GB/day and US$279/month at 10 GB/day, list price in US dollars. Pay monthly by card, or annually by card or invoice. See pricing
In New Zealand you buy from nano directly. Buying through a procurement process, or need a vendor questionnaire answered? Email sales@nano.rs. nano, LLC is a US company. Every license includes every feature; only GB/day and support level vary.
Retention costs you storage you own, not license. It defaults to 365 days; set what your policy needs and tier older events to your own object storage. Storage and retention
Event logs MUST be archived and retained for an appropriate period as determined by the agency, and agencies SHOULD retain DNS, proxy and event logs for a minimum of 12 months. The 18-month figure that is often quoted comes from Australia's ISM, not the NZISM. In nano, retention defaults to 365 days and you set what your agency's policy needs.
Under Cloud First, agencies must only store data classified RESTRICTED or below in a public cloud service, whether it is hosted onshore or offshore. A SaaS SIEM is a public cloud service. nano runs where you put it: your own account in a New Zealand cloud region for RESTRICTED and below, or your own servers or an air-gapped network for anything above.
Security logs usually carry personal information such as user names and IP addresses, so Principle 5 applies: you need security safeguards that are reasonable in the circumstances. If a privacy breach has caused or is likely to cause serious harm, you notify the Privacy Commissioner as soon as practicable. With nano, the logs stay in your environment, and nano never receives them.
No. nano is software you install and operate in your own environment. Your logs are collected, stored, searched and analyzed there, and nano has no copy of them. nano has no standing access to your install. Support sees only what you choose to share. A connected install sends nano a daily license check-in and one usage number per day (total GB ingested), and downloads content and feeds. Air-gapped installs send nano nothing.
nano, LLC holds no New Zealand government certification or endorsement, and using nano does not make a system compliant with the NZISM. It is the SIEM you run inside your own environment; your certification and accreditation process covers your system, including how nano is configured in it.
Not today. In New Zealand you buy from nano directly, online or through your procurement process. Our partner Threatbear works in Australia.
Anywhere you control: your own account in AWS Asia Pacific (New Zealand) or Azure New Zealand North, your own servers in your data center, Kubernetes with Helm, or an air-gapped network. nano does not host anything for you.
Online, in US dollars, the same way as everywhere else. Pay monthly by card, or annually by card or invoice. Every license includes every feature, including air-gapped operation; only the GB/day and support level change the price. If your procurement team needs an order form, vendor forms or a security questionnaire, email sales.
Last reviewed 14 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.