On This Page

Home / Cribl Detect/ Prepare Data (Preview)/Cribl Detect Architecture

Cribl Detect Architecture ​

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.Read access 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 detections run in products you already operate, and findings land in storage you already use for search. Cribl Detect doesn’t introduce a separate data plane.

Components ​

Cribl Detect uses these Cribl Suite components:

ComponentRole
Cribl StreamOptionally acquires Pull Sources and processes incoming security data. When a single-event detection matches, Cribl Stream emits a finding and an OCSF-structured copy of the event.
Cribl EdgeForwards security data into the detection path.
Cribl SearchSingle-event detections evaluate eligible events in the Cribl Search processing pipeline before storage. After storage, Cribl Search runs correlation detections against lakehouse engine data and supports investigations of the source events behind an alert.
Cribl Search lakehouse engineA lakehouse engine dedicated to Cribl Detect stores findings and events.
Cribl InsightsMonitors operational health, such as Pipeline throughput and Node resources, separately from security detections.

You choose whether to create a single-event or correlation detection. Cribl Detect sends the enabled rule to the Cribl product that can evaluate it efficiently: single-event detections deploy to Cribl Stream, and correlation detections deploy to Cribl Search. See Detection Engines.

Data Path ​

  1. Cribl Search Sources receive security data. Cribl Stream can optionally acquire data from Pull Sources or process the data, and Cribl Edge can forward data into this path.
  2. Dataset rules route the data to a Dataset on the lakehouse engine linked to Cribl Detect.
  3. The processing Pipeline normalizes the data to OCSF and enriches it. Single-event detections evaluate eligible events in the Cribl Search processing pipeline before storage. A match emits a finding and an OCSF-structured event copy.
  4. Correlation detections run after storage against lakehouse engine data.
  5. Findings stay available for searching and for later detections.
  6. Alerts group findings that need investigation. Cribl Detect stores alerts in their own Dataset and applies any alert suppression configured on the detection. Cribl Detect sends Notifications when it creates an alert. Configure targets, templates, and policies in Cribl Detect under Alerts > Notifications.

The evaluate-and-store work runs in Cribl Stream, Cribl Search, and the lakehouse engine.

See Cribl Detect Concepts for object definitions and About Event Data and Schema Normalization for how events are shaped for detection.