Using MetaDefender Core Server
In order to use the multi-scanning functionality of MetaDefender Core, MetaDefender Kiosk requires a MetaDefender Core Server.
The MetaDefender Core Server can be installed on the same system as MetaDefender Kiosk or on another machine.
By default, MetaDefender Kiosk uses a locally installed MetaDefender Core Server if one is available.
To specify a remote MetaDefender Core Server, use the Remote MetaDefender Core Server URL option in the Advanced Configuration settings of the 8.3. Configuring Global Kiosk Settings page.
The Security Rule drop-down menu determines which MetaDefender Core security rule is used to process files from MetaDefender Kiosk.
When used with MetaDefender Core version 4.8.0+, a media manifest can be added to media processed by MetaDefender Kiosk.
This setting enables the creation of a signed Media Manifest that contains the scan results for all files that were scanned as part of the session.
This manifest can be validated by other MetaDefender products.
Kiosk can also validate files according to the Media Manifest file that exists on the media to be processed.
If a file is found on the media but not found within the manifest, it will be sent to Core for processing.
Kiosk can retrieve previously existing results for files by performing a hash lookup instead of uploading a file to Core for processing.
This cannot be used in conjunction with Media Manifest since the manifest always contains the latest results.
A max file size can be specified for files to be scanned by MetaDefender Core, all files larger than this will still be processed by Kiosk without being processed by Core.
The files that are larger are treated as allowed.
Using Vault Server
To reduce user time spent at the Kiosk, processing files can be offloaded to a Vault server connected to a MetaDefender Core.
Files will be uploaded directly from Kiosk to Vault, once uploading is done, the session will complete and the user may remove their media and proceed.
Meanwhile, Vault will send the uploaded files to MetaDefender to process and based on the configuration, notify the user when the files are ready for retrieval.
Security Rule: Core security that Vault will use to process the uploaded files
Vault Server : See 6. Configuring with Vault for instructions and more details
Select a Vault account option for file uploads: Choose a Vault account option in this section
File Chunk Upload Size: Size of chunks a file will be broken into for uploading to Vault
Vault account options for file uploads
If you select the Always upload to a Vault guest account radio button, MetaDefender Kiosk creates and provides a temporary guest login ID to the Kiosk user both on the scan results screen as well as in the digital and printed logs.
If you select the Attempt to use user credentials if they are available radio button, MetaDefender Kiosk uploads files to the user account that matches the one used during authentication.
If authentication fails, files will be uploaded to the Vault guest account.