Post-Quantum Cryptography (PQC)
Files.com plans to introduce post-quantum cryptography across the platform as protocol, client, and library support matures. There is no specific deployment date. Evaluate current encryption requirements against the encryption and key-management controls in use today; the transition plan below does not establish that every connection already uses PQC.
Public-key cryptographic schemes such as RSA and elliptic curve cryptography rely on mathematical problems that a sufficiently capable quantum computer could solve efficiently. This matters when your organization needs files and exchanges to remain confidential for many years.
The National Institute of Standards and Technology (NIST) has standardized post-quantum algorithms, including ML-KEM for key establishment and ML-DSA for digital signatures. These are designed to resist both classical and quantum computing attacks.
Our Approach and Plans
Deploying PQC requires compatible protocol implementations, browsers, operating systems, file transfer clients, and cryptographic libraries. A standardized algorithm alone does not make a connection interoperable.
Files.com will launch PQC support across the platform, covering encryption in transit via HTTPS, FTPS, SFTP, and other endpoints, as soon as ecosystem support is sufficiently mature. The implementation will follow NIST-approved algorithms and industry best practices for performance, compatibility, and long-term trust.
Files.com will continue to support legacy ciphers where compatibility is required. Customers configure SFTP cipher compatibility for the whole site.
For encryption at rest, Files.com uses Amazon Web Services (AWS) encryption capabilities and plans to adopt its PQC tooling as it becomes available. As part of that transition, Files.com will re-encrypt existing data as quickly as practical.