Keywords not captured in iConsole
Article ID: 131235
Updated On:
Products
CA Security Command Center
CA Data Protection (DataMinder)
CA User Activity Reporting
Issue/Introduction
As part of a Document Classification the Extract() function cane be used to extract and save attributes which fired the trigger as part of a capture or control event. Refer to the product documentation for more information.
https://docops.ca.com/ca-data-protection/15-2/en/reviewing/policy/document-classifications
The extracted attributes are highlighted in the iConsole when a triggered event is displayed.
Why does the iConsole not highlight all words in an event that match those in the policy classification?
https://docops.ca.com/ca-data-protection/15-2/en/reviewing/policy/document-classifications
The extracted attributes are highlighted in the iConsole when a triggered event is displayed.
Why does the iConsole not highlight all words in an event that match those in the policy classification?
Environment
CA Data Protection 14.x\ 15.x
Resolution
CA Data Protection employs lazy analysis. When the MinScore() criteria is met no further processing is required so no further instances of policy trigger words are captured. This is by design for performance purposes.
The scope of what ti analyze is governed by the “check which items” and the “search which sections or documents” policy trigger settings; and by whether the classifier and/or the search text test are enabled.
If the “Search which sections or documents” test is enabled (i.e. the key string test), and its scope is NOT “classified documents”; then this test is performed first (as it is assumed that this will likely be more efficient than the classifier itself).
When document classification is employed, the different parts of the mail event (Subject, Body, Attachments) are searched one at a time (as data streams), and analysis stops as soon as it finds a match.
For example, if a trigger consists of three elements Apples, Kiwi and Oranges and has a MinScore for this trigger is 1. When the classifier reviews the attachment and finds the trigger it does not need to search any further (subject or body) and it captures the instances "Oranges and Kiwi" in the database and those are the elements that it highlights in the iConsole.
The scope of what ti analyze is governed by the “check which items” and the “search which sections or documents” policy trigger settings; and by whether the classifier and/or the search text test are enabled.
If the “Search which sections or documents” test is enabled (i.e. the key string test), and its scope is NOT “classified documents”; then this test is performed first (as it is assumed that this will likely be more efficient than the classifier itself).
When document classification is employed, the different parts of the mail event (Subject, Body, Attachments) are searched one at a time (as data streams), and analysis stops as soon as it finds a match.
For example, if a trigger consists of three elements Apples, Kiwi and Oranges and has a MinScore for this trigger is 1. When the classifier reviews the attachment and finds the trigger it does not need to search any further (subject or body) and it captures the instances "Oranges and Kiwi" in the database and those are the elements that it highlights in the iConsole.
Additional Information
Orchestria APM, Orchestria EPM, Orchestria, CA DLP and CA DataMinder are all previous brands for the product now known as CA Data Protection
Feedback
Yes
No
Powered by
