<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>odiesec.io</title><link>https://odiesec.io/</link><description>Recent content on odiesec.io</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://odiesec.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Adaptive Deception: Establishing a Baseline</title><link>https://odiesec.io/blog/adaptive-deception-baseline/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://odiesec.io/blog/adaptive-deception-baseline/</guid><description>&lt;p&gt;The previous post &lt;a href="https://odiesec.io/blog/adaptive-deception/"&gt;laid out the premise&lt;/a&gt;: if adaptive deception works, it should make an autonomous attacker slower, noisier, more expensive to run, or easier to detect. Before I can test that, I need a defensible baseline.&lt;/p&gt;
&lt;p&gt;The first baseline window closed on &lt;code&gt;2026-05-06&lt;/code&gt;: 50 autonomous attacker runs against the same GOAD Active Directory lab, before any deception conditions were introduced.&lt;/p&gt;
&lt;p&gt;This is the measurement shakedown: enough successful attacker behavior to show the harness can support a locked baseline, and enough failure detail to know what has to be separated from the deception signal. A later post will compare that locked baseline against a deception condition.&lt;/p&gt;</description></item><item><title>Adaptive Deception: Raising the Cost of AI Intrusion</title><link>https://odiesec.io/blog/adaptive-deception/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://odiesec.io/blog/adaptive-deception/</guid><description>&lt;p&gt;Between late December 2025 and mid-February 2026, a single threat actor used Claude Code and OpenAI&amp;rsquo;s GPT-4.1 to breach nine Mexican government agencies. Claude Code generated and executed about 75% of the remote commands across the intrusion. The attacker exfiltrated 150 gigabytes of taxpayer, civil registry, electoral, and health data, including 195 million taxpayer records.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
&lt;p&gt;The breach matters because of leverage. One operator used an agent to compress reconnaissance, command generation, error recovery, and iteration into a continuous loop. If autonomous tooling makes intrusion that cheap to run, defenders need ways to slow it down and raise its cost.&lt;/p&gt;</description></item><item><title>Dissection of a BEC: The Entry</title><link>https://odiesec.io/blog/bec-the-entry/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://odiesec.io/blog/bec-the-entry/</guid><description>&lt;p&gt;In the previous post, we pulled the UAL for &lt;code&gt;schen@meridianadvisory.com&lt;/code&gt;, ingested it into ADX, and oriented ourselves. The data showed a 2,733-event spike on November 19, three inbox rules created from an unfamiliar IP, and a two-day gap between the first rule and the mass phishing event. We knew what the threat actor (TA) did. We didn&amp;rsquo;t yet know when they got in or how.&lt;/p&gt;
&lt;p&gt;The UAL records authentication as &lt;code&gt;UserLoggedIn&lt;/code&gt; and &lt;code&gt;UserLoginFailed&lt;/code&gt; operations, but those events don&amp;rsquo;t have all of the information. The Entra ID sign-in logs give you what the UAL doesn&amp;rsquo;t: device information, geolocation, conditional access evaluation, session identifiers, and authentication method detail as structured fields. For authentication events, the sign-in logs are the primary source.&lt;/p&gt;</description></item><item><title>Dissection of a BEC: The Catalyst</title><link>https://odiesec.io/blog/bec-the-catalyst/</link><pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate><guid>https://odiesec.io/blog/bec-the-catalyst/</guid><description>&lt;p&gt;This series walks through a Business Email Compromise (BEC) investigation we worked in November 2025. A single user account at an accounting firm was compromised for just over two days before detection. The Threat Actor (TA) attempted a payment diversion, got caught, and pivoted to a mass credential harvesting campaign. We reconstructed the full attack timeline from the Microsoft 365 Unified Audit Log (UAL), Entra ID sign-in logs, and Message Trace logs.&lt;/p&gt;</description></item><item><title>Training Review: GIAC Certified Forensic Analyst (GCFA)</title><link>https://odiesec.io/blog/training-review-gcfa/</link><pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate><guid>https://odiesec.io/blog/training-review-gcfa/</guid><description>&lt;p&gt;I&amp;rsquo;ve taken training across offensive, defensive, cloud, and forensics. These reviews cover what each course delivered and whether it was worth the cost.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;I started out in digital forensics and later transitioned into offensive security. Over the last few years, my interest in the defensive side picked back up, and I&amp;rsquo;ve been shifting more towards purple teaming. My employer offers a tuition assistance benefit, so I used it to take SANS&amp;rsquo;s Advanced Incident Response, Threat Hunting (FOR508) course via OnDemand in June 2025. The FOR508 material overlaps with earlier DFIR work, so I came to it with more context than a first-time practitioner would.&lt;/p&gt;</description></item><item><title>Training Review: Offensive Security Certified Professional (OSCP)</title><link>https://odiesec.io/blog/training-review-oscp/</link><pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate><guid>https://odiesec.io/blog/training-review-oscp/</guid><description>&lt;p&gt;I&amp;rsquo;ve taken training across offensive, defensive, cloud, and forensics. These reviews cover what each course delivered and whether it was worth the cost.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;I took OffSec&amp;rsquo;s PEN-200 (Penetration Testing with Kali Linux) course and passed the OSCP (Offensive Security Certified Professional) exam with 75 points in August 2020. At the time, I was working in digital forensics on the defensive side. I had taken eLearnSecurity&amp;rsquo;s eJPT and PTP beforehand, and used the PTP exam as preparation the week before OSCP. PTP gives you about a week to complete the hands-on portion, so it served as a practice run for a longer proctored exam. My company organized a cohort where a group of us studied together and sat for the exam on the same timeline. That cohort format helped with accountability and gave us people to troubleshoot with when we got stuck on lab machines.&lt;/p&gt;</description></item><item><title>About</title><link>https://odiesec.io/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://odiesec.io/about/</guid><description>&lt;p&gt;I&amp;rsquo;m Ryan, a cybersecurity researcher, penetration tester, and cloud security consultant. I&amp;rsquo;ve spent the last 13+ years doing penetration tests, red team assessments, and incident response investigations. Most of my current work is in Microsoft 365 and Azure environments focused on offensive testing, IR, and building detection capabilities.&lt;/p&gt;
&lt;p&gt;I have a Masters in Cybersecurity and hold OSCP, OSEP, GCFA, and GREM certifications.&lt;/p&gt;
&lt;p&gt;I speak at security conferences including Wild West Hackin&amp;rsquo; Fest, SAINTCON, Hack Space Con, Hack Red Con, BSides Las Vegas, BSides NoVa, BSides Roanoke, and DEF CON Cloud Village. Topics I&amp;rsquo;m currently focused on: adversary deception, M365 canary tokens, device code phishing, cloud IR methodology, and anything where offense informs defense.&lt;/p&gt;</description></item><item><title>Presentations</title><link>https://odiesec.io/presentations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://odiesec.io/presentations/</guid><description/></item></channel></rss>