A general view of the Disarmer product in relation to other key elements in the network is provided in the following diagram:
Data flows between the user application (Votiro Disarmer API consumer) and Disarmer. Communication consists of multiple bi-directional messages that include queuing, tracking, and file transfers.
The Votiro Disarmer engine is at the heart of the Votiro sanitization solution. The engine is provided with a front-end Management consule that is used for the following:
|n||Monitoring and analyzing sanitization activity in the Disarmer engine.|
|n||Creating and editing sanitization policies that are regularly updated in the Disarmer engine.|
|n||Storing metadata that describes the files, along with the original and sanitized files themselves for incident management and zero-day identification.|
The next diagram shows how sanitization requests flow between the Disarmer API and the Disarmer Sanitization Nodes, which are managed by the Sanitization Node Manager Controller (SNMC).
|n||A sanitization request enters the system via the API service: a sanitization request for the file is queued in the Sanitization Queue, while the file to be sanitized is still in the File Repository.|
|n||The SNMC is the sanitization system watchdog. It performs a health check by polling the nodes every defined time period (depending on the configuration) to ensure that there are n sanitization node processes running at any time.|
|n||The maximum number of sanitization nodes running at any time equals the number of processor cores in the computer where Disarmer is running, provided the available memory per node is no less than 2 GB.|
|n||Should the SNMC detect that any node is non-responsive (because it has crashed or hanged), it terminates that node and spawns a new one in its place.|
|n||Each node polls the Sanitization Queue for a new incoming request, which is a reference containing the file name in the File Repository.|
|n||When a request comes to the top of the Sanitization Queue, the next available node pulls the reference from the queue and accesses the referenced file in the File Repository to begin the sanitization process.|
|n||After sanitization begins, it is stored in the InProcess Queue for status tracking and each status update is queued in the Status Queue. Status updates are polled by the API service and reflected to the user.|
|n||As part of the sanitization, the node passes the file to the Votiro Scanner service for antivirus scanning.|