Integrations

MetaDefender Storage Security integrates with various cloud and on-premises storage solutions, represented as storage units.

We provide a list (see table below) of officially supported integrations that are continuously tested for full functionality.

IMPORTANT Please get in touch with us if your specific storage provider isn't shown.

We likely already support storage systems that use S3-compatible interfaces or standard protocols such as SMB, NFS, or SFTP.

Cloud Object Storages

Storage Name

Integration Type

Tagging

Event-Based

Metadata Copy

Autodiscovery

Amazon S3

Native

Yes

Yes

Yes

Yes

Wasabi

S3 Compatible

Yes

Yes

Yes

Yes

Cloudian®

S3 Compatible

Yes

Yes

Yes

Yes

Oracle Cloud

S3 Compatible

No

No

Yes

Yes

Oracle Cloud

Native

No

Yes

Yes

No

MinIO

S3 Compatible

Yes

Yes

Yes

Yes

Cubbit

S3 Compatible

Yes

No

Yes

Yes

Azure Blob

Native

No

Yes

No

Yes

Google Cloud

Native

Yes

Yes

No

Yes

Alibaba Cloud

Native

No

Yes

No

No

Scality RING

S3 Compatible

Yes

Yes

Yes

Yes

File Storages

Storage Name

Integration Type

Event-Based

Autodiscovery

Replace Original

Scan File Versions

Box

Native

Yes

No

No

No

OneDrive

Native

No

No

Yes

No

SharePoint Online

Native

Yes

Yes

Yes

No

Microsoft Teams

Native

No

No

Yes

No

SharePoint On-Premise

Native

No

No

No

Yes

Azure Files

Native

No

No

No

No

OPSWAT Managed File Transfer (MFT)

Native

No

No

No

No

Network Attached Storages (NAS)

Storage Name

Integration Type

Event-Based

Delete empty folders

Autodiscovery

NFS

Native

Yes

Yes

No

NFS with Data Wrapping

NFS

Yes

No

No

SMB

NFS (recommended)

Native

Yes

Yes

No

NetApp ONTAP

SMB

Yes

No

No

Amazon EFS

NFS

Yes

Yes

No

Dell Isilon

SMB

Yes

No

No

SFTP

Native

Yes

Yes

No

FTP

Native

Yes

No

No


Extra functionalities

How Replace Original works

With Replace Original enabled, MetaDefender Storage Security overwrites the content of the original file with the sanitized content. No new file is created: the file keeps its name, location and sharing, so users keep opening the same file and now get the sanitized version.