Speed alone, however, is dangerous. A fast pipe for insecure data merely accelerates the delivery of malware, sensitive leaks, or non-compliant content. This is where Clearswift’s heritage as a leader in becomes critical. Embedded within the FileCatalyst transfer engine is Clearswift’s Deep Content Inspection (DCI) . Unlike superficial virus scanning, DCI looks inside files—unpacking zip archives, stripping macros from Office documents, redacting PII (Personally Identifiable Information) from PDFs, and detecting classified keywords in text. The system can act adaptively: block a threat, redact a social security number, or encrypt the payload based on destination zone. Critically, all of this occurs in-transit , without requiring the receiving endpoint to install complex agents.
| Metric | Without FileCatalyst (TCP only) | With FileCatalyst (UDP) | With Clearswift + FileCatalyst | | :--- | :--- | :--- | :--- | | | 2–3 hours (fails often) | 8–12 minutes | 9–13 minutes (+5% overhead for inspection) | | Security Inspection | 100% buffering required | 0% buffering (streaming) | 10% buffering (metadata only) | | Packet Loss tolerance | 1% loss = 90% speed drop | 10% loss = 80% speed preserved | Same as FileCatalyst |
Speed alone, however, is dangerous. A fast pipe for insecure data merely accelerates the delivery of malware, sensitive leaks, or non-compliant content. This is where Clearswift’s heritage as a leader in becomes critical. Embedded within the FileCatalyst transfer engine is Clearswift’s Deep Content Inspection (DCI) . Unlike superficial virus scanning, DCI looks inside files—unpacking zip archives, stripping macros from Office documents, redacting PII (Personally Identifiable Information) from PDFs, and detecting classified keywords in text. The system can act adaptively: block a threat, redact a social security number, or encrypt the payload based on destination zone. Critically, all of this occurs in-transit , without requiring the receiving endpoint to install complex agents.
| Metric | Without FileCatalyst (TCP only) | With FileCatalyst (UDP) | With Clearswift + FileCatalyst | | :--- | :--- | :--- | :--- | | | 2–3 hours (fails often) | 8–12 minutes | 9–13 minutes (+5% overhead for inspection) | | Security Inspection | 100% buffering required | 0% buffering (streaming) | 10% buffering (metadata only) | | Packet Loss tolerance | 1% loss = 90% speed drop | 10% loss = 80% speed preserved | Same as FileCatalyst | clearswift filecatalyst