Draft. Work in progress: an outline with working notes. The finished post will replace it.

/ offensive-security, engineering, infrastructure

Building offensive infrastructure as infrastructure

C2, telemetry, test environments and deployment pipelines deserve the same engineering discipline as production systems.

Offensive tooling is often built fast and thrown away. That works until you need to rebuild it under time pressure, prove what it did, or hand it to someone else. Treating it as real infrastructure fixes most of that.

Repeatable by default

  • Infrastructure as code for everything that gets deployed.
  • GitOps: the repo is the source of truth.
  • [TODO: what this changed in practice]

Telemetry you can trust

  • Log what the infrastructure does, not just what the target does.
  • [TODO: telemetry pipeline sketch]

Operational hygiene

  • Teardown is part of the deployment.
  • Secrets, access and cost controls.
  • [TODO: checklist]

A worked example

[TODO: the phishing simulation platform as a generic case study - front end, telemetry API, cloud infra, CI/CD, dashboards. No client campaigns.]

cd ../writing

tony@site:~/blog/offensive-infrastructure-as-infrastructure/