Field notes, coordinated vulnerability disclosures and open-source tools. This is the public side of how I map systems, validate impact and make findings reproducible.
What I test first, where authorization checks fail and how small implementation details become useful attack paths.
Published vulnerabilities with affected versions, technical impact, remediation status and full write-ups where disclosure permits.
Small, focused utilities for reconnaissance and security testing. The source, installation steps and limitations are public.
Map the surface before narrowing in. Test boundaries with more than one identity. Keep enough evidence for another engineer to reproduce the result. The posts, CVEs and tools above show that method in public.
Review the deliverable first, then send the system, roles and target date when you are ready.