Sanitized defensive engineering case studies

Security operations delivery that makes offensive findings actionable.

My primary track remains Offensive Security, VAPT, and Application Security. These projects demonstrate the supporting operational depth required to understand telemetry, detection coverage, investigation workflows, implementation constraints, and how security issues move from evidence to closure.

Defensive depth

Browser-viewable summaries with downloadable technical documentation.

Each summary focuses on the objective, controlled delivery process, validation approach, and operational value. Customer-specific assets, credentials, internal addresses, and restricted implementation details remain excluded.

01

SIEM / XDR validation lab

Wazuh 5 Beta SOC Lab for ISO 27001

An isolated validation environment used to assess beta capabilities, endpoint telemetry, agent coverage, certificates, and compliance-oriented behavior without introducing change risk to the stable SOC stack.

Wazuh 5SIEM / XDRDockerWindows / LinuxISO 27001

Objective

Evaluate a new Wazuh release and its compliance and telemetry capabilities in a controlled lab before considering broader operational use.

Delivery approach

  • Separated the beta environment from the stable SOC stack.
  • Validated certificates, agent connectivity, and ingestion behavior.
  • Onboarded representative Windows and Linux coverage.

Validation controls

  • Agent health and connectivity checks
  • Endpoint-telemetry ingestion verification
  • Compliance and platform behavior review

Operational value

Demonstrated disciplined change containment and evidence-based validation before production adoption, improving deployment confidence and reducing avoidable operational risk.

02

SIEM analytics & unified visibility

Wazuh + Grafana + Zabbix SOC Dashboard

A host-focused visibility workflow that correlated security events from Wazuh and OpenSearch with infrastructure-health information from Zabbix and Grafana.

WazuhOpenSearchGrafanaZabbixTelemetry

Objective

Reduce investigation friction by presenting security and availability signals in a shared operational view rather than requiring separate, disconnected checks.

Delivery approach

  • Used OpenSearch-backed Wazuh data for security-event visibility.
  • Mapped infrastructure-health context from Zabbix into Grafana.
  • Organized the dashboard around host-level investigation.

Validation controls

  • Confirmed security-event visibility
  • Checked host and availability signal alignment
  • Reviewed dashboard usefulness for investigation workflows

Operational value

Improved the analyst’s ability to compare endpoint, security, and infrastructure conditions during investigation and troubleshooting.

03

SIEM ingestion & log engineering

Firewall Syslog Ingestion into Wazuh 5

A network-security telemetry pipeline that moved firewall events through collection, Wazuh processing, and indexing so they became searchable and usable for investigation.

FirewallSyslogWazuhOpenSearchLog Pipeline

Objective

Establish reliable firewall-event visibility in the SIEM and ensure the full collector-to-engine-to-indexer path behaved as expected.

Delivery approach

  • Configured and reviewed the firewall-to-collector path.
  • Troubleshot processing and connector behavior.
  • Verified indexing and searchability of network events.

Validation controls

  • Collector receipt and event-format checks
  • Processing and data-stream verification
  • Search and investigation usability checks

Operational value

Created dependable network-event visibility that can support investigation, rule development, and correlation with endpoint or application-security activity.

04

SOAR-aligned workflow automation

Wazuh-to-GLPI Incident Orchestration

A custom alert-to-incident workflow that converted selected Wazuh alerts into controlled, deduplicated GLPI tickets with usable security context.

WazuhGLPISOAR-alignedDeduplicationITSM

Objective

Move high-value alerts into an accountable incident workflow while avoiding uncontrolled ticket duplication and excessive operational noise.

Delivery approach

  • Defined an alert-to-ticket integration flow.
  • Applied deduplication and controlled ticket-creation logic.
  • Preserved incident context for operational follow-up.

Validation controls

  • Confirmed eligible alerts created incidents
  • Checked duplicate-event handling
  • Reviewed ticket context and workflow consistency

Operational value

Established a repeatable SOAR-aligned path from detection to assigned operational work, improving traceability and reducing manual alert handling.

Evidence boundary

These pages intentionally provide recruiter-friendly summaries rather than customer-specific implementation records. Sensitive assets, credentials, internal topology, and restricted operational details remain excluded.

Offensive-first · Detection-informed

Looking for assessment depth with operational context?

I’m targeting VAPT, Penetration Testing, Application Security, Product Security, and Offensive Security roles where exploit validation, clear reporting, remediation coordination, and defensible closure matter.