Development#
Build what the mission needs
Warning
Authorization required. Code patterns and infrastructure recipes in this section are general-purpose, but the section also covers tooling the operator builds for offensive engagements (implants, redirectors, C2 planes). Apply those only against systems the operator owns or has written authorization to test. See Disclaimers for the full text.
Development takes place in the operator’s lab. The off-the-shelf tools almost never fit mission parameters. Operators must be self-sufficient, building and employing their own hardware and software systems in support of the mission.
Hardware. Electronic components, microcontrollers, computers, buses, radio, and the hardware-hacking techniques the operator uses to build their own hardware capabilities.
Software. Programming, algorithms, architecture, markup, data formats, DSLs, databases, queues, and utilities the operator uses to build their software with.
Cloud. Immutable cloud infrastructure the operator builds, deploys, operates, and destroys in support of their mission.
The discipline is to build, deploy, and operate technology in support of the mission.
Electricity, components, microcontrollers, computers, radio, and the hardware-hacking tools the operator builds capabilities with.
Tools arduino, kicad, rtl-sdr, hackrf, gnuradio.
Programming languages, algorithms, architecture, data formats, DSLs, databases, queues, and the utilities the operator builds capabilities with.
Tools git, python, go, rustc, gcc.
Immutable cloud infrastructure the operator builds, deploys, and destroys for each mission.
Tools aws, az, gcloud, docker, kubectl, terraform, ansible, helm.