<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mitre-Attack on Suspicious Bytes</title><link>/en/tags/mitre-attack/</link><description>Recent content in Mitre-Attack 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/mitre-attack/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>Building a Threat Actor Profile</title><link>/en/posts/building-a-threat-actor-profile/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>/en/posts/building-a-threat-actor-profile/</guid><description>&lt;p&gt;Cyber threat intelligence is only useful when it changes a decision. A good actor
profile turns scattered observations into something a defender can act on this
week, not just read.&lt;/p&gt;
&lt;h2 id="structure-beats-prose"&gt;Structure beats prose&lt;/h2&gt;
&lt;p&gt;A profile that reads like a story is hard to operationalise. Capture it as
structured fields instead:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Aliases and overlapping clusters&lt;/li&gt;
&lt;li&gt;Targeted sectors and regions&lt;/li&gt;
&lt;li&gt;Observed techniques (mapped to ATT&amp;amp;CK)&lt;/li&gt;
&lt;li&gt;Known infrastructure patterns&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;Intelligence without a confidence level is just a rumour with good formatting.
State what you know, how well you know it, and how you&amp;rsquo;d be proven wrong.&lt;/p&gt;</description></item></channel></rss>