<?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: Haningtone stirio</title>
    <description>The latest articles on DEV Community by Haningtone stirio (@haningtone).</description>
    <link>https://dev.to/haningtone</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%2F3915553%2F6a32a39c-cfa0-48ca-b1fa-c1f738d1a307.jpg</url>
      <title>DEV Community: Haningtone stirio</title>
      <link>https://dev.to/haningtone</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/haningtone"/>
    <language>en</language>
    <item>
      <title>Building a Production-Ready SOC Triage Tool with Python &amp; Streamlit</title>
      <dc:creator>Haningtone stirio</dc:creator>
      <pubDate>Wed, 06 May 2026 09:24:13 +0000</pubDate>
      <link>https://dev.to/haningtone/building-a-production-ready-soc-triage-tool-with-python-streamlit-5cjb</link>
      <guid>https://dev.to/haningtone/building-a-production-ready-soc-triage-tool-with-python-streamlit-5cjb</guid>
      <description>&lt;p&gt;&lt;strong&gt;Building a Production-Ready SOC Triage Tool with Python &amp;amp; Streamlit&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Live Demo:&lt;/strong&gt; (&lt;a href="https://hansec-soc-triage-threat-intelligence-3n25rk85kwfaho2luyss4v.streamlit.app/" rel="noopener noreferrer"&gt;https://hansec-soc-triage-threat-intelligence-3n25rk85kwfaho2luyss4v.streamlit.app/&lt;/a&gt;)  &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Problem That Needed Solving&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Every SOC analyst knows this pain:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Another alert? Let me grep the logs... copy the IP... open AbuseIPDB... manually check 50 IPs... create a ticket... repeat.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Manual log triage takes 5-10 minutes PER suspicious IP.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When you have 100+ IPs to investigate, that's &lt;strong&gt;8+ hours&lt;/strong&gt; of manual work.&lt;/p&gt;

&lt;p&gt;I built a solution that reduces this to &lt;strong&gt;30 seconds&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;What I Built&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SOC Triage &amp;amp; Threat Intelligence Automator&lt;/strong&gt; - A tool that:&lt;/p&gt;

&lt;p&gt;✅ &lt;strong&gt;Ingests&lt;/strong&gt; - Apache/Nginx combined logs&lt;br&gt;&lt;br&gt;
✅ &lt;strong&gt;Detects&lt;/strong&gt; - SQLi, XSS, and Path Traversal attacks using REGEX&lt;br&gt;&lt;br&gt;
✅ &lt;strong&gt;Enriches&lt;/strong&gt; - IPs with AbuseIPDB threat intelligence&lt;br&gt;&lt;br&gt;
✅ &lt;strong&gt;Presents&lt;/strong&gt; - a clean, actionable dashboard via Streamlit&lt;/p&gt;

&lt;p&gt;Watch It In Action&lt;br&gt;
(&lt;a href="https://dev-to-uploads.s3.amazonaws.com/uploads/articles/dhrwxachfhmsbuqy255c.png" rel="noopener noreferrer"&gt;https://dev-to-uploads.s3.amazonaws.com/uploads/articles/dhrwxachfhmsbuqy255c.png&lt;/a&gt;)&lt;/p&gt;

</description>
      <category>automation</category>
      <category>python</category>
      <category>security</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
