HPE Alletra Storage ArcusOS Web Server Security Technical Implementation Guide
Pick two releases to diff their requirements.
Open a previous version of this STIG.
Supporting documents 4 PDFs
Bundled by DISA alongside this STIG release: overview, revision history, and readme files. Download the full archive or open an individual PDF.
- RMF Control
- SC-28
- Severity
- M
- CCI
- CCI-001199
- Version
- ASMP-WS-000630
- Vuln IDs
-
- V-283027
- Rule IDs
-
- SV-283027r1193771_rule
Checks: C-87590r1193769_chk
Verify HPE Alletra Storage MP is configured to provide backend drive encryption with the following command: Cli%controlencryption status -d Licensed Enabled BackupSaved State SeqNum Keystore FIPS non-SEDs FailedDisks nodeNonSED yes yes yes normal 0 --- yes 12 0 0 If the output does not show licensed, enabled, BackupSaved, and FIPS as "yes" this is a finding. If the state is not "normal", this is a finding. If Keystore is not "EKM", this is a finding.
Fix: F-87495r1193770_fix
Enable data at rest encryption. If "cli% showlicense" does not show "SED Encryption" under "License features currently enabled:", then import a SED Encryption license with the "cli% setlicense" command. Create a CSR for the EKM: cli% createcert ekm-client -f -csr -CN ekm_username Sign the CSR with a CA and import the entire certificate chain with: Cli% importcert ekm-client -f stdin Paste the ekm-client certificate chain. Import the EKM Server Certificates: Cli% createcert ekm-server -f stdin Paste the ekm-server certificate chain. Set the connection to the EKM with the following command: cli% controlencryption setekm -setserver <EKM_IP> -port 5696 -ekmuser ekm_username -kmipprotocols (supported protocols by the ekm) -passwordnoprompt <ekm_user_password> Enable encryption with the following command: cli% controlencryption enable -ekm /common/encryptionBackup Enter passwords and save the encryption backup file off of the array for disaster recovery.
- RMF Control
- AC-12
- Severity
- M
- CCI
- CCI-002361
- Version
- ASMP-WS-000730
- Vuln IDs
-
- V-283037
- Rule IDs
-
- SV-283037r1193801_rule
Checks: C-87600r1193799_chk
Verify the WSAPI Session Timeout value is set with the following command: %cli showwsapi -d -------------------------------WSAPI Server Configuration-------------------------------- service State: Enabled HPE GreenLake for Block Storage UI State: Active server State: Active HTTPS Port: 443 Number of Sessions Created: 0 System Resource Usage: 96 Number of Sessions Active: 0 Version: 1.14.0 Event Stream State: Enabled Max Number of SSE Sessions Allowed: 5 Number of SSE Sessions Created: 0 Number of SSE Sessions Active: 0 Session Timeout: 10 Minutes Policy : per_user_limit API URL: https://s2475-cluster.lr4-storage.net/api/v1 If "Session Timeout" is set to a value greater than "10 minutes", this is a finding.
Fix: F-87505r1193800_fix
Configure the WSAPI Session Timeout to a value less than or equal to 10 minutes: cli% setwsapi -timeout 10
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-002314
- Version
- ASMP-WS-000740
- Vuln IDs
-
- V-283038
- Rule IDs
-
- SV-283038r1193804_rule
Checks: C-87601r1193802_chk
Verify the RDA service is disabled and controlrecoveryauth is set to use ciphertext with the following commands: cli% stoprda RDA service is already disabled. cli% controlrecoveryauth status Recovery authentication method is Ciphertext. If the message returned is not "RDA service is already disabled", this is a finding. If the message returned is not "Recovery authentication method is Ciphertext", this is a finding.
Fix: F-87506r1193803_fix
Configure the system to disable remote access: Stop the RDA service: cli% stoprda Are you sure you want to stop RDA service? select q=quit y=yes n=no: Enter "y" to confirm the action. Set the recovery authentication to ciphertext: cli% controlrecoveryauth setmethod ciphertext
- RMF Control
- Severity
- M
- CCI
- CCI-003831
- Version
- ASMP-WS-001150
- Vuln IDs
-
- V-283073
- Rule IDs
-
- SV-283073r1193911_rule
Checks: C-87637r1193909_chk
Verify an SNMPv3 user account is configured: cli% showsnmpuser Username AuthProtocol PrivProtocol Alletrasnmpuser HMAC-SHA-96 CFB128-AES-128 If the output is not displayed in the above format, this is a finding.
Fix: F-87542r1193910_fix
Configure SNMPv3 alert notifications using the following sequence of operations: Create and enable an SNMPv3 user, and create associated keys for authentication and privacy. cli% createuser Alletrasnmpuser all browse Enter the password and confirm. cli% createsnmpuser Alletrasnmpuser At the prompt, enter the password. At the next prompt, reenter the password.
- RMF Control
- Severity
- M
- CCI
- CCI-003831
- Version
- ASMP-WS-001160
- Vuln IDs
-
- V-283074
- Rule IDs
-
- SV-283074r1193914_rule
Checks: C-87638r1193912_chk
Identify the SNMP trap recipient and report SNMP configuration: cli% showsnmpmgr HostIP Port SNMPVersion User Notify AlertClear <snmp trap recipient IP> 162 3 Alletrasnmpuser standard standard If the SNMP trap recipient IP address is incorrect, this is a finding. If the SNMP port is not "162", this is a finding. If the SNMP version is not "3", this is a finding. If the SNMP user ID is incorrect, this is a finding.
Fix: F-87543r1193913_fix
Configure SNMPv3 alert notifications using the following sequence of operations: Add the IP address of the SNMPv3 trap recipient, where permissions of the account are used: cli% addsnmpmgr -version 3 -snmpuser Alletrasnmpuser <ip address>
- RMF Control
- Severity
- M
- CCI
- CCI-004909
- Version
- ASMP-WS-001390
- Vuln IDs
-
- V-283090
- Rule IDs
-
- SV-283090r1193962_rule
Checks: C-87654r1193960_chk
Verify the system includes only approved certificates with the following command: s2475 cli% showcert Service Commonname Type Enddate Fingerprint cli* lr4-vlan3489-ca.lr4-storage.net rootca Mar 27 16:00:17 2034 GMT 741809eb70791ab41d4b695ffef01beb7ea3531e ekm-client test-user cert Mar 11 10:24:42 2034 GMT 7eae686ffe489b200a4a4bf353db4a0b139043db ekm-client CipherTrust Root CA rootca Mar 11 10:24:42 2034 GMT c2b3e77b89279d830299d60561152b2bedbf6ef6 ekm-server CipherTrust Root CA rootca Mar 11 10:24:42 2034 GMT c2b3e77b89279d830299d60561152b2bedbf6ef6 ldap lr4-storage-CA rootca May 31 17:38:44 2032 GMT 409e507985813f294f9c9464e488e46d903f4f58 syslog-sec-client lr4-vlan3489-ca.lr4-storage.net rootca Mar 27 16:00:17 2034 GMT 741809eb70791ab41d4b695ffef01beb7ea3531e syslog-sec-server lr4-vlan3489-ca.lr4-storage.net rootca Mar 27 16:00:17 2034 GMT 741809eb70791ab41d4b695ffef01beb7ea3531e wsapi lr4-vlan3489-ca.lr4-storage.net rootca Mar 27 16:00:17 2034 GMT 741809eb70791ab41d4b695ffef01beb7ea3531e For each certificate listed above, utilize the system documentation to verify the fingerprint(s) match the authorized certificate(s). If the fingerprint(s) listed above do not match the certificate(s) listed in the system documentation, this is a finding.
Fix: F-87559r1193961_fix
Install the correct certificate for each service using the importcert command. importcert <SSL_service> [-f] -ca <CA_bundle>