STIGViewer Support

The FortiGate device must authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-234201FGFW-ND-000210SV-234201r961506_ruleCCI-001967medium
Description
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network, internet). A remote connection is any connection with a device communicating through an external network (e.g., internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply the requirement to those limited number (and type) of devices that truly need to support this capability.
STIGDate
Fortinet FortiGate Firewall NDM Security Technical Implementation Guide2025-11-19

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

IAC-04Identification & Authentication for Devices
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (49) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(10)Authenticate Remote Commands
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-18(1)Authentication and Encryption
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-4(17)Domain Authentication
1.00
AC-7Unsuccessful Logon Attempts
1.00
AU-8Time Stamps
1.00

+39 more (top 10 by confidence shown)

CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

Details

Check Text (C-234201r961506_chk)

Log in to the FortiGate GUI with Super-Admin privilege. 1. Click System. 2. Click SNMP. 3. Verify the SNMPv3 settings are configured and enabled. 4. Select each SNMPv3 user and click Edit. 5. On Security Level, verify the SNMPv3 user is configured to use SHA256 as the Authentication Algorithm. If the FortiGate device is not configured to authenticate SNMP messages using a FIPS-validated HMAC, this is a finding. or 1. Open a CLI console, via SSH or available from the GUI. 2. Run the following command: # show full-configuration system snmp user | grep -i 'security-level\ |auth-proto' For each SNMPv3 user, the output should be similar to: set security-level auth set auth-proto sha256 If the security-level parameter is not set to auth or auth-priv, and the auth-proto is not set to SHA, this is a finding.

Fix Text (F-37351r850531_fix)

Log in to the FortiGate GUI with Super-Admin privilege. 1. Click System. 2. Click SNMP. 3. Select each SNMPv3 user. 4. Click Edit. 5. On Security Level, click Authentication. 6. Select SHA256 for the Authentication Algorithm. 7. Change the Password if required. 8. Click OK. 9. Click Apply. or 1. Open a CLI console, via SSH or available from the GUI. 2. Run the following command: # config system snmp user # edit {NAME} # set status enable # set security-level auth # set auth-proto sha256 # set auth-pwd {PASSWORD} # next # end