Scan Bypass

The Scan Bypass feature lets you transfer pre-encrypted or password-protected files through CFT without malware scanning. It’s mainly used for Sensitive-High data transfers and supports files with special encryption types. When Scan Bypass is not enabled, CFT scans files using malware scanning by default.

Note: If you are sending files that are Sensitive-Normal or below, you are not required to use the Scan Bypass feature.

When to use Scan Bypass:

• You are transferring Sensitive-High data that must remain encrypted. In this case, you must enable the Sensitive-High Transfers feature, which will automatically turn on Scan Bypass.
• Your files exceed standard malware scanning limits, such as maximum archive size or number of files within an archive.
• You are using encryption types that are not supported by CFT.
• You have special encryption requirements, such as non-MDC PGP or SLIFT signatures.
• You are sending a zipped or archived file containing more than 1,000 files (scanner limitation).

Important: When Scan Bypass is enabled, the following CFT functions are disabled: malware scanning, CFT encryption, CFT decryption and CDR.

Prerequisites

Before proceeding:

• Ensure that the Sender has files that are either pre-encrypted or password-protected before sending.
• Ensure that the encryption type used to encrypt files is supported. View supported encrypted file types.

Important: For OpenPGP-encrypted files, ensure the encryption packets are version 4. Legacy version 3 PKESK packets may be misclassified by CFT and can fail processing with FileBypassFailed. You can verify with gpg --list-packets <file> — check that the symkey/public-key encrypted packet shows version 4.

Set up Scan Bypass

To enable Scan Bypass in a transfer, follow these steps: