Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› ARP Spoofing
Cyber Security

ARP Spoofing

← Back to Glossary
By NHI Mgmt Group Updated November 4, 2026 Domain: Cyber Security

ARP spoofing is a network attack where false Address Resolution Protocol messages redirect traffic to an attacker-controlled device on the same local network. In development and staging environments, it can expose tokens, environment variables, or internal service calls when systems accept the wrong MAC address mapping.

How ARP spoofing works

ARP spoofing abuses a local network protocol that many environments still trust implicitly. By sending forged ARP replies, an attacker can persuade hosts that the attacker’s MAC address belongs to a legitimate IP address, which diverts traffic at Layer 2 and creates an interception or redirection point on the same broadcast domain.

This is not a remote internet attack in the usual sense. It depends on proximity to the target segment, whether physical, wireless, virtual, or bridged through a compromised host, and it succeeds when systems accept poisoned address mappings without stronger validation.

Why ARP spoofing is dangerous

Once traffic flows through the attacker-controlled device, the attack can enable passive sniffing, active modification, and selective blocking. That makes it especially dangerous for plaintext protocols, poorly segmented internal services, and development or staging networks where trust assumptions are often weaker than in production.

Its value to an adversary comes from its simplicity and reach, because one successful poisoning campaign can affect multiple hosts on the same subnet and expose credentials, tokens, cookies, service calls, or other sensitive traffic in transit.

ARP spoofing is often discussed alongside other Layer 2 and man-in-the-middle techniques because the end result is similar: the attacker inserts themselves into trust relationships that were never meant to be mediated by an untrusted node. The Layer 2 Attacks Guide explains the adjacent attack surface and the switch-hardening controls that reduce exposure.

How organisations reduce exposure

Exposure starts with knowing where ARP spoofing is even possible. The relevant questions are which assets share a broadcast domain, where critical services still rely on local-link trust, and whether attacker access can be gained through a guest network, unmanaged endpoint, compromised virtual machine, or adjacent segment.

Defences work best when they combine network design and control enforcement. Segmentation limits who can see the traffic, while switch protections such as DHCP snooping, dynamic ARP inspection, port security, and 802.1X reduce the chance that forged mappings will be accepted in the first place. The Man-in-the-Middle Attacks Guide covers the interception path and the transport-layer defences that remain important even when Layer 2 controls exist.

Visibility also matters. If an environment has no baseline for expected MAC and IP pairings, no alerting on duplicate address behaviour, and no review of unusual neighbour cache changes, spoofing can persist long enough to collect data or alter traffic without immediate notice. The OSI and TCP/IP Models Guide is a useful reference for understanding where these controls sit in the stack and why Layer 2 visibility is distinct from higher-layer inspection.

Detection and response patterns

Detection usually depends on spotting inconsistency: duplicate IP-to-MAC mappings, gateway MAC changes, neighbour table churn, or traffic flows that suddenly take an unexpected path. In practice, the most reliable detection comes from correlating host observations, switch telemetry, and network security monitoring rather than relying on one data source alone.

When spoofing is suspected, the response should assume that traffic on the affected segment may already have been observed or altered. That means validating whether sensitive sessions were active during the event, checking for credential or token exposure, and reviewing whether internal service traffic or administrative access crossed the poisoned path.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

CIS Controls v8, NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-12 — Network Infrastructure ManagementARP spoofing is a Layer 2 network-control problem requiring switch hardening and segmentation.
Recommendation — Harden switch and subnet controls to prevent forged local network mappings.
NIST SP 800-53 Rev 5SC-7 — Boundary ProtectionARP spoofing exploits weak local trust boundaries and traffic redirection.
CM-7 — Least FunctionalityLimiting unnecessary Layer 2 exposure reduces opportunities for local spoofing attacks.
Recommendation — Enforce protected network boundaries and restrict lateral traffic paths. Remove unnecessary local-link exposure and limit services on shared segments.
NIST CSF 2.0PR.AA-05 — Identity Management, Authentication and Access ControlLocal spoofing can expose sessions and credentials that depend on trusted network access.
Recommendation — Protect session and access paths against interception on untrusted local networks.

Practitioner Guidance

Why practitioners should care: ARP spoofing is a low-complexity local attack that can undermine trust inside networks that otherwise look well controlled. Practitioners should treat any shared Layer 2 environment as an interception surface, especially where development, staging, contractor access, or flat subnets increase the chance of lateral reach.

What to watch for: Repeated address changes, gateway impersonation, and unexplained MAC movement are the operational signals that deserve immediate review. If the environment depends on session tokens, internal APIs, or admin traffic on the same subnet, assume the blast radius is wider than one captured flow.

Practitioner takeaway: Reduce the attack’s usefulness by hardening the switch layer, shrinking Layer 2 trust zones, and validating that internal traffic still remains safe when the local network can no longer be trusted.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org