Air Gapped
Overview
An air-gapped network is physically or logically isolated from unsecured networks, in particular the internet.
Why
- Isolation blocks unauthorized access, data exfiltration, and network attacks
- The pattern is used where security requirements are highest, including finance, military, government, and critical infrastructure
- Public repositories such as Maven Central, npm, PyPI, and Docker Hub are not reachable from the inside
- External artifacts need scanning, approval, and an audit trail before use
How
- Host dependencies, build tools, and frameworks on an internal JFrog Platform
- Put an external Artifactory on the boundary for validation, and an internal one for development. The external instance can be a JFrog SaaS site
- Plan high availability for both environments, plus encrypted transfer, audit logging, and incident response
- Choose a connectivity model below: one-way network, or no network at all
Scenarios
One-Way Connection Scenario →
The internal environment can open controlled connections outward. Inbound connections stay blocked.
No Network Connection Scenario →
The internal and external environments have no network path between them. Artifacts move on physical media.