Offensive Security Automation

From an organisation name to repeatable reconnaissance

I built a tool that started with an organisation name and automated reconnaissance and lightweight checks, making repeated assessment preparation reusable.

Growing MSSP with Offensive ServicesSecurity Engineer2 min read

Reconnaissance was recurring preparation for offensive engagements. I built a tool that took an organisation name as its starting point and automated discovery and lightweight checks, giving assessors a repeatable starting workflow.

Across my wider offensive automation work, I used Python, Bash and PowerShell and maintained documentation for the code I developed. This supported reuse and made the implementation understandable alongside the assessment process.

Methods, evidence & technical decisions

An organisation name as the input

The tool began with an organisation name and automated reconnaissance and lightweight testing for assessment preparation. It converted a repeated discovery activity into a reusable workflow.

Open this detail ↗
Maintaining the automation

Across my wider offensive automation work, I used Python, Bash and PowerShell and documented the code I developed. I maintained the implementation context needed for others to understand and reuse that work.

Open this detail ↗

Skills used in this work

This work connects to

Security automationOffensive security

Your exploration

Viewed history

Saved only in this browser.

Ask my portfolio

Ask about my work.

Ask about an investigation, a technology or my contribution. Answers link to the relevant case and technical detail.

Every answer links to the work.
How this works

When AI is connected, your question, recent questions and relevant published pages are sent to MiniMax to select supporting passages. Otherwise, this searches the site directly. Answers quote the saved website and link to their sources. This website does not save chat transcripts. Clearing or leaving the page clears this conversation.

Help improve this website

Report an issue

Spotted something broken or inaccurate? Tell me what happened and what you expected.