Conversation

Ticket

Paste this into your ticketing tool.

Add an encryption details section to /security

Who needs it: CTOs and IT or security reviewers checking a vendor
Section: /security › Encryption (card)

What is missing:
- The encryption standard used for data at rest is not named.
- The protocol and version used for data in transit is not named.
- How encryption keys are managed and rotated is not explained.
- Whether customers can bring or manage their own keys is not stated.
- Whether backups are encrypted is not stated.

Where: New section on /security, placed after "Security and control, built into every hub".
  Related sections: Encryption · Data region choice · Audit history · Security and control
  Main topics: Encryption at rest standard · Encryption in transit protocol · Key management and rotation · Customer-managed keys · Backup encryption · How to request technical security documentation

What to do:
1. Confirm with the security team and engineering the encryption standards, transit protocol, key management practice, customer-managed key options and backup encryption.
2. Add the new section to /security covering each confirmed point.
3. Link the "Encryption" card and the "Security and control" guide card on /resources to the new section.

Done when: /security names the encryption standards for data at rest and in transit and explains how keys are managed.

From: conversation 4999b8d42d38, question 1: "How about data encryption details"