-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
featureNew feature or requestNew feature or requestresearchPreliminary research and testingPreliminary research and testing
Description
Implement encryption in transit (TLS) and at rest for our chat messages and user metadata.
Update:
GDPR does not explicitly require encryption at rest or in transit. But they are one of the primary ways to demonstrate compliance. In Article 32 it mentions "appropriate technical and organisational measures". Those measures should ensure:
- Confidentiality
- Integrity
- Availability
- Resilience of processing systems
Encryption in transit (TLS) is required in practice because it would be hard to say that we used "appropriate" measures.
Encryption at rest is not explicitly required, but often required depending on risk. There are a few types of encryption at rest:
- Disk/Infra encryption - Encrypted volumes or databases
- Application-level encryption - Messages encrypted before storing in DB (Latency cost)
- End-to-end (E2E) encryption - Maximum privacy, not required by GDPR, hard features
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
featureNew feature or requestNew feature or requestresearchPreliminary research and testingPreliminary research and testing