[{"content":"Think Red is where I publish red team tradecraft: concepts, lab research, engagement craft, and the tools I build. Every offensive technique comes with the defender\u0026rsquo;s side, covering how to detect it and how to mitigate it.\nThink like an adversary. Write like a defender.\nFocus areas Adversary emulation and threat-informed red teaming Active Directory and identity attack paths Red team infrastructure and OPSEC AI and LLM red teaming Detection engineering from the attacker\u0026rsquo;s point of view How I work All research is performed in environments I own or am explicitly authorized to test. Nothing here comes from client engagements unless it has been generalized and approved. Techniques are mapped to MITRE ATT\u0026amp;CK and paired with detection and mitigation guidance. Disclosure If you find a security issue with this site, or believe something I published needs correcting, see /.well-known/security.txt or email thinkred@jmsg.me.\nElsewhere GitHub: thinkred-dev RSS: /index.xml Views are my own and do not represent any employer. See the disclaimer.\n","permalink":"https://thinkred.dev/about/","summary":"\u003cp\u003e\u003cstrong\u003eThink Red\u003c/strong\u003e is where I publish red team tradecraft: concepts, lab research, engagement craft, and the tools I build. Every offensive technique comes with the defender\u0026rsquo;s side, covering how to detect it and how to mitigate it.\u003c/p\u003e\n\u003cblockquote\u003e\n\u003cp\u003e\u003cem\u003eThink like an adversary. Write like a defender.\u003c/em\u003e\u003c/p\u003e\n\u003c/blockquote\u003e\n\u003ch2 id=\"focus-areas\"\u003eFocus areas\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eAdversary emulation and threat-informed red teaming\u003c/li\u003e\n\u003cli\u003eActive Directory and identity attack paths\u003c/li\u003e\n\u003cli\u003eRed team infrastructure and OPSEC\u003c/li\u003e\n\u003cli\u003eAI and LLM red teaming\u003c/li\u003e\n\u003cli\u003eDetection engineering from the attacker\u0026rsquo;s point of view\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"how-i-work\"\u003eHow I work\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eAll research is performed in \u003cstrong\u003eenvironments I own or am explicitly authorized to test\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eNothing here comes from client engagements unless it has been generalized and approved.\u003c/li\u003e\n\u003cli\u003eTechniques are mapped to \u003ca href=\"https://attack.mitre.org/\"\u003eMITRE ATT\u0026amp;CK\u003c/a\u003e and paired with detection and mitigation guidance.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"disclosure\"\u003eDisclosure\u003c/h2\u003e\n\u003cp\u003eIf you find a security issue with this site, or believe something I published needs correcting, see \u003ca href=\"/.well-known/security.txt\"\u003e\u003ccode\u003e/.well-known/security.txt\u003c/code\u003e\u003c/a\u003e or email \u003cstrong\u003e\u003ca href=\"mailto:thinkred@jmsg.me\"\u003ethinkred@jmsg.me\u003c/a\u003e\u003c/strong\u003e.\u003c/p\u003e","title":"About"},{"content":"All content on this site is provided for educational purposes and for use in authorized security testing only.\nOnly test systems you own or have explicit, written permission to test. Unauthorized access to computer systems is illegal in most jurisdictions. Techniques and tools are demonstrated in isolated lab environments. Use them at your own risk. Content is provided \u0026ldquo;as is\u0026rdquo;, without warranty of any kind. I am not responsible for misuse or damage resulting from the use of this information. Views expressed here are my own and do not represent any current or former employer or client. Vulnerabilities are handled through coordinated disclosure. Nothing here discloses unpatched vulnerabilities in third-party products. Questions or concerns: thinkred@jmsg.me\n","permalink":"https://thinkred.dev/disclaimer/","summary":"\u003cp\u003eAll content on this site is provided \u003cstrong\u003efor educational purposes and for use in authorized security testing only\u003c/strong\u003e.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eOnly test systems you own or have \u003cstrong\u003eexplicit, written permission\u003c/strong\u003e to test. Unauthorized access to computer systems is illegal in most jurisdictions.\u003c/li\u003e\n\u003cli\u003eTechniques and tools are demonstrated in isolated lab environments. Use them at your own risk.\u003c/li\u003e\n\u003cli\u003eContent is provided \u0026ldquo;as is\u0026rdquo;, without warranty of any kind. I am not responsible for misuse or damage resulting from the use of this information.\u003c/li\u003e\n\u003cli\u003eViews expressed here are my own and do not represent any current or former employer or client.\u003c/li\u003e\n\u003cli\u003eVulnerabilities are handled through coordinated disclosure. Nothing here discloses unpatched vulnerabilities in third-party products.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eQuestions or concerns: \u003cstrong\u003e\u003ca href=\"mailto:thinkred@jmsg.me\"\u003ethinkred@jmsg.me\u003c/a\u003e\u003c/strong\u003e\u003c/p\u003e","title":"Disclaimer"}]