メインコンテンツへスキップ

Restrict AI egress destinations, ports, and protocols with cloud firewall

Implementation Effort: Medium - Requires source-specific acquisition, firewall policy design, and coordination of exceptions and recovery access.
User Impact: Medium - Incorrect acquisition or broad block rules can interrupt AI workloads and unrelated internet access.

Overview​

Global Secure Access (GSA) cloud firewall can allow or block acquired connections using supported destination, port, and protocol conditions. It is an optional extension for AI workloads that need network-layer egress controls beyond ordinary web filtering.

This supports Use least privilege access by limiting outbound connections and Assume breach by constraining egress after compromise. Traffic acquisition and firewall enforcement are separate: defining a firewall rule does not cause its traffic to be forwarded.

Prerequisites​

  • Complete AI network readiness and identify the client versus remote-network source.
  • Internet Access licensing, GSA administrative access, and Conditional Access access for applicable client scenarios.
  • Approval for the client-cloud-firewall and broad wildcard-acquisition previews where used.
  • An inventory of destinations, ports, protocols, IPv4/IPv6 paths, existing acquire modes, bypasses, and recovery requirements.
  • Appropriate acquisition for nonstandard ports or UDP; Default Acquire covers TCP 80/443.

Limitations​

  • Policies default to Allow, and new rules are disabled by default. A policy's existence does not imply default-deny enforcement.
  • Conditions within a rule are combined with AND. For clients, the selected applicable profile's firewall decision is terminal rather than cumulative across profiles.
  • Remote networks use their documented baseline/five-tuple path; that guide does not support destination fully qualified domain name (FQDN) rules. Client FQDN matching requires a destination name and does not replace IP restrictions.
  • Private Access routing takes precedence and is not evaluated by Internet Access cloud firewall rules. Broad 0.0.0.0/0 acquisition covers IPv4, not IPv6.
  • The client preview does not acquire/filter DNS queries. QUIC acquisition or blocking does not imply supported end-to-end QUIC forwarding.
  • The client-preview and remote-network guides describe different support boundaries. Cloud firewall does not provide payload-level data loss prevention (DLP) or Model Context Protocol (MCP) tool authorization.

Reference​