DEADWIRE / SECURITY FIELD MANUAL
Understand the system.
Prove the technique.
Build a working model of security, test it in a bounded lab, and leave evidence someone else can reproduce. Deadwire is building a connected course from an authorized private library. Four developed lessons are available; the wider course is still being written.
Read available lessons → View the 24-week route
4 lessons
Developed; 14 more outlines
90 min
Daily study budget
24 weeks
Suggested learner route
In review
Book-derived expansions
Choose your next step
01 / ORIENT
Start with the map
Understand prerequisites, choose a route, and learn what counts as completion.
02 / PRACTICE
Build your lab
Prepare a disposable environment, then reproduce the bundled web authorization exercise.
03 / DEMONSTRATE
Make the evidence clear
Record observations, explain the result, and distinguish what you predicted from what you tested.
One focused session
Planned allocation, not measured progress. Carry unfinished work forward; reading alone does not demonstrate mastery. The weekly plan places each session in the wider route.
Know what is ready
The web-authorization lesson and three SCADA/OT chapters are developed, with local or offline exercises. Fourteen other chapter pages remain short outlines. Book distillation, source review, and learner validation are ongoing. The coverage map names missing topics—including mobile security, exploit development, and deeper industrial protocols—so planned coverage is not confused with published teaching material.
| Label | What it establishes |
|---|---|
| Outline | A short scope sketch; the full lesson is still missing. |
| Developed | An explanation and exercise are written; review and learner validation remain separate. |
| Generated | A model draft exists; its claims still need review. |
| Approved | A human accepted the note with source references. |
| Verified | A technique has recorded human lab evidence. |
Library processing status · Source coverage · Acceptance and evaluation
Source books and learning evidence stay in the private Hacking/Deadwire workflow. Published lessons use original explanations with provenance. Engineers can start at the Luna handoff or architecture decisions.
Lab boundary
Run exercises only on systems you own or are explicitly authorized to test. Each active exercise needs a defined scope and cleanup; Deadwire does not execute commands extracted from books.