Title
Create new category
Edit page index title
Edit category
Edit link
System Requirements
To deploy My OPSWAT Central Management On-Premises, ensure your system meets the minimum requirements for your deployment mode.
Only 64-bit platforms are supported.
Jump to: MSI Installation - Windows | RPM Installation - Linux [RHEL] | Virtual Appliance[OVA]
Common Requirements
These requirements apply to all deployment modes.
Hardware
| Component | Minimum |
|---|---|
| CPU | 8 vCPUs, AVX2 support |
| Memory | 32 GB RAM |
| Storage | 500 GB SSD (see Storage Usage Information for sizing guidance) |
Networking and Port Requirements
| Port | Protocol | Direction | Destination / Source | Purpose |
|---|---|---|---|---|
| 9000, 443 | TCP | Inbound | Product instances | Communications from products to My OPSWAT Central Management |
| 443 | TCP | Outbound | https://update.dl.opswat.com, https://opswat-gears-cloud.s3-us-west-2.amazonaws.com/ | Product/module updates (if enabled) |
| 443 | TCP | Outbound | https://activation.dl.opswat.com | License activation (if online) |
| 443 | TCP | Outbound | Configured proxy servers | Outbound traffic via proxy (if configured) |
<SMTP port> | TCP | Outbound | Configured SMTP server | Send emails (if configured) |
<IdP port> | TCP | Outbound | Configured IdP servers | SSO user directory authentication (if configured) |
| 443 | TCP | Outbound | https://metascanbucket.s3.amazonaws.com/, https://opswat-gears-cloud-clients.s3.us-west-2.amazonaws.com/, https://s3.amazonaws.com/mem-onpremise/production/patch/, https://s3.amazonaws.com/mem-onpremise/production/vulnerability/ | MetaDefender Endpoint updates (if enabled) |
- Internal ports ranging from 30000 to 30071. Conflicts within this port range can lead to improper system behavior.
- If you route traffic through proxy servers, there's no need to set up outbound rules for other outbound connections, except the proxy connections.
- To ensure proper communication between product instances and the My OPSWAT Central Management, the FQDN and ports must be allowed through your firewall or proxy.
MSI Installation — Windows
Operating System
| OS Family | Supported Versions |
|---|---|
| Microsoft Windows | 11 |
| Microsoft Windows Server | 2016, 2019, 2022, 2025 |
Note: Windows Server 2016 must have all patches installed.
Prerequisites
Directory Paths
| Directory | Default Path |
|---|---|
| Installation, Data backup | C:\Program Files\OPSWAT\MOCM |
| Troubleshooting log files | C:\ProgramData\OPSWAT\MOCM\Logs |
RPM Installation — Linux (RHEL)
Operating System
Red Hat Enterprise Linux 9.4 or later (64-bit only).
Required Packages
Install the following packages before running the RPM installer:
| Package | Required Version | Installation Guide |
|---|---|---|
| nginx | >= 1.30.1 | nginx.org |
| rabbitmq-server | >= 4.1.4 | rabbitmq.com |
| redis | >= 8.2.1 | redis.io |
| erlang | 27.3.4.2 to 27.x (< 28.0.0) | Bundled with rabbitmq-server (same link above) |
| openssl | >= 3.6.1 | Available via dnf install openssl |
Note: RPM installation requires only the packages above. No hypervisor or VMware requirement — it runs on any infrastructure (VMware, cloud VMs, bare metal, etc.).
Air-gapped environments: For installations without internet access, contact OPSWAT support for offline installation guidance.
Directory Paths
| Directory | Default Path |
|---|---|
| Main installation folder | /opt/mocm |
| Service folder | /usr/lib/systemd/system |
| Event log folder | /var/log/mocm |
| Database folder | /var/lib/mocm |
| Config files (nginx, MongoDB, RabbitMQ) | /etc/opt/mocm |
| Nginx config | /etc/nginx |
| Nginx data | /usr/share/nginx |
| RabbitMQ config | /etc/rabbitmq |
| RabbitMQ data | /var/lib/rabbitmq |
| Redis config | /etc/redis |
| Redis data | /var/lib/redis |
Virtual Appliance (OVA)
Note: VMware requirements below apply only to Virtual Appliance (OVA) deployment. They are NOT required for MSI or RPM installations.
Hypervisor Requirements
- VMware vSphere 7.0 or 8.0
- VMware Workstation Player 17
Directory Paths
| Directory | Default Path |
|---|---|
| Main installation folder | /var/opt/mocm |
| Service folder | /etc/systemd/system |
| Event log folder | /var/log/mocm |
| Database folder | /var/lib/mocm |
| Config files (nginx, MongoDB, RabbitMQ) | /etc/opt/mocm |
| Nginx config | /etc/nginx |
| Nginx data | /usr/share/nginx |
| RabbitMQ config | /etc/rabbitmq |
| RabbitMQ data | /var/lib/rabbitmq |
| Redis config | /etc/redis |
| Redis data | /var/lib/redis |
Storage Usage Information
MetaDefender Endpoint
On average, each MetaDefender Endpoint (MDE) sends approximately 150 MB of data to Central Management per month.
To calculate the required disk space based on your data retention policy:
Required Disk Size = 150 MB × [Number of Endpoints] × [Data Retention Period in Months]
For example, to manage 1,000 MetaDefender Endpoints with 1-month data retention period:
Extra Disk Space Needed = 1,000 Endpoints × 0.15 GB × 1 Month = 150 GB
Total disk space requirement:
- 100 GB for the operating system
- 150 GB for endpoint data
Disk space needed to manage 1000 endpoints: 250 GB
MetaDefender Core
The required extra disk space depends on two key factors:
- Number of scanning engines
- Number of managed MetaDefender Core instances & Scanning volume
Number of scanning engines: On average, each scanning engine requires approximately 5 GB of storage in Central Management. For example, with 20 engines, you should allocate an additional 100 GB of disk space.
Number of managed MetaDefender Core instances & Scanning volume: Additional disk space is required to store scanning reports generated by MetaDefender Core. As a baseline, allocate at least 100 GB for storing these reports, with further increases based on the number of managed instances and overall scanning activity.
- Note: On average, each file scan generates a report of approximately 10 KB. Therefore, for every 1 million scanned files, you should allocate an additional 10 GB of disk space.
For example, to manage MetaDefender Cores with 20 engines:
Extra Disk Space Needed = 100 GB for engine database + 100 GB for report storage = 200 GB
Total disk space requirement:
- 100 GB for the operating system
- 200 GB for engine & report data
Disk space needed to manage Cores with 20 engines & 1 million scanned files: 300 GB
Browser Versions Supported
Supported browsers for launching the My OPSWAT Central Management console are Chrome, Firefox, and Microsoft Edge on desktop (mobile view has not been supported yet, but in our roadmap). We recommend that you should use the most current version of the browser.
Screen Resolution
We recommend that you use a screen resolution of 1300x768 or larger to properly display My OPSWAT Central Management console interface.