<?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>Think Red</title><link>https://thinkred.dev/</link><description>Recent content on Think Red</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://thinkred.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>About</title><link>https://thinkred.dev/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://thinkred.dev/about/</guid><description>&lt;p&gt;&lt;strong&gt;Think Red&lt;/strong&gt; is where I publish red team tradecraft: concepts, lab research, engagement craft, and the tools I build. Every offensive technique comes with the defender&amp;rsquo;s side, covering how to detect it and how to mitigate it.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Think like an adversary. Write like a defender.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="focus-areas"&gt;Focus areas&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Adversary emulation and threat-informed red teaming&lt;/li&gt;
&lt;li&gt;Active Directory and identity attack paths&lt;/li&gt;
&lt;li&gt;Red team infrastructure and OPSEC&lt;/li&gt;
&lt;li&gt;AI and LLM red teaming&lt;/li&gt;
&lt;li&gt;Detection engineering from the attacker&amp;rsquo;s point of view&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="how-i-work"&gt;How I work&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;All research is performed in &lt;strong&gt;environments I own or am explicitly authorized to test&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Nothing here comes from client engagements unless it has been generalized and approved.&lt;/li&gt;
&lt;li&gt;Techniques are mapped to &lt;a href="https://attack.mitre.org/"&gt;MITRE ATT&amp;amp;CK&lt;/a&gt; and paired with detection and mitigation guidance.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="disclosure"&gt;Disclosure&lt;/h2&gt;
&lt;p&gt;If you find a security issue with this site, or believe something I published needs correcting, see &lt;a href="https://thinkred.dev/.well-known/security.txt"&gt;&lt;code&gt;/.well-known/security.txt&lt;/code&gt;&lt;/a&gt; or email &lt;strong&gt;&lt;a href="mailto:thinkred@jmsg.me"&gt;thinkred@jmsg.me&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Disclaimer</title><link>https://thinkred.dev/disclaimer/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://thinkred.dev/disclaimer/</guid><description>&lt;p&gt;All content on this site is provided &lt;strong&gt;for educational purposes and for use in authorized security testing only&lt;/strong&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Only test systems you own or have &lt;strong&gt;explicit, written permission&lt;/strong&gt; to test. Unauthorized access to computer systems is illegal in most jurisdictions.&lt;/li&gt;
&lt;li&gt;Techniques and tools are demonstrated in isolated lab environments. Use them at your own risk.&lt;/li&gt;
&lt;li&gt;Content is provided &amp;ldquo;as is&amp;rdquo;, without warranty of any kind. I am not responsible for misuse or damage resulting from the use of this information.&lt;/li&gt;
&lt;li&gt;Views expressed here are my own and do not represent any current or former employer or client.&lt;/li&gt;
&lt;li&gt;Vulnerabilities are handled through coordinated disclosure. Nothing here discloses unpatched vulnerabilities in third-party products.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Questions or concerns: &lt;strong&gt;&lt;a href="mailto:thinkred@jmsg.me"&gt;thinkred@jmsg.me&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>