EchlonLabs · Offensive security

Storm

The offensive half of StormShield. Storm runs controlled adversary-simulation exercises — the work security teams use to test their detection, response, and people — against targets that have agreed to be tested.

What it is

Defences are only as good as the last time someone tried to get past them. Storm is a red-team toolkit for running that test on purpose: structured, scoped, and measured. It exists so an organisation can find its own gaps before someone uninvited does — and so Storm's findings feed straight into Shield, the defensive side, to close them.

What it covers

Awareness testing

Simulated social-engineering campaigns that measure how an organisation's people respond, to target training where it's actually needed.

Controlled exploit testing

Staged attack-chain exercises run in an isolated lab, to validate whether a defence actually holds under a realistic sequence.

Campaign tracking

A dashboard that records how an authorised engagement unfolds, so results are reviewable and reportable rather than anecdotal.

Feeds the defence

Findings hand off to Shield's workflow engine, turning an offensive result into a tracked defensive fix.

Rules of engagement

Authorised testing only. Storm is built for engagements run with the explicit, written permission of the system owner, against systems and people defined as in-scope. It is a tool for improving security, not for attacking anyone. Unauthorised use against systems you do not own or are not permitted to test is illegal, and is not a use this project supports.

Python · Flask Isolated lab Self-hosted Authorised engagements