Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Type "group --info | grep inactivity" and review the timeout value. If it is greater than 15 minutes, this is a finding.
Type "group --edit --inactivity_timeout 15".
Type "userpolicy --info" and review output for line: "Number of authentication attempts". If the value is 2 or less, this is not a finding.
Type "userpolicy --edit --allowed_attempts 2".
Attempt a login to NimOS by typing "ssh username@array", where username is a valid user, and array is an array DNS name. If the correct DoD banner is not displayed before a password prompt, this is a finding.
Type "group --edit --login_banner", and then copy-paste or type the required banner. Then, to display the banner before login, type "group --edit --login_banner_after_auth no".
Type "userpolicy --info" and review output for line: "Minimum Length". If it is 15 or more, this is not a finding.
Set minimum password length to 15 by typing "userpolicy --edit --min_length 15".
Type "userpolicy --info" and review output for line: "Minimum Uppercase characters". If it is 1 or more, this is not a finding.
Set minimum number of uppercase characters to 1 by typing "userpolicy --edit --upper 1".
Type "userpolicy --info" and review output for line: "Minimum Lowercase characters". If it is 1 or more, this is not a finding.
Set minimum number of lowercase characters to 1 by typing "userpolicy --edit --lower 1".
Type "userpolicy --info" and review output for line: "Minimum Digits". If it is 1 or more, this is not a finding.
Set minimum number of numeric characters to 1 by typing "userpolicy --edit --digit 1".
Type "userpolicy --info" and review output for line: "Minimum Special characters". If it is 1 or more, this is not a finding.
Set minimum number of special characters to 1 by typing "userpolicy --edit --special 1".
Type "userpolicy --info" and review output for line: "Minimum number of characters change from previous password". If it is 8 or more, this is not a finding.
Set minimum number of characters changed from previous password to 8 by typing "userpolicy --edit --previous_diff 8".
Type "group --info | grep inactivity" and review the timeout value. If it is greater than 10 minutes, this is a finding.
To set the inactivity timeout to 10 minutes, type "group --edit --inactivity_timeout 10".
Run the command "userauth --list". If the output is "No domains configured", this is a finding.
To configure AD, run the following commands: "userauth --join <domain> --domain_user administrator" and enter the domain administrator password to join <domain>. "userauth --list" will show the domain and its status. To create a mapping between an AD group and one of the four device RBAC roles, run the following command: "userauth --add_group <domain_group> --domain <domain> --role {administrator|poweruser|operator|guest}" This command allows any member of <domain_group> in <domain> AD domain to log in to the device with one of the selected roles. To display the group to role mappings, run "userauth --list_group --domain <domain>".
Type "cert --list". Review the output to confirm that the custom-ca and custom certificates exist, and the "Use" values specified for HTTPS and APIS are both "custom". If not, this is a finding.
To create and import a custom, CA-signed certificate, follow these steps: 1. Type "cert --gen custom-csr". Copy the displayed CSR and submit it to an appropriate signing authority. 2. Type "cert --import custom-ca" and paste the PEM-encoded CA certificate chain as input to the command. 3. Type "cert --import custom" and paste the signed certificate obtained from the CA.
Type "group --info | grep -i syslog" and review the output lines. The "Syslogd enabled" value should be "Yes", and the "Syslogd server" and "Syslogd port" values should contain the correct syslog server and port values. If not, this is a finding.
Configure email alerts (optional) group--edit [--smtp_serversmtp server] [--smtp_portsmtp port] [--smtp_auth {yes | no}] [--smtp_username username] --smtp_encrypt_type ssl [--smtp_from_addr email addr] [--smtp_to_addr email addr] [--send_event_data {yes | no}] [--alert_level {info | warning | critical}] To specify and enable logging of alerts, type "group --edit --syslog_enabled yes --syslog_server <server> --syslog_port <port>", where <server> and <port> are the server DNS name or IP address, and <port> is the port to send syslog messages to.
Log in to https://infosight.hpe.com using HPE Passport credentials. Click on the Main Menu icon in the upper left corner. Select Resources >> Alletra 6000, Nimble Storage >> Documentation. Determine current array OS version using User Interface (UI). Refer to Nimble "GUI Administration Guide" Version: NOS 5.2.x, section "Hardware and Software Updates", subsection "Find the Array OS Version" to determine the version of the OS that is currently in use by the array. Determine available array OS update versions using InfoSight. *Any version of Nimble OS software greater than the "current array OS version" might qualify to be an update to the "current array OS version". The option exists to bypass several releases to come up to the newest available release depending upon requirements. *Call HPE Support with any questions about choosing an appropriate release or the process to upgrade a release. - Follow above instructions to log in to HPE InfoSight. - Choose a "Software Version" from the left panel equal to or greater than the current array OS version. For example, 5.2.x would be equal to the current version and 5.3.x would be greater than the current version. - Open the Release Notes document for each version that is greater than the current array OS version. For example, "NimbleOS Release Notes Version NOS 5.2.1.700" is greater than NOS 5.2.1.600. - Review the entire release notes document. - Determine if this is a release should be used for an upgrade. - Confirm that the "From Version", for example 5.2.1.600, can be used to go to the version for which the release notes are applicable; for example 5.2.1.700. If the operating system version is no longer supported by the vendor, this is a finding.
To upgrade to a supported version, type "software --list". Select the last version listed with at least number 5.2.x. Type "software --download <version<, where <version< is the version selected. After the download is complete, type "software --update" and accept the terms and conditions. The update progress can be monitored using "software --update_status". Once finished, use "version" to verify that the new software has been installed correctly.
Verify that in Administration >> Security Policies page in the UI, "Unlimited" for the number of sessions is unchecked and a limit is specified. If a limit is not specified, this is a finding.
On the Administration >> Security Policies page in the UI, uncheck "Unlimited" for the number of sessions and specify a new limit.
To Determine if the HPE Nimble Array is configured to synchronize internal information system clocks with the primary NTP server: ArrayA:/# ntpq ntpq> sysinfo associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync, system peer: cxo-nmbldc-01.nimblestorage.com:123 system peer mode: client leap indicator: 00 stratum: 4 log2 precision: -24 root delay: 37.321 root dispersion: 265.639 reference ID: 10.157.24.95 reference time: e509b178.9f897118 Thu, Oct 7 2021 11:48:40.623 system jitter: 0.000000 clock jitter: 0.673 clock wander: 0.003 broadcast delay: -50.000 symm. auth. delay: 0.000 If the HPE Storage Array is not configured to synchronize internal information system clocks with the primary and secondary time sources located in different geographic regions using redundant authoritative time sources, this is a finding.
Configure the HPE Nimble Array to synchronize internal information system clocks with the primary time source: ArrayA:/# group --edit --ntpserver <ip_address_of_ntp_server> There would be a finding here given we only support primary ntp source.
Type "group --info | grep -i syslog" and review the output lines. The "Syslogd enabled" value should be "Yes", and the "Syslogd server" and "Syslogd port" values should contain the correct syslog server and port values. If not, this is a finding.
To specify and enable logging of alerts, type "group --edit --syslog_enabled yes --syslog_server <server> --syslog_port <port>", where <server> and <port> are the server DNS name or IP address, and <port> is the port to send syslog messages to.
Navigate to Administration >> Alerts and Monitoring page of the storage array management interface. Verify the checkbox is not checked. If HPE InfoSight is enabled, this is a finding.
In HPE Nimble Storage arrays, data collection is disabled by default. Navigate to Administration >> Alerts and Monitoring page of the storage array management interface. Uncheck the checkbox.
Ensure cloud console is disabled. Type "group --info |grep -i "cloud enabled". If the response is "cloud enabled: Yes", this is a finding.
Disable cloud console Navigate to Administration >> Customization >> Data Services Cloud Console. Uncheck "Connect to Data Services Cloud Console".
Verify cloud console is disabled. Type "group --info |grep -i "cloud enabled". If the response is "cloud enabled: Yes", this is a finding.
Disable Alletra cloud console. Type "group --edit --cloud_management off". If the response is as follows, contact your HPE sales account team to request approval: "ERROR: Failed to change system configuration. Updating cloud management is not permitted."