01.01.2013 Views

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Web</strong> filtering<br />

Media type filtering 6<br />

Media type filtering properties<br />

Most of the media type filtering rules in a library rule set use the MediaType.EnsuredTypes property.<br />

There are several other properties, however, which let rules behave differently when included in their<br />

criteria.<br />

There is, for example, the MediaType.NotEnsuredTypes property. If you use this property in the criteria<br />

of a blocking rule, the rule blocks media whose types are on a blocking list even if the probability that<br />

they actually are of this type is less than 50%. You could do this if you wanted to make sure a media<br />

type gets blocked under all circumstances.<br />

The following table lists the properties of the rules in a library rule set for media type filtering.<br />

Table 6-8 Media type filtering properties<br />

Property Description<br />

MediaType.EnsuredTypes Property of media that have their types ensured with a probability of more than<br />

50%<br />

This level of probability is assumed if a media type signature from an internal list<br />

on the appliance can be found in the object code of the media.<br />

MediaType.NotEnsuredTypes Property of media for which the probability that they actually are of their respective<br />

types is less than 50%<br />

MediaType.FromFileExtension Property of media for which types are assumed based on the extensions of the<br />

media type file names<br />

Extensions and the media types associated with them are looked up in an internal<br />

catalog on the appliance. There are, however, extensions that are used by more<br />

than one media type.<br />

MediaType.FromHeader Property of media for which types are assumed according to the content type field<br />

of the headers sent with the media<br />

Headers are read and evaluated in a standardized format. To filter headers in their<br />

original formats, you can use the Header.Get property.<br />

MediaType.IsSupported Property of embedded or archived media that can be extracted by the opener<br />

module of the appliance.<br />

List.OfMediaType.IsEmpty Property of media with types that are not on an internal list<br />

For information on other properties, see the List of properties in the appendix. For a procedure to let a<br />

rule use a different property, see Modifying a media type filtering rule.<br />

Processing data in MIME format<br />

<strong>Web</strong> objects can be filtered on the appliance when they are multi-part objects transmitted in MIME<br />

(Multi-Purpose Internet Mail Extension) format, which is used for data sent in POST messages. Several<br />

MIME type filtering properties are available for configuring within filtering rules.<br />

The MIME format provides a header and header parameters for each part of a multi-part object, for<br />

example, for each member of an archive. The information contained in a MIME header and its<br />

parameters specifies the type of the object in question. The format is also known as<br />

multipart/form-data format.<br />

You can use the Composite Opener module of the appliance in a rule to open multi-part objects that are<br />

transmitted in MIME format and extract individual parts from it. You can then block or allow these parts<br />

depending on whether a particular header or header parameter is sent with them, or depending on the<br />

value that a header or header parameter has.<br />

You can set up rules for this using special MIME data filtering properties. These rules are similar to the<br />

ones you can use for media type filtering.<br />

<strong>McAfee</strong> <strong>Web</strong> <strong>Gateway</strong> <strong>7.1.5</strong> <strong>Product</strong> <strong>Guide</strong> 201

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!