Middle East · Saudi Arabia and UAE

A SIEM in your own environment, logs kept where you decide.

Saudi Arabia's Essential Cybersecurity Controls name SIEM directly and set a 12-month floor for event logs, and UAE banks keep confidential data in the UAE. nano is a SIEM you run yourself: in a Saudi or UAE 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
Saudi and UAE rules for security logs

Four 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
Saudi Arabia: NCA Essential Cybersecurity Controls (ECC-2:2024), 2-12nca.gov.sa · ECC-2:2024 ↗ Saudi government agencies and their affiliated companies and entities, inside and outside the Kingdom, and private-sector entities that own, operate or host critical national infrastructure Activate cybersecurity event logs for critical information assets, for critical and privileged accounts, and for remote access. Identify the Security Information and Event Management (SIEM) techniques used to collect them, monitor them continuously, and keep them for at least 12 months (2-12-3). nano is the SIEM: it collects the logs from your sources, runs detections continuously as events arrive, and keeps them for the period you set, on storage your entity controls.
Saudi Arabia: SAMA Cyber Security Framework, 3.3.14rulebook.sama.gov.sa · CSF 3.3.14 ↗ Organizations regulated by the Saudi Central Bank (SAMA) A security event management process with a security operations center, continuous (24x7) security event monitoring, "adequately protected logs", and automated, centralized analysis and correlation of security logs (SIEM). No retention period is set. Centralized collection, correlation and detections in one place your SOC operates, with role-based access and an audit log of administrative actions inside nano.
UAE: CBUAE Outsourcing Regulation for Banks, Article 6centralbank.ae · Outsourcing Regulation ↗ Banks licensed by the Central Bank of the UAE "Banks must ensure that the Master System of Record, which includes all Confidential Data, is continuously maintained and stored within the UAE." Customer Confidential Data must not be shared outside the UAE without Central Bank approval and the customer's prior written consent.Circular No. 14/2021. Security logs can carry customer data. Run nano in a UAE cloud region or your own UAE data center and the logs stay in the UAE; nano never receives a copy.
UAE: Personal Data Protection Law (Federal Decree-Law No. 45 of 2021)u.ae · data protection laws ↗ Organizations that process personal data in the UAE General obligations to secure personal data and keep it confidential, and requirements for transferring and sharing personal data across borders. With nano, logs that carry personal data stay in the environment you run and are not transferred to a SIEM vendor.
NCA ECC-2:2024 · 2-12 Cybersecurity Event Logs and Monitoring Management

Five minimum requirements. Where nano fits each.

Control 2-12-3 lists what an entity's event log and monitoring requirements must include as a minimum.

2.12.3.1 and 2.12.3.2

Logs for critical assets and privileged access

Every install starts with zero log sources. You add your critical systems, identity providers, VPN and remote access sources from the catalog, so what you log is your own decision, written down in one place.

2.12.3.3 and 2.12.3.4

SIEM collection, monitored continuously

Logs arrive through HEC-compatible endpoints, HTTP, OTLP, cloud pull or Vector agents. Detections run as events arrive, and related alerts group into cases with the evidence and the timeline. Case management

2.12.3.5

At least 12 months

Retention defaults to 365 days and you set what your policy needs. A longer period costs you storage you own, not license, and older events can tier to your own object storage. For a 12-month rule, set at least 366 days so a full year is always kept. Storage and retention

Where to run nano in Saudi Arabia and the UAE

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 Saudi or UAE cloud account, your data center, or an air-gapped network

01 · Sources
  • firewall
  • VPN
  • identity provider
  • privileged access
  • Windows
  • 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 the region

The Saudi or UAE region you pick.

  • AWS Middle East (UAE) me-central-1
  • Microsoft Azure UAE North
  • Google Cloud Dammam me-central2, Saudi Arabia

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 ECC asks, 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 Saudi Arabia and the UAE

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.

What does NCA ECC 2-12 require for event logs?

Control 2-12-3 lists the minimum: cybersecurity event logs activated for critical information assets, and for critical and privileged accounts and remote access; identification of the Security Information and Event Management (SIEM) techniques used to collect them; continuous monitoring; and a retention period of at least 12 months. The controls apply to Saudi government agencies and their affiliated entities, and to private-sector entities that own, operate or host critical national infrastructure.

Does ECC-2:2024 require hosting inside the Kingdom?

Not anymore. ECC-2:2024 deleted the earlier sub-control that required an entity's information hosting and storage to be inside the Kingdom, and moved controls on data localization to the National Data Management Office (NDMO) at SDAIA. Entities refer to the NDMO on localization. With nano, the logs stay wherever you run it, including in Saudi Arabia.

Does the SAMA Cyber Security Framework set a log retention period?

No. Section 3.3.14 asks for a security event management process with a SOC, 24x7 monitoring, adequately protected logs and SIEM-based correlation, but it does not set a length. In nano, retention defaults to 365 days and you set what your policy needs.

Can a UAE bank keep security logs outside the UAE?

Under Article 6 of the CBUAE Outsourcing Regulation for Banks, the Master System of Record, including all Confidential Data, is kept within the UAE, and customer Confidential Data is not shared outside the UAE without Central Bank approval and the customer's prior written consent. Security logs can contain customer data. With nano running in a UAE region or your own UAE data center, the logs stay in the UAE.

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 the NCA, SAMA or the CBUAE?

No. nano, LLC holds no NCA, SAMA, CBUAE or other regional certification or approval, and using nano does not make you compliant with the ECC or any framework. It is the SIEM you run; your assessor looks at your environment, including how you use it.

Where in Saudi Arabia and the UAE can I run nano?

Anywhere you control: your own account in Google Cloud Dammam (me-central2) in Saudi Arabia, AWS Middle East (UAE) or Azure UAE North; 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 the Middle East?

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