Fortinet black logo

Collector System Requirements

Home FortiEDR/XDR 6.2.0 Collector System Requirements
6.2.0
6.2.0
6.0.0
5.2.0

Processor, CPU, and memory requirements

Processor, CPU, and memory requirements

The communicating device on which you install the FortiEDR Collector must meet the following requirements:

Component

Requirements
Processor

  • Intel or AMD x86 (32-bit and 64-bit)

  • Apple M1 (ARM)

  • Apple M2 (ARM)

Number of CPUs

1% to 2% CPU usage

FortiEDR Collector CPU consumption is highly dynamic by nature and varies depending on several factors:

  • Variety of files and processes on the endpoint

  • Activity on the endpoint

  • Enabled features
Physical Memory

  • 200 MB to 250 MB without a Response (Threat Hunting) license

  • 300 MB to 350 MB with a Response (Threat Hunting) license
Disk Space

  • 750 MB without a Response (Threat Hunting) license

  • 1 GB with a Response (Threat Hunting) license

A Response (Threat Hunting) license results in more disk usage due to Threat Hunting audit activity data collection, such as activity on the device and the connection to the Core component status.
Previous
Next

Processor, CPU, and memory requirements

The communicating device on which you install the FortiEDR Collector must meet the following requirements:

Component

Requirements
Processor

  • Intel or AMD x86 (32-bit and 64-bit)

  • Apple M1 (ARM)

  • Apple M2 (ARM)

Number of CPUs

1% to 2% CPU usage

FortiEDR Collector CPU consumption is highly dynamic by nature and varies depending on several factors:

  • Variety of files and processes on the endpoint

  • Activity on the endpoint

  • Enabled features
Physical Memory

  • 200 MB to 250 MB without a Response (Threat Hunting) license

  • 300 MB to 350 MB with a Response (Threat Hunting) license
Disk Space

  • 750 MB without a Response (Threat Hunting) license

  • 1 GB with a Response (Threat Hunting) license

A Response (Threat Hunting) license results in more disk usage due to Threat Hunting audit activity data collection, such as activity on the device and the connection to the Core component status.
Previous
Next