Air Gap vs Network Segmentation

Published
Length
3 min read

Luis Felipe Dias

All posts

When weighing air gap vs network segmentation, the core difference is physical separation versus logical rules. Teams pick an air gap for total isolation and use network segmentation for connected apps. Both approaches aim to stop lateral movement across your servers and databases. Your choice depends on how often engineers and apps must reach those systems. How air gap vs network segmentation works in practice An air gap isolates a computer or local network from the public internet. It also

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

When weighing air gap vs network segmentation, the core difference is physical separation versus logical rules. Teams pick an air gap for total isolation and use network segmentation for connected apps.

Both approaches aim to stop lateral movement across your servers and databases. Your choice depends on how often engineers and apps must reach those systems.

How air gap vs network segmentation works in practice

An air gap isolates a computer or local network from the public internet. It also cuts off links to any other internal office networks. No cables or wireless links bridge the gap between these machines and outside systems. Teams move data in and out by hand with removable media like flash drives.

This setup fits nuclear plants, defense systems, and offline root key storage. It stops remote hackers from reaching the target over a wire. Yet it makes daily updates, patching, and log collection very slow for staff.

Network segmentation takes a different path for connected cloud and data center systems. It splits one large network into smaller zones using firewalls, VLANs, and routing rules. Each zone holds a specific group of servers, such as web apps or payment databases. Firewall rules decide which zones can talk to each other over specific ports.

Most cloud teams use segmentation every day to isolate production from staging. It lets apps send data across zones while blocking broad lateral movement. Engineers can still reach segmented hosts over the network to fix bugs or run updates.

Tradeoffs and limits at the network layer

Both models have clear limits once an approved user or process enters the zone. An air gap cannot inspect what a local admin does at the console. If a bad update enters on a USB drive, the local network cannot stop it. Auditing actions inside an offline room also takes manual effort from security teams.

Network Segmentation + K8s RBAC Role vs ClusterRole: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Network segmentation faces a similar blind spot with allowed network paths. A firewall rule only checks IP addresses, ports, and basic packet headers. Once a firewall opens the configured port to a database zone, network rules step back. The network cannot see which person is running queries over that open port.

Static network zones also struggle when engineers need quick access to fix production issues. Opening firewall ports for an on-call engineer leaves wide paths open for too long. Shared database passwords inside a zone also make audit logs hard to trace.

Pairing network zones with runtime session controls

Modern engineering teams keep network segmentation as a strong base layer. Subnets and firewall rules still block outside scans and rogue traffic between server tiers. Still, teams now pair those static network boundaries with runtime controls at the session level.

Instead of trusting every packet inside a subnet, teams check user identity per session. Engineers log in with their work identity before they run a single query or command. Security teams can approve sensitive commands one by one rather than opening a whole subnet.

Runtime checks also protect sensitive data that flows across approved network paths. Data masking rewrites matched fields like emails, phone numbers, card numbers, and national IDs in results. This gives teams tight control over database and server actions inside any network segment.

Govern statements and responses across databases and APIs

Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.

First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.

Frequently asked questions

Can malware still infect an air-gapped system?

Yes, malware can cross an air gap on infected USB drives or laptops. Inside staff or vendors who walk into the room can also run harmful commands.

Does network segmentation stop bad database queries?

No, network segmentation only controls which IP addresses and ports can talk. Once a port is open, a firewall cannot block a destructive SQL query.

Do teams use air gaps and network segmentation together?

Yes, many groups segment their main cloud networks and keep an air gap for backup keys. Each method protects a different tier of risk in the same company.

The query runs. The emails stay hidden.