![NetApp AltaVault AVA400 Administration Manual Download Page 109](http://html.mh-extra.com/html/netapp/altavault-ava400/altavault-ava400_administration-manual_1669933109.webp)
NetApp AltaVault Cloud Integrated Storage Administration Guide
109
Beta Draft
Configuring AltaVault appliances for FIPS-compliant cryptography Configuring AltaVault appliances for FIPS-compliant cryptography
If you specify a key size that is not 2048-bit or higher with FIPS mode enabled, the system blocks the key generation
and warns that the key size is not supported in FIPS mode.
NTP
NTP using either SHA authentication keys or no authentication keys is FIPS compliant. NTP using MD5 keys is not
FIPS compliant.
If you configure an MD5 key for NTP using the following command, the system generates a warning message and the
system will not be FIPS compliant:
amnesiac (config) # ntp authentication key <id> type MD5 secret <secret password>
To verify that NTP is running in FIPS mode, examine the system log when NTPD starts (this occurs whenever the NTP
configuration is modified) and ensure that the NTPD entry sets FIPS mode:
Mar 18 15:49:57 amnesiac pm[4989]: [pm.NOTICE]: Launched ntpd with pid 27617
Mar 18 15:49:57 amnesiac ntpd[27617]: ntpd [email protected] Thu May 17 21:31:11 UTC 2012 (1)
…
Mar 18 15:49:57 amnesiac ntpd[27617]: FIPS_mode_set(1)
For more information about system logs, see
“Viewing system logs” on page 142
RADIUS and
The RADIUS and protocols are not FIPS compliant. These protocols use noncompliant hash algorithms.
The system displays a warning message if you configure these features in FIPS mode.
The following commands generate a configuration warning in FIPS mode:
aaa accounting per-command default
aaa authentication [console-login | login] default [radius | ]
aaa authorization per-command default
SNMP
SNMP is FIPS compliant except if SNMP user passwords are configured with noncompliant hash algorithms. If you
configure an SNMP user password with MD5 or DES protocols using the following command, the system generates
a warning message and the system will not be FIPS compliant:
snmp-server user <username> password plain-text <password> [auth-protocol MD5 priv-protocol DES
priv-key plain-text <password>]
To verify that SNMP runs in FIPS mode, look for entries similar to the following in the system log when SNMP starts
(this occurs whenever the SNMP configuration changes) and ensure that FIPS mode is set:
Mar 18 16:05:10 amnesiac pm[4989]: [pm.NOTICE]: Launched snmpd with pid 31709
Mar 18 16:05:10 amnesiac snmpd[31709]: FIPS_mode_set(1)
…
Mar 18 16:05:10 amnesiac snmpd[31709]: NET-SNMP version 5.3.1
For more information about system logs, see
“Viewing system logs” on page 142
SSH
SSH requires the use one of the following ciphers to run in FIPS mode:
Summary of Contents for AltaVault AVA400
Page 2: ...Beta Draft ...
Page 10: ...Beta Draft Contents ...