<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Nmosi Chinecherem</title>
    <description>The latest articles on DEV Community by Nmosi Chinecherem (@nmosic).</description>
    <link>https://dev.to/nmosic</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3895757%2F486b15f2-0220-4aae-8d85-e007c63e41d4.jpg</url>
      <title>DEV Community: Nmosi Chinecherem</title>
      <link>https://dev.to/nmosic</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nmosic"/>
    <language>en</language>
    <item>
      <title>I Built a Production SOC Pipeline That Caught Real Hackers in 3 Minutes</title>
      <dc:creator>Nmosi Chinecherem</dc:creator>
      <pubDate>Fri, 24 Apr 2026 09:53:25 +0000</pubDate>
      <link>https://dev.to/nmosic/i-built-a-production-soc-pipeline-that-caught-real-hackers-in-3-minutes-1a17</link>
      <guid>https://dev.to/nmosic/i-built-a-production-soc-pipeline-that-caught-real-hackers-in-3-minutes-1a17</guid>
      <description>&lt;p&gt;How I went from zero to a full threat detection and response system using OpenCanary, Wazuh, Shuffle, and TheHive — and what happened when I turned it on.&lt;/p&gt;

&lt;p&gt;The Problem I Was Trying to Solve&lt;br&gt;
I've been studying cybersecurity for years, reading about SOC pipelines, SIEM platforms, and incident response workflows. But there's a massive gap between reading about something and actually building it.&lt;br&gt;
I wanted to build a real Security Operations Centre pipeline — not a lab with simulated attacks, but something that would face the actual internet and catch real threats. Something I could point to and say: "I built this, it works, and here's the proof."&lt;br&gt;
So I built one.&lt;/p&gt;

&lt;p&gt;What I Built&lt;br&gt;
A complete, end-to-end SOC pipeline consisting of four components working together:&lt;br&gt;
Internet → OpenCanary Honeypot → Wazuh SIEM → Shuffle SOAR → TheHive IR&lt;br&gt;
OpenCanary — A honeypot that pretends to be a vulnerable server, running fake SSH, FTP, HTTP, and Telnet services. Attackers think they've found a real target.&lt;br&gt;
Wazuh — A SIEM that collects logs from the honeypot, applies custom detection rules, and fires high-priority alerts when attackers interact with the honeypot.&lt;br&gt;
Shuffle — A SOAR platform that receives Wazuh alerts via webhook and automatically routes them to TheHive for case management.&lt;br&gt;
TheHive — An incident response platform that creates structured cases from every alert, ready for analyst investigation.&lt;/p&gt;

&lt;p&gt;The Architecture&lt;br&gt;
Each component runs on its own server:&lt;br&gt;
ComponentRoleOpenCanary 0.9.7HoneypotWazuh 4.9.2SIEM + DetectionShuffleSOAR AutomationTheHive 5.5.14Incident Response&lt;br&gt;
The data flow is fully automated. When an attacker hits the honeypot, within seconds a structured incident case is created in TheHive — no human intervention required.&lt;/p&gt;

&lt;p&gt;What Happened When I Turned It On&lt;br&gt;
This is the part that surprised me.&lt;br&gt;
Within 3 minutes of deploying the honeypot, a real attacker from IP 105.127.14.91 connected to the fake SSH service and attempted to log in with:&lt;br&gt;
json{&lt;br&gt;
  "USERNAME": "root",&lt;br&gt;
  "PASSWORD": "ella1Mootie",&lt;br&gt;
  "src_host": "105.127.14.91",&lt;br&gt;
  "logtype": 4002&lt;br&gt;
}&lt;br&gt;
Within hours, dozens of attackers from across the world were hitting the honeypot. I captured credentials like 888888, 87654321, wsx33, and Abc123... — real passwords people use in brute force attacks.&lt;br&gt;
The Wazuh rule I wrote fired at level 15 (the highest priority) for every SSH brute force attempt, and Shuffle automatically processed each alert.&lt;br&gt;
This wasn't a simulation. These were real attackers, real credentials, real threat intelligence.&lt;/p&gt;

&lt;p&gt;How I Built It&lt;br&gt;
Step 1: The Honeypot (OpenCanary)&lt;br&gt;
OpenCanary is lightweight, runs on Python, and supports over a dozen fake services. I installed it on Ubuntu 22.04 and configured it to listen on ports 22 (SSH), 21 (FTP), 80 (HTTP), and 23 (Telnet).&lt;br&gt;
The key insight: move the real SSH service to port 2222, and put the honeypot on port 22. Any attacker scanning the internet will hit the honeypot first.&lt;br&gt;
json{&lt;br&gt;
  "ssh.enabled": true,&lt;br&gt;
  "ssh.port": 22,&lt;br&gt;
  "ftp.enabled": true,&lt;br&gt;
  "http.enabled": true,&lt;br&gt;
  "telnet.enabled": true,&lt;br&gt;
  "logger": {&lt;br&gt;
    "class": "PyLogger",&lt;br&gt;
    "kwargs": {&lt;br&gt;
      "handlers": {&lt;br&gt;
        "file": {&lt;br&gt;
          "class": "logging.FileHandler",&lt;br&gt;
          "filename": "/var/log/opencanary/opencanary.log"&lt;br&gt;
        }&lt;br&gt;
      }&lt;br&gt;
    }&lt;br&gt;
  }&lt;br&gt;
}&lt;br&gt;
Step 2: Custom Wazuh Detection Rules&lt;br&gt;
I wrote four custom rules to detect and classify honeypot interactions:&lt;br&gt;
xml&lt;br&gt;
  &lt;br&gt;
    json&lt;br&gt;
    opencanary&lt;br&gt;
    OpenCanary: Honeypot interaction detected&lt;br&gt;
  &lt;/p&gt;

&lt;p&gt;&lt;br&gt;
    100200&lt;br&gt;
    ^4002$&lt;br&gt;
    OpenCanary: SSH brute force login attempt on honeypot&lt;br&gt;
  &lt;br&gt;
&lt;br&gt;
Rule 100201 fires at level 15 — the maximum — because any login attempt on a honeypot is by definition malicious. There are no false positives.&lt;br&gt;
Step 3: Automated Alert Routing with Shuffle&lt;br&gt;
I configured Wazuh to send all level 7+ alerts to a Shuffle webhook. Shuffle then processes each alert and forwards it to TheHive's API as a structured alert.&lt;br&gt;
The Wazuh integration block:&lt;br&gt;
xml&lt;br&gt;
  shuffle&lt;br&gt;
  &lt;a href="http://YOUR_SHUFFLE_IP:3001/api/v1/hooks/YOUR_WEBHOOK_ID" rel="noopener noreferrer"&gt;http://YOUR_SHUFFLE_IP:3001/api/v1/hooks/YOUR_WEBHOOK_ID&lt;/a&gt;&lt;br&gt;
  7&lt;br&gt;
  json&lt;br&gt;
&lt;br&gt;
Step 4: TheHive for Incident Response&lt;br&gt;
TheHive receives structured alerts with full context — attacker IP, username attempted, password used, timestamp, and the originating agent. Each alert becomes a case that analysts can investigate, assign, and close.&lt;/p&gt;

&lt;p&gt;What I Learned&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The internet is hostile by default.
Within minutes of exposing any service to the internet, automated scanners find it. The speed and scale of internet-wide scanning is remarkable.&lt;/li&gt;
&lt;li&gt;Honeypots generate high-fidelity intelligence.
Unlike SIEM alerts that often have false positives, honeypot alerts are almost always genuine. Nobody has a legitimate reason to connect to a honeypot.&lt;/li&gt;
&lt;li&gt;Automation is not optional in a modern SOC.
When you're receiving hundreds of alerts per day, manual triage is impossible. The Wazuh → Shuffle → TheHive pipeline processes every alert automatically, ensuring nothing is missed.&lt;/li&gt;
&lt;li&gt;Building is better than reading.
I learned more about SOC architecture in the process of building this pipeline than I did in months of studying. There is no substitute for hands-on experience.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The Full Stack&lt;br&gt;
All configuration files, custom rules, and integration scripts are available on GitHub:&lt;br&gt;
github.com/agunna99/soc-honeypot-pipeline&lt;br&gt;
The repository includes:&lt;/p&gt;

&lt;p&gt;OpenCanary configuration&lt;br&gt;
Custom Wazuh detection rules&lt;br&gt;
TheHive integration script&lt;br&gt;
Shuffle workflow setup guide&lt;/p&gt;

&lt;p&gt;What's Next&lt;/p&gt;

&lt;p&gt;Adding IP enrichment using threat intelligence feeds (VirusTotal, AbuseIPDB)&lt;br&gt;
Implementing automated IP blocking when attackers are detected&lt;br&gt;
Adding email/Slack notifications for critical alerts&lt;br&gt;
Publishing threat intelligence reports from captured attack data&lt;/p&gt;

&lt;p&gt;Final Thoughts&lt;br&gt;
Building a production SOC pipeline from scratch taught me that security is not just about tools — it's about architecture, data flow, and automation. Every component in this pipeline serves a specific purpose, and together they create something more powerful than any individual tool.&lt;br&gt;
If you're learning cybersecurity, build things. Deploy them. See what happens. The internet will teach you things no course or textbook can.&lt;br&gt;
The code is open source. Use it, improve it, and share what you build.&lt;/p&gt;

&lt;p&gt;Favour Nmosi is a cybersecurity engineer building open-source security tools.&lt;br&gt;
GitHub: github.com/agunna99&lt;/p&gt;

&lt;p&gt;Tags: #cybersecurity #soc #honeypot #wazuh #thehive #shuffle #siem #soar #opencanary #infosec #security&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
