<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Threat-Hunting on Suspicious Bytes</title><link>/en/tags/threat-hunting/</link><description>Recent content in Threat-Hunting on Suspicious Bytes</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 30 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/threat-hunting/index.xml" rel="self" type="application/rss+xml"/><item><title>Detecting Lateral Movement</title><link>/en/posts/detecting-lateral-movement/</link><pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate><guid>/en/posts/detecting-lateral-movement/</guid><description>&lt;p&gt;Once an attacker has a foothold, the interesting part begins: moving from the
first host toward whatever they actually came for. That east-west movement leaves
traces if you know which events to join.&lt;/p&gt;
&lt;h2 id="signals-worth-joining"&gt;Signals worth joining&lt;/h2&gt;
&lt;p&gt;Lateral movement rarely shows up as a single smoking-gun event. It emerges from
correlation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Network logon events (&lt;code&gt;4624&lt;/code&gt; type 3) from unusual sources&lt;/li&gt;
&lt;li&gt;Service or scheduled-task creation on the destination&lt;/li&gt;
&lt;li&gt;Remote process creation shortly after&lt;/li&gt;
&lt;/ol&gt;
&lt;blockquote&gt;
&lt;p&gt;Correlate across hosts, not just within one. A single &lt;code&gt;4624&lt;/code&gt; is noise; a chain
of them following an account around the estate is a story.&lt;/p&gt;</description></item><item><title>Getting started with Threat Hunting with a minimal approach</title><link>/en/posts/starting-with-threathunting/</link><pubDate>Sat, 27 Sep 2025 00:00:00 +0000</pubDate><guid>/en/posts/starting-with-threathunting/</guid><description>&lt;h2 id="start-hunting-today"&gt;Start Hunting Today!&lt;/h2&gt;
&lt;p&gt;Threat hunting doesn&amp;rsquo;t require enterprise tools. You can simply start with what you already have.&lt;/p&gt;
&lt;h3 id="minimum-requirements"&gt;Minimum Requirements&lt;/h3&gt;
&lt;p&gt;Start with things you probably already have. Work from there, and then think about improving and growing.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Centralized logging&lt;/strong&gt; (Sysmon, firewall, proxy logs)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Query capability&lt;/strong&gt; (ELK, Splunk, or even grep)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Baseline knowledge&lt;/strong&gt; of your network&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2-4 hours per week&lt;/strong&gt; of dedicated hunting time&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Baselining is the hardest part for beginners, so start small. Pick one thing you can describe as &amp;ldquo;normal&amp;rdquo; (which hosts talk to the internet, which accounts run as admin, what runs at startup) and write it down. That single baseline becomes the yardstick for your first hunts.&lt;/p&gt;</description></item></channel></rss>