Keep, Copy, Move or Delete Files
Configuring Keep, Copy/Move/Delete Remediation Actions
- Navigate to Workflows from the left-side navigation menu.
- Select the workflow for which you want to configure these remediations actions.
- Select the node for which you want to configure these remediations (Allowed Original, Allowed Sanitized, Blocked Original, Blocked Sanitized)
- Click on the box of the specific node.
Technical Considerations
Move and Re-processing -> when a sanitized file is moved from Storage A to Storage B, it will not be re-sanitized or re-encrypted on Storage B, even if Deep CDR is enabled there.
- Similarly, if Real-Time Processing is enabled on Storage B, the moved file will not be processed again.
File Overwriting -> moving a file with the same name and path as an existing file on the destination storage will overwrite the existing file.
By default, "Keep" is the selected option -> which will keep the file as is.
For the sanitized versions (Allowed Sanitized, Blocked Sanitized), Copy and Delete options are unavailable.
Keeping/Moving Sanitized Files
Sanitized files, created by OPSWAT's Deep CDR, can be moved to one or more storage units (up to a maximum of 5 destinations per remediation type).
Note: The File Sanitization feature must be enabled to configure this action - see Enabling Deep CDR: Deep Content Disarm and Reconstruction (Deep CDR)
Click on the Sanitized Remediation (Allowed Sanitized or Blocked Sanitized) node to open the modal window
Choose the action:
- " Keep the file" -> the sanitized file is kept in the source storage location
- "Move the file" -> the sanitized file is moved to another storage unit (or units). Configure the destination storage(s) as described below.
Configure the destination storage (for b option only):
Select one or multiple storage unit destinations out of the dropdown list
- Additionally, narrow down the destination for certain types of storages (SharePoint Cloud, OneDrive, Box, SharePoint On-Premises), depending on how they are integrated
Note: A valid connection with the destination storage(s) is required.
Select Keep folder structure to maintain the source's structure.
Keeping/Copying/Moving/Deleting Allowed Original Files
Files marked as allowed during processing can be deleted, copied or moved to one or more storage units (up to a maximum of 5 destinations per remediation type).
Click on the Allowed Original Remediation node to open the modal window
Select "Keep the file" to keep the file in the same storage, "Move the file" to move the file to another storage unit (or units), "Copy the file" to copy the file to another storage unit (or units), or "Delete the file" to delete it.
Choose the action:
- Keep the file -> the allowed file is kept in the same location
- Copy the file -> the allowed file is copied to another storage unit (or units). Configure the destination storage(s) as described below.
- Move the file -> the allowed file is moved to another storage unit (or units). Configure the destination storage(s) as described below.
- Delete the file -> the allowed file is deleted.
Configure the destination storage(for option b and c):
Select one or multiple storage unit destinations out of the dropdown list
- Additionally, narrow down the destination for certain types of storages (SharePoint Cloud, OneDrive, Box, SharePoint On-Premises), depending on how they are integrated
Note: A valid connection with the destination storage(s) is required
Select Keep folder structure to maintain the source's structure.
Copying/Moving/Deleting Blocked Original Files
Files marked as blocked during processing can be deleted, copied or moved to another storage unit.
Click on the Blocked Original Remediation node to open the modal window
Select "Keep the file" to keep the file in the same storage, "Move the file" to move the file to another storage unit (or units), "Copy the file" to copy the file to another storage unit (or units), or "Delete the file" to delete it.
Choose the action:
- Keep the file -> the blocked file is kept in the same location
- Copy the file -> the blocked file is copied to another storage unit (or units). Configure the destination storage(s) as described below.
- Move the file -> the blocked file is moved to another storage unit (or units). Configure the destination storage(s) as described below.
- Delete the file -> the blocked file is deleted.
Configure the destination storage:
Select one or multiple storage unit destinations out of the dropdown list
- Additionally, narrow down the destination for certain types of storages (SharePoint Cloud, OneDrive, Box, SharePoint On-Premises), depending on how they are integrated
Note: A valid connection with the destination storage(s) is required
Select Keep folder structure to maintain the source's structure.
Storage types with additional configuration needed
For a number of the possible storage integrations - SharePoint Cloud, OneDrive, Box, SharePoint On-Premises - extra specifications may be necessary when selecting them as destinations as follows:
- If the SharePoint Cloud integration only has the Site specified, you will be asked to enter the name of the Document Library to which the files should be moved/copied to
- If the OneDrive integration only has the Group specified, you will be asked to enter the name or email of the User to which the files should be moved/copied to
- If the SharePoint On-Premises integration only has the Site URL specified, you will be asked to enter the name of the Document Library to which the files should be moved/copied to
- If the Box integration has the All Users or A specific group selected, you will be asked to enter the name or email of the User to which the files should be moved/copied to
Destination storage restrictions
Marking a storage as a destination for a remediation restricts certain actions on that storage such as deleting it, or altering it's configuration in a way that makes the remediation invalid (in the case of destination storages that support users or libraries as a remediation configuration).
Scan restrictions
Starting a scan requires a valid workflow configuration.
The configuration can become invalid if one of the technologies that was enabled and used on the workflow is no longer available on the configured Scan Pool.
Handling Remediation Issues
When remediation actions are configured in a workflow and a user initiates a scan using that workflow, there is a possibility that some files may be discovered and scanned by the Scan Instance but fail during the application of remediation actions.
In such cases, the scan report will indicate a Remediation Failed status.
To obtain further details about this issue, users can filter the files marked as Remediation Failed and click on individual files to access their specific reports.
On the right side of the report, the Remediation Actions tab will display all remediation actions taken on the file, including their success or failure.
To diagnose the cause of the failure, users can click on the failed remediation to view the specific exception that led to the failure.
Typically, for Move or Copy remediation actions, the issue is related to the destination storage.
Troubleshooting Reference
| Issue | Common causes | First steps |
|---|---|---|
| Copy/Move failures | Storage permissions, network connectivity, disk space | Check storage health, verify credentials |
| Performance issues | Multiple destinations, large files, network latency | Review remediation complexity, optimize storage placement |
| Configuration Errors | Invalid storage selections, missing permissions | Validate workflow configuration, test connections |
Integration considerations
Storage requirements
- Make sure the destination storages have sufficient capacity (recommend 2x source storage size)
- Verify network bandwidth between source and destination storages
Security Best Practices
- Use service accounts with minimum required permissions
- Enable encryption for sensitive file transfers
- Regular security audits of remediation workflows
Next steps after configuring remediation actions:
Test Workflows -> run test scans with sample files to verify remediation behavior
Plan scaling -> consider future storage and performance requirements
