enclave-egress-filter

You can filter outbound network traffic by configuring exact and wildcard domain patterns to match outbound requests against registered services. This enforces secure egress policies and controls access paths for approved domains.

Credential leak detection scans outbound request bodies to identify exposed credentials and prevent data breaches. This mechanism ensures sensitive authentication data is not accidentally transmitted over the network to unauthorized destinations.

Yes, you can enforce data tier access control by applying a data tier hierarchy. This restricts network access paths and ensures only authorized users and services can communicate across specific security boundaries.

Credential injection securely embeds authentication credentials directly into outbound request headers. This ensures safe communication with registered services without exposing sensitive data in the request body or URL parameters.

The best way to scope access paths and methods is by enforcing fine-grained access control via glob patterns. This allows precise policy enforcement on specific URL paths and HTTP methods for registered services.

Yes, you must configure domain patterns and service definitions before enabling egress filtering. This prerequisite setup ensures the proxy can accurately evaluate and match outbound requests against your secure network policies.