Inserting credentials into RSA DLP Datacenter Agent/Grid scan groups
Originally Published: 2008-06-11
Article Number
Applies To
RSA Product/Service Type: Data Loss Prevention, DataCenter
RSA Version/Condition: 8.x, 9.x, and 9.6.x and up.
Platform: Windows
O/S Version: 2003 SP2, 2008, 2008 R2, 2012
Issue
Resolution
If the "Runas" user for the agent scan group does not have admin access to target systems, or if the target systems are not domain members or are on domains other than the Enterprise Coordinator / Site Coordinator system, additional Credential settings within Datacenter are required.
In order for a scan group to successfully scan remote servers, valid administrative credentials will need to be applied to the agent scan group in question.To apply one or more credential entries (Datacenter will try each credential listed if the first or subsequent credentials fail) follow steps given below:
- For DLP 9.x, make sure that the credential needed is added under the Admin->Users & Groups->Credentials page.

- Edit the configuration for the Agent scan group in question on the Admin->Datacenter page or sub page.
- On the edit Agent Group screen select the Optional Settings button

- Select the Credentials tab and select/insert one or more accounts you wish to use to scan the remote machines.
- There are two sections in the credentials page. The top section is for entering domain credentials for machines that are joined to a domain and the bottom section is for entering credentials for machines that are not part of a domain.
- In the top section use the domain credential in the format domain\account name, for example RSA\AdminUser. For 9.x, this credential has to be entered in Step 1.
Or
- In the lower section, gain access to machines that are not in an Active Directory. Please provide credentials in NTLM format, e.g. Machine\AdminUser. For 9.x, this credential has to be entered in Step 1.

Workaround
This involves having two accounts with same name and password on the each domain.
To configure you create an user account with the same name and password as the same account used to scan on the same domain as the DLP system.
Example:
DLP domain is domain A
DomainA
DLPScanUser
password is changeMe!
DomainB
DLPScanUser (non trusted domain)
password is changeMe!
Related Articles
StandAlone Scan 23Number of Views What files on a workstation with RSA Authentication Agent 7.4.x for Windows may potentially show as false positive from a … 39Number of Views Scan of RSA Certificate Manager 6.7 show vulnerabilities with Apache 1.3.33 36Number of Views Apache vulnerability 'Apache HTTP Server mod_rewrite' from scan 45Number of Views RSA Authentication Manager Multiple Vulnerabilities in PostgreSQL - False Positive 81Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?