#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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.