Rule ID
SV-266086r1024925_rule
Version
V1R2
CCIs
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.
From the BIG-IP Console: cat /etc/ntp/keys #Verify this key is installed on all the NTP servers and clients participating in the NTP time synchronization. tmsh list sys ntp include #Verify there is a line similar to the following: #server <ntp server> key <trusted key number matched to /etc/ntp/keys> iburst trustedkey <trusted key number matched to /etc/ntp/keys> If the BIG-IP appliance is not configured to authenticate Network Time Protocol sources using authentication that is cryptographically based, this is a finding.
From the BIG-IP console, type the following commands: echo "1 M <passphrase> #MD5 Key" > /etc/ntp/keys Note: This command assumes that no other keys have been previously configured in the /etc/ntp/keys file. Running this command will overwrite the file. #Make sure this key is installed on all the NTP servers and clients participating in the NTP time synchronization. tmsh edit sys ntp all-properties #Replace the "include" section with the following (add as many ntp server lines as necessary for the environment, but configure at least 2): include "server <ntp server> key <trusted key number matched to /etc/ntp/keys> iburst trustedkey <trusted key number matched to /etc/ntp/keys> server <ntp server> key <trusted key number matched to /etc/ntp/keys> iburst trustedkey <trusted key number matched to /etc/ntp/keys>" tmsh save sys config