Scan Configuration
Scan Pools
MetaDefender Storage Security uses scan pools to group MetaDefender Core or Cloud instances.
These two types of scan pools can be used to balance the load of scan requests.
To learn more about the required permissions and the endpoints used by MDSS for MD Core, please read the following KB article: Which endpoints from MD Core does MDSS utilize?
MD Cloud instances utilize private processing by default to ensure maximum data privacy and security. With private processing:
- All submitted files are automatically deleted immediately after analysis completion
- Scan results are only accessible to the original API key owner
Scan configurations
MetaDefender Storage Security employs scan configurations to offer a versatile method for initiating scanning processes using various workflow rules from either MetaDefender Core or MetaDefender Cloud.
Scan configurations are linked with scan pools to ensure uniform configuration across all instances of MetaDefender Core/Cloud.
The default workflow rule for MetaDefender Core is 'MetaDefender Storage Security'.
For MetaDefender Cloud rules, please check the following documentation.
When creating a new scan configuration, you can select a name, associate it with a scan pool, and optionally designate a secondary scan pool for failover in cases where all scan instances from the primary pool are unavailable or unresponsive.
