Deployment Guide › Client Agents: File and Print › Deploy the CFSA › Configure the User Policy › Data At Rest Triggers

Data At Rest Triggers

The general trigger settings let you specify which types of document you want the CFSA to scan. For example, you can edit the triggers to detect specific file formats (such as Microsoft Word documents). They can also analyze a file’s text content. For information about these general trigger settings, see the Administration console online help.

This section focuses on the key Data At Rest settings for the CFSA. Specifically, you need to edit the following settings in the Data At Rest capture and control triggers:

• Which File Sources?

  In each Data At Rest trigger, this setting instructs the trigger to process files or documents captured or scanned by any of the following:

  • Client File System Agent
  • File Scanning Agent
  • File Importer
  • External Agent API for File

  You must ensure that the Client File System Agent check box is selected! This enables the trigger to analyze local files scanned by the CFSA.

• Top Level File Lists

  All Data At Rest triggers include Top Level File Lists. Use these lists to detect normal files or zip files. You edit these lists to identify the names of files that you want to apply policy to when a scan runs. For example, you can specify:

  • * to analyze all files
  • *.docx to analyze all .docx files
  • A list of specific .zip files to analyze.

  For each trigger, you can choose whether to use an Included, Excluded or Ignored file list.

• Individual/Embedded File List

  If required, Data At Rest triggers can look for files contained within a zip file or embedded in a master file. To do this, edit the Individual/Embedded File Lists. For each trigger, you can choose to use an Included or Excluded file list.

  Using these lists in conjunction with the Top Level File Lists, you can feasibly search all .zip files for a specific file. For example, set Included Top Level Names to *.zip and Included Individual/Embedded File Names to *.doc to search for all .doc files contained within .zip files.

• Copy File to Location

  Data At Rest control actions also support ‘copy’ action, permitting you to copy scanned files to an alternative location. When used in combination with a ‘delete’ actions (see below), a copy action effectively becomes a ‘move file’ action.

• Intervention

  In each Data At Rest control action, the Intervention setting determines how the CFSA handles scanned files. The available options allow you to categorize delete scanned files. If necessary, you can specify DoD deletions; these ensure that deleted files cannot be recovered (see below). You can also replace deleted files with an explanatory stub file to alleviate any user concerns or categorize the resulting file event.

  Note: DoD deletion is forensic deletion, so called because the storage media are purged to guarantee that a file cannot be recovered and used to obtain evidence in legal discovery. ‘DoD’ is a reference to Department of Defense approved methods for purging storage media.