Information
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.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
Configure the network device to authenticate SNMP messages using a FIPS-validated HMAC.
Configure the Arista network device following the example SNMP parameters to ensure messages are authenticated using FIPS-validated HMAC:
switch(config)#snmp-server engineID local f5717f444ca880dbb200
switch(config)#snmp-server chassis-id ID CC-7050X3
switch(config)#snmp-server contact FedSE
switch(config)#snmp-server location JITC
switch(config)#snmp-server view snmpview system included
switch(config)#snmp-server group testers v3 priv read snmpview
switch(config)#snmp-server user jitc-sw testers v3 localized f8527f444ca990dcc200 auth sha 7b65225a6abf5111cd951e6cb7e105aef5bcd734 priv aes a1aedb1986642e766d4c8032d58e73b72bc3528b
switch(config)#snmp-server host 192.168.10.31 version 3 priv jitc-sw
switch(config)#snmp-server enable traps snmp authentication
switch(config)#snmp-server enable traps snmp link-down
switch(config)#snmp-server enable traps snmp link-up