nano SIEM
Reference

Supported sources

Supported in:Self-hosted

nano's OCSF 1.9 parser catalog: each source's log source name and the OCSF classes it emits, and the ways to send data on each deployment.

Find an OCSF 1.9 parser in the catalog for your log source and choose a supported ingest method for your deployment.

nano ships a catalog of 64 OCSF 1.9 parsers. For an unlisted source, send JSON or syslog through a generic parser, or build a custom parser.

How a source is identified

Each event belongs to a log source, and the log source picks the parser. The source's name is stored on every event as metadata.log_source (lowercase), so you can filter on it:

metadata.log_source=okta | stats count by class_name, activity_name

How a sender names the source depends on the protocol (a HEC envelope field, the X-Source-Type HTTP header, or the source the ingest credential was issued for). See Ingest data.

Deploy one parser per source name. Where the catalog has several parsers for one source (for example, Windows Event Log as rendered text or XML), choose the one that matches how your collector sends the data.

Ways to send data

MethodOpen coreSelf-run
HEC:8088/services/collector/eventhttps://<ingest-host>/services/collector
HTTP / HTTPS JSON (JSON, arrays, NDJSON)http://<host>/ingest or Vector :8080https://<ingest-host>/ingest
OTLP/HTTP logs, traces and metrics:4318 (loopback by default)https://<ingest-host>/otlp/v1/{logs,traces,metrics}
OTLP gRPC:4317 (loopback by default)In-cluster only
Native Vector protocol (mutual TLS from v2.0.30):6000, client certificate required:6000 on the server or on each ingest server, client certificate required; in-cluster on Kubernetes when you enable it
SyslogDisabled by default; enable in VectorDisabled by default; enable in Vector
Pull: AWS S3/SQS, GCP Pub/Sub, KafkaConfigured per log sourceConfigured per log source
SaaS collectors (scheduled pull from a vendor API)Not availableYes
Collectors that forward over HEC, HTTPS or OTLP (Vector, Cribl, Fluent Bit, OpenTelemetry Collector)YesYes

Self-run on Kubernetes receives events on a dedicated ingest hostname, separate from the app, so ingest load can't affect the UI and API; this is coming to Self-run on Docker Compose. OTLP traces and metrics are stored in their own ClickHouse tables, not normalized to OCSF.

OTLP logs arrive as the otlp_log source. With the OpenTelemetry logs parser deployed they become API Activity (class_uid=6003). Without it, the generic parser stores each record as a Base Event (class_uid=0) with its body in message and the full record in raw_data, so check which you have before writing class-based searches:

metadata.log_source=otlp_log | stats count by class_uid

See Deployment models for each deployment's endpoints.

Parser catalog

The class column lists the OCSF classes each parser can emit; see the class table for names. 0 (Base Event) is used for records the parser can't classify.

Endpoint

Sourcemetadata.log_sourceOCSF classes
CrowdStrike Falconcrowdstrike_falcon1001, 1005, 1006, 1007, 1009, 2004, 3002, 4001, 4003, 5001, 5020, 6003, 201002, 201004
LimaCharlielimacharlie0, 1001, 1005, 1007, 2004, 3002, 4001, 4003, 5001, 5003, 6002, 201001, 201002, 201004
Linux auditdlinux_auditd1001, 1007, 3002, 3006, 3007, 4001
Microsoft Defender for Endpointdefender_edr1001, 1007, 2004, 3002, 4001, 4003, 5001, 201001, 201002
Microsoft Sysmonwindows_sysmon1001, 1005, 1007, 4001, 4003, 201001, 201002
Microsoft Sysmon (XML)windows_sysmon1001, 1002, 1005, 1007, 1012, 4001, 4003, 6002, 201001, 201002, 201003
Moat EDRmoat_edr, moat0, 1001, 1007, 2004, 4001, 6002
SentinelOnesentinelone1001, 1007, 2004, 4001, 4003, 6003, 201001, 201002
Sysmon for Linux (XML)linux_sysmon1001, 1007, 4001, 6002
VMware Carbon Blackcarbon_black1007, 2004
Windows Event Logwindows_event1007, 3002, 3003
Windows Event Log (rendered text)windows_event1001, 1006, 1007, 1008, 3002, 3003, 3004, 3006, 3007, 4006, 201001, 201002, 201004
Windows Event Log (XML)windows_event0, 1001, 1006, 1007, 1008, 1009, 3002, 3003, 3006, 3007, 201002, 201004

Network

Sourcemetadata.log_sourceOCSF classes
Broadcom ProxySGbroadcom_proxy0, 4002
Check Pointcheckpoint2004, 3002, 4001, 4002
Cisco ASAcisco_asa2004, 3002, 4001
Cisco Merakimeraki2004, 3002, 4001, 4002
Cisco Umbrellacisco_umbrella0, 4002, 4003
Cloudflarecloudflare0, 4002, 4003
Conduit MITM Proxyconduit_proxy0, 4002
Fortinet FortiGatefortinet2004, 3002, 4001, 4002, 4003
Infoblox DHCPinfoblox_dhcp4004
Juniper SRXjuniper_srx2004, 4001, 4002
MikroTik RouterOSrouteros0, 3002, 4001, 4003, 4004
Palo Alto Networks PAN-OSpalo_alto2004, 3002, 4001, 4002, 6003
SonicWallsonicwall2004, 3002, 4001, 4002
Sophos Firewallsophos0, 2004, 3002, 4001, 4002, 4009, 4014
Squidsquid_proxy0, 4002
Zeekzeek0, 2004, 3002, 4001-4009, 4014
Zscaler Internet Accesszscaler_zia0, 2004, 4001, 4002, 4003, 6003

Cloud and SaaS

Sourcemetadata.log_sourceOCSF classes
AWS Application Load Balanceraws_alb4002
AWS CloudTrailaws_cloudtrail6003
AWS GuardDutyaws_guardduty2004
AWS S3 server access logsaws_s3_access6003
AWS VPC Flow Logsaws_vpc_flow4001
AWS WAFaws_waf4002
Azure Activity Logazure_activity6003
Azure Firewallazure_firewall4001, 4002, 4003
GitHub audit loggithub_audit0, 3002, 3006, 3007, 6003
Google Cloud Audit Logsgcp_audit6003
Google Workspacegoogle_workspace, gws_login, gws_admin, gws_token, gws_drive0, 3002, 3006, 3007, 6003, 6006
Kubernetes audit logkubernetes_audit6003
Microsoft 365microsoft_3650, 3002, 3006, 3007, 4009, 6003, 6006
Microsoft Entra ID sign-in logsazure_signin3002
Slack access logsslack_access, slack_access_log0, 3002
Slack audit logslack_audit0, 3002, 3006, 3007, 6003

Identity, email and security tools

Sourcemetadata.log_sourceOCSF classes
1Passwordonepassword0, 3002, 3006, 3007, 6003
Auth0auth00, 3002, 3007, 6003
Cisco Duoduo0, 3002, 3006, 3007, 6003
CyberArk PAMcyberark0, 3002, 3006, 3007, 6003
F5 BIG-IP ASMf5_waf4002
Mimecastmimecast0, 4009
Netskopenetskope, netskope_* streams0, 2004, 4001, 4002, 6003
Oktaokta0, 3002, 3006, 3007, 6003
Proofpointproofpoint0, 4009
Qualys VMDRqualys0, 2004
Rapid7 InsightVMrapid7_insightvm0, 2004
Suricatasuricata2004, 4001, 4002, 4003, 4004

Applications

Sourcemetadata.log_sourceOCSF classes
Apache HTTP Serverapache_access0, 4002
Nginxnginx0, 4002
OpenTelemetry logsotlp_log6003; 0 without this parser (see above)

Host

Sourcemetadata.log_sourceOCSF classes
systemd-journaldlinux_journald0, 3002, 4001

Generic

Sourcemetadata.log_sourceOCSF classes
Generic JSONjson_generic0, 4001, 4002
Generic syslogsyslog0, 3002, 4001

Sources without a catalog parser

  • Send JSON with the Generic JSON source (json_generic), or syslog lines with Generic syslog (syslog). Both produce OCSF events; fields that don't map are kept under unmapped, and the original line is kept in raw_data.
  • Or write a parser for the source. See Parser extensions.

What's next

On this page