Platform Deployment Guide › Content Registration › How to Set Up Content Agents › Set Up Content Agent Triggers

Set Up Content Agent Triggers

After you have published a content agent, you assign the agent to triggers in your user policies.

These triggers fire when CA DataMinder detects a file that matches a fingerprint in the content index associated with your content agent.

For example, you can set up triggers to block a protected document from being sent as an email attachment or copied to a USB device.

In technical terms, the content agent generates a fingerprint of the file and then compares this fingerprint with those in its content index. If the fingerprints match, CA DataMinder infers that the file is protected.

Follow these steps:

1. Log on to the Administration console using an account that has the 'Policies: Edit policy' administrative privilege.
2. Expand the User Administration branch.
3. Right-click a user or group and click Edit Policy.

   The User Policy Editor screen appears.

4. Select the trigger that you want to assign a content agent to.

   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.

5. Edit the Trigger Name and Policy Class settings as required.

   Reviewers can search for 'protected document events' in the iConsole or Data Management console, using these trigger names and policy classes as search filters.

6. Edit the Use Content Agents For Files? trigger setting.

   Set the value to 'Use content agents to analyze text content'.

7. Edit the Which Content Agents? trigger setting.

   Add the content agents that you want to associate with this trigger.

8. Edit other trigger settings as required.

   For example, you can assign smart tags or a severity rating to the trigger.

9. Edit the Control Action setting.

   Select the control action that you want. For example, to block protected files from being copied or sent, select a 'Block' control action. If you want users to encrypt protected files before copying or sending them, select an 'Enforce Encryption' control action.

10. Repeat steps 3 through 7 for any other triggers that you want to assign the content agent to.
11. Click File, Save to save the policy changes.

    The Policy Change Summary dialog appears.

12. Click Save.

    Your content agent is now assigned to a policy trigger. The user policy is now configured to detect any documents protected by the content agent.