Agent configuration in an air-gapped deployment demands precision. There are no shortcuts. Every dependency must be packaged. Every configuration must be self-contained. The agent must run, update, and report without ever touching an external network.
An air-gapped setup means the perimeter is not just defended; it is absolute. Agents must be installed with all required binaries, drivers, and configuration files in place at the moment of deployment. No post-install fetches. No hidden cloud calls. This requires careful pre-build staging, checksum validation, and full offline install workflows.
Start by defining configuration parameters locally and storing them within a secure medium—removable media, encrypted storage, or pre-approved internal repositories. Ensure every deployment artifact is signed and verified before execution. Automate as much as possible, but contain that automation within the air-gapped ecosystem. Infrastructure-as-code still works here—just make sure the code lives inside your isolated environment.