Not yet. Slack has not publicly announced post-quantum cryptography support. All Slack communications use TLS with classical key exchange, and Slack does not offer end-to-end encryption.
Key Takeaway: Slack is NOT quantum safe. Scan your Slack integrations with QScout. Review data retention policies to limit HNDL exposure window. Consider Slack Enterprise Key Management (EKM) for additional control. Monitor Salesforce Trust for PQC announcements.
Slack is NOT quantum safe today. **Current State:** Slack uses TLS 1.2 for all connections between clients and Slack servers. Messages are encrypted in transit and at rest (AES-256), but Slack does NOT offer end-to-end encryption — Slack (Salesforce) can access message content server-side. **PQC Progress:** Slack (now owned by Salesforce) has not publicly disclosed PQC migration plans: - **TLS**: Classical RSA/ECDSA key exchange for all connections. - **Enterprise Key Management (EKM)**: Available for Enterprise Grid — uses classical key wrapping. - **No E2EE**: Unlike Signal or WhatsApp, Slack does not offer end-to-end encryption, meaning PQC for Slack requires server-side migration by Salesforce. **HNDL Risk:** Slack channels contain years of institutional knowledge, code snippets, credentials (despite policies against it), strategic discussions, and customer data. The long-lived nature of Slack message archives makes HNDL risk particularly severe. **What Organizations Should Do:** Audit Slack integrations, bots, and webhook configurations. Consider data retention policies to limit HNDL exposure. Use QScout to discover all communication platform cryptographic dependencies.
| Full Name | Slack (Salesforce) |
| Category | communication |
| Quantum Vulnerability | All Slack TLS connections use classical key exchange (RSA/ECDH) vulnerable to quantum attack. No E2EE means PQC migration depends entirely on Salesforce/Slack server-side changes. |
| NIST Status | Slack/Salesforce has not publicly announced alignment with NIST PQC standards. |
| Deprecation Timeline | Slack/Salesforce has not published PQC migration timelines. |
| Replaced By | Slack TLS will need to migrate to ML-KEM for key exchange when Salesforce deploys PQC support |
Scan your Slack integrations with QScout. Review data retention policies to limit HNDL exposure window. Consider Slack Enterprise Key Management (EKM) for additional control. Monitor Salesforce Trust for PQC announcements.
QScout discovers every instance of Slack across your infrastructure in 7 days — with zero operational disruption. 72-hour time to first findings.