Join our Newsletter — 33% off our NHI Course

Interior Gateway Protocol (IGP)

An Interior Gateway Protocol is a routing protocol that moves traffic between networks inside one organization or autonomous system. In technical terms, IGPs such as OSPF and IS-IS exchange route information among routers under a single administrative control, enabling reachability, path selection, and resilient internal network convergence.

How an Interior Gateway Protocol Works

An Interior Gateway Protocol, or IGP, is the control plane that lets routers inside one organization share reachability and choose paths. It keeps internal traffic moving even as links fail, costs change, or topology shifts.

In practice, IGPs such as OSPF and IS-IS do not merely advertise networks, they continually converge on a shared view of the internal topology. That convergence is what makes internal routing stable enough for enterprise networks, data centres, and backbone domains that need fast local decision-making without relying on external routing.

Why IGPs Matter to Network Design

IGPs are a core part of how large networks stay segmented yet connected. They allow different parts of the same autonomous system to exchange routes automatically, which reduces manual route management and helps avoid brittle static configurations.

That design choice also affects resilience. A well-run IGP can reroute around failures quickly, but the protocol only behaves as intended when the network team has clear area design, summarisation strategy, and a controlled routing domain. Poor design can create route churn, inefficient paths, or unexpected blast radius during outages.

Operational Characteristics of IGPs

IGPs are optimized for internal trust boundaries, not for exchanging routes with the wider internet. Their scope is intentionally limited to a single administrative domain, which means operators can tune metrics, adjacency formation, and convergence behaviour to match internal policy and performance needs.

Because the protocol is distributed, every participating router becomes part of the routing decision process. That makes consistency important: mismatched configurations, unstable adjacencies, or inconsistent summarisation can create black holes, loops, or suboptimal forwarding even when the underlying links are healthy.

IGP, BGP, and the Routing Boundary

IGPs and BGP solve different problems. An IGP handles internal reachability inside an organisation, while BGP is used to exchange routes between autonomous systems. In a normal network architecture, the IGP provides the internal foundation that lets edge routers and core routers reach one another reliably, while BGP handles external policy and interdomain routing.

That separation matters because internal routing mistakes often become visible only when they affect redistribution, summarisation, or the handoff between internal and external routing domains. For readers who want a deeper view of routing integrity and the external boundary, the BGP and Routing Security Guide covers the adjacent security model on the internet-facing side.

Risk and Threat Considerations

IGPs create a high-trust routing environment, so a misconfigured or compromised router can influence how internal traffic flows across the organisation. The main risk is not just packet loss, but traffic diversion, route instability, and exposure of internal paths that were assumed to be protected by the routing domain.

Failure mechanism: If route advertisements, adjacency state, or redistribution rules are not tightly controlled, the protocol can propagate incorrect reachability information quickly across the internal network.

Impact: That can cause traffic blackholing, asymmetric paths, service disruption, and, in a compromise scenario, rerouting through infrastructure the defender did not intend to trust.

Standards & Framework Alignment

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

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

Framework Control / Reference Relevance
NIST CSF 2.0 PR.PS-01 — Configuration Management IGPs depend on controlled router configuration and routing-policy consistency.
PR.AA-05 — Least Privilege Routing control planes should be restricted to authorised administrative access.
DE.CM-01 — Networks and Network Services Monitored IGP instability is detected through routing and adjacency monitoring.
Recommendation — Standardise routing configurations and review changes before they affect production adjacencies. Restrict who can change routing policy, redistribution, and neighbour settings. Monitor route churn, adjacency loss, and abnormal topology changes for rapid response.
NIST SP 800-53 Rev 5 AC-4 — Information Flow Enforcement Routing policy enforces how internal traffic is allowed to move across segments.
CM-2 — Baseline Configuration IGP behaviour relies on a controlled baseline across routers and areas.
Recommendation — Enforce routing boundaries so only intended traffic paths are propagated. Maintain and review routing baselines to keep internal topology behaviour predictable.

Practitioner Guidance

Why practitioners should care: An IGP is foundational infrastructure, so its health directly affects application availability, failover speed, and the reliability of every dependent network service. Treat router adjacency, route origin, and redistribution boundaries as operational controls, not just configuration details.

What to watch for: Sudden route flaps, unexpected topology changes, or a router advertising reachability it should not own are early warning signs that the routing domain needs investigation. In well-managed environments, operators also align internal routing practice with broader routing security guidance such as the routing security guide when the internal edge meets external routing.