In transit: protecting the connection
TLS protects a connection between two endpoints, such as a browser and a server. Certificates help identify the server; encryption protects the content from interception during transfer. TLS 1.3 is specified in RFC 8446.
The receiving server can read the content. HTTPS alone therefore does not prevent an AI provider from processing a submitted text. Data minimisation and an appropriate model route provide additional protection.
At rest: AES-256-GCM for stored secrets
AI Link uses application-level AES-256-GCM for stored credentials and secrets, including access tokens for connected services. AES-256 uses a 256-bit key. GCM adds an authentication tag that allows alterations to the encrypted content to be detected.
This layer is distinct from encryption of entire disks or databases. It is also not end-to-end encryption against the processing service: authorised processes need access to carry out their work.
What your IT team should ask
A transparent security architecture describes the full scope of protection: encrypted data, key management and backup restoration. Together with provider selection and access controls, this supports an informed technical assessment.
- Review transport, storage and processing separately
- Limit key access to services that need it
- Test recovery and key changes together
Sources & further reading
Original research, provider documentation and further reading on the concepts and figures discussed here.