AWS wickr: Document Wickr serverless data retention encryption architecture
Summary
Added a diagram and step-by-step description of serverless data retention: end-to-end encrypted messages routed through Wickr Message Routing, decrypted and re-encrypted inside an AWS Nitro Enclave using a customer managed KMS key accessed via a cross-account IAM role, stored in the customer's encrypted retention S3 bucket, with on-demand decryption into a separate S3 bucket and CloudWatch monitoring.
Security assessment
New architecture documentation that describes cryptographic controls (E2E encryption, Nitro Enclave isolation, customer managed KMS keys), least-privilege cross-account IAM role use, ciphertext-only relay to the enclave, and CloudWatch monitoring of the retention bucket and key. It adds security-relevant architecture guidance but addresses no specific vulnerability or incident, so medium.
Evidence
A Wickr client sends an end-to-end encrypted message through Wickr Message Routing. Within the AWS Nitro Enclave, Wickr decrypts messages and re-encrypts them with your customer managed KMS key before sending them to your encrypted retention Amazon S3 bucket.
Diff
diff --git a/wickr/latest/adminguide/architecture.md b/wickr/latest/adminguide/architecture.md index 2580023..78989ae 100644 --- a//wickr/latest/adminguide/architecture.md +++ b//wickr/latest/adminguide/architecture.md @@ -12,0 +13,34 @@ This guide documents the new AWS Wickr administration console, released on March +The following diagram shows the components of serverless data retention and which account each one runs in. Wickr Message Routing and the Nitro Enclave run in the Wickr-managed service account. Your AWS KMS keys, the cross-account IAM role, the retention and decrypted Amazon S3 buckets, the on-demand decryption workflow, and CloudWatch monitoring run in your account. + +A Wickr client sends an end-to-end encrypted message through Wickr Message Routing. Within the AWS Nitro Enclave, Wickr decrypts messages and re-encrypts them with your customer managed KMS key before sending them to your encrypted retention Amazon S3 bucket. The service uses your key through the cross-account IAM role. For more information, see [Where data retention components run](./serverless-method.html#where-components-run). + + + +The numbered steps in the diagram show how every message is retained: + + 1. A Wickr client sends an end-to-end encrypted copy of the message to the data retention bot user, through Wickr Message Routing. + + 2. Wickr Message Routing fetches the Data Retention Service keys, which are stored encrypted with your KMS key. It sends them with the ciphertext to the enclave host. + + 3. The enclave host assumes the cross-account IAM role in your account. The host relays only ciphertext to the Nitro Enclave. + + 4. The enclave uses your KMS key to decrypt the Data Retention Service keys. Wickr then decrypts the message and re-encrypts it with your customer managed KMS key. + + 5. The encrypted message is stored in your retention Amazon S3 bucket. + + + + +The lettered steps show on-demand decryption, which runs only when you start it: + + 1. Your compliance team starts the decryption workflow for a date range. + + 2. The workflow reads the encrypted objects from the retention bucket and decrypts them with your KMS key. + + 3. The workflow writes the decrypted output to the decrypted Amazon S3 bucket in your account. + + + + +CloudWatch monitors the retention bucket and your KMS key. +