3.4.3 Move or Delete Files

The following options are available right now:

Move / Delete blocked files

Files that were marked as blocked during file processing can be deleted or moved to another storage altogether.

Configuration

  1. From the left-side navigation menu, go to Storage units

  2. Select the storage for which you wish configure Move/Delete post actions

  3. Click on Remediation actions in the actions dropdown

  4. Go to Move/Delete tab in the Remediation Actions menu

  5. Check If the file is blocked then remediation option

  6. Choose how the blocked file should be handled by selecting one of the two available options

    1. Delete file - the blocked file will be deleted from your storage (Please note that the file might still be stored in Trash Bin)

    2. Move file - the blocked file will be moved to another storage; select the destination storage and the corresponding user account, if needed (Please note that a valid connection should be established beforehand with the destination storage in order to proceed with this post action)

  7. Choose if other types of file should be treated as blocked files

    1. Files with sensitive data - if checked, files containing sensitive information will also be deleted or moved to the configured storage, depending on the selected post action

    2. Files with vulnerabilities - if checked, files containing vulnerabilities will also be deleted or moved to the configured storage, depending on the selected post action

images/download/attachments/2577681/delete_blocked_file.png

Move sanitized files

Sanitized files can be moved to another storage too. Please note that in order to configure this post action, File Sanitization Feature should be enabled (check Enable Deep CDR steps in the section above).

Configuration

  1. From the left-side navigation menu, go to Storage units

  2. Select the storage for which you wish configure Move/Delete post actions

  3. Click on Remediation actions in the actions dropdown

  4. Go to Move/Delete tab in the Remediation Actions menu

  5. Check If the file is sanitized then remediation option

  6. Configure the destination storage - select the destination storage and the corresponding user account, if needed (Please note that a valid connection should be established beforehand with the destination storage in order to proceed with this post action)

images/download/attachments/2577681/move_sanitized_file.png

Technical details / concerns

  • When moving files to a specific user account, they will be moved to the root folder of that account. This means that the original path will not be kept. For example, for a Box storage to Box storage move, if the file to be moved is located at /All Files/My Folder/file.txt and you want to move it to a Box user called John, the new file path would be: /All Files/file.txt

  • Similarly, when moving files between S3 or S3-Compatible storage units, the path will not be kept and the file will be moved to the root location of the destination storage (if the destination storage contains a FolderLocation - that would be the root location). Please note that the folder structure is not recreated, fow now.

  • When Move sanitized files post action it’s enabled on storage A, any file that it’s moved to storage B won’t be sanitized / encrypted again on storage B if there’s enabled Deep CDR on storage B. The same logic it’s applied when Real-Time Processing it’s enabled on storage B, the moved file won’t be processed again.