liveBook · Manning

Egress control

As explained in Grokking Software Architecture

Egress filtering is the control of outbound network traffic according to approved destinations, protocols, ports, or policies.

Egress control filters outbound network traffic. It limits which destinations, protocols, or ports a system can use, rather than focusing only on traffic coming in. section 11.7.1

A practical outbound rule sets a clear boundary:

  • Allow an internal service to connect only to explicitly approved destinations, such as api.stripe.com. section 11.7.1
  • Block connections to every other destination, so a compromised server has less room to download malware or send stolen data outside. section 11.7.1

The forgotten exit

A company may guard its inbound network but leave outbound traffic unrestricted. If an attacker compromises a server, strict egress rules can prevent it from reaching unapproved internet destinations—helping turn that server into a dead end. section 11.7.1

How Grokking Software Architecture covers it

How deep it goes
Defines destination allowlisting and explains its threat rationale, without detailing configuration steps.
Examples
Uses api.stripe.com as an approved destination and the Target HVAC breach as a motivating case.
What you can do after
Evaluate how outbound allowlisting can limit a compromised server’s ability to download malware or extract stolen data.
How it connects
Connects egress filtering with Zero Trust, least privilege, and network segmentation.

Also explained in

Compare how 2 books explain egress control →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.