Title

The TippingPoint SMS must authenticate Network Time Protocol sources using authentication that is cryptographically based. (Cat I impact)

Discussion

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., the 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.

Check Content

In the SMS client, ensure NTP authentication is enabled. 1. Log in to the serial console or ESXi virtual console. 2. Run the command ntp-auth. If NTP auth is not enabled for client and server, this is a finding.

Fix Text

In the SMS client, ensure NTP authentication is enabled. 1. Log in to the serial console or ESXi virtual console. 2. Run the command ntp-auth. 3. Select "Y" to change the NTP Authentication settings. 4. Select “A”, enter a key ID. 5. Select "V" to add the key value. 6. Select "T" and ensure SHA1 is added. 7. Select "K" and enter the key ID number. 8. Select "U" and "E" for enable for client and server authentication.

Additional Identifiers

Rule ID: SV-242250r961506_rule

Vulnerability ID: V-242250

Group Title: SRG-APP-000395-NDM-000347

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.