<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Detection-Engineering on Blue Team Write-ups</title><link>https://zviarcyber.github.io/tags/detection-engineering/</link><description>Recent content in Detection-Engineering on Blue Team Write-ups</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://zviarcyber.github.io/tags/detection-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Learn Sigma — Reading a Detection Rule for Bitsadmin Abuse</title><link>https://zviarcyber.github.io/posts/learn-sigma-letsdefend/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://zviarcyber.github.io/posts/learn-sigma-letsdefend/</guid><description>&lt;h2 id="abstract">Abstract&lt;/h2>
&lt;p>A walkthrough of the LetsDefend &lt;strong>Learn Sigma&lt;/strong> lab. The goal isn&amp;rsquo;t to run a tool, but to
&lt;em>read&lt;/em> a real Sigma rule — &lt;code>proc_creation_win_bitsadmin_download.yml&lt;/code> — and understand how its
sections (&lt;code>logsource&lt;/code>, &lt;code>selection&lt;/code>, &lt;code>condition&lt;/code>, &lt;code>fields&lt;/code>, &lt;code>tags&lt;/code>) work together to detect an
attacker abusing the legitimate Windows utility &lt;code>bitsadmin.exe&lt;/code> to download malicious payloads.
Understanding how a detection rule is built is what lets a SOC analyst know &lt;em>why&lt;/em> an alert
fired, judge false positives, and eventually write rules of their own.&lt;/p></description></item></channel></rss>