Component | Specifications |
CPU | 8 CPUs |
Memory | 32 GB |
Storage | 250 GB virtual disk, with IOPS 2400, attached to an AWS Instance. |
Operating System | Kernel Version |
CentOS 7 | 3.10.0-1127.19.1.el7.x86_64 |
Tool Name | Version |
Zabbix | 4.2.1 |
Internal Script to gather data |
The data in the following table outlines the number of alerts ingested and the total time taken to ingest those alerts.
Single Invocation Test run on a single-node FortiSOAR™ appliance
Number of alerts created in FortiSOAR™ | Total time (in seconds) taken to create all alerts in FortiSOAR™ | Total number of playbooks executed in FortiSOAR™ |
1 | 0.32 | 1 |
5 | 0.42 | 1 |
10 | 0.59 | 1 |
25 | 1 | 1 |
50 | 2 | 1 |
100 | 6 | 1 |
The data in the following table outlines the number of alerts ingested, the total time taken to ingest those alerts, and the total time taken for all the triggered playbooks to complete their execution.
Single Invocation Test run on a single-node FortiSOAR™ appliance
Number of alerts created in FortiSOAR™ | Total time (in seconds) taken to execute all the playbooks | Total number of playbooks executed in FortiSOAR™ |
1 | 1.60 | 2 |
5 | 2.34 | 6 |
10 | 3.79 | 16 |
25 | 7.88 | 37 |
50 | 12.70 | 73 |
100 | 26.19 | 144 |
Important: The setup for this test is exactly the same, however this test additionally requires the "VirusTotal" connector to be configured.
The data in the following table outlines the number of alerts ingested, the total time taken to ingest those alerts, and the total time taken for all the triggered playbooks to complete their execution.
Single Invocation Test run on a single-node FortiSOAR™ appliance
Number of alerts created in FortiSOAR™ | Total time (in seconds) taken to execute all the playbooks | Total number of playbooks executed in FortiSOAR™ * |
1 | 5.22 | 4 |
5 | 7.67 | 16 |
10 | 11.53 | 31 |
25 | 25.87 | 76 |
50 | 50.19 | 151 |
100 | 1 minute 41 seconds | 301 |
The data in the following table outlines the number of alerts ingested and the total time taken to ingest those alerts.
Single Invocation Test run on a two-node active-active FortiSOAR™ cluster
Number of alerts created in FortiSOAR™ | Total time (in seconds) taken to create all alerts in FortiSOAR™ | Total number of playbooks executed in FortiSOAR™ |
1 | 0.60 | 1 |
5 | 0.47 | 1 |
10 | 0.78 | 1 |
25 | 1.40 | 1 |
50 | 2.78 | 1 |
100 | 5.76 | 1 |
The data in the following table outlines the number of alerts ingested, the total time taken to ingest those alerts, and the total time taken for all the triggered playbooks to complete their execution.
Single Invocation Test run on a two-node active-active FortiSOAR™ cluster
Number of alerts created in FortiSOAR™ | Total time (in seconds) taken to execute all the playbooks | Total number of playbooks executed in FortiSOAR™ |
1 | 1.60 | 2 |
5 | 7.20 | 6 |
10 | 4.25 | 16 |
25 | 8.57 | 37 |
50 | 13.25 | 73 |
100 | 21.22 | 144 |
Important: The setup for this test is exactly the same, however this test additionally requires the "VirusTotal" connector to be configured.
The data in the following table outlines the number of alerts ingested, the total time taken to ingest those alerts, and the total time taken for all the triggered playbooks to complete their execution.
Single Invocation Test run on a two-node active-active FortiSOAR™ cluster
Number of alerts created in FortiSOAR™ | Total time (in seconds) taken to execute all the playbooks | Total number of playbooks executed in FortiSOAR™ |
1 | 4.64 | 4 |
5 | 5.69 | 16 |
10 | 9.23 | 31 |
25 | 15.87 | 76 |
50 | 32.76 | 151 |
100 | 1 minute 72 seconds | 301 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.