About Event Data and Schema Normalization
Preview Feature
Cribl is still developing this Preview feature. We don’t recommend using it in a production environment, because the feature might not be fully tested or optimized for performance, and related documentation could be incomplete.
Access requires App Platform, the Cribl Detect feature, and a Role that grants
Apps.Readaccess to the Cribl Detect app.Please continue to submit feedback through normal Cribl support channels, but assistance might be limited while the feature remains in Preview.
Cribl Detect prepares security data before detections evaluate it. After you enable Cribl Detect and the engine configuration is available, Open Cybersecurity Schema Framework (OCSF) normalization runs in the lakehouse engine dedicated to Cribl Detect, with curated OCSF pipelines for priority sources. Cribl Detect keeps the original (raw) event. Detections, findings, and investigations use that prepared data.
In the Cribl Detect experience, you don’t need to create the normalization pipeline yourself. Cribl Detect ships the normalization path using the lakehouse engine. Custom Cribl Stream Pipelines are for gaps or customization. See Get Started to choose a lakehouse engine and connect Sources.
OCSF Normalization
OCSF is a standard event schema. Cribl Detect writes events in that shape so single-event and correlation detections can use the same field names across sources.
Single-event detections evaluate eligible events in the Cribl Search processing pipeline before storage. When a detection matches, Cribl Stream emits a finding and an OCSF-structured copy of the event. Correlation detections evaluate stored OCSF data. See Cribl Detect Concepts and Cribl Detect Architecture.
Events without a curated mapping are stored as OCSF base events. Detections that expect specific OCSF fields work best with mapped events.
Send Data Already Mapped to OCSF
If you already map a Source to OCSF in a Cribl Stream Pipeline or upstream of Cribl, you can send those events
as they are. Cribl Detect recognizes an event as pre-mapped OCSF when the event has a class_uid in its parsed_event
object, or when _raw contains a JSON object with a class_uid. It passes these events through to detection without
parsing them again. Cribl Detect doesn’t check metadata.version when it recognizes pre-mapped OCSF events.
Raw Event Retention
Cribl Detect retains the raw event for threat hunting, triage, and investigation. The _raw field of each record in
sec_ocsf_original_events stores the original event. Detections evaluate the normalized OCSF record. Findings and the OCSF
event copies land in the lakehouse engine dedicated to Cribl Detect. See
Lakehouse Engines in Cribl Search.
Access to each Dataset depends on the DatasetRead share assigned to the
user.
Findings Schema
Findings follow the OCSF 1.8.0 Detection Finding class. Each finding records the
product associated with the triggering event in finding_info.data_sources,
such as Okta or CrowdStrike Falcon. This value identifies the source of a
finding without requiring you to open the source event.
Connect Data Sources
Connect security data through Cribl Search Sources, then use Dataset rules to route the data to a Dataset on the linked engine. See Connect Your Sources. You can also forward data from Cribl Stream. For pre-mapped events, see Send Data Already Mapped to OCSF.
Templates use event readiness to show whether the events a template needs are available.
For available Cribl Search Sources, see Get Data In. For the full Cribl Stream Source catalog, see Sources.
Next Steps
- Enrich Event Data: Add context that detections can use.
- Threat Feeds: Use threat intelligence in detection workflows.
- Cribl Detect Architecture: Follow the data path after events are prepared.
- Browse Detection Templates: Check Event Readiness before you create a detection.