Documentation Version: er2.0.27-docs-1.1

About Enterprise Recon 2.0

Enterprise Recon 2.0 (ER2) is a software appliance and agent solution that consists of:

The Master Server sends instructions to Agents, which scan designated Targets to find and secure sensitive data and sends reports back to the Master Server.



How ER2 Works

ER2 is made up of these components described in the following sections.

Master Server

The Master Server acts as a central hub for ER2. Node Agents connect to the Master Server and receive instructions to scan and remediate data on Target hosts. You can access the Master Server from the:

Web Console

The Web Console is the web interface which you can access on a web browser to operate ER2. Access the Web Console on a network host to perform tasks such as scanning a Target, generating reports, and managing users and permissions.

Master Server Console

(Administrator only) The Master Server console is the Master Server’s command-line interface, through which administrative tasks are performed. Administrative tasks include updating the Master Server, performing maintenance, and advanced configuration of the appliance. See Master Server Console.

Targets

Targets are designated scan locations, and may reside on a network host or remotely.

For details on how to manage Targets, see Targets Overview.

For instructions on how to connect to the various Target types, see Add Targets.

Node and Proxy Agents

A Node Agent is a service that, when installed on a Target host, connects to and waits for instructions from the Master Server. If a Node Agent loses its connection to the Master Server, it can still perform scheduled scans and save results locally. It sends these scan reports to the Master Server once it reconnects. The host that the Node Agent is installed on is referred to as the Node Agent host. For details, see Install Node Agents

A Proxy Agent is a Node Agent which is installed on a Proxy host, a network host that is not a Target location for a given scan. A Proxy Agent scans remote Target locations that do not have a locally installed Node Agent. For these Target locations, the Proxy Agent acts as a middleman between the Master Server and the intended Target location. A Target location that requires the use of a proxy agent is usually a remote Target location such as Cloud Targets and Network Storage Locations.


Target A is a file server and does not have a locally installed Node Agent.
Host B is not a Target location but has a Node Agent installed.
To scan Target A, ER2 can use the Node Agent on Host B as a Proxy Agent, and scan Target A as a Network Storage Location.