Console section that manages RCS access.
Group of complex events, actions and acquisition modules that make up the advanced agent configuration.
The person who enables user access to the system, creates work groups and defines operations, targets and the type of data to be collected.
Software probes installed on devices to monitor. They are designed to collect evidence and communicate it to the Collector.
Rules that create alerts when new evidence is stored or agents communicate back for the first time.
Console section that manages new evidence alerts.
Group of users who receive notifications via mail whenever a system alarm is triggered (for example, when the database exceeds available free space limits). Normally this group is not linked to an operation.
Person in charge of analyzing the data collected during operations.
(optional) Protects the server against external attacks and permits anonymity during investigations. Transfers agent data to Collectors.
Console section that reports all users' and system actions. Used to monitor abuse of RCS.
Environment designed to decrypt and save collected information. In distributed architecture, it includes Master Node and Shard databases.
(Broadband Remote Access Server) routes traffic to/from DSLAM to the ISP network and provides authentication to the ISP subscribers.
Receives data sent by agents directly or through the Anonymizer chain.
Computer on which the RCS Console is installed. It directly accesses the RCS Server or Master Node.
Console section used by the Analyst. Used to have a quick overview of the status of the most important operations, targets and agents.
(Digital Subscriber Line Access Multiplexer) network device, often located in the telephone exchanges of the telecommunications operators. It connects multiple customer digital subscriber line (DSL) interfaces to a high-speed digital communications channel using multiplexing techniques.
Collected data evidence. The format depends on the type of evidence (i.e.: image).
Alerts, usually in the form of emails, sent to analysts when new evidence matches the set rule.
A template for agent configuration and compiling.
Environment designed to communicate with agents to collect information and set their configurations. In distributed architecture, it includes the Collector and Network Controller.
Settings that define how to identify HTTP traffic, what resource should be injected and what method is to be used for the injection.
Console section that monitors components and license status.
Component that checks Network Injector and Anonymizer status and sends them new configurations and software updates.
Hardware component that monitors the target’s network traffic and injects an agent into selected Web resources. It comes in two versions, Appliance or Tactical: the former is for deployment at the ISP, the latter for use on the field.
Rackable version of the Network Injector, for installation at ISP. See: Tactical Network Injector.
Investigation aimed at one or more targets, whose devices will be recipients for agents.
(Remote Control System) the product documented hereto.
Software designed to interact with the RCS Server.
One or more computers, based on the installation architecture, were essential RCS components are installed: Shard databases, Network Controllers and Collector.
(Secure SHell) a network protocol for secure data communication, remote shell services or command execution.
Console section that manages the system.
The person who installs the servers and consoles, updates software and restores data in case of faults.
The portable version of Network Injector, for tactical use. See: Network Injector Appliance.
(Test Access Port) a hardware device installed in a network that passively monitors the transmitted data flow.
The physical person under investigation.
The person assigned by the Administrator to create and manage agents.
(Virtual Private Server) a remote server where the Anonymizer is installed. Commonly available for rent.