Recommended System Configuration

MetaDefender Core supports a wide range of deployment options, including air-gapped environments, providing the flexibility to choose the environment that best suits customers' requirements and infrastructure.

• Physical server.
• Virtualization platforms like VMware, Hyper-V and XenServer.
• Cloud Deployment.
• Container Deployment.

The recommendations below are for MetaDefender Core, API usage only. For any other use cases, please consult the user guide of the licensed products for accurate recommendations.

For certain use cases these might be adjusted and customized on specific needs and SLAs. We highly recommend to engage our ProServ team to assist in fine tuning MetaDefender and get the maximum performance out of your systems.

Microsoft Windows Deployments

[Windows] Supported Operating Systems

Only support 64-bit platforms____.

• Windows 10, Windows 11 23H2, 11 IoT (22H2) only for End-User systems (e.g. Kiosk deployments)

  • Based on Microsoft License Terms, you're not allowed to use Windows Desktop as a server, therefore, MetaDefender Core can't be used on these systems for server use cases.

• Windows Server 2016, 2019, 2022, 2025

Fast Startup mode is unsupported.

[Windows] Recommended System Configuration

The resources listed below (CPU, RAM, disk space) are the minimum recommended for MetaDefender Core:

• It is suggested to use SSD for system where MetaDefender Core is installed.
• See more disk space details in Storage Usage Information.
• For a better performance with Deep CDR and Proactive DLP technologies (if licensed), consider adding 8GB RAM, 4 CPU cores (at least 12 CPU cores in total) additionally.
• SBOM processing requires more disk space, please allow at least 15GB free disk for the engine to work properly.

[Windows] Third Party Dependencies

• .NET framework 4.5 or above
• Microsoft Visual C++ Redistributable for Visual Studio 2015-2022 (version 14.38 or higher); x64 version.
• PostgreSQL: Only applicable when using a pre-installed PostgreSQL server running remotely.
  • From 14.5 to 14.18
  • From 15.7
  • From 16.4

Some engines also have dependencies as described below:

[Windows] Installation Details

MetaDefender Core on Windows uses "C:\Program Files\OPSWAT" folder for storing resources or the installation directory.

MetaDefender will use its resources folder to store temp files as part of the analysis. It's recommended to exclude this folder from real-time protection monitoring. Knowledge base:

• How to set up exclusions on anti-malware software to prevent disruption
• Mitigating scan failure triggered by real-time protection service
• Can local AVs interrupt ongoing scans?

Linux Deployments

[Linux] Supported Operating Systems

Only support 64-bit platforms.

• Red Hat Enterprise Linux 8, 9
• Rocky Linux 9
• Oracle Linux 9 (version 9.5 or later)
• Debian 11, 12
• Ubuntu 22.04, 24.04
• Amazon Linux 2023 is supported via Amazon Machine Image (AMI)

The product may not function correctly with Red Hat Enterprise Linux or Rocky Linux operating systems running old kernel version such as 372.9, 372.13.

The recommended solution is to upgrade to at least kernel version 372.26. This should help ensure proper functionality.

[Linux] Recommended System Configuration

The resources listed below (CPU, RAM, disk space) are the minimum recommended for MetaDefender Core:

• It is suggested to use SSD for system where MetaDefender Core resides on.
• See more disk space details in Storage Usage Information.
• For better performance with Deep CDR and Proactive DLP technologies (if licensed), consider adding 8GB RAM, 4 CPU cores (at least 12 CPU cores in total) additionally.

[Linux] Third Party Dependencies

Dependencies list:

• openssl
• grep
• lib32stdc++6 (>= 4.5)
• libc6-i386 (>= 2.10)
• procps
• zlib1g
• libcurl3 (>= 7.19.7)
• libcurl4
• postgresql:
  • From 14.5 to 14.18
  • From 15.7
  • From 16.4

Not all the above dependencies will need to be installed, it is dependent on different Unix distro and version

Some engines also have dependencies as described below:

Note: Some dependencies may need to be installed from external repositories, not from the OS default repositories.

[Linux] Installation Details

MetaDefender Core default installation path is using /var folder for storing resources:

• /var/lib/ometascan : installation folder with all its resources (database, DLP processed / CDR sanitized / quarantined file storage, engine package and definition updates).
• /var/log/ometascan : application logs.
• /var/run/ometascan : runtime folder for Core related processes.
• /var/lib/ometascan : all successful deployed engines data files.
• /usr/lib/ometascan : all shared libraries required by MetaDefender Core, bundled PostgreSQL server related binaries and libraries.
• /var/tmp/ometascan/resources : all temporary processing files for MetaDefender Core to process.

Storage Usage Information

Based on the configuration, MetaDefender Core will need additional disk space to store analysis/result data, quarantined files and temporary files:

Custom Engines

The recommendations above are specific for MetaDefender pre-packaged bundles.

However for additional Custom Engines, please review the Knowledge base to review additional requirements (if any) for the selected engine.

Browser Requirements for the MetaDefender Core Management Console

One of the following browsers is suggested to view the MetaDefender Core Management Console:

• Microsoft Edge
• Chrome
• Firefox
• Safari

Chrome, Firefox, Safari and Microsoft Edge browsers are tested with the latest available version at the time of release.

Network Bandwidth

In online environment where MetaDefender Core is configured to download engine update packages directly from OPSWAT update server source, then using gigabit network speed (125 MB/sec) is highly recommended to avoid potential network related issue while downloading files, or at least 100 Mbps (12.5 MB/sec) network speed.