Web filtering When the users of your network submit requests for web access, Web Gateway filters these requests, according to the web security policy that is implemented. The filtering process also covers responses that are sent back from the web as well as embedded objects sent with requests and responses. Default filtering Web filtering includes several fields of web security. Anti-malware filtering — Protects your network against viruses and other malware. Filtering is performed based on the results achieved by scanning web objects, for example, files sent from a web server in response to a request. URL filtering — Controls access to web objects based on evaluating their URLs. URLs are categorized and can be allowed or blocked according when categories are considered to convey inappropriate content. Media type filtering — Controls access to web objects based on recognizing the media types that they belong to., for example, to exclude downloads consuming overmuch bandwidth Extended filtering Several fields of web security belong to web filtering, for example, anti-malware filtering, URL filtering, and media type filtering. Some of them are covered by default rule sets. Global whitelisting — Excludes objects from web filtering HTTPS filtering — Filtering to exclude downloads consuming overmuch bandwidth By importing more rule sets from the built-in or the online library, you can enlarge coverage of these fields and also extend it to other fields, which are not covered by default. Application filtering — Excludes objects from web filtering Streaming media filtering — Filtering to exclude downloads consuming overmuch bandwidth Data loss prevention — Filtering to exclude downloads consuming overmuch bandwidth Anti-malware filtering Anti-malware filtering ensures that the users of your network cannot access web objects that are infected by viruses and other malware. The filtering process detects infections and blocks access accordingly. URL filtering URL filtering ensures that the users of your network cannot access web objects that are considered a risk for web security or are not allowed because they contain inappropriate subject matter or for other reasons. Media type filtering Media type filtering ensures that the users of your network can only access media belonging to types that are allowed under your web security policy. For example, access to streaming media might not be allowed because it consumes too many resources. Application filtering Application filtering ensures that the users of your network cannot access unwanted applications, which could be, for example, Facebook, Xing, and others. The filtering process application names and reputation scores and blocks access accordingly. Filtering can also be applied to individual functions of applications. Streaming media filteringStreaming media filtering ensures that web objects of this media type are detected when they are received on Web Gateway and handled according the configured rules. Global whitelisting Global whitelisting ensures that all further filtering is skipped for the web objects that are whitelisted, so access to them cannot be blocked. SSL scanning SSL scanning ensures that SSL-secured web traffic can be processed and made available to other filtering functions on Web Gateway. This scanning mode is also known as HTTPS scanning. Hardware Security Module Use of a Hardware Security Module (HSM) enhances security when dealing with private keys for the certificates that are exchanged between clients and servers in SSL-secured communication. Advanced Threat Defense After a web object has been scanned by Web Gateway for infections by viruses or other malware, it can additionally be scanned by the McAfee® Advanced Threat Defense (Advanced Threat Defense) web security product. Data loss prevention Data loss prevention (DLP) ensures that sensitive content is not allowed to leave your network. The prevention process detects this content and blocks traffic going out to the web accordingly. Using an on-premise DLP server from the cloud You can perform DLP filtering using an on-premise DLP server with an ICAP client that runs in the cloud.