Skip to content
#0390
ContainersSnapshotsTerminal

One attack box per client engagement

You run pentests for six clients at a time. Each engagement has its own credentials, its own captured loot, its own notes. On one laptop they all sit in sibling folders, one cd apart.

On Hoody each engagement is a container cloned from your tooling snapshot: nmap, Burp, wordlists, your scripts. Client A's engagement never shares a filesystem with client B's. The client's VPN credentials live in their container and nowhere else. At the end you snapshot the box as the evidence record, export the report, and delete the container. The snapshot stays, frozen, if the client disputes a finding six months later.

The shared laptop was a contractual problem waiting to happen. Six engagements, six computers, on a server you rent alone, each one's walls drawn by the kernel instead of by folder discipline.

Six engagements, six computers, on a server you rent alone, each one's walls drawn by the kernel instead of by folder discipline.