Trust & security

We can't lose your logs. We never have them.

nano runs in your environment. Here is exactly what reaches nano, what we run on our side to sell and support it, and where we stand on certifications.

Your logs Never received by nano
Sent to nano Daily license check-in, one GB/day number
Downloaded Signed releases, content and feeds (hourly)
AI Off by default; your own endpoint
Air-gapped No connection to nano at all
Company nano, LLC, United States
Certifications None (see below)
Report a vulnerability
Data flows

What your install sends and downloads.

Every connection a connected install makes to nano. Log content, hosts, users, IP addresses from your events, source names and event rates are never sent. Full detail, and how to turn each one off.

FlowWhat it carriesWhen, and how to stop it
Sent to nano
License check-inDeployment ID, the running version, a random nonce, your license token and the install ID.Once a day. Use an offline license file or air-gapped mode instead.
Usage reportOne number per completed UTC day: total GB ingested. Nothing else about the data.Once a day, with an online license. None with an offline license or air-gapped mode.
Downloaded from nano
ContentSigned log-source parsers, detection rules, playbooks and catalogs. Every install starts with zero log sources; nothing is onboarded for you.Hourly. No data is sent. CONTENT_CHANNELS_AUTO_UPDATE=false, or point it at your own mirror.
Enrichment feedsOne signed bundle: IPinfo Lite (country, continent, network owner), ThreatFox and the Tor exit-node list. Events are enriched locally.Hourly. No data is sent. PLATFORM_FEEDS_AUTO_UPDATE=false, or your own mirror.
Releases and imagesSigned, digest-verified images and bundles.When you install or upgrade. On Kubernetes, a registry-credential refresh calls nano about every 20 minutes; it can be turned off.
Not via nano
pivt AIPrompts go straight to the model endpoint you configure: any OpenAI-compatible API, including self-hosted models, or the Anthropic Messages API.Off until you configure a provider.
Threat-intel lookupsURLhaus, VirusTotal and others are optional lookups that go directly to that provider with your key.Off until an admin adds one.
Air-gapped
AIRGAP_MODEStops all connections to nano: no check-in, no usage report, no content or feed polling. The license and the content, SOAR and feed packs are carried across the gap by hand.Included with every license, if your environment requires it.
Verify the software

Don't take our word for it.

What runs in your environment is signed, inspectable and quiet.

01 · Releases

Signed releases, with an SBOM.

Images are pulled and verified by digest. For air-gapped installs, the signed image bundle loads into your own registry. Every release ships a CycloneDX SBOM, attached to the release and to each image as an attestation. Open-source SBOMs are public; Self-run customers can request the SBOM for the commercial modules. Latest release and SBOMs

02 · Content

Signed content and feeds.

The install verifies each content and enrichment bundle's signature before using it, and keeps running on what it has if updates stop.

03 · Source

An open-source engine.

The core engine is AGPL-3.0, so you can read what ingest, search and detections do. The paid license adds the commercial modules on the same installer. Open source vs the paid product

04 · Telemetry

No product telemetry.

No analytics, telemetry or crash-reporting service is built into the nano server or web app. Health metrics go only to an OTLP endpoint you set.

Inside your install

Controls in the software you run.

Identity, access and audit run inside your install, under your own controls. Your servers, network, TLS certificates, disk encryption and backups stay yours to operate.

01 · Input

Input validation.

All API input is validated in Rust. Serde enforces JSON shape, strong types (UUIDs, enums) handle primitives, and per-handler rules reject bad values before they hit the database. SQL injection is closed at compile time via sqlx parameterized queries.

02 · Identity

SSO and roles.

OIDC single sign-on against your identity provider, with roles that control who can search, change detections or administer the install.

03 · Audit

Structured audit logs.

Administrative actions are recorded with timestamps, actor identity and affected resources, inside your install. Platform audit

04 · Storage

Your disks, your retention.

Events are stored in ClickHouse on disks you own, with optional tiering to your own S3-compatible storage. You set the retention. Storage settings

Our platform

How we secure app.nano.rs.

app.nano.rs is where you buy, license and download nano. It holds your account and billing details, never your logs. These controls apply to our platform, not to your SIEM.

01 · Transport and storage

Encrypted in transit and at rest.

All connections use TLS 1.2+. Secrets and credentials we store are encrypted with AES-256-GCM before they reach the database.

02 · Sessions

Short sessions, optional 2FA.

Sessions expire after 48 hours. Two-factor authentication is available for every account, and cross-site request forgery protection covers every state-changing request.

03 · Rate limits

Rate limiting.

API rate limits are enforced per organization to prevent abuse.

04 · Webhooks

Webhook validation.

Inbound webhooks (Stripe, GitHub, partners) are cryptographically verified before processing to prevent spoofing and replay attacks.

Compliance

Where we stand.

nano, LLC is a US company. We hold no SOC 2, ISO 27001, IRAP or C5 certification, and none is underway. Using nano does not make you compliant with any framework. Because nano runs inside your environment, it sits within your own controls and assessments rather than asking you to trust a vendor-hosted service.

We never sell your data or use it to train models.

  • Logging requirements by regulation: Essential Eight, ISM, SOCI, CPS 234, NIS2, DORA, the Cyber Resilience Act and more.
  • Australia: IRAP, PSPF and running nano in an Australian region or your own data center.
  • Europe: GDPR, NIS2 and the US CLOUD Act question.
  • Data Processing Agreement: GDPR Article 28 terms, with the EU Standard Contractual Clauses and the UK Addendum for transfers.
  • Responsible disclosure: report a vulnerability to security@nano.rs. We respond within 48 hours.
Sub-processors

Who processes your data.

For your self-hosted install, the vendors we use touch your account and billing details only. Your log data: none. The DPA (Section 7.2) is the authoritative list.

VendorPurposeData processed
nano customers
StripePayment processingBilling info, payment methods, invoices
CloudflareDNS, CDN, security, transactional email, content and feed downloadsWebsite and app traffic, notification email addresses
Google CloudContainer registry and release downloadsnano application images and bundles
MixpanelProduct analytics for app.nano.rsPseudonymous usage events, session replays, email, org ID; app.nano.rs only, consent-gated
Your infrastructure
Your servers or cloud accountRuns nanoAll log data stays on your infrastructure. nano never receives it.

Material changes to sub-processors are notified 30 days in advance, as set out in the DPA.

Read it. Then run it.

Trust pages are easy to write. Open source code and a documented list of data flows are harder. Both are here.

Security questionnaires welcomed: security@nano.rs