Fortinet white logo
Fortinet white logo

User Guide

Prerequisite

Prerequisite

Prior to running a SAST or DAST scan from a host/machine through the CI/CD pipeline (automatic/manual), ensure that the Docker engine is installed in that host/machine, and has required user access/permission to run the Docker. To install the Docker engine across different platforms, see Docker.

System Requirements

The system requirements for a FortiDevSec default scan can vary depending on the following factors.

  • Codebase size: Factors like number of lines of code, number of files, and size of individual files can all impact resource utilization..

  • Code complexity: Factors like nesting of control flow statements, dependencies between functions and files, complex looping structures, and use of advanced algorithms can all impact resource utilization.

  • Scanner configuration: The number of scanners used and whether scans are run serially or in parallel impact resource utilization.

  • Life of the repository: Older repositories with a larger number of commits may require more processing power for secret scanning due to the increased data volume.

Following are the hardware requirements for the system where you will run SAST or DAST scans.

Component Minimum Requirements
CPU 2 cores
Memory 4 GB
Storage 10 GB or more free disk space.

Notes:

  • The minimum requirements are derived from an environment with an average repository size of 1 GB, a file count of 2,000, and a vulnerability count of 10,000.

  • You might need to scale resource allocation based on the size and complexity of your repository.

Prerequisite

Prerequisite

Prior to running a SAST or DAST scan from a host/machine through the CI/CD pipeline (automatic/manual), ensure that the Docker engine is installed in that host/machine, and has required user access/permission to run the Docker. To install the Docker engine across different platforms, see Docker.

System Requirements

The system requirements for a FortiDevSec default scan can vary depending on the following factors.

  • Codebase size: Factors like number of lines of code, number of files, and size of individual files can all impact resource utilization..

  • Code complexity: Factors like nesting of control flow statements, dependencies between functions and files, complex looping structures, and use of advanced algorithms can all impact resource utilization.

  • Scanner configuration: The number of scanners used and whether scans are run serially or in parallel impact resource utilization.

  • Life of the repository: Older repositories with a larger number of commits may require more processing power for secret scanning due to the increased data volume.

Following are the hardware requirements for the system where you will run SAST or DAST scans.

Component Minimum Requirements
CPU 2 cores
Memory 4 GB
Storage 10 GB or more free disk space.

Notes:

  • The minimum requirements are derived from an environment with an average repository size of 1 GB, a file count of 2,000, and a vulnerability count of 10,000.

  • You might need to scale resource allocation based on the size and complexity of your repository.