Requirements for deploying MetaDefender OT Security

Deployment guidelines | Components' Requirements & Sizing

Component

Criteria

MetaDefender OT Security Network Sensor

MetaDefender OT Security Site Server

MetaDefender OT Security Enterprise Management Server

MetaDefender OT Security AIO

Software Installation options

Pre-Bundled Linux Image or VMWare virtual appliance (OVA file)

Pre-Bundled Linux Image or VMWare virtual appliance (OVA file)

Pre-Bundled Linux Image or VMWare virtual appliance (OVA file)

Pre-Bundled Linux Image or VMWare virtual appliance (OVA file)

Typical number of Assets

  • ~100 Assets per Sensor (Industrial PC DIN Rail form factor)

  • 500 - 1000 Assets per Sensor (1U server form factor)

Up to 5,000 Assets per Site Server

Multiple Sites Supported

Up to 5,000 Assets

Network Throughput Processing

  • 200Mbps (Industrial PC DIN Rail form factor)

  • 500Mbps (1U server form factor)




Typical HW specs

  • CPU Cores: 4 - 8

  • RAM: 8GB - 16GB

  • Storage: SSD 250GB - 500GB

* HW specs for the network sensor + site manager bundle should be similar to or higher than specs for the Site Server

  • CPU Cores: 16 - 32

  • RAM: 32GB - 64GB

  • Storage: SSD 4TB - 8TB

* HW specs for the network sensor + site manager bundle should be similar to or higher than specs for the Site Server

  • CPU Cores: 16 - 32

  • RAM: 32GB - 64GB

  • Storage: SSD 5TB - 10TB

  • CPU Cores: 16 - 32

  • RAM: 32GB - 64GB

  • Storage: SSD 4TB - 8TB

  • HW specs for the AIO should be similar to or higher than specs for the Site Server

Networking

3 x Gb Ethernet Interfaces

  1. Gbps Ethernet port: connects to the SPAN port on the switch of OT network, for passive monitoring/ discovery

  2. Gbps Ethernet port: connects to the OT network, for active discovery

  3. Gbps Ethernet port (Northbound interface): for connection to MD OT Security Site Manager.

The same physical interface can be used for #2 and #3 if there will be appropriate network segmentation and/ or routing configurations.

Using the interface #1 (which connects to the SPAN port of switch) with other purposes is NOT recommended as there is heavy network traffics at the SPAN port; and issues on inter-network connection (routing) observed at the interface connected to the SPAN port for some types of switch.

2 - 4 x Gb Ethernet Interfaces

  1. Gbps Ethernet port (Southbound interface): for connecting with the sensors

  2. Gbps Ethernet port (Northbound interface): for connection to MD OT Security Enterprise Manager.

  3. (for Site + Sensor bundle) Ethernet ports for sensor monitoring & discovery

2 - 3 x Gb Ethernet Interfaces

  1. Gbps Ethernet port (Southbound interface): for connecting with the Site Managers

  2. Gbps Ethernet port: exposes the Enterprise Management Console, users accessing to the IP of this interface for interacting with the Enterprise Management Console

  3. Gbps Ethernet port (optional): for Enterprise Manager connecting to Internet for (online) license activation and auto update/ upgrade of MD OT Security product.

The same physical interface can be used for #2 and #3 if there will be appropriate routing configurations.

2 - 4 x Gb Ethernet Interfaces

  1. Gbps Ethernet ports for sensor monitoring & discovery (following the networking of the Network Sensor)

  2. Gbps Ethernet port: exposes the Enterprise Management Console, users accessing to the IP of this interface for interacting with the Enterprise Management Console

  3. Gbps Ethernet port (optional): for Enterprise Manager connecting to Internet for (online) license activation and auto update/ upgrade of MD OT Security product.

The same physical interface can be used for #2 and #3 if there will be appropriate routing configurations.