Policy Guide › What Is in a User Policy? › Actions › Data At Rest Actions

Data At Rest Actions

Data At Rest actions let you control scanned and imported files. You can delete specified items, replace them with explanatory 'stub' files, copy or move them to a new location, or simply categorize the files. CA DataMinder supports the following actions:

• Deleting files: If required, you can silently delete scanned files. From a user’s viewpoint, they will only be aware that their file no longer exists when they next try to view it. You can still capture, copy or move the original file.
• DoD Overwriting and Deleting: You can use DoD deletions to ensure deleted files cannot be recovered. From a user’s viewpoint, they will only be aware that their file no longer exists when they next try to view it. You can still capture, copy or move the original file.

  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 refers to the U.S .Department of Defense approved methods for purging storage media.

• Replacing files: You can delete scanned files and replace them with an explanatory stub file to alleviate any user concerns. This explanatory message is defined in the Data At Rest trigger. For example, you can inform a user that their file was inappropriate and has been removed to a new location. You can still capture, copy or move the original file.
• DoD Overwriting and Replacing: You can use DoD deletions to delete files and replace them with an explanatory stub file. You can still capture, copy or move the original file.
• Moving or copying files: You can copy scanned files to an alternative location. You can combine Copy and Delete operations to effectively move scanned files to a new location.
• Categorizing files: You can set up a control action to automatically categorize files. You define the categories in Data At Rest triggers (for example ‘Sales Contract’).
• Capturing files: Data At Rest capture actions let you specify how much file detail is captured. For example, you can capture the file itself, or just its metadata (file attributes), or both.

  Any Data At Rest control action can also invoke a capture action.