OpenControls Logo

STIG Viewer

STIGViewer Support

The HPE Alletra Storage ArcusOS device must implement cryptographic mechanisms to prevent unauthorized disclosure and modification of all information at rest on all system components.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283027ASMP-WS-000630SV-283027r1193771_ruleCCI-001199medium
Description
Data at rest is inactive data which is stored physically in any digital form (e.g., databases, data warehouses, spreadsheets, archives, tapes, off-site backups, mobile devices, etc.). Data at rest includes, but is not limited to, archived data, data that is not accessed or changed frequently, files stored on hard drives, USB thumb drives, files stored on backup tape and disks, and files stored off-site or on a storage area network. While data at rest can reside in many places, data at rest for a web server is data on the hosting system storage devices. Data stored as a backup on tape or stored off-site is no longer under the protection measures covered by the web server. There are several pieces of data that the web server uses during operation. The web server must use an accepted encryption method, such as SHA1, to protect the confidentiality and integrity of the information.
STIGDate
HPE Alletra Storage ArcusOS Web Server Security Technical Implementation Guide2026-03-03

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
END-02Endpoint Protection Measures
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (40) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-2(3)Disable Accounts
1.00
AC-2(8)Dynamic Account Management
1.00
AC-3Access Enforcement
1.00
AC-3(7)Role-based Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00
AU-10Non-repudiation
1.00
AU-4(1)Transfer to Alternate Storage
1.00
AU-5Response to Audit Logging Process Failures
1.00

+30 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.13.16
1.00
CCI1 mapping
CCI-001199
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

PR.DS-01
1.00

Who does this work

7 NICE work roles and 7 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-283027r1193771_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 Text (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.