CA DataMinder policy engines apply Data In Motion triggers to all files received from the NBA. The mechanism to identify the policy participant (that is, to determine which user policy gets applied) depends on the NBA output mode:
When the NBA outputs files via a socket connection, policy engines always apply the Default Policy for Files. This setting is defined in policy engines’ machine policy; for details, see Default Policy for Files.
By default, the Default Policy for Files setting specifies the ‘DefaultFileUser’ account (this account is created automatically when you install a CMS). However, you may prefer to specify a custom CA DataMinder user account for the NBA (for example, ‘NBA Policy User’). You can then tailor this account’s user policy to apply triggers to files processed by the NBA.
If the NBA runs in passive mode and outputs items to disk, when the files are subsequently imported as part of Import Policy job, the correct user policy is specified by the ImpFile.PolicyParticipant import parameter. This parameter specifies an SMTP email address that the policy engine can map to an existing CA DataMinder user account.
If the policy participant is not specified, or the user account does not exist, policy engines apply the Default Policy for Files (see above).
Warnings and Encryption Are Not Supported
The NBA does not support warnings or encryption. Although the NBA applies outgoing Data In Motion triggers to files entering or leaving the corporate network, it cannot apply Warn or Encryption control actions. The NBA can only apply Block, Quarantine or Categorize control actions to these files.
|
Copyright © 2014 CA.
All rights reserved.
|
|