Partnership Tenzir × nano

Shape telemetry upstream. Turn OCSF into investigations.

Tenzir gives security teams a programmable control point before storage: collect, parse, enrich, reduce, and route each stream. The security-ready path becomes OCSF before it reaches nano, so source-specific transformation stays upstream of the SIEM.

The open-core ocsf+tenzir profile bundles Tenzir 6.6.0 and writes OCSF directly into nano's ClickHouse OCSF store over the native protocol. nano turns those records into search, detections, investigations, and cases.

See how it fits together → Read the solution brief → Visit Tenzir →
LIVE · Tenzir streaming into nano
Tenzir makes telemetry security-ready. nano makes OCSF actionable. The handoff is a direct write into nano's ClickHouse OCSF store.
ocsf+tenzir profile· Tenzir ≥ 6.6.0· OCSF-first storage· licensed per GB/day

fig 01 · Tenzir pipelines feeding nano's ClickHouse in real time.

Why together

Each does one job well.

Tenzir owns everything upstream of storage: collection, parsing, OCSF normalization, in-stream enrichment, volume reduction, and routing. nano accepts OCSF first and owns search, detections, alert queues, triage, and cases. The two compose through one direct ClickHouse write.

· makes the data right

Collect, normalize, enrich, reduce.

01Collect telemetry from any source: endpoint, identity, network, cloud, SaaS.
02Parse and map to stable OCSF event classes before anything lands.
03Enrich in-stream with geo, asset, and threat-intel context at ingest.
04Deduplicate, filter, and route before the nano write, controlling what enters the OCSF store.
to_clickhouse
· makes it actionable

Search, detect, triage, close.

01Search promoted OCSF fields in nano's ClickHouse store.
02Run detections as code against the OCSF records Tenzir writes.
03Investigate alerts with entity context, risk, evidence, and the next pivots in one workflow.
04Cases bundle alert, evidence, timeline, and notes; playbooks keep response consistent.
The data flow

From raw telemetry to a queryable OCSF row.

On Tenzir 6.6.0 and newer, to_clickhouse sends event and source_type straight into nanosiem.ocsf_logs_raw. nano's materialized-view chain derives the searchable OCSF record in nanosiem.ocsf_logs.

01 · Sources
endpoint · edr identity · okta network · suricata cloud · saas
02 · Tenzir pipeline
shape · map to OCSF enrich · dedupe · reduce route each stream upstream to_clickhouse · Tenzir ≥ 6.6.0
03 · nano OCSF store
ocsf_logs_raw · direct landing materialize → ocsf_logs search · detections · risk alert → investigation → closed case

fig 02 · One path. Source-specific parsing stays out of the database; ClickHouse stays fast.

The economics

Control volume before storage.

Tenzir controls which telemetry enters nano. nano is licensed per GB/day of ingest, so reducing volume upstream in Tenzir lowers the nano license you need. Both run inside your environment: Tenzir writes directly to your nano ClickHouse, and nothing passes through nano. About nano

01 · Reduce upstream

Shape the OCSF path.

Tenzir deduplicates, filters, reduces, and routes upstream. Send the security-relevant OCSF stream to nano and direct other streams wherever your policy requires.

02 · Per GB/day downstream

Pay for what reaches nano.

nano is priced per GB/day of ingest on a continuous curve, with nothing per seat, endpoint or query. Reducing average GB/day upstream lowers the license you need downstream.

03 · Open-core profile

The direct path ships.

Choose the open-core ocsf+tenzir profile to start a bundled Tenzir 6.6.0 node with the direct ClickHouse sink already wired to nano's OCSF store.

In practice

From alert to closed case, on clean data.

Because Tenzir keeps the data model stable upstream, nano's searches and detections operate on consistent OCSF fields even when source formats differ. Risk, evidence, and entity context stay connected to the same stored record.

OCSF-first storage means the normalized record Tenzir writes is the record nano searches, detects on, and carries into an investigation.

Read the full solution brief →
land-in-nano.tql
// shape, reduce, and route before this sink
this = { event: this, source_type: "tenzir" }
source_type = source_type.otherwise("unknown")
unordered { batch 65536, timeout=2s }

to_clickhouse table="nanosiem.ocsf_logs_raw",
  host=$ch_host, port=$ch_port,
  user=$ch_user, password=env("CLICKHOUSE_INGEST_PASSWORD"),
  tls=false, mode="append"
×

Run the shipped OCSF path.

Start the open-core ocsf+tenzir profile, map one source to OCSF, and write it directly into nano's ClickHouse store with Tenzir 6.6.0 or newer.

Install nano → Read the solution brief

Visit Tenzir · tenzir.com

open-core ocsf+tenzir profile · Tenzir ≥ 6.6.0 · direct ClickHouse write · OCSF-first storage