enclave-token-map

Tokenizing sensitive data in proxy responses converts sensitive values to opaque tokens, preventing cross-service data exfiltration while enabling secure handling. This ensures data is protected during storage and transmission across services.

Same-origin policy enforcement for data tokens ensures that tokens can only be resolved back to their real values within the originating service. This mechanism prevents unauthorized services from accessing the original sensitive data.

Automated token lifecycle management in a secure proxy pipeline requires implementing tokenization logic and token resolution support within the originating service. This automatically creates and resolves tokens without manual intervention.

Latch Enclave supports tokenization for securing sensitive session data by providing a secure environment where tokens are automatically managed. This prevents cross-service data exfiltration and ensures secure handling in proxy responses.

You need to implement token resolution within your originating service to use tokenization effectively. The proxy pipeline handles token creation, but the originating service must support resolving tokens back to their real values.

The best way to prevent cross-service data exfiltration in proxy responses is to implement tokenization with same-origin enforcement. This converts sensitive values to opaque tokens that can only be resolved within the originating service.