Get Started
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.
Set up Cribl Detect by following this process in order. Each step depends on the one before it. You can’t link a lakehouse engine until it finishes provisioning, and no events reach Cribl Detect until both a Source and a Dataset rule are in place.
Setup at a Glance
| Process | Action | Where | Completion Criteria |
|---|---|---|---|
| 1. Open Cribl Detect | Find the product and the Detect Home screen. If your Organization has no lakehouse engine, select Create an Engine to Start. Otherwise, select Select Lakehouse Engine. | Products in Cribl.Cloud | N/A |
| 2. Choose or Create a Lakehouse Engine | Create one, or select an existing one | Cribl Detect Detect Home screen | Engine status Ready |
| 3. Link the Lakehouse Engine | Bind the lakehouse engine to Cribl Detect | Cribl Detect Detect Home screen | All link steps, then engine Ready |
| 4. Connect Your Sources | Send security data to the linked engine | Cribl Search Get Data In | First events arriving |
| 5. Add Dataset Rules | Route the events into the linked engine | Cribl Search Get Data In | Events landing in the target Search Dataset |
| 6. Verify Events Are Flowing | Query the security Datasets that are created by linking a lakehouse engine | Cribl Search | Results from sec_ocsf_original_events |
| 7. Enable Your First Detection | Create a detection from a template | Cribl Detect Detections | First finding and, for an alerting detection, an alert |
| 8. Add Enrichment and Threat Feeds | Add context and indicators of compromise | Cribl Detect Enrichment and Threat Feeds | Optional. Add them once events are flowing |
| 9. Respond to Security Findings | Review findings and inspect an alert | Cribl Detect alerts | Alert details to investigate |
Steps 4. Connect Your Sources and 5. Add Dataset Rules are critical and you must not skip them. Linking an engine sets up the security data path, but Cribl Detect won’t receive any events until a Source sends data and a Dataset rule routes that data into the linked engine.
Before You Start
Ensure you meet the following requirements:
| Requirement | Reason |
|---|---|
| A Cribl.Cloud Organization | Cribl Detect runs in Cribl.Cloud alongside Cribl Stream, Cribl Search, and Cribl Lake. |
| Access to the Cribl Detect app | Your Role must grant Apps.Read access to __cribl_security. |
| Permissions to configure the data path | Cribl Search must be available, and your Role must grant LocalSearchSources.Create, DatatypeRulesets.Create, and DatasetRulesets.Create to configure the Get Data In stages. |
| Security data to send | Any Source that Cribl Search can receive, or data forwarded from Cribl Stream or Cribl Edge. |
You don’t need to build an OCSF normalization Pipeline, create the security Datasets, or install a Pack by hand. Linking an engine does all of that for you. See What Linking Creates.
If Cribl Detect doesn’t appear in your Organization, verify that the product is available in your deployment and that you have access to the app.
Open Cribl Detect
On the Cribl.Cloud top bar, select Products > Cribl Detect.
Until you link an engine, Cribl Detect shows its setup screen (Detect Home in the sidebar) instead of the product. What you see depends on whether your Organization already has lakehouse engines.
| Your Organization | Buttons on Detect Home |
|---|---|
| Has no lakehouse engine | Create an Engine to Start and Connect your Sources |
| Has at least one lakehouse engine | Select Lakehouse Engine and Connect your Sources |
If the screen shows an error and a Retry button, Cribl Detect couldn’t reach Cribl Search to read your engines. Select Retry.
Choose or Create a Lakehouse Engine
A lakehouse engine is the storage and compute unit that ingests your security data, stores it, and answers searches over it. Cribl Detect needs one engine dedicated to security data.
Choose one of the following:
- Use an existing engine: Select Select Lakehouse Engine, then skip to Link the Engine. Select an engine whose ingest limit and retention you’re willing to share with security data.
- Create a new engine: Follow the steps in Create a Lakehouse Engine. This is the recommended path, because security data then gets its own ingest limit, retention, and cost line.
Create a Lakehouse Engine
On the Cribl Detect setup screen, select Create an Engine to Start. If your Organization already has engines, select Select Lakehouse Engine, then Create new Lakehouse Engine.
In the New Engine dialog, complete the fields:
Field What to enter ID Required. Enter up to 20 letters, numbers, or underscores. You can’t change the ID later, and mainis reserved.Description Optional. Enter a description of what the engine is for so other admins don’t repurpose it. Engine Size Required. Select a size that covers your daily security volume with some headroom. The default is XSmall, and you can resize the engine later. Select Save.
For the size-to-volume table and how engines are billed, see Lakehouse Engine Sizing.
Wait for the Lakehouse Engine to Provision
Cribl Detect confirms that provisioning started. Select Done to close the dialog. Provisioning takes several minutes, and you can’t link the engine until it reports Ready.
Check progress in either Cribl Detect or Cribl Search:
- In Cribl Detect, select Select Lakehouse Engine. Engines that aren’t ready list
their status in parentheses, such as
security_prod (provisioning), and you can’t select them. - In Cribl Search, select Products > Search > Data > Engines, then read the Status column.
| Engine status | What it means | What to do |
|---|---|---|
| Provisioning | Cribl is setting the engine up. | Wait. |
| Delayed | Setup is taking longer than the few minutes expected. | Keep waiting. If the status does not move to Ready or Failed, contact Support. |
| Ready | The engine is operational. | Continue to Link the Engine. |
| Failed | The engine hit an unrecoverable error. | Contact Support, and create a new engine. |
For all statuses, see Check Lakehouse Engine Status.
Link the Engine
Linking turns a lakehouse engine into the Cribl Detect data path.
- Go to Products > Cribl Detect.
- Select Select Lakehouse Engine.
- Select your engine from the drop-down. Only engines in the Ready state are selectable.
Cribl Detect then runs the link workflow and reports each step as it goes:
- Checking engine and datasets.
- Creating security datasets.
- Preparing the security pack.
- Attaching the security pipeline.
- Verifying the security pipeline.
- Saving configuration.
- Refreshing the engine.
Leave the page open until the workflow finishes.
The last step restarts the lakehouse engine. It remains listed but is temporarily unavailable while its status changes from Ready; after a few minutes, it returns to Ready.
When linking finishes, the setup screen shows the engine with a Ready badge. If linking finishes with a caveat, the badge displays Linked instead. The only remaining action is Connect your Sources. To confirm the link later, open Config in Cribl Detect. See Configure Cribl Detect.
What Linking Creates
Linking creates these Search Datasets on the engine you selected:
| Dataset | Holds | Retention |
|---|---|---|
sec_ocsf_original_events | Every ingested event, normalized to OCSF, with the original preserved. | 10 years |
sec_ocsf_detection_signals | Findings that detections produce. | 10 years |
sec_ocsf_detection_alerts | Alerts raised from findings, including the effects of alert suppression. | 10 years |
sec_ocsf_detection_dq | Data-quality records for events that couldn’t be processed. | 90 days |
sec_signals_last_sent | Bookkeeping for Notification delivery. | 1 day |
sec_event_inventory | A rolling inventory of the event types seen, which powers Event Readiness in templates. | 7 days |
sec_ai_triages | AI triage decisions for alerts. | 10 years |
sec_ai_triage_results | AI triage results for alerts. | 10 years |
Linking also installs the security Pack and attaches it to the engine. Because the Pack is attached at the engine, you don’t route events to it yourself. Everything that engine ingests is normalized to OCSF and enriched. Single-event detections evaluate eligible events in the Cribl Search processing pipeline before storage. Correlation detections run after storage against lakehouse engine data.
Cribl Detect manages these Datasets and the Pack, so don’t rename or re-target them. Cribl Search reserves the security Dataset names for Cribl Detect: you can’t create a Dataset with one of these names, or clear or delete these Datasets yourself. To remove them, unlink the engine from Config in Cribl Detect. See Manage the Engine Link.
Cribl Detect has app-level access to all eight security Datasets. Each user’s DatasetRead shares determine which Datasets
they can access in Cribl Search. See Share Datasets.
If linking fails, Cribl Detect displays the reason for failure and removes the security Datasets, Pack, and Pipeline attachment it created during the link attempt. Cribl Detect won’t change the lakehouse engine itself or any pre-existing configuration.
Connect Your Sources
Next, send security data to the engine you linked.
- In Cribl Detect, select Connect your Sources, which opens the Get Data In tab in Cribl Search. You can also select Products > Search > Data > Get Data In > 1. Sources.
- Add a Source for each system whose security data you want Cribl Detect to
evaluate:
Where your data is now Source to use Cribl Stream or Cribl Edge already has it Cribl HTTP. Every new engine ships with a default in_cribl_httpSource.Syslog senders such as network devices or Linux hosts Syslog Windows event forwarding Windows Event Forwarder Splunk forwarders or HEC senders Splunk HEC, Splunk TCP Anything that can POST events over HTTP Raw HTTP
Each Source lists its endpoint, plus Events in and Bytes in counters. Those counters are the fastest way to tell whether data is arriving. To test the path without a real sender, see Send Sample Data to a Lakehouse Engine.
Cribl Detect ships curated OCSF mappings for priority Sources, described in Connect Data Sources. Events from a Source without a curated mapping are still stored and searchable. Cribl Detect wraps them as an OCSF base event, so you can add a mapping later without losing the data.
For the full catalog and per-Source settings, see Sources.
Add Dataset Rules
A Source accepts events. A Dataset rule decides which Search Dataset each event lands in, and therefore which engine ingests it. This step connects your Sources to Cribl Detect.
If you don’t already have a Search Dataset on the linked engine, add one. Select Products > Search > Data > Datasets > Add Dataset, set Engine to the engine you linked, and set a retention period. See Create Search Datasets.
Select Products > Search > Data > Get Data In > 3. Dataset Rules.
Select Add Dataset Rule, then name and describe the rule.
In Kusto expression to match, use the Kusto expression to define the events you want Cribl Detect to evaluate. Match on the Source, the Datatype, or both:
__inputId = "syslog:security_syslog"datatype = "syslog_rfc3164" and __inputId = "syslog:security_syslog"In Send data to, choose a Search Dataset on the engine you linked to Cribl Detect.
Toggle on Enabled, then confirm with Add.
Rules are evaluated top-down and the first match wins, so put specific rules above broad ones. For expression syntax and more examples, see Organize Data with Dataset Rules.
Events that match no Dataset rule fall back to the catch-all main Dataset,
which lives on the first lakehouse engine in your Organization. If that isn’t the
engine you linked to Cribl Detect, those events never reach Cribl Detect.
Dataset rules apply to events as they arrive, and aren’t retroactive. Events that arrived before the rule existed stay in the Search Dataset they were written to.
The required data path is:
Source → Dataset rule → Cribl Detect-linked Search Dataset → OCSF normalization/enrichment → Cribl Detect
Verify Events Are Flowing
Check the path in two places, in this order.
Confirm events are arriving at the Source. Select Products > Search > Data > Get Data In, then select Live Data to sample what’s coming in. See View Live Data.
Confirm events reached Cribl Detect. Select Products > Search, then run:
dataset="sec_ocsf_original_events" | limit 10
Results mean the whole path works. Your Source received the events, a Dataset rule routed them into the linked engine, and Cribl Detect normalized them to OCSF.
After you enable detections, verify that they’re working with this query:
dataset="sec_ocsf_detection_signals" | limit 10Enable Your First Detection
Events alone don’t produce findings; you have to enable a detection.
- In Cribl Detect, select Detections > Templates.
- Check Event Readiness on a template to see whether your data supports it. Observed means the events the template needs are already arriving.
- Select a detection, then select Create in the flyout window.
- On Review, turn on Enable detection. See Browse Detection Templates for more details.
From there, you can generate detections from a CVE in Detection Lab, Create a Custom Detection, and manage what you’ve created in Inventory.
Add Enrichment and Threat Feeds
Enrichment and threat feeds are both optional, and both make detections sharper. Add them once events are flowing.
Use Enrich Event Data to add context that detections can evaluate with event data. The most common enrichment provider is CSV. Add an Enrichment Provider, then Add an Enrichment Rule.
Use Threat Feeds to load indicators of compromise into the threat_intel lookup. Add feeds from the
catalog or My Feeds, connect an API source on Services, then sync.
Respond to Security Findings
When a detection matches, it stores a finding. One or more findings can create an alert. Review the alert details and related findings to investigate the activity. See Findings and Alerts and Notifications.
Troubleshooting
| What you see | Cause | Fix |
|---|---|---|
Your engine is greyed out in the drop-down, with a status such as (provisioning) | The engine isn’t Ready yet. | Wait for provisioning to finish. |
Engine '<id>' is not ready (current status: '<status>') | You tried to link an engine that’s still provisioning, resizing, or recovering. | Wait until Cribl Search reports Ready, then link again. |
Engine already linked. Unlink first. | Cribl Detect links one engine per Organization. | To move to a different engine, unlink the current one, then link the new one from Config. |
Dataset '<name>' already exists on engine '<other>'. Cannot link to '<id>'. | Security Datasets from an earlier link still live on another engine. | Link that engine instead. |
sec_ocsf_original_events stays empty | No Source is sending data, or no Dataset rule routes it to the linked engine. | Check the Source counters, then review your Dataset rules. |
Next Steps
- About Cribl Detect: What Cribl Detect does and how it fits in the Cribl suite.
- Prepare Data: Normalize data and add security context.
- Detections: Create and manage detection rules.
- Respond to Findings: Investigate detected activity and route alerts.
- Cribl Detect Concepts: Detections, findings, alerts, and Notifications.