After setting up your content agents and building the content indexes, you must assign the agents to triggers in your user policies. These triggers fire when they detect a file that matches a fingerprint in the content agent's index.
You also need to give these triggers distinctive names and, typically, an appropriate policy class. This enables reviewers to easily search for fingerprinted files captured or blocked by CA DataMinder.
Follow these steps:
For email triggers, you can only assign content agents to a Content Agent trigger.
For Data In Motion and Data At Rest triggers, you can assign content agents to any trigger.
Reviewers will search for 'fingerprint events' using these trigger names and policy classes.
Copyright © 2014 CA.
All rights reserved.
|
|