Policy Guide › Categorizing Events › Add Categorization to Existing Triggers

Add Categorization to Existing Triggers

You can incorporate categorization into any of your existing email, Data At Rest, or Data In Motion control triggers. CA DataMinder event categorization has been designed to integrate with your existing user policies with minimum disruption.

For example, if you already have a warning trigger that activates when a user sends an email to an unauthorized recipient, you can include an appropriate category, or a range of possible categories, in the trigger.

1. Set up a new categorize action. But see the recommendations about the control action number.

   The sole purpose of this categorize control action is to ensure that category smart tags are saved with the event on the CMS if an existing trigger fires. Without this new control action, adding categorization to your existing triggers will not work.

   In your chosen control action:

   1. Set the Intervention setting:
      • For Data At Rest control actions, choose 'Categorize'.
      • For E-mail or Data In Motion control actions, choose 'Categorize: single category only' or 'Categorize: multiple categories allowed'.
   2. Disable email and file capturing in the new control action. This ensures that emails and files are only captured if an existing trigger fires. Set the following settings to False:
      • Capture Authorized Activity?
      • Capture Prohibited Activity?
2. Modify your existing triggers to support categorization.

   For each applicable trigger, edit the Message To Users setting so that its existing message is retained (for example, a warning that the current email may be non-compliant, or a notification that the original file has been replaced) but appended with a relevant category.

   You do not need to change the existing Control Action trigger setting.

3. Add a single new email control trigger that explicitly invokes the categorize control action. Without this new trigger, categorization will not work.
   1. Set the general trigger criteria. These must be sufficiently flexible so that the trigger always fires when your existing triggers fire. For example, you can set up a recipient-based trigger that fires when the recipient matches '*' (that is, the trigger will always fire).
   2. Edit the Smart Tags setting to include a categorization variable such as %category%.
   3. Skip this step if adding a Data At Rest trigger. If adding an email or Data In Motion trigger, edit the Message To Users setting. You need to add an explanatory message. You do not need to specify any categories; these are now specified in your existing triggers (step 2 ). In terms of syntax, you need only add the <dialog text>, but without double quotes and without a trailing = symbol.
   4. The new trigger must point to the categorize control action that you set up in step 1. Set the Control Action setting accordingly.