Skip to content
I—AboutII—ExperienceIII—WorksIV—StackV—AlbumsVI—WritingVII—Contact
FR|EN

BAHOMDA

WEN’SAA GRÉGOIRE

Cybersecurity — Security Operations · Penetration Testing · Infrastructure Management

Handle · ROGUE/r06u3

  • About
  • Experience
  • Works
  • Stack
  • Albums
  • Writing
  • Contact

Contact

gregoire.bahomda@proton.me
LinkedInGitHub
Language|FR|EN

© 2026 BAHOMDA Wen’Saa Grégoire. All rights reserved.

← 02 — Works

Security Operations · Professional

Security Operations Center — Detection and incident response

A security incident management and response cell: Wazuh for detection, Shuffle for automation, TheHive and Cortex for cases and enrichment.

Nature
Professional
Since 2025
Technologies
Wazuh · Shuffle · TheHive · Cortex · FortiGate · pfSense
Links
GitHub
Context

Building a Security Operations Center around Wazuh, Shuffle, TheHive and Cortex. FortiGate provides primary perimeter filtering, pfSense the secondary layer.

Problem

An isolated alert does not produce a response: without correlation, triage and traceability, a security event remains a signal.

Objective

Connect telemetry to a documented decision: detect, triage, investigate, contain and close.

Approach
  1. 01Deployed Wazuh (manager, indexer, dashboard) and enrolled log sources.
  2. 02Wrote and tuned detection rules while reducing noise.
  3. 03Automated notifications and first-level actions with Shuffle.
  4. 04Managed cases, observables and tasks in TheHive.
  5. 05Enriched observables with Cortex.
  6. 06Perimeter filtering and logging: FortiGate as primary, pfSense as secondary.
Architecture

Sources → Wazuh → Shuffle → TheHive (+ Cortex) → analyst. FortiGate and pfSense at the network edge.

Outcome

A complete chain: an event produces a triaged alert, opens a case in TheHive and triggers the defined notifications.