Table of Contents
Advertisement
Configuring Custom Policy Fields
Copyright © 2010, Juniper Networks, Inc.
Click the Add icon. The New URL Entries dialog box appears. Enter your configuration
4.
changes, then repeat to add a second URL Entry.
For the first URL entry, enter www.games1.com then click OK.
For the second URL entry, enter www.games2.com then click OK.
Click OK to save the new Custom List.
5.
Predefined Categories
The security devices can use the predefined SurfControl Web categories to determine
the category of a URL. SurfControl Content Portal Authority (CPA) servers maintain a
large database of web content classified into approximately 40 categories.
To view the predefined SurfControl Web categories, select Web Filtering (Integrated)
> Web categories > Predefined Categories.
Custom Policy Fields objects represent metadata information that you can store and
use in a structured manner. Users can add custom objects to the policy table, such as
ticket Number, vendor contact, and so on, for each rule in the rulebase. NSM provides a
shared object to store these custom detail data while the table contains a column that
corresponds to these custom details.
The Custom Detail column (visible in Expanded Mode and hidden in Compact Mode)
captures the information about the rule, but does not push the information to the device.
The column is able to display multiple shared objects in each cell.
This allows for a better filtering mechanism for the information, reduces data redundancy
(in the case where all rules need to have the same e-mail address associated with them),
and provides multiple properties for user's needs.
The custom detail object is user configurable. The metadata is designed to capture the
following information about each object:
Name -- Determines to which definition of the metadata the objects need to comply.
Required -- Indicates if the metadata for a custom detailed object is defined with the
"Required" option set to true, all rules in all rulebases that do not have a value selected
for this MetaData displays the yellow warning triangle with a warning message. The
policy will not be saved if no value is provided.
Validation String -- A shared object definition in the metadata requires the user to
select from a list of Custom Detail objects. A String definition in the metadata allows
the user to enter a plain test string. Each instance supports no more than a single string
value.
Field Type -- If a regular expression is provided in the definition of an object, the custom
detail object is validated against the regular expression. This is required and the custom
object instance cannot be saved until this expression is satisfied.
Comments -- This column allows the user to input any comments associated with the
new object.
Chapter 8: Configuring Objects
379
Advertisement
Table of Contents
