STIGViewer Support

The FortiGate device must authenticate Network Time Protocol (NTP) sources using authentication that is cryptographically based.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-234202FGFW-ND-000215SV-234202r961506_ruleCCI-001967medium
Description
If NTP is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to network devices, which will make log timestamps inaccurate and affect scheduled actions. NTP authentication is used to prevent this tampering by authenticating the time source.
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-234202r961506_chk)

Log in to the FortiGate GUI with Super-Admin privilege. 1. Open a CLI console, via SSH or available from the GUI. 2. Run the following command: # diagnose sys ntp status The output should be similar to: ipv4 server(URL of NTP server) 123.123.123.123 -- reachable(0xbf) S:1 T:242 selected server-version=4, stratum=2 reference time is e213a5fb.2250b45e -- UTC Wed Mar 11 18:01:31 2020 clock offset is 0.000801 sec, root delay is 0.000381 sec root dispersion is 0.053268 sec, peer dispersion is 287 msec If the output does not return server-version is equal to 4, this is a finding.

Fix Text (F-37352r611794_fix)

Log in to the FortiGate GUI with Super-Admin privilege. 1. Open a CLI console, via SSH or available from the GUI. 2. Run the following command: # config system ntp # set ntpsync enable # set type custom # set syncinterval {INTEGER} # config ntpserver # edit {ID} # set server {IP ADDRESS} # set authentication enable # set key {PASSWORD} # set key-id {INTEGER} # next # end