Source
Encryption, key custody & recovery — found from sitemap — Files.com
Checked for Files.com on 17 Nov 2026
- Page
- https://www.files.com/security-reference/data-handling-and-encryption/transfer-encryption-and-algorithms
- Checked
- 17 Nov 2026, 11:44 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:c2290ad37ce5170dda82d636cb8e2a85af49777252b71b89811fd0168c565bb7
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Sftp algorithms mac sha1 Report an error
“Files.com's supported SFTP algorithms include this MAC for client compatibility.”
-
Ftps cipher preference Report an error
“For FTPS, Files.com's server preference determines which mutually supported cipher suite is selected, with AES-GCM preferred over AES-CBC.”
-
Ssh negotiation Report an error
“For SSH, the client's preference order determines the selected encryption and message authentication algorithms among the choices the server accepts”
-
Cipher reporting Report an error
“Files.com provides current and historical cipher reporting to identify the algorithms used by your clients.”
-
Ftps cbc support Report an error
“Files.com's FTPS cipher list includes AES-CBC for integrations whose clients cannot negotiate GCM.”
-
Ftps cbc mac then encrypt Report an error
“Files.com's FTPS implementation uses MAC-then-encrypt for CBC, with the padding and timing protections described above.”
-
Sftp legacy setting Report an error
“The SFTP Ciphers setting can expand the algorithms permitted on a site.”
-
Ciphers setting before auth Report an error
“Algorithm negotiation occurs before user authentication.”
-
Sftp hostkey separate Report an error
“An SFTP server host key is separate from an SSH key used to authenticate a Files.com user.”
-
Wildcard certificate limitation Report an error
“A wildcard certificate does not make every matching hostname a configured Files.com domain.”
-
Custom domain cname Report an error
“For a customer-provided certificate, use the exact CNAME destination shown in the Custom Domain interface; do not infer it from the site's first domain.”
-
Tls12 cbc fresh iv Report an error
“TLS 1.2 uses a fresh initialization value for each CBC record, avoiding the predictable record chaining used by TLS 1.0.”
-
Plan files com Report an error
From the vendor’s structured data (JSON-LD) on https://www.files.com/security-reference/data-handling-and-encryption/transfer-encryption-and-algorithms, captured 17 Nov 2026
{ "offers": { "@type": "Offer", "price": "199", "priceCurrency": "USD" } } -
Platforms Report an error
From the vendor’s structured data (JSON-LD) on https://www.files.com/security-reference/data-handling-and-encryption/transfer-encryption-and-algorithms, captured 17 Nov 2026
{ "operatingSystem": "Web, Windows, macOS, Linux, iOS, Android" }
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Agency Producer Encryption, key custody & recovery
- The Data Protection Officer Encryption, key custody & recovery
- The Skeptic Encryption, key custody & recovery
- The Tax Adviser Encryption, key custody & recovery