Technical Library | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Refine Web Security Policies > Managing traffic based on file type
Managing traffic based on file type
Web Security Help | Web Security Solutions | Version 7.8.x
Related topics:
*
Enforcement based on file extension
*
Enforcement based on file analysis
*
Working with file type definitions
*
Adding custom file types
*
Adding file extensions to a file type
When you create or edit a category filter, you can configure file type blocking for permitted categories. This allows your organization to restrict access to particular file types from websites in some or all permitted categories. For example, you could permit the category Sports, but block multimedia (audio and video) files from sites in the Sports category.
How file type blocking is implemented depends on your Websense Web security solution.
*
Websense Web Filter and Websense Web Security (no Content Gateway or hybrid service proxy) allow you to block file types based solely on file extension (see Enforcement based on file extension).
For example:
1.
The General Email category is permitted in the active category filter, but file type blocking is enabled for Compressed Files in the category.
2.
An end user attempts to download a file with a file with a .zip extension (like "myfile.zip").
3.
The user receives a block page indicating that the download was blocked by file type, because the ".zip" file extension is associated with the Compressed Files file type.
*
Websense Web Security Gateway and Gateway Anywhere (which include Content Gateway and the hybrid service) enable 2-part file type blocking, based on a combination of file extension (see Enforcement based on file extension) and analysis of requested files (see Enforcement based on file analysis).
For example:
1.
The General Email category is permitted in the active category filter, but file type blocking is enabled for Compressed Files in the category.
2.
An end user attempts to download a file with a file with a .zip extension (like "myfile.zip").
3.
The user receives a block page indicating that the download was blocked by file type, because the ".zip" file extension is associated with the Compressed Files file type.
4.
The user attempts to download another file from email. This file does not have a known file extension (for example, "myfile.111").
5.
The file is scanned to find its file type.
*
If analysis determines that the file is in a compressed format, the user receives a block page indicating that the download is blocked by file type.
*
If analysis determines that the file is not compressed, the download request is permitted.
Combine protocol-based policy enforcement with file type enforcement to better manage Internet audio and video media. Protocol filters handle streaming media, while file type enforcement handles files that can be downloaded and then played.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Refine Web Security Policies > Managing traffic based on file type
Copyright 2016 Forcepoint LLC. All rights reserved.