How should I encrypt embeddings and metadata at rest and in transit?

To protect against embedding inversion attacks, encrypt embeddings at rest where warranted. The provided sources do not explicitly detail encryption methods for metadata or for data in transit.

• Encrypt embeddings at rest where warranted to mitigate the risk of embedding inversion attacks, where an attacker reconstructs original text from embeddings in a vector database. This addresses the OWASP LLM Top 10 risk of "Embedding Inversion Attacks (L2)".
• Treat vector databases as containing the original text for access control purposes. This implies that the security measures applied to the original sensitive data should also be applied to its embeddings.
• Consider differentially-private embedding techniques for highly sensitive data as an additional mitigation for embedding inversion attacks.
• Implement classification inheritance where any data derived from classified inputs, including embeddings and summaries, inherits at least the classification of its inputs. This helps manage PII leakage through derived data (L2, L5).
• Govern embedding stores at the same level as the raw text they were derived from. This ensures consistent security treatment for both original and derived data.