<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>MENASEC</title><description>Detection engineering for modern blue teams.</description><link>https://menasec.net/</link><item><title>What your EDR doesn&apos;t see: telemetry blind spots and the coverage you put on top</title><link>https://menasec.net/2026/09/edr-telemetry-blind-spots/</link><guid isPermaLink="true">https://menasec.net/2026/09/edr-telemetry-blind-spots/</guid><description>Every EDR has things it doesn&apos;t show you, and most of them are not bugs, they&apos;re design. Here&apos;s where the sensor goes quiet in 2026, how I figure out what&apos;s missing, and the extra telemetry and coverage I lean on so the quiet spots aren&apos;t where an intrusion lives.</description><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Kerberoasting from the blue side: catching service-ticket abuse without drowning in 4769</title><link>https://menasec.net/2026/08/kerberoasting-detection-blue-side/</link><guid isPermaLink="true">https://menasec.net/2026/08/kerberoasting-detection-blue-side/</guid><description>Every guide tells you to alert on event 4769. Nobody tells you that 4769 is one of the highest-volume events your domain controllers produce, so a naive rule buries you. Here&apos;s how I filter it down to the requests that are actually an attack, and the honeypot trick that skips the noise entirely.</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate></item><item><title>A Sysmon baseline that actually catches things in 2026</title><link>https://menasec.net/2026/08/sysmon-baseline-2026/</link><guid isPermaLink="true">https://menasec.net/2026/08/sysmon-baseline-2026/</guid><description>Most Sysmon configs I inherit are either the default (which sees almost nothing useful) or a 4,000-line monster tuned for someone else&apos;s environment. Here are the event types that earn their place on the endpoint, what each one catches, and where the false positives come from.</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Catching token theft with process-access telemetry, integrity jump and all</title><link>https://menasec.net/2021/12/detecting-token-stealing-using-sysmon/</link><guid isPermaLink="true">https://menasec.net/2021/12/detecting-token-stealing-using-sysmon/</guid><description>Token stealing elevates from a high-integrity process to SYSTEM by duplicating another process token, and it does it quietly. Two Sysmon events see it if you point them at the right processes and read the access mask instead of the image name.</description><pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Hunting malicious BITS jobs in 2026, and the log most people never turned on</title><link>https://menasec.net/2021/05/hunting-for-suspicious-usage-of/</link><guid isPermaLink="true">https://menasec.net/2021/05/hunting-for-suspicious-usage-of/</guid><description>The Background Intelligent Transfer Service is still a quiet way to download a payload, run a command on job completion, and survive a reboot without dropping an obvious autorun. Here is where the telemetry lives, the three event IDs that actually help, and how to tune out Windows Update.</description><pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Tuning an abnormal child-process rule when you have no telemetry to tune against</title><link>https://menasec.net/2021/01/how-to-design-abnormal-child-processes/</link><guid isPermaLink="true">https://menasec.net/2021/01/how-to-design-abnormal-child-processes/</guid><description>Parent-child anomaly rules are some of the highest-value detections you can write, and also the ones that drown you in false positives. Here is how we scope one when there is no production EDR telemetry to learn the benign baseline from: read the parent binary itself.</description><pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Designing a detection from the primitive up, not the tool down</title><link>https://menasec.net/2020/11/how-to-design-detection-logic-part-1/</link><guid isPermaLink="true">https://menasec.net/2020/11/how-to-design-detection-logic-part-1/</guid><description>A working method for turning an attack technique into a rule that survives contact with a real attacker: find the primitive the technique cannot avoid, test whether the change is rare, weigh how cheaply it can be bypassed, and check it carries enough context to page someone over.</description><pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Registry Symbolic Links: The Quiet Redirect Sysmon Can Still See</title><link>https://menasec.net/2020/09/discovering-windows-registry-symbolic/</link><guid isPermaLink="true">https://menasec.net/2020/09/discovering-windows-registry-symbolic/</guid><description>Registry symbolic links let one key transparently resolve to another, which makes them a tidy hiding spot. Here is how the SymbolicLinkValue tell surfaces in Sysmon registry telemetry and how we alert on it.</description><pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate></item><item><title>The System-Account Fingerprint of Files Pushed Over SMB</title><link>https://menasec.net/2020/08/new-trick-to-detect-lateral-movement/</link><guid isPermaLink="true">https://menasec.net/2020/08/new-trick-to-detect-lateral-movement/</guid><description>The usual share-access events are noisy and often off. A quieter way to catch lateral file staging is to watch the receiving host, where inbound SMB writes show up under the System account in Sysmon file-creation telemetry.</description><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Detecting lateral movement in 2026: what changed since the RDP-over-SSH era</title><link>https://menasec.net/2026/07/detecting-lateral-movement-2026/</link><guid isPermaLink="true">https://menasec.net/2026/07/detecting-lateral-movement-2026/</guid><description>The endpoint-and-network detections you learned for lateral movement still fire, but they&apos;re covering a smaller slice of what actually happens now. The shift is toward identity telemetry, RMM abuse, and living-off-the-land. Here&apos;s what I&apos;d tune first in 2026.</description><pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Hunting TeamViewer Abuse When the Tool Is Already Approved</title><link>https://menasec.net/2019/11/hunting-for-suspicious-use-of/</link><guid isPermaLink="true">https://menasec.net/2019/11/hunting-for-suspicious-use-of/</guid><description>Remote support software is a blessed insider on most networks, which is exactly why attackers reach for it. How we hunt abnormal TeamViewer and RMM sessions with process, file, and network telemetry in 2026.</description><pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate></item><item><title>The ESENT Trail Left Behind When NTDS.dit Walks Out the Door</title><link>https://menasec.net/2019/11/forensics-traces-of-ntdsdit-dumping/</link><guid isPermaLink="true">https://menasec.net/2019/11/forensics-traces-of-ntdsdit-dumping/</guid><description>Copying the AD database off a domain controller is quiet on the wire but noisy in the Application log. A 2026 walk through the ESENT, VSS, and Sysmon traces that actually catch NTDS extraction.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate></item><item><title>The .NET CLR usage log: a per-tool execution receipt attackers forget about</title><link>https://menasec.net/2019/07/interesting-difr-traces-of-net-clr/</link><guid isPermaLink="true">https://menasec.net/2019/07/interesting-difr-traces-of-net-clr/</guid><description>Every time a managed executable runs, the CLR quietly writes a small log file named after it. It survives deletion, it names the tool, and hardly anyone collects it. Here&apos;s what it catches and where it goes blind.</description><pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate></item><item><title>What Network Level Authentication does to your RDP hunt</title><link>https://menasec.net/2019/04/the-impact-of-network-level/</link><guid isPermaLink="true">https://menasec.net/2019/04/the-impact-of-network-level/</guid><description>NLA is a good control that quietly breaks a detection a lot of teams still rely on. Once it&apos;s on, the failed-RDP signal you were watching moves, and the source IP you wanted ends up in a log you probably haven&apos;t enabled.</description><pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Named pipes as a C2 channel: hunting the pivot with Sysmon EID 17 and 18</title><link>https://menasec.net/2019/04/detecting-namedpipe-pivoting-using/</link><guid isPermaLink="true">https://menasec.net/2019/04/detecting-namedpipe-pivoting-using/</guid><description>SMB-linked beacons and PsExec-style tools talk over named pipes, which suits the operator because pipes are invisible to the network sensor and buried in noise on the host. Here is how I pull the pivot out of that noise.</description><pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Scheduled tasks for persistence and remote execution: what to log, what to alert on</title><link>https://menasec.net/2019/03/threat-hunting-25-scheduled-tasks-for/</link><guid isPermaLink="true">https://menasec.net/2019/03/threat-hunting-25-scheduled-tasks-for/</guid><description>A scheduled task is two detections wearing one name. One is quiet persistence that survives reboots; the other is a remote-execution hop that plants a task over the network. Different telemetry, different tuning, one technique ID.</description><pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Certutil as a downloader: catching the classic LOLBIN fetch</title><link>https://menasec.net/2019/03/initial-access-execution-evidences-for/</link><guid isPermaLink="true">https://menasec.net/2019/03/initial-access-execution-evidences-for/</guid><description>Certutil.exe was built to manage certificates and is best known for quietly pulling down whatever you point it at. The command line gives it away every time, and so does the decode variant. Here is the detection and where it still slips past.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Hunting the process that launched from a Run key or the Startup folder</title><link>https://menasec.net/2019/03/how-to-hunt-for-processes-starting-from/</link><guid isPermaLink="true">https://menasec.net/2019/03/how-to-hunt-for-processes-starting-from/</guid><description>Autostart persistence is decades old and still works, because the process it launches looks like a normal child of a normal parent. We hunt the launch itself here, from the registry write through to the process that appears at logon, on Sysmon telemetry.</description><pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Event 4648 in practice: reading logon-with-explicit-credentials without chasing every runas</title><link>https://menasec.net/2019/03/an-overview-of-windows-eventid-4648/</link><guid isPermaLink="true">https://menasec.net/2019/03/an-overview-of-windows-eventid-4648/</guid><description>Event 4648 fires whenever a process supplies credentials that differ from the logged-on user. That makes it a decent lateral-movement and credential-reuse signal and a genuine false-positive machine. Here is how I read the three fields that matter and tune the rest out.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate></item><item><title>The macro that never spawns a child of Word: detecting WMI and COM launches from Office</title><link>https://menasec.net/2019/02/threat-hunting-doc-with-macro-invoking/</link><guid isPermaLink="true">https://menasec.net/2019/02/threat-hunting-doc-with-macro-invoking/</guid><description>The standard malicious-macro rule watches for winword.exe spawning cmd or PowerShell. A macro that launches its payload through WMI or a shell COM object breaks that parent-child link on purpose. Here is how to detect it without depending on Office being the parent.</description><pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate></item><item><title>RDP sourced from 127.0.0.1: catching remote desktop tunneled over reverse SSH</title><link>https://menasec.net/2019/02/threat-hunting-25-rdp-over-reverse-ssh/</link><guid isPermaLink="true">https://menasec.net/2019/02/threat-hunting-25-rdp-over-reverse-ssh/</guid><description>An attacker who can&apos;t reach RDP through the firewall can still pull the session out over a reverse SSH tunnel, and the giveaway is a remote desktop logon whose source address is the loopback. Here is how we detect it in 2026.</description><pubDate>Thu, 04 Jun 2026 00:00:00 GMT</pubDate></item><item><title>When the endpoint can&apos;t see it: hunting from the Windows DNS server&apos;s analytical log</title><link>https://menasec.net/2019/02/threat-hunting-24-microsoft-windows-dns/</link><guid isPermaLink="true">https://menasec.net/2019/02/threat-hunting-24-microsoft-windows-dns/</guid><description>Client-side DNS telemetry only covers the hosts you instrumented. The Windows DNS Server analytical channel logs every query the resolver answers, including the ones no endpoint agent ever saw. Here is how I turn it on and what I hunt in it.</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate></item><item><title>Catching LSASS credential dumps that use ProcDump and Task Manager</title><link>https://menasec.net/2019/02/threat-hunting-21-procdump-or-taskmgr/</link><guid isPermaLink="true">https://menasec.net/2019/02/threat-hunting-21-procdump-or-taskmgr/</guid><description>Attackers stopped bringing mimikatz to the party. They dump LSASS with signed tools you already trust, ProcDump and Task Manager, and let a cracker do the rest offline. The catch isn&apos;t the tool name, it&apos;s the handle.</description><pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate></item><item><title>The child of explorer.exe nobody clicked: detecting DCOM lateral movement</title><link>https://menasec.net/2019/02/threat-hunting-18-lateral-movement-via/</link><guid isPermaLink="true">https://menasec.net/2019/02/threat-hunting-18-lateral-movement-via/</guid><description>ShellWindows and ShellBrowserWindow let an attacker run a command on a remote host through DCOM, and the payload lands as a child of explorer.exe with no one sitting at the keyboard. That mismatch is the whole detection.</description><pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate></item><item><title>Catching a SharpHound run: the LDAP burst and the session fan-out</title><link>https://menasec.net/2019/02/threat-hunting-7-detecting/</link><guid isPermaLink="true">https://menasec.net/2019/02/threat-hunting-7-detecting/</guid><description>BloodHound&apos;s collector doesn&apos;t exploit anything. It just asks the domain a lot of questions, very fast, from one host. Two behaviors give it away, and one honeytoken makes the whole thing cheap to catch.</description><pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate></item></channel></rss>