About Halo's ICAP Server

ICAP (Internet Content Adaptation Protocol) is designed to delegate tasks like virus scanning and content filtering to dedicated servers. Our ICAP server mediates between ICAP clients (such as proxy servers, firewalls, or gateways) and the Glasswall Halo service. When a file passes through the ICAP client, it is sent to Glasswall Halo for sanitization via ICAP before returning to the client.

This ensures complete protection of content traversing your zero-trust boundaries, whether incoming or outgoing from your environments. 

Why use Glasswall Halo's ICAP server?

• Setup automated file sanitization without user intervention
• Seamless integration with existing security infrastructure
• Full control over web content, ensuring your business and users are protected
• Industry standard way to support transparent inspection of traffic

Use cases

• Safety net for users opening files from seemingly trustworthy URLs
• Users uploading files of unknown origin to your servers
• Inline security with either a forward or reverse proxy workflow
• Where file sandboxes or denotation chambers degrade user experience to become unworkable

How it works

ICAP requests are split into two types:

• Response modifications where a user requests to download files or content from a server
• Request modifications where a user sends or uploads a file or content to a server

In both scenarios, files are processed by Glasswall Halo with millisecond speed and returned free from threats.

Learn more

• ICAP FAQs
• Deployment
• Integrations
• Supported Media Types
• ICAP Profiles