Previous Topic: Plain Text Embedded File Agents Are SupersededNext Topic: Using Content Agents to Detect Spreadsheets


Using Content Agents to Detect Printed Files

CA DataMinder content agents can usually detect when a user tries to print a protected file. When this happens, the content agent invokes a Data In Motion trigger to, for example, block the print job. However, there are some limitations depending on the file type:

Text files

These include Microsoft Word and PDF documents.

Content agents can detect when a user tries to print extracts from a protected text file. However, an agent can only do this if it is configured to detect emails or files containing at least two-thirds of the text content from a protected document.

In practical terms, this means that the agent's Evaluation properties must use the 'Detect documents or their derivatives' method with the percentage similarity set to 70% or lower.

Note: If you choose a percentage similarity higher than 70%, the agent will be unable to match a print job to a protected document because of the presence of extra data such as print headers.

Spreadsheets and tables

These include Microsoft Excel files and information stored in tables in Microsoft Word documents.

Content agents cannot detect when a user tries to print a protected spreadsheet. Likewise, they cannot detect when a user tries to print a table copied from a protected file.

Images

These include Microsoft Visio drawings and all other image files, including PNGs, GIFs, and JPEGs.

Content agents cannot detect when a user tries to print protected Visio drawings or other images.

Presentations

These include Microsoft PowerPoint files.

Content agents can detect when a user tries to print slides from a protected presentation. However, if the slides have a decorative background, such as an image, this can sometimes interfere with the agent's ability to detect the text content. In turn, this may mean that policy triggers do not fire.