Policy Guide › What Is in a User Policy? › Actions › Data In Motion Actions

Data In Motion Actions

Data In Motion actions let you control files being moved across a network, copied to removable devices or sync folders, or sent to a printer. They can also control HTTP requests, such as attempts to post files or comments to web sites.

In most cases, you can block and categorize the files. For files being copied to removable devices, network locations, and sync folders, you can also force or advise users to encrypt unencrypted files. The full range of actions is summarized below.

• Blocking files: You can block a file or document. The blocking is either silent, or the user is shown an advisory dialog.

  When a file is blocked, CA Data Protection displays an advisory dialog. For example, the advisory is shown if a user tries to print an unauthorized file or copy it to a USB device.

• Warning users: If required, you can warn users when, for example, they try to print a file. If the user chooses to continue, CA Data Protection records the fact that they did this despite being explicitly warned against doing so.

  Note: Warnings are not supported for events detected by the NBA or Client Network Agent.

• Encrypting files: You can set up a control action to encrypt an unencrypted file when a user attempts to copy it to a target such as a removable device or sync folder. CA Data Protection also copies an encryption utility to the target. This utility enables the user to decrypt the file when they want to copy it from the target onto another computer.

  Note: CA Data Protection cannot encrypt files being copied to network locations. Do not use Advise Encryption or Enforce Encryption control actions to prevent unencrypted files being copied to shared locations on your network.

• Categorizing files: You can set up a control action to automatically categorize files. You define the categories in Data In Motion triggers (for example ‘Sales Contract’).
• Silent monitoring: If required, you can silently record each occurrence when an file triggers a control action, but without blocking the file or displaying a warning. The user is completely unaware that their activity triggered a control event.
• Capturing files: Data In Motion 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 In Motion control action can also invoke a capture action.