Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Pivoting is the use of a compromised machine as a relay to reach networks the attacker cannot touch directly, turning one foothold into access across segmented environments.

What Is Pivoting?
Pivoting is what an attacker does when the thing they want is unreachable from where they are. The compromised machine becomes a relay: traffic goes to it, the machine forwards that traffic onward using its own network position, and responses come back the same way. A workstation in a sales office suddenly becomes a route into a finance VLAN that the attacker could never have reached from the internet.
It is the plumbing that makes lateral movement possible. MITRE ATT&CK catalogues the behaviour under Internal Proxy (T1090.001) and Protocol Tunnelling (T1572).
| Pattern | What it does | Typical use |
|---|---|---|
| Local port forward | A port on the attacker’s machine maps to one service behind the pivot | Reaching a single database or admin interface |
| Remote port forward | A port on the compromised host maps back to a service on the attacker’s machine | Delivering payloads into a segment with no outbound access |
| Dynamic proxy | A SOCKS proxy that forwards any destination the pivot can reach | Running whole toolsets against an internal network |
The dynamic proxy is the one that changes the economics of an intrusion. With a single SOCKS listener in place, tools that know nothing about tunnelling can be pushed through it using a wrapper such as Proxychains, and the attacker operates against the internal network almost as though they were sitting on it.
On Linux hosts, SSH does most of the work: the client supports local, remote, and dynamic forwarding natively, so a stolen key often is the pivot. Where SSH is unavailable, operators reach for purpose-built relays. Chisel tunnels TCP over HTTP with optional TLS. Ligolo-ng creates a virtual interface so the whole target subnet appears routable. Socat relays arbitrary streams. Command-and-control frameworks build the capability in: Metasploit has route and autoroute with a SOCKS auxiliary module, and Sliver and comparable implants expose port forwards from the operator console.
Windows gives attackers options without any tooling at all. netsh interface portproxy creates persistent forwards, and SSH client and server components now ship with the operating system. That is a living off the land approach, and it leaves far less to detect.
Organisations often protect a sensitive segment by controlling who can route to it, then grant broad access to a management jump host or a developer subnet. Pivoting turns any compromise inside those trusted zones into access to everything they can reach. Cloud environments have the same shape: a compromised bastion host or a build agent with a VPC peering relationship becomes the route into private subnets that have no internet gateway at all.
Double-hop pivots compound the problem. Host A reaches host B, host B reaches host C, and each hop inherits the trust of the one before it, which is precisely why network segmentation that is enforced only at the perimeter achieves very little.
Pivot traffic looks wrong if you know your baseline. Useful signals include:
netsh portproxy registry changes under PortProxy, both of which endpoint telemetry picks up.Segment internally and enforce it with host firewalls as well as network ACLs, so workstation-to-workstation traffic is simply dropped. Control egress: default-deny outbound with an authenticated proxy removes most tunnelling options and makes the remainder noisy. Put administrative access behind dedicated privileged access workstations that are not used for email or browsing. Apply the same thinking in cloud accounts, using security groups, private endpoints, and least-privilege roles rather than broad peering.
Assumed-breach testing is the honest way to measure this. Our Red Team Services start from a foothold and show how far a pivot actually travels in your environment before anyone notices.
Lateral movement is the goal of reaching another system; pivoting is one of the mechanisms that makes it possible. An attacker who authenticates directly from host A to host B has moved laterally without pivoting. An attacker who tunnels traffic through host A to reach a network they cannot route to has pivoted, and will usually move laterally once the tunnel is up.
It constrains it rather than stopping it, and that is still valuable. Segmentation determines which systems a compromised host can reach, so good design means a pivot from a sales laptop opens very little. The common failure is segmenting at the perimeter while leaving internal zones flat, which lets one foothold reach everything once an attacker is inside.
Default-deny egress with an authenticated proxy removes the easy options and forces attackers into protocols you inspect. Tunnelling over HTTPS or DNS still works in many environments, so pair filtering with analysis: look for long-lived sessions, unusual request sizes, destinations with no reputation, and TLS fingerprints that do not match the browsers and agents you deploy.
Internal infrastructure tests often include it, particularly where segmentation is a stated control. A time-boxed external test may never get the foothold needed. If your specific question is whether segmentation holds under attack, ask for an assumed-breach or red team engagement that starts inside the network, since that is the only way to exercise it properly.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.