Search Security Data with Logs
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.
Use Logs to search your security data without leaving Cribl Detect. Hunt for activity across your events, check what a detection would match, or look at the source events behind a finding.
Logs reuses the Cribl Search query box, including Kusto Query Language (KQL) support, autocomplete, and query history. Search results open in the Cribl Detect event viewer, so you keep the Cribl Detect sidebar and can return to your detections and alerts.
Open Logs
In the Cribl Detect sidebar, select Logs.
Search Security Data
Cribl Detect stores security data in the Datasets on the lakehouse engine that you
linked. You can query only Datasets for which your Role grants DatasetRead
access. These are the most useful Datasets to start with:
| Dataset | What to search for |
|---|---|
sec_ocsf_original_events | Ingested events, normalized to OCSF, with the original event preserved. |
sec_ocsf_detection_signals | Findings that your detections produced. |
For example, to review the latest findings:
dataset="sec_ocsf_detection_signals" | limit 10For the full list of security Datasets, see What Linking Creates. For field names, see About Event Data and Schema Normalization.
KQL Reference
For KQL operators and functions, see the Cribl Search KQL Reference.