Tunneling software is software that carries one network protocol or traffic stream inside another, so data can pass through systems that would otherwise block it. It is used with VPNs, SSH tunnels and similar relays, and it can hide source, destination or application details from intermediate controls.
How tunneling software works
Tunneling software encapsulates one protocol inside another so traffic can cross a network path that would otherwise reject, inspect, or reshape it. That can be a legitimate design choice, such as remote access or site connectivity, but the same mechanism also changes how visibility, filtering, and policy enforcement behave between endpoints and intermediate controls.
The key idea is not simple encryption, although tunneling often uses it. The important security property is transport indirection: a control that understands the outer protocol may not understand the inner one, so the traffic can appear ordinary at one layer while carrying something very different inside.
Where tunneling software is used
Tunneling is common in VPNs, SSH port forwarding, application relays, and protocols that need to traverse strict firewalls or NAT. In practice, it lets a client or service reach a destination through a permitted channel, which is why it is useful for administration, remote work, and connectivity across segmented environments.
It also appears in environments where direct exposure is undesirable. For example, a protected internal service may be reached only through a tunnel rather than being opened to the broader network. In that case, the tunnel becomes part of the access path and should be treated as a security boundary, not just a convenience feature.
Why tunneling changes security controls
Tunneling can bypass port-based filtering, application allowlists, proxy inspection, and some network detection logic because the meaningful payload is hidden inside an allowed wrapper. That does not make the traffic malicious by itself, but it does mean defenders need to understand both the outer session and the inner protocol if they want accurate policy enforcement.
Tunneling also shifts trust. Intermediate systems may see a single encrypted session or a benign carrier protocol, while the real application traffic, commands, or data exchange happens inside it. That can complicate segmentation, data loss prevention, and logging, especially when tunnels are created by users, scripts, or software that security teams do not centrally manage.
For broader control context, tunneling is often evaluated alongside access and monitoring expectations in NIST SP 800-53 Rev 5 Security and Privacy Controls and traffic-policy design in NIST Cybersecurity Framework 2.0, because the security issue is not only that the tunnel exists, but that it can obscure what is actually being transported.
Detection and governance considerations
Because tunneling can hide the real destination and application, organisations usually need layered detection rather than relying on a single perimeter rule. Network telemetry, endpoint visibility, proxy logs, and configuration review all matter, especially when tunnels are created dynamically or allowed for legitimate operations but rarely audited.
Governance also matters because authorised tunneling can become shadow access if no one knows who set it up, why it exists, or when it should be removed. A stable inventory of approved tunneling paths, their owners, and their expected business purpose helps separate sanctioned remote access from risky bypass channels. In mature control programs, this is commonly aligned with least-privilege networking and boundary enforcement concepts such as NIST Cybersecurity Framework 2.0 and, where traffic must be tightly segmented, NIST SP 800-207 Zero Trust Architecture.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST CSF 2.0 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-4 — Information Flow Enforcement | Tunneling affects how traffic is permitted and inspected across boundaries. |
| Recommendation — Enforce boundary flow rules so tunneled traffic is allowed only when explicitly approved. | ||
| NIST CSF 2.0 | PR.AA-05 — Network Segmentation | Tunneling can bypass or blur segmentation and trust boundaries. |
| Recommendation — Segment network paths so tunnels do not create uncontrolled lateral access. | ||
| NIST Zero Trust (SP 800-207) | Zero Trust Architecture | Tunneling changes trust assumptions and can obscure application-level access paths. |
| Recommendation — Verify each tunneled connection explicitly instead of trusting the carrier path. | ||
Practitioner Guidance
What to watch for: Treat tunnel creation, tunnel configuration changes, and unexpected long-lived sessions as security events worth reviewing. A tunnel that is technically valid can still be operationally unsafe if it weakens inspection, bypasses segmentation, or is left in place after the business need has ended.
Governance implication: Tunneling software should have an owner, an approved use case, and an explicit review path. If it is used to carry administrative or high-value application traffic, its access model should be documented and periodically revalidated rather than assumed safe because the transport is encrypted.
Related resources from NHI Mgmt Group
- How should security teams handle exposed secrets in modern software pipelines?
- What is the difference between software supply chain risk and NHI risk?
- Why do leaked secrets need a different reporting path than ordinary software bugs?
- What is the difference between SaaS supply chain security and software supply chain security?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org