STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Fortinet FortiGate Firewall NDM Security Technical Implementation Guide

V-234217

CAT II (Medium)

The FortiGate device must protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.

Rule ID

SV-234217r961620_rule

STIG

Fortinet FortiGate Firewall NDM Security Technical Implementation Guide

Version

V1R5

CCIs

CCI-002385

Discussion

DoS prohibit a resource from being available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of network devices to mitigate the impact of DoS attacks that have occurred or are ongoing on device availability. For each network device, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or restricting the number of sessions the device opens at one time). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks. The security safeguards cannot be defined at the DoD-level because they vary according to the capabilities of the individual network devices and the security controls applied on the adjacent networks (for example, firewalls performing packet filtering to block DoS attacks).

Check Content

Log in to the FortiGate GUI with Super-Admin privilege.

1. Click Policy and Objects.
2. Click on IPv4 DoS Policy or IPv6 DoS Policy.
3. Identify the port designated for FortiGate device management.
4. Select the policy and click Edit.
5. Verify appropriate L3 Anomalies and L4 Anomalies are configured to meet the organization requirement.
6. Verify the policy is Enabled.

If appropriate DoS policies are not defined or are disabled, this is a finding.

Fix Text

Log in to the FortiGate GUI with Super-Admin privilege.

1. Click Policy and Objects.
2. Click IPv4 DoS Policy or IPv6 DoS Policy.
3. Identify the port designated for FortiGate device management.
4. Click +Create New.
5. Define the Incoming Interface, Source Address, Destination Address, and Services.
6. Configure L3 Anomalies, and L4 Anomalies to meet the organization requirement.
7. Click OK.