<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Securityresearch - Tag - Forensic wheels</title><link>https://polymathmonkey.github.io/weblog/tags/securityresearch/index.html</link><description/><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 05 Jun 2026 12:32:13 +0200</lastBuildDate><atom:link href="https://polymathmonkey.github.io/weblog/tags/securityresearch/index.xml" rel="self" type="application/rss+xml"/><item><title>Threathunting like a nerd</title><link>https://polymathmonkey.github.io/weblog/securityresearch/threathuntinglikeanerd/index.html</link><pubDate>Fri, 05 Jun 2026 12:04:00 +0200</pubDate><guid>https://polymathmonkey.github.io/weblog/securityresearch/threathuntinglikeanerd/index.html</guid><description>The Tooling Problem Most threat hunters use one of three things to document their work: a Word document, a Jupyter notebook, or a dedicated platform like TheHive or Aurora. Word documents are fine until you want to run a query from inside the document. Jupyter notebooks are fine until you want to write prose that does not look like a GitHub README. TheHive is fine until you are a solo analyst running a homelab and you do not want to maintain another service.</description></item></channel></rss>