SiloBSD
Reproducible air-gapped infrastructure
Reproducible infrastructure for building air-gapped systems with a controlled, inspectable, repeatable setup process.
Designed for controlled experimentation.
SiloBSD treats an air-gapped machine as a reproducible system boundary. Inputs are prepared outside the final environment, transferred deliberately, verified, and consumed through a documented setup process.
What is inside.
- Offline installation media
- Declarative setup workflow
- Controlled transfer boundary
- Verification and audit points
Make the boundary visible.
Redoubt projects document their important boundaries so the system can be inspected before it is trusted.
Inspect the flow.
SiloBSD treats an air-gapped machine as a reproducible system boundary. Inputs are prepared outside the final environment, transferred deliberately, verified, and consumed through a documented setup process.
From setup to repeatable result.
A documented workflow makes an experiment easier to reset, compare, and reproduce.
| STEP | ACTION |
|---|---|
| 01 | Prepare and verify source material |
| 02 | Build trusted installation media |
| 03 | Install the base FreeBSD system |
| 04 | Apply the SiloBSD configuration |
| 05 | Verify the resulting offline state |
Boundaries before convenience.
These are design constraints, not claims of absolute security.
An air gap is a boundary, not a guarantee.
Verify every removable or transferred artifact.
Document the trusted computing base and maintenance procedure.
Plan how updates enter the offline environment.
Inspect the repository first.
Clone or obtain the project source, read the documentation, verify inputs, then reproduce the environment in a disposable or appropriately isolated system.
$ git clone <project-source> $ cd silobsd $ read the documentation $ verify inputs before execution