When PortalProtect finds a word that matches a keyword in a content filter policy, it can take action to prevent the undesirable content from being posted to SharePoint. You can configure PortalProtect to send notifications whenever it takes an action against undesirable content.
Each PortalProtect Content filtering policy contains a list of keywords, phrases, or compliance patterns. Compliance patterns can be associated with credit card numbers, Social Security Numbers, and country specific identification information. PortalProtect is now fully integrated with Active Directory (AD) user(s)/group(s), and SharePoint user(s)/group(s). Policies can be applied to the following:
Active Directory user(s)/group(s)
SharePoint site(s)/SharePoint user(s)/group(s)
Real-time content filtering for documents—filters the content of documents uploaded or downloaded to SharePoint document libraries in real-time.
Real-time content filtering for Web content—filters the Web content for SharePoint Lists when you create a new item or update an existing one (for example: Tasks, Links, Calendar, Announcements, and so forth).
PortalProtect applies the content filtering policies according to the order shown in the Content Filtering screen. You can configure the order in which the policies are applied. PortalProtect will perform filtering according to each policy until a content violation triggers an action that prevents further scanning (such as block or pass). You can change the order of these policies to optimize content filtering. Additionally, the content filter provides a synonym checking feature that enables you to extend the reach of your policies.
Content filtering for files scans during
uploading and downloading, whereas content filtering for Web scans list
items when they are added or modified.
Content filtering for files cannot scan the content of .eml
files.
Credit card numbers and country specific identification information
Sexually harassing language
Racist language
Profanity
For Active Directory integrated policies, you can specify selected Active Directory User(s) and Group(s) as policy excluded accounts. For example, consider that AD Group1 contains an exclusion for ADuser1 and ADuser2. In this case, ADUser1, and ADUser2 will be excluded according to the AD Group1 policy. For SharePoint user(s) and Group(s) integrated policies, you can specify selected SharePoint site(s) and user(s)/group(s) within the site(s).
PortalProtect and MOSS 2010/WSS 4.0 provides real-time policy exceptions. MOSS 2007/WSS 3.0 does not provide for this functionality.
Exclusion only works in an AD environment. The Exception list does not support AD users/groups across the forest and also does not support global AD groups.