enclave-latch-proxy

To securely manage network traffic for Latch Enclave sessions, you can use a proxy Skill that intercepts and filters HTTP requests, enforces domain access control, and prevents credential leaks.

Credential injection works by automatically inserting secure credentials into filtered outbound HTTP requests, ensuring that agents can access required services without manually handling sensitive tokens.

Yes, you can enforce access control policies by domain and service. The proxy filters outbound requests, ensuring that only explicitly permitted domains and services receive network traffic.

You can scan outgoing HTTP requests for credential leaks by routing traffic through a filtering proxy that inspects payloads and blocks any outbound communication containing exposed credentials.

Yes, you need EgressFilter and TlsInterceptor. The proxy requires these dependencies, alongside TokenMap, IngressFilter, and CredentialManager, to intercept, filter, and secure network traffic.

The best way to log network traffic for audit purposes is to route all communications through a secure proxy that automatically records inbound and outbound HTTP requests while enforcing access control.