Skip to main content

What Gets Scanned

Malware Scanning checks files uploaded into a folder. Whether a given file is checked depends on how it was written to the folder.

What Counts as an Upload

Files.com scans a file uploaded into a protected folder through any interface, including the web interface, the Desktop App, the Files.com CLI, the API and SDKs, and the file transfer protocols. It also covers uploads from outside your user base, through an Inbox or an upload-enabled Share Link. Files that a Sync delivers into a protected folder are scanned as well.

When the folder is a configured Remote Server Mount, Files.com scans the file before writing it to the remote server. An infected file is never written to your remote storage or your partner's server.

Where the Scan Runs Among Your Other Folder Settings

When a protected folder has other Folder Settings on it, Malware Scanning runs after the settings that organize, limit, and rename uploads, and before GPG Encryption, GPG Decryption, and Auto Unzip. The scan inspects the file contents as they were uploaded, before Files.com encrypts, decrypts, or unzips the file.

If the folder also has GPG Decryption, the scan inspects the encrypted file, so the result does not cover the decrypted contents. Files.com decrypts the file after the scan.

GPG Encryption is not affected. The file is uploaded as plaintext, the scan inspects it, and Files.com encrypts it afterwards.

If the folder also has Auto Unzip, the scan checks the archive first. Files.com extracts it only when the scan finds no threat.

Writes That Are Not Scanned

Files are not scanned in these three cases:

  • The Remote Server folders under _/RemoteServers in the underscore folder. Folder Settings cannot be configured on them.
  • The Child Site folders under _/Sites. Folder Settings cannot be configured on them either.
  • Writes made directly to your external storage, outside Files.com. A file that another system writes to your S3 bucket or SFTP server is listed in the mounted folder without a Files.com upload, so it is not scanned.

Offset and Append Uploads Are Rejected

Malware Scanning needs a complete file, so an upload that writes a file in place across multiple requests is rejected. An offset or append upload into a protected folder fails. Upload the complete file instead.