<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>posts on cybercolin.com</title><link>https://cybercolin.com/posts/</link><description>Recent content in posts on cybercolin.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 11 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cybercolin.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>0x2: creating an execution trace plugin for qemu tcg</title><link>https://cybercolin.com/posts/qemu_tcg_execution_traces/</link><pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate><guid>https://cybercolin.com/posts/qemu_tcg_execution_traces/</guid><description>&lt;h2 id="overview"&gt;overview&lt;/h2&gt;
&lt;p&gt;While researching record/replay systems for malware analysis, I came across &lt;a href="https://panda.re"&gt;panda.re&lt;/a&gt;, a platform built on top of QEMU that enables deterministic replay of virtual machines.&lt;/p&gt;
&lt;p&gt;PANDA is currently built for QEMU version 2.9.1 (with ongoing efforts to update to later versions), while the latest QEMU version is 11.0.3 as of the time of this post being written. Along with this, PANDA is primarily designed around recording and replaying individual virtual machines.&lt;/p&gt;</description></item><item><title>0x1: uncovering network artifacts in process memory</title><link>https://cybercolin.com/posts/network_artifacts_process_memory/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://cybercolin.com/posts/network_artifacts_process_memory/</guid><description>&lt;h2 id="overview"&gt;overview&lt;/h2&gt;
&lt;p&gt;It seems that in Windows forensics, historical network connection data is incredibly short lived once a socket closes, and unless additional logging like Sysmon is configured beforehand, native OS-level evidence of past connections is very sparse.&lt;/p&gt;
&lt;p&gt;While IR environments regularly analyze live memory, traditional disk focused analysis often skips memory forensics entirely. Although memory forensics is typically the only way to obtain volatile kernel structures, remnants of connection metadata can absolutely be found in user mode memory, long after a socket has been closed.&lt;/p&gt;</description></item><item><title>0x0: hello world</title><link>https://cybercolin.com/posts/hello_world/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://cybercolin.com/posts/hello_world/</guid><description>&lt;p&gt;This is the first post on my new site. I look forward to sharing about cybersecurity, digital forensics, programming, reverse engineering, and any other topics that interest me.&lt;/p&gt;</description></item></channel></rss>