The correction is integrated into the TP (See the green boxes)
What you will learn in this TP
- Create an S3 collector
- Replay a filtered period
- Create and export a Pack
- Monitor Cribl
- Validate the checklist
Introduction #
What you will learn in this section
- Create an S3 collector
- Replay a filtered period
- Create and export a Pack
- Monitor Cribl
- Validate the checklist
Context. A security incident requires finding all traffic from one address over the last hour, including what had been filtered. Right after, the platform must pass the go-live review.
Prerequisites: a machine with Docker and Docker Compose (4 GB free memory), curl and jq, the Lab 3 and 4 instances · Estimated time: 90 min
A targeted replay from the archive, an exported Pack, internal monitoring and a validated checklist.Setup #
Guided steps, with their solution.
1. S3 collector
Why? The path mirrors the archive partitioning: only the useful partitions are read.
On the Lab 3 instance, create an S3 collectorcoll_archive(endpointhttp://minio:9000, bucketarchive, same keys) with the path below, and check it with Preview.See the correction
Path: /${_time:%Y}/${_time:%m}/${_time:%d}/${_time:%H}/${sourcetype}/ Fields to add: replayed = true2. Replay
Why? Only the investigation's address and period are re-injected.
Add areplay_siemroute at the top (filterreplayed==true, pipelinepassthru,out_siem, Final). Run Run › Ad hoc over the last hour with the filter below and count the received events.See the correction
Collector filter: /src=10\.0\.3\.\d+/.test(_raw) # then docker logs --since 5m siem 2>&1 | grep -c 'replayed'3. Package as a Pack
Why? A versioned Pack ships identically to staging then production.
Create thefw_reducePack, copy thepl_fw_reducepipeline into it with a sample, export it, then replace the pipeline in thefw_siemroute with the Pack.See the correction
# Packs › Add Pack › Create Pack: id fw_reduce, version 1.0.0 # Copy pl_fw_reduce into the Pack, then Export › fw_reduce_1.0.0.crbl ls -lh ~/Downloads/fw_reduce_*.crbl # Import into another environment: Packs › Add Pack › Import from file4. Monitor Cribl
Why? If Cribl stops, the SIEM goes blind: you must know immediately.
Enable the Cribl Internal source (logs and metrics) and route it toout_files. Create a “source silent for 5 minutes” notification onin_syslogand test it by stopping the sending.See the correction
curl -s localhost:9000/api/v1/health | jq . zcat $(find $HOME/cribl-out -path '*cribl*' -name '*.json.gz' | head -1) | jq -c '{_metric: ._metric, level, channel}' | head -35. Checklist
Why? The review asks for evidence.
Gather one proof per line: full archive, replay tested, gain measured, no personal data on output, persistent queue tested (Lab 4), alert received, configuration in Git. Note what is still missing (TLS, SSO, remote Git).See the correction
git -C $HOME/cribl-config log --oneline | head -5 2>/dev/null || docker exec cribl git -C /opt/cribl/config-volume log --oneline | head -5 zcat $(find $HOME/cribl-out -name '*.json.gz') | grep -c '@exemple.fr' || echo '0 adresse en clair / clear address'
Difficulty level : ●●●●○ (4/5)
My progress
Sign in to track your progress and take notes. Sign in
💬 Questions about this lesson
No questions yet: be the first to ask for help or share your configuration.
Recommended Articles
Archiving, replaying and searching: S3, Replay, Cribl Lake and Cribl Search
Keeping all data cheaply and finding it on demand: partitioned S3 destination, JSON and Parquet f...
Automating Cribl: REST API, Packs, Git and Terraform
Managing Cribl as code: REST API (authentication, group paths, commit and deploy), reusable Packs...
Cribl Stream and Edge best practices
Best practices for running Cribl in production: route and pipeline design, naming, performance, c...
Reducing, transforming and optimizing volumes with Cribl
Reducing the volume sent to SIEMs and observability tools without losing useful information: Drop...
Cribl: the data pipeline for observability and security
Discover Cribl: why a telemetry data pipeline, the Cribl suite (Stream, Edge, Lake, Search, Cribl...
Cribl Stream in production: distributed architecture, persistent queues and monitoring
Taking Cribl Stream to production: Leader, Worker Groups and processes, commit and deploy, scalin...
Sources, destinations and routes in Cribl Stream
Receiving and sending data with Cribl Stream: push, pull, collector and internal sources, event b...
Bindplane best practices
Checklist for operating Bindplane: organizing by labels and fleets, measured reduction, masking a...
Capstone project: the four signals of the OpenTelemetry Demo in the Grafana stack
A capstone project spanning the observability courses: deploy the OpenTelemetry Demo, send metric...