RSA G&L Datareach - Technical Info

[#1]

Architecture

Components

Master Controller is the component responsible for serving as a central configuration point. All agent configurations, drivers, certificates and data to be collected are centrally managed on the Master Controller. The Master Controller is also responsible for collating the data collected by all the agents, error handling and piping data to the Oracle database.

Agents are responsible for collecting data from endpoints. These endpoints can be any JDBC compliant databases, AWS, UNIX or Windows systems.

Database stores all the data and metadata collected from the target systems.  All the pruning and data validation stored procedures are contained in this database. Data Reach requires an Oracle 11g or above database for staging the collected data. This can be a standalone Oracle database, or the database used by RSA G&L.

Plugins provide optional integrations with third party system for host configurations (CMDB), credentials (PAM) and ticketing systems for error handling. The plugin architecture allows Data Reach to maintain a small footprint and features added as needed.

3rd Party Integrations

Host List Providers (Targets) ServiceNow JDBC Credential Providers (Credentials) HashiCorp Vault Thycotic Secret Server ManageEngine Password Manager Pro Local (CSV) CyberArk Error Handlers (Error Reporting) ServiceNow Zendesk Support Jira Service Desk Slack

Deployment Types

Single Server In this scenario, all 3 components are installed directly on your G&L application server.

Agent, Local Database In this scenario, the master controller and the database are installed on the G&L application server, while agents are deployed throughout your environment.

Agent, Dedicated Database In this scenario, agents are deployed throughout your environment.  The dedicated Oracle database instance separate from G&L must be provided by the organization. In this deployment, the master controller can be installed on any of the systems.