United States · Your boundary

Your security logs stay inside your own boundary.

There is no US law on where security logs must live. What matters is keeping the logs, and the CUI, CJI, PHI or customer data inside them, in your own environment: out of a vendor's SaaS, out of your assessment scope and out of your vendor chains. nano is a SIEM you run yourself, and none of your log data ever reaches nano.

Buy nano
Talk to sales
US rules for security logs

Nine rulebooks. Where running it yourself matters.

What each asks of your security logs, and where a SIEM you run yourself changes the picture and where it does not, as of November 2026.

Rule Who it binds What it asks of logs How running nano yourself helps
CMMC and NIST SP 800-171 nist.gov · SP 800-171 Rev. 2 ↗acquisition.gov · DFARS 7012 ↗ecfr.gov · 32 CFR 170 ↗ DoD contractors and subcontractors handling FCI or CUI, through DFARS 252.204-7012 and 32 CFR Part 170 The 800-171 Rev. 2 audit family: create and retain audit logs, trace actions to individual users, alert on logging failures, correlate review, protect audit information. DFARS 7012: report within 72 hours, keep images and packet capture for at least 90 days. Under 32 CFR 170.4, log files ingested by a security tool are Security Protection Data. Keeps a vendor out of scopeYour SIEM is still a Security Protection Asset and is assessed. But it runs inside your enclave, so no third-party SIEM provider stores your log data. Under 32 CFR 170.4, storing that data is what makes a SaaS SIEM provider an External Service Provider in your scope.
CJIS Security Policy v6.1 le.fbi.gov · CJIS v6.1 ↗ Agencies with access to criminal justice information (CJI), and contractors through the CJIS Security Addendum Review audit records weekly (AU-6) and retain them for at least one year (AU-11). Vendor staff with unescorted access to unencrypted CJI need fingerprint-based record checks (PS-3), and private contractors sign the Security Addendum (SA-9). Keeps a vendor out of scopenano runs in your agency's environment. nano has no standing access to your install. Support sees only what you choose to share. nano staff are not in your CJI screening chain for log data. You don't need to send support any CJI, and nano will sign the CJIS Security Addendum.
HIPAA Security Rule, 45 CFR 164.312(b) ecfr.gov · 45 CFR 164 ↗ Covered entities and business associates Audit controls that "record and examine activity" in systems with electronic PHI, and regular review of activity records. The Security Rule sets no retention period for logs. Keeps a vendor out of scopeLogs that carry PHI stay in your environment. nano never receives them and has no standing access to your install, so no SIEM vendor joins your business associate chain for log data. nano holds no HIPAA certification (there is none). If your support cases may include PHI, nano will sign a business associate agreement.
NYDFS, 23 NYCRR Part 500 dfs.ny.gov · 23 NYCRR 500 ↗ DFS-licensed covered entities; 500.14(b) applies to Class A companies only Audit trails designed to detect and respond to cybersecurity events, kept at least three years (500.6). Class A: "a solution that centralizes logging and security event alerting" since 1 May 2025, unless the CISO approves compensating controls in writing (500.14(b)). Notice within 72 hours (500.17). One fewer service providerCentralizes logging and alerting in your own environment, with retention on storage you own. That leaves one fewer third-party service provider holding your security logs.
FTC Safeguards Rule, 16 CFR 314.4(c)(8) ecfr.gov · 16 CFR 314 ↗ Non-bank financial institutions under FTC jurisdiction, such as auto dealers, mortgage brokers, tax preparers and fintechs "monitor and log the activity of authorized users and detect unauthorized access or use of, or tampering with, customer information by such users." Notify the FTC within 30 days of a notification event involving at least 500 consumers (314.4(j)). One fewer service providerCollects user activity from the systems that hold customer information and runs your detections on it. It removes one service provider to oversee; the rule itself does not prefer self-hosting.
SEC Form 8-K Item 1.05 and Regulation S-P sec.gov · Form 8-K ↗ecfr.gov · 17 CFR 248.30 ↗ SEC registrants (8-K); broker-dealers, investment companies, registered advisers and transfer agents (Reg S-P) File Item 1.05 within four business days after determining that a cybersecurity incident is material. Reg S-P: give notice as soon as practicable, and no later than 30 days after becoming aware of unauthorized access to or use of customer information. No scope differenceWhere logs live makes no difference here. What helps is having the evidence for the materiality decision and the notice in one searchable place.
OMB M-26-14 (federal agencies) whitehouse.gov · M-26-14 ↗fedramp.gov · scope ↗ Federal civilian executive agencies; national security systems are excluded Replaces M-21-31, which it rescinds. Logs actively searchable for at least 6 months after creation and retrievable for a year. Agencies "may consider collecting logs in enterprise security information and event management software or equivalent". Software you operateKeep recent logs searchable on fast disk and tier older ones to your own object storage. FedRAMP authorizes cloud services; nano is software you operate in your own environment.
PCI DSS v4.0.1, Requirement 10 (global) PCI DSS v4.0.1 ↗ Entities that store, process or transmit cardholder data; binding by contract, not by law Audit logs enabled for all system components (10.2.1), reviewed at least daily (10.4.1), with automated review required since 31 March 2025 (10.4.1.1). Keep 12 months, the most recent three immediately available (10.5.1). No scope differenceSelf-hosting does not shrink PCI scope. What helps: 12 months on your own storage under a per-GB/day license, and detections that automate review.
CIRCIA (not yet in force) reginfo.gov · CIRCIA ↗federalregister.gov · 2024-06526 ↗ Covered entities in critical infrastructure sectors, as the final rule will define The 2024 proposal: report covered incidents within 72 hours and ransom payments within 24 hours, and preserve data for at least two years. The final rule has been at OIRA for review since 1 October 2026. No scope differenceIf the proposal holds, long retention on storage you own is what helps.
Where to run nano in the US

Your enclave, your account, 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 enclave, your agency network, your US cloud account, or an air-gapped network

01 · Sources
  • firewall
  • VPN
  • identity provider
  • Windows
  • Linux / SSH
  • EHR or case system
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

The US region you pick.

  • AWS Any US region, or AWS GovCloud (US) if that is where your enclave lives
  • Microsoft Azure Any US region, or Azure Government
  • Google Cloud Any US region

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, inside your enclave or agency network. Logs and backups stay on storage you own, for as long as your retention policy says.

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

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, based in Connecticut. Every license includes every feature; only GB/day and support level vary.

Retention

One year or three, without a bigger license.

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.

Is there a US law that says where security logs must be stored?

No. The United States has no general data-localization law, and the rules on this page do not say which state or region your logs have to sit in. What they do regulate is who handles the data: whether a SIEM vendor that stores your logs comes into your CMMC assessment scope, your CJIS personnel screening or your HIPAA business associate chain. Running nano yourself keeps the logs, and the CUI, CJI or PHI inside them, in your own environment.

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 FedRAMP authorized, CMMC certified or CJIS compliant?

No. nano, LLC holds no FedRAMP authorization, CMMC certification, StateRAMP authorization or HITRUST certification, and the FBI does not certify products for CJIS. FedRAMP authorizes cloud services; nano is software you operate in your own environment. Using nano does not make you compliant with anything. It helps you produce the logging evidence these frameworks ask for.

Does a self-hosted SIEM take my SIEM out of CMMC scope?

No. Under 32 CFR 170.4 a SIEM provides security functions and ingests log files, so it is a Security Protection Asset and is assessed either way. What changes is the vendor: a SaaS SIEM stores your Security Protection Data, which makes its provider an External Service Provider in your scope, while a SIEM you run inside your enclave has no such provider. Confirm your scoping with your C3PAO or assessor.

Where in the United States can I run nano?

Anywhere you control: your own account in any US region of AWS, Azure or Google Cloud, including AWS GovCloud (US) or Azure Government if that is where your enclave lives; your own servers; Kubernetes with Helm; or an air-gapped network. nano does not host anything for you.

Does OMB M-21-31 still apply?

No. OMB Memorandum M-26-14 of 22 May 2026 states: "Effective immediately, OMB Memorandum M-21-31 is rescinded." M-26-14 requires agencies' retained logs to be actively searchable for at least 6 months after creation and retrievable for a year. It excludes national security systems.

Is CIRCIA reporting required yet?

No. As of November 2026, the CIRCIA final rule is at OIRA for regulatory review (received 1 October 2026) and is not binding. The 2024 proposal would require covered incidents to be reported within 72 hours, ransom payments within 24 hours, and data preserved for at least two years.

Is nano a US company?

Yes. nano, LLC is a US company, based in Connecticut. You buy online in US dollars, and because you run nano yourself, your logs stay in the environment you choose.

How do I buy nano in the United States?

Online, in US dollars. 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