We would like to request a native integration between F5 Distributed Cloud HTTP Load Balancer/WAF and OPSWAT MetaDefender for inline file security.
Our use case is to protect web applications hosted behind F5 Distributed Cloud from malicious file uploads. We currently use F5 Distributed Cloud as our HTTP Load Balancer and WAF, and we would like uploaded files to be inspected by OPSWAT MetaDefender before they are delivered to the backend application.
The desired traffic flow is:
Internet/User
→ F5 Distributed Cloud HTTP Load Balancer + WAF
→ OPSWAT MetaDefender
→ File scan / CDR
→ Allow or Block
→ Backend Application
We would like F5 Distributed Cloud to provide a native, supported integration with OPSWAT MetaDefender, preferably through ICAP/ICAPS or an equivalent native integration mechanism.
The desired functionality would include:
Ability to configure an OPSWAT MetaDefender endpoint directly from F5 Distributed Cloud.
Ability to send HTTP file uploads to OPSWAT for inspection.
Support for TLS-secured ICAP/ICAPS where applicable.
Allow/block decisions based on the OPSWAT scan result.
Configurable behavior when the OPSWAT service is unavailable or times out.
File type and file-size filtering before sending content for inspection.
Support for malware scanning and Content Disarm and Reconstruction (CDR).
Logging of the inspection result in F5 Distributed Cloud.
Visibility of the OPSWAT verdict and relevant transaction information in F5 logs/events.
High-availability and scalable handling of file inspection requests.
Support for OPSWAT MetaDefender Cloud/ICAP Cloud as well as, where applicable, customer-hosted MetaDefender deployments.
This capability would allow customers to use F5 Distributed Cloud as the application delivery and WAF layer while using OPSWAT MetaDefender as the specialized file-security layer.
We understand that OPSWAT already documents integration with F5 Distributed Cloud Services and that MetaDefender ICAP is designed for integration with WAFs and load balancers. We would therefore like F5 to consider making this integration a first-class, officially supported configuration within the F5 Distributed Cloud platform.
Could you please advise whether this capability is currently available, on the roadmap, or whether an enhancement request can be opened for it?
Thank you.