#egress-policy

BGP Egress Policy is a networking outbound control that decides where workloads may send traffic for interdomain routing. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used BGP Egress Policy when a route advertisement changed, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

CDN Egress Policy is a networking outbound control that decides where workloads may send traffic for content delivery and edge caching. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used CDN Egress Policy when a cache region served an asset, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

DNS Egress Policy is a networking outbound control that decides where workloads may send traffic for name resolution and delegation. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used DNS Egress Policy when a resolver returned stale data, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

Firewall Egress Policy is a networking outbound control that decides where workloads may send traffic for network traffic filtering. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used Firewall Egress Policy when a new rule matched traffic, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

HTTP Egress Policy is a networking outbound control that decides where workloads may send traffic for application-layer request routing. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used HTTP Egress Policy when a client retried a request, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

Latency Egress Policy is a networking outbound control that decides where workloads may send traffic for time between request and response. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used Latency Egress Policy when a user saw slow responses, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

Load Balancer Egress Policy is a networking outbound control that decides where workloads may send traffic for traffic distribution. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used Load Balancer Egress Policy when traffic shifted between regions, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

Packet Egress Policy is a networking outbound control that decides where workloads may send traffic for unit of network transmission. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used Packet Egress Policy when packet loss increased, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

Service Mesh Egress Policy is a networking outbound control that decides where workloads may send traffic for east-west service communication. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used Service Mesh Egress Policy when a service called another service, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

Subnet Egress Policy is a networking outbound control that decides where workloads may send traffic for address segmentation. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used Subnet Egress Policy when a workload moved networks, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

TLS Egress Policy is a networking outbound control that decides where workloads may send traffic for encrypted transport setup. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used TLS Egress Policy when a certificate neared expiration, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”

VPN Egress Policy is a networking outbound control that decides where workloads may send traffic for private tunnel connectivity. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

“The network engineering team used VPN Egress Policy when a remote user connected, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”