The Target of Evaluation (TOE) is NetApp Storage Encryption (NSE) running ONTAP 9.14.1, an authorization acquisition product that obtains and maintains authorization data used to access encrypted data stored on a full disk encryption product. It provides authorization data to third party self-encrypting drives (SEDs).
\r\nONTAP 9.14.1 is a proprietary operating system and data management software that provides storage for applications that read and write data over block- or file-access protocols, in storage configurations that range from high-speed flash to lower- priced spinning media. All drives used by the TOE are FIPS validated third party SED devices.
\r\nThe TOE is provided pre-installed on NetApp disk storage appliances consisting of storage controllers and one or more enclosures of SEDs. It supports third party SEDs that follow either the Trusted Computing Group’s (TCG) Opal or Enterprise standards. Both standards support the use of an authentication key (AK) and one or more data encryption keys (DEK) per drive. The AK is used by a client (client in this case indicating ONTAP, the NetApp operating system) to unlock a drive. Once the drive verifies that the AK is correct, it uses the AK to decrypt the drive’s DEK(s).
","evaluation_configuration":"The non-TOE hardware required by and provisioned with the TOE is identified in the table below.
\r\n| \r\n NetApp Controllers \r\n | \r\n\r\n Disk Type \r\n | \r\n\r\n Controller Form Factor \r\n | \r\n
| \r\n AFF A150 \r\n | \r\n\r\n SSD \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n AFF A220 \r\n | \r\n\r\n SSD \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n AFF A250 \r\n | \r\n\r\n NVMe/SSD \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n AFF A300 \r\n | \r\n\r\n SSD \r\n | \r\n\r\n 3U \r\n | \r\n
| \r\n AFF A320 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 2U \r\n | \r\n
| \r\n\r\n | \r\n\r\n NVMe/SSD \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n AFF A800 \r\n | \r\n\r\n NVMe/SSD \r\n | \r\n\r\n 4U/48 internal drives \r\n | \r\n
| \r\n AFF A900 \r\n | \r\n\r\n NVMe/SSD \r\n | \r\n\r\n 8U \r\n | \r\n
| \r\n AFF C190 \r\n | \r\n\r\n SSD \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n AFF C250 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n AFF C400 \r\n | \r\n\r\n NVME \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n AFF C800 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n ASA A150 \r\n | \r\n\r\n SSD \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n ASA A250 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n ASA A400 \r\n | \r\n\r\n NVMe/SSD \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n ASA A800 \r\n | \r\n\r\n NVMe/SSD \r\n | \r\n\r\n 4U/48 internal drives \r\n | \r\n
| \r\n ASA A900 \r\n | \r\n\r\n NVMe/SSD \r\n | \r\n\r\n 8U \r\n | \r\n
| \r\n ASA C250 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n ASA C400 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n ASA C800 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n ASA AFF A220 \r\n | \r\n\r\n SSD \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n FAS2720 \r\n | \r\n\r\n HDD/SSD \r\n | \r\n\r\n 2U/12 internal drives \r\n | \r\n
| \r\n FAS2750 \r\n | \r\n\r\n HDD/SSD \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n FAS2820 \r\n | \r\n\r\n HDD/SSD \r\n | \r\n\r\n 2U/12 internal drives \r\n | \r\n
| \r\n FAS500f \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n FAS8200 \r\n | \r\n\r\n HDD/SSD \r\n | \r\n\r\n 3U \r\n | \r\n
| \r\n FAS8300 \r\n | \r\n\r\n HDD/SSD \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n FAS8700 \r\n | \r\n\r\n HDD/SSD \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n FAS9500 \r\n | \r\n\r\n HDD/SSD \r\n | \r\n\r\n 8U \r\n | \r\n
The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the TOE was evaluated are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 Revision 5. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 Revision 5. The product, when configured as identified in the guidance documentation, satisfies all of the security functional requirements stated in the NetApp Storage Encryption (NSE) Running ONTAP 9.14.1 Security Target. The evaluation was completed in November 8, 2024. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"Cryptographic Support
\r\nThe TOE includes NIST CAVP-validated cryptographic algorithms supporting cryptographic functions. The TOE provides key wrapping, key derivation, and validation of the Border Encryption Value (BEV).
\r\nSecurity Management
\r\nThe TOE supports management functions for forwarding requests to change the DEK to the Encryption Engine (EE), forwarding requests to cryptographically erase the DEK to the EE, allowing authorized users to change authorization factors or set of authorization factors used, and initiate TOE software updates using a command line interface.
\r\nProtection of the TSF
\r\nThe TOE provides trusted firmware updates, protects keys and key material, and supports Compliant power saving states. The TOE runs a suite of self-tests during initial start-up (on power on).
","features":[{"id":1506,"feature_name":"Cryptographic Hashing"},{"id":1505,"feature_name":"Cryptographic Signature Verification"},{"id":1493,"feature_name":"DRBG"},{"id":1492,"feature_name":"Full Drive Encryption"},{"id":1509,"feature_name":"Keyed-hash message authentication"},{"id":1499,"feature_name":"Symmetric Key Generation"}]}