https://9insomnie.github.io/tags/security/Recent content in Security on N0irxHugoen-us<a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener">CC BY-NC 4.0</a>Fri, 17 Jul 2026 00:48:17 +0800https://9insomnie.github.io/posts/2026/07/building-an-ai-assisted-penetration-testing-workspace-why-i-created-it/Thu, 16 Jul 2026 10:00:00 +0800https://9insomnie.github.io/posts/2026/07/building-an-ai-assisted-penetration-testing-workspace-why-i-created-it/<h2 id="the-problem-with-chaotic-pen-testing">The Problem with Chaotic Pen Testing</h2> <p>Over the years, I&rsquo;ve worked on dozens of penetration testing engagements, and one pattern kept bothering me: every time I started a new target, I was reinventing the wheel.</p> <p>The typical workflow looked something like this:</p> <ul> <li>Run a few tools, dump the output into a folder</li> <li>Scribble notes in random text files</li> <li>Find a vulnerability, write a quick PoC, forget where I saved it</li> <li>Start the next target, do it all over again</li> </ul> <p>The knowledge I gained from one engagement rarely carried over to the next. Attack patterns I&rsquo;d figured out on a Spring Boot app were lost when I moved to a Laravel target. PoCs I&rsquo;d crafted sat forgotten in some archive folder. Every recon started from scratch.</p>