Singapore · CII, MAS and PDPA

Twelve months of protected logs, on storage you own.

Owners of critical information infrastructure now keep protected logs for at least 12 months, and MAS expects financial institutions to collect, review and retain theirs. nano is a SIEM you run yourself: in a Singapore cloud region, in your data center, or air-gapped. Your logs stay there, and none of your log data ever reaches nano.

Buy nano
Talk to sales
Singapore rules for security logs

Three rulebooks. One place your logs live.

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
Cybersecurity Code of Practice for CII (2026), section 6CSA · CCoP (2026) ↗ Owners of critical information infrastructure (CII) Generate, collect and store logs of access to the CII, network and remote connections, and firewall, DNS, web proxy and NIDS/NIPS logs. Keep them "protected against unauthorised access, modification and deletion" and "stored for a minimum period of 12 months after the date of the event", provide logs to the Commissioner when required, and correlate cybersecurity events to find incidents.In effect from 29 July 2026, superseding earlier versions of the Code. Every source in one store you own, kept for the period you set. Detections correlate events across sources as they arrive, and cases hold the evidence and the timeline.
MAS Technology Risk Management Guidelines, section 12.2mas.gov.sg · TRM Guidelines ↗ Financial institutions regulated by MAS "A process to collect, process, review and retain system logs should be established", with the logs "protected against unauthorised access", and events correlated across system logs to find suspicious patterns. The Guidelines set no retention period.Guidelines, January 2021. Collects security, application, database, network and operating system logs into one place you control, and the retention period is your institution's decision.
Personal Data Protection Act (PDPA)pdpc.gov.sg · obligations ↗pdpc.gov.sg · data breach ↗ Organizations in Singapore Make reasonable security arrangements to protect personal data from unauthorized access, collection, use, disclosure or similar risks. Notify the PDPC of a notifiable data breach no later than 3 calendar days after determining it is notifiable. Security logs carry personal data such as user names and IP addresses. With nano they stay in your environment and never go to a SIEM vendor, and you search the evidence for a breach assessment in one place.
Code of Practice for CII (2026) · section 6

Collect, protect, keep, correlate.

Section 6 covers logging, and monitoring and detection. Here is where nano fits the clauses CII owners ask about most.

6.1.1 and 6.1.2

The log sources the Code names

Every install starts with zero log sources. You add firewall, DNS, web proxy, intrusion detection, remote access and identity sources from the catalog, so the list of what you collect is your own decision, written down in one place.

6.1.4

Protected and kept 12 months

The log store sits on infrastructure you control, roles limit who can see and change what inside nano, and nano has no standing access to your install. Retention defaults to 365 days; set it to what your policy needs. For a 12-month rule, set at least 366 days so a full year is always kept. Storage and retention

6.2.1

Monitor, correlate, respond

Detections run across every source as events arrive, and related alerts group into cases with the evidence and the timeline, ready for your incident reporting and response plans. Case management

Where to run nano in Singapore

Your account, your region, your hardware.

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 environment

Your Singapore cloud account, your data center, or an air-gapped network

01 · Sources
  • firewall
  • DNS
  • web proxy
  • NIDS / NIPS
  • identity provider
  • core banking or OT
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 cloud account in Singapore

The Singapore region you pick.

  • AWS Asia Pacific (Singapore) ap-southeast-1
  • Microsoft Azure Southeast Asia
  • Google Cloud Singapore asia-southeast1

You pay the provider directly, and your existing cloud controls apply to the log store.

Your servers

On hardware you own.

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 at least the 12 months the Code asks of CII owners, or longer.

Air-gapped

No connection to nano at all.

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

What a connected install exchanges with nano

Every connection. No log content in any of them.

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.
Pricing and buying from Singapore

Buy online. The infrastructure stays yours.

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.

List price · US$

From US$149/month.

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

Procurement

Order forms and vendor paperwork.

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

12 months or more, your choice.

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

FAQ

Questions we get asked.

How long must CII owners keep logs in Singapore?

Under the Cybersecurity Code of Practice for Critical Information Infrastructure (2026), in effect from 29 July 2026, CII owners keep the logs the Code lists for a minimum of 12 months after the date of the event, protected against unauthorised access, modification and deletion. The Code also asks for a consistent time source, a log structure that supports analysis and sharing, and a log retention policy.

Do the MAS TRM Guidelines set a log retention period?

No. Section 12.2 asks financial institutions to establish a process to collect, process, review and retain system logs, protect them against unauthorised access, and correlate events across them. It does not set a length. In nano, retention defaults to 365 days and you set what your institution's policy needs.

What does the Code say about putting CII on cloud?

A CII owner informs the Commissioner of any plan to implement any part of the CII on cloud computing systems, and may do so only after a cybersecurity risk assessment that is submitted to the Commissioner within 30 days of its completion. Where a cloud provider is engaged, it appoints a person in Singapore to accept service of notices and legal process. nano runs on your own servers as well as in your own cloud account, so you choose which applies.

How quickly do I report a data breach under the PDPA?

If a data breach is notifiable, you notify the PDPC no later than 3 calendar days after determining that it is notifiable, and notify affected individuals as the PDPA requires. nano helps with the evidence: logs from every source in one searchable place, and cases that keep the timeline.

Does nano store my logs or have access to my install?

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.

Is nano approved by CSA or MAS?

No. nano, LLC holds no CSA, MAS or other Singapore certification or approval, and using nano does not make you compliant with the Code or the TRM Guidelines. It is the SIEM you run; your auditor looks at your environment, including how you use it.

Where in Singapore can I run nano?

Anywhere you control: your own account in AWS ap-southeast-1, Azure Southeast Asia or Google Cloud asia-southeast1; your own servers in your data center; Kubernetes with Helm; or an air-gapped network. nano does not host anything for you.

How do I buy nano in Singapore?

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.

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