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

Installing and administering Cribl Stream

Installing Cribl Stream with Docker or on Linux, running it as a service, understanding $CRIBL_HO...

Cribl Edge: collecting close to the sources

Deploying Cribl Edge on Linux, Windows and Kubernetes: the agent's role, Fleets and Subfleets, co...

Pipelines and functions: parse, enrich, mask

Building Cribl Stream pipelines: pre-processing, processing and post-processing, the function cat...

Elastic Security: SIEM, detection rules and investigation

Use Elastic Security as a SIEM: ECS data sources, detection rule types (query, EQL, ES|QL, thresh...

Testing and securing Terraform: validate, terraform test, tflint, Checkov and policies

Ensure the quality of Terraform code: fmt and validate, native terraform test tests with mocked p...

RUM and Synthetic Monitoring with Datadog: synthetic transaction monitoring and user experience

Measure user experience with Datadog: browser and mobile RUM, Core Web Vitals, Session Replay, li...

Installing and deploying ClickStack: all-in-one, Docker Compose, Helm and Managed ClickStack

Deploying ClickStack to fit the need: all-in-one container with persistence, Docker Compose and i...

Logstash in production: persistent queues, DLQ and multiple pipelines

Make Logstash reliable in production: persistent queue, dead letter queue, multiple pipelines and...

Dynatrace: GDPR and data privacy

Learn how to configure Dynatrace to comply with the GDPR, mask sensitive data and enable the coll...

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!