Competitor MappingReference node
Default server-side encryption
Competitor mapping for Google Cloud Platform.
This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.
Details
- Provider
- Google Cloud Platform
- Service term
- Default server-side encryption
- Provider documentation
- External reference
Behavioral divergences
Default server-side encryption
Quake AI concept: Encryption
- GCP always-on AES-256-GCM Google-managed (no config), +CMEK/CSEK; Swift optional proxy middleware (keymaster+encryption), AES-256-CTR on body/ETag/user-meta (plaintext client→encrypt cluster), requires root secret config/daemon.
- GCP encrypts metadata/checksums; Swift selective (no names/size/sysmeta).
- GCP auto decrypt reads; Swift decrypts GET/HEAD w/ keymaster.
- GCP client optional; Swift recommends client-side for transit+storage.
Related
Diverges from (incoming)
Citations
- Google Cloud Platform
- Google Cloud Platform
These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.