Sources and tools for logging and monitoring
Every install starts with zero log sources. You choose the ones your essential functions depend on from the catalog, so the list of what you monitor is your own decision, written down in one place.
No UK law says where security logs must live. What regulators and assessors ask is whether you monitor the right systems, keep the logs secure, and can report on time. nano is a SIEM you run yourself, inside your own boundary, so the evidence is yours 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 |
|---|---|---|---|
| NCSC Cyber Assessment Framework v4.0, Principle C1ncsc.gov.uk · CAF C1 ↗ | Operators of essential services under the NIS Regulations 2018, NHS bodies through the CAF-aligned DSPT, and government departments | Monitor the security status of the systems behind your essential functions "in order to detect security events indicative of a security incident". Six outcomes, C1.a to C1.f, from log sources to threat intelligence. "Duration and level of logging is a business decision"; at Achieved, log data is "held for a suitable retention period".Guidance, but it is the standard regulators assess against. | One place for the outcome evidence: the sources you log, who can reach the logs, the alerts and the triage, all inside your own boundary. |
| Cyber Security and Resilience (Network and Information Systems) Billgov.uk · CSR Bill factsheet ↗parliament.uk · bill 4035 ↗ | Operators of essential services and relevant digital service providers, and, new in scope, managed service providers and data centers | As proposed: "a light touch, initial notification" within 24 hours of becoming aware of an incident, and a full report within 72 hours. Managed service providers, data centers and digital service providers also notify customers likely to be affected.Not yet law as of November 2026. | Alerts as detections fire, and cases that hold the evidence and the timeline you report from. An MSP can run nano inside each customer's environment, so each customer's logs stay with that customer. |
| NHS CAF-aligned DSPT, objective Cdigital.nhs.uk · DSPT objective C ↗ | NHS trusts, integrated care boards, commissioning support units and arm's-length bodies | Security monitoring along CAF lines, and "No member of staff should view, copy, delete or modify log files unless they have a legitimate reason to." Independent audit is required. No fixed retention period. | The log store sits on infrastructure your organization controls. Inside nano, roles limit who can see and change what, and administrative actions are written to nano's own audit log. |
| FCA PS26/2 and PRA PS7/26fca.org.uk · PS26/2 ↗ | Banks, insurers, payment firms and other FCA- or PRA-regulated firms | A single regime for operational incident and third-party reporting, binding from 18 March 2027. | The evidence for an incident report in one searchable place. nano is software you run, not a third-party service that holds your logs. |
| UK GDPR international transferslegislation.gov.uk · DUAA Sch. 7 ↗ | All controllers; security logs usually carry personal data such as user names and IP addresses | Transfers to another country rest on a data protection test: protection there must be "not materially lower" than under UK law (Article 45B, as amended by the Data (Use and Access) Act 2025). | Run nano in a UK region or your own UK data center and the logs are not transferred to a SIEM vendor at all. nano never receives them. |
Principle C1, security monitoring, breaks into six contributing outcomes. The NHS DSPT uses the same objective. Here is where nano fits each one.
Every install starts with zero log sources. You choose the ones your essential functions depend on from the catalog, so the list of what you monitor is your own decision, written down in one place.
"You hold log data securely and grant appropriate user and system access only to accounts with a business need." The log store is on infrastructure you control, roles and source visibility limit access inside nano, and nano itself has no standing access to your install. Platform audit log
Detections run across every source as events arrive and raise alerts for your team. Turn on nano's optional monitoring stack and route its alerts to get told when ingest stalls or drops events. Monitoring
Related alerts group into cases that hold the evidence and the timeline, so triage decisions are recorded where the data is. Case management
Your team, or your MSP, operates nano. Search, detections and cases work the same way across every source, which keeps what an analyst has to learn small.
Search one user, host or IP across sources in one timeline. Threat and IP enrichment feeds, such as ThreatFox and Tor exit nodes, add context, and you can turn each one off. Enrichment feeds
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 UK 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 you decide.
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
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.
The CAF leaves retention to you, and with nano it 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
No. No UK law requires security logs to be stored in the UK. What UK rules ask about is control and evidence: whether you monitor the right systems, keep the logs secure and accessible only to people with a business need, and can report an incident on time. If your logs go abroad, including to a SIEM vendor's cloud, UK GDPR transfer rules apply because logs usually carry personal data. Running nano in a UK region or your own data center keeps the logs where you put them, and nano never receives them.
Principle C1, security monitoring, asks you to monitor the security status of the systems supporting your essential functions to detect security events that indicate an incident. It has six contributing outcomes: C1.a sources and tools for logging and monitoring, C1.b securing logs, C1.c generating alerts, C1.d triage of security alerts, C1.e personnel skills, and C1.f understanding user and system behavior and threat intelligence. The CAF does not set a retention period: "Duration and level of logging is a business decision", and at Achieved level log data is "held for a suitable retention period".
No. As of November 2026 it is still a Bill: it completed its House of Lords stages on 2 November 2026 and has returned to the Commons for consideration of Lords amendments. Royal Assent, and then secondary legislation, are still to come. As proposed, it requires an initial notification within 24 hours of becoming aware of an incident and a full report within 72 hours, and it brings managed service providers and data centers into scope.
As proposed, relevant managed service providers come into scope alongside operators of essential services and digital service providers, with the 24-hour and 72-hour reporting clocks and a duty to notify customers likely to be affected by an incident. With nano, you can run a separate install inside each customer's environment, so each customer's logs stay with that customer and you report from evidence you can search.
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.
No. nano, LLC holds no NHS approval, NCSC assurance, Cyber Essentials certification or other UK certification, and using nano does not make you compliant with the CAF or the DSPT. It is the SIEM you run; your assessor or auditor looks at your environment, including how you use it.
No. nano, LLC is a US company. Because you run nano yourself, nano never holds your log data, so there is no copy on nano's side for anyone to request. Your logs stay in the UK environment you choose.
Anywhere you control: your own account in AWS London, Azure UK South or Google Cloud London; 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.