About record views

You must create record views to use in a content filtering policy condition. You use views to specify which fields or combinations of fields in a record you want Symantec Messaging Gateway to match in a message.
You can create one or more views from a record. The benefit of multiple views is that you can create several conditions for a policy, and each condition can use a different view. Multiple views also let you use the same record for several different policies, and each policy can use a different view.
The
Record Resource Views
page lists all of the views that you have created. This page indicates the number of fields that you have selected for the view. It also shows the number of policies that use that view as a condition.
How to configure a record view describes the options that you use to create a view. It also provides an example. For the sake of our example, assume that Record A exists. Also assume that Record A and View A are used in a content filtering policy that is enabled.
How to configure a record view
Option
Description
Example
View Name
You should specify a unique name that describes the purpose of the view.
In our example, the view is named View A.
Field Selection
When you create a view, all of the fields that you mapped for that record appear in the
Fields
list on the
Add Record Resource page
. You specify which fields you want to use in the view.
Assume that Record A consists of the following fields:
  • Credit card number pattern
  • Email pattern
  • IP address pattern
  • Number pattern
  • Percent pattern
  • US phone pattern
  • US ZIP code pattern
  • SSN/ITIN pattern
Now assume that you select the following fields for this view:
  • Credit card number pattern
  • Email pattern
  • IP address pattern
  • US phone pattern
  • US ZIP code pattern
  • SSN/ITIN pattern
Minimum number of matched selected fields required for an occurrence
This option specifies how many of the fields in your view must appear in a message to constitute an "occurrence."
For example, assume that you select six fields for your view, and the
Minimum number of matched selected fields required for an occurrence
is four. If any of the four (or more) fields that you selected are found in a message, Symantec Messaging Gateway considers it an occurrence.
An occurrence is not a violation. When you create a policy that uses this view, you can specify how many occurrences can occur in a message before the policy is violated.
Assume that you specify the
Minimum number of matched selected fields required for an occurrence
as three. A message that meets or exceeds three matches is considered an occurrence.
So if the only match in a message is
Email address pattern
, there is no occurrence.
If the only match in a message is
Email address pattern
and
US phone pattern
, there is no occurrence.
However, if a message contains matches for
Email address pattern
and
US phone pattern
, and
SSN/ITIN
pattern, the result is an occurrence.
Exception Combinations
Specific combinations of fields may be acceptable in a message. So Symantec Messaging Gateway lets you exclude the combination of fields from being considered a match.
You can create multiple exceptions.
Assume that you create an exception that consists of
US phone pattern
and
Email address pattern
. If Symantec Messaging Gateway detects this combination of fields in a message, it does not consider it an occurrence.
Example 1
A message contains the following matches:
  • Email address pattern
  • US phone pattern
  • SSN/ITIN pattern
No occurrence is detected because the combination of
US phone pattern
and
Email address pattern
is permitted. Therefore, the only matches are: (1)
SSN/ITIN pattern
and
US phone pattern
, and (2)
SSN/ITIN pattern
and
Email address pattern
. Both matches have only two patterns, which are less than the threshold of three patterns.
Example 2
A message contains the following matches:
  • Email address pattern
  • US phone pattern
  • SSN/ITIN pattern
  • US ZIP code pattern
An occurrence is detected. Though the combination of
US phone pattern
and
Email address pattern
is permitted, their combination with other patterns is not permitted. Hence the matches with the following patterns exists: (1)
Email address pattern
,
SSN/ITIN pattern
, and
US ZIP code pattern
; (2)
US phone pattern
,
SSN/ITIN pattern
, and
US ZIPcode pattern
.
Example 3
A message contains the following matches:
  • US phone pattern
  • SSN/ITIN pattern
  • US ZIP code pattern
  • IP address pattern
An occurrence is detected. The message contains four matches, which exceed the threshold for an occurrence and none of the matches are an exception.