RousselTMLEARNING

TP · Cribl: from discovery to expertise

Final lab: replay, ship as a Pack and validate production

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. 1. S3 collector

    Why? The path mirrors the archive partitioning: only the useful partitions are read.

    On the Lab 3 instance, create an S3 collector coll_archive (endpoint http://minio:9000, bucket archive, same keys) with the path below, and check it with Preview.
  2. 2. Replay

    Why? Only the investigation's address and period are re-injected.

    Add a replay_siem route at the top (filter replayed==true, pipeline passthru, out_siem, Final). Run Run › Ad hoc over the last hour with the filter below and count the received events.
  3. 3. Package as a Pack

    Why? A versioned Pack ships identically to staging then production.

    Create the fw_reduce Pack, copy the pl_fw_reduce pipeline into it with a sample, export it, then replace the pipeline in the fw_siem route with the Pack.
  4. 4. 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 to out_files. Create a “source silent for 5 minutes” notification on in_syslog and test it by stopping the sending.
  5. 5. 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).

Difficulty level : ●●●●○ (4/5)

My progress

  • ⏱ Estimated time : ≈ 1 h 30

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.

Ask a question about this lesson →

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...

Support us

♥ SUPPORT US

Support RousselTM Learning

Courses, articles, labs and certificates stay free with no intrusive ads. A voluntary contribution, of any amount you choose, pays for hosting, lab environments and new content.

Contribute with PayPal Any amount · card or PayPal accountLearn more
QR code PayPal
Or scan this QR code with your phone

Thank you, every contribution counts!