RCS is installed at the operating center and proprietary authority's tapping rooms. It can come with special devices (hardware and software) installed at remote organizations such as Internet providers or remote servers.
Software components are installed on several server. The architecture layout is provided below:
Figure 1: RCS architecture: logical layout
Architecture components are provided below:
Component | Function | Installation |
---|---|---|
Agent |
Software bugs tap and communicate the investigation target's data and information to an Anonymizer. |
|
Anonymizing chain Anonymizer |
Geographically distributed Anonymizer groups that guarantee Collector anonymity and redirect collected data to protect servers from remote attacks. It transfers agent data to servers. Several Anonymizers can be set up in a chain to increase the level of protection. Each chain leads to one Collector. |
VPS (Virtual Private Server) |
Collector |
One per Anonymizing Chain:the Collector service collects agent data communicated by the last Anonymizer in the chain, the Carrier service sends data to shards and the Master Node. It requires a single license. |
one or more servers in front end environment |
Firewall |
Optional but highly recommended, it protects the trusted environment (where data is processed and saved) from the untrusted environment (where data is collected). |
RCS server |
RCS console |
Setup, monitoring and analysis console used by operating center workers. |
|
Master Node |
Heart of the RCS server, it manages data flows, component status and includes the first Shard database. It includes the Worker service to decode data before saving it in the database. |
RCS server |
Network Controller |
One per architecture, it is included in first Collector installation. Sends configurations to Network Injector, Anonymizer chains and constantly acquires their status. |
one server in front end environment |
Network Injector |
(optional) Fixed hardware component (Appliance) or notebook (Tactical), it runs sniffing and injection operations on the target's HTTP connections. |
|
Shard x | Additional RCS distributed database partitions. Shard 0 is included in Master Node. It includes Worker service to decode data and enter it in the database. | one or more servers in back end environment |
Target |
Investigation targets. Each device owned by the target is a data source and can be monitored by an agent. |
- |
RCS9.3 | User's and Installation Guide | © COPYRIGHT 2013