An Anonymizer is used to redirect data from a group of agents and Network Injectors. The Anonymizer is installed on a server connected to Internet which cannot be reconnected to the rest of the infrastructure like, for example, a VPS (Virtual Private Server), rented for this purpose.
Several Anonymizers can be set up in a chain to increase the level of protection. Each chain leads to one Collector.
An Anonymizer can have different status:
Status | Symbol in RCS Console, System, Frontend |
---|---|
In operating chain |
![]() |
Not in chain |
![]() |
Disabled |
![]() |
Anonymizer not recognized since it has not yet come into contact with the Collector |
![]() |
Anonymizer with faults |
![]() |
Once installed and set up, the Anonymizer sends status and logs to the Collector and receives settings and updates from the Collector via the Anonymizer chain. For example, Anonymizer 2 sends its status to Anonymizer 1 that sends it to Collector 1.
NOTE: if an Anonymizer does not belong to any chain (i.e.: Anonymizer X in the diagram), it uses the first Anonymizer chain in the configuration to communicate with the Collector.
NOTE: to exclude an Anonymizer from all communications, simply disable it.
A faulty Anonymizer (i.e.: Anonymizer 2 in the diagram) interrupts communications between the Collector and Anonymizers in this chain and is thus faulty. To continue working with the other Anonymizers in the chain, move the faulty Anonymizer out of the chain and update the configuration.