<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel>
  <title>Nadim Saliby · Security Researcher</title>
  <link>https://blog.nadimjsaliby.com</link>
  <description>Field notes on DevSecOps and cybersecurity.</description>
  <item>
    <title>Registry as a Sensor: Wiring Harbor and Trivy into Wazuh, with a Wolfi Agent to Prove It</title>
    <link>https://blog.nadimjsaliby.com/posts/wazuh-harbor-registry-supply-chain.html</link>
    <guid>https://blog.nadimjsaliby.com/posts/wazuh-harbor-registry-supply-chain.html</guid>
    <pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
    <description>A Harbor→Wazuh webhook bridge, a 25-rule supply-chain detection pack with three correlation chains (vulnerable image deployed, unscanned image deployed, already-deployed image found vulnerable), and a Wazuh agent rebuilt from source on Wolfi that scored 0 CVEs against the official manager image&#x27;s 567. Validated live on Wazuh 4.14.5: 23 of 25 rules fire from one script, 40 alerts.</description>
  </item>
  <item>
    <title>Wazuh on K8s: 7 Frameworks, Auto-Remediation, One Chart</title>
    <link>https://blog.nadimjsaliby.com/posts/wazuh-k8s-hardening-multi-framework-compliance.html</link>
    <guid>https://blog.nadimjsaliby.com/posts/wazuh-k8s-hardening-multi-framework-compliance.html</guid>
    <pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate>
    <description>An open-source Helm chart that wraps Wazuh agents with Kubernetes-native enforcement: CIS, NIST 800-53, PCI-DSS, HIPAA, SOC2, MITRE ATT&amp;CK runtime detection, admission webhook, and a remediation CronJob: all from one deploy.</description>
  </item>
  <item>
    <title>Closing the Kernel-Level Gap in Wazuh: an eBPF Sidecar with Tetragon</title>
    <link>https://blog.nadimjsaliby.com/posts/wazuh-ebpf-tetragon-kernel-detection.html</link>
    <guid>https://blog.nadimjsaliby.com/posts/wazuh-ebpf-tetragon-kernel-detection.html</guid>
    <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
    <description>A custom Wazuh rule pack and reproducible Docker lab that pairs a stock Wazuh agent with a Tetragon eBPF sidecar to catch what stock Wazuh cannot: short-lived process exec, fileless memfd payloads, sub-second TCP connects, kernel module loads, bpf() syscall use, sensitive-file argv reads, setuid escalation. 1 decoder family, 15 rules, 4 distros, 1.59M events validated.</description>
  </item>
  <item>
    <title>Catching Shadow AI in the Network: DNS, Egress, and Browser Telemetry with Wazuh</title>
    <link>https://blog.nadimjsaliby.com/posts/wazuh-network-shadow-ai-detection.html</link>
    <guid>https://blog.nadimjsaliby.com/posts/wazuh-network-shadow-ai-detection.html</guid>
    <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
    <description>A custom Wazuh rule pack and reproducible Docker lab that catches browser-side shadow AI on developer endpoints: DNS lookups, TLS egress, extension manifests, and native messaging hosts. 4 decoders, 15 rules, MITRE ATT&amp;CK mapped, validated live on Wazuh 4.14.5.</description>
  </item>
  <item>
    <title>Detecting Rogue MCP Servers and Shadow AI Agents on Endpoints with Wazuh</title>
    <link>https://blog.nadimjsaliby.com/posts/wazuh-rogue-mcp-shadow-ai-detection.html</link>
    <guid>https://blog.nadimjsaliby.com/posts/wazuh-rogue-mcp-shadow-ai-detection.html</guid>
    <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
    <description>A custom Wazuh rule pack and reproducible Docker lab that catches rogue MCP servers, shadow AI agent activity, and indirect prompt-injection chains on engineering endpoints. 6 decoders, 17 rules, MITRE ATT&amp;CK mapped, validated live on Wazuh 4.14.5.</description>
  </item>
  <item>
    <title>Wazuh Migration: Missing Historical Alerts</title>
    <link>https://blog.nadimjsaliby.com/posts/wazuh-alerts-disappear-after-migration.html</link>
    <guid>https://blog.nadimjsaliby.com/posts/wazuh-alerts-disappear-after-migration.html</guid>
    <pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate>
    <description>What caused historical alerts to disappear from Wazuh dashboards after migration, and the safer reindex workflow that fixed it.</description>
  </item>
</channel></rss>
