The TOE is NetApp Storage Encryption (NSE) running ONTAP 9.16.1, an authorization acquisition product that obtains and manages authorization data use to access encrypted data stored on a FIPS validated full disk encryption product. The TOE provides authorization data to FIPS validated third party self-encrypting drives (SEDs).
","evaluation_configuration":"The TOE is NetApp Storage Encryption (NSE) running ONTAP 9.16.1, an authorization acquisition product that obtains and manages authorization data used to access encrypted data stored on a FIPS validated full disk encryption product. The TOE provides authorization data to FIPS validated third party self-encrypting drives (SEDs).
\r\nThe physical boundary of the TOE encompasses the NetApp ONTAP 9.16.1 software.
\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 A1K \r\n | \r\n\r\n NVMe/SSD \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n AFF A20 \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 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 A30 \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 AFF A400 \r\n | \r\n\r\n NVMe/SSD \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n AFF A50 \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 A70 \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 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 A90 \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 C30 \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 C60 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n AFF C80 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 4U/48 internal drives \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 A1K \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 4U \r\n | \r\n
| \r\n ASA A20 \r\n | \r\n\r\n NVMe \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 A30 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n ASA C30 \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 A50 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 2U/24 internal drives \r\n | \r\n
| \r\n ASA A70 \r\n | \r\n\r\n NVMe \r\n | \r\n\r\n 4U/48 internal drives \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 A90 \r\n | \r\n\r\n NVMe \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 FAS50 \r\n | \r\n\r\n HDD/SSD \r\n | \r\n\r\n 2U \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 FAS70 \r\n | \r\n\r\n HDD/SSD \r\n | \r\n\r\n 4U \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 FAS90 \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
\r\n
The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The evaluation demonstrated that the product meets the security requirements contained in the Security Target. The criteria against which the NetApp Storage Encryption (NSE) running ONTAP 9.16.1 was judged 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 NetApp Storage Encryption: Common Criteria Configuration Guide, Version 1.6, February 25, 2026, satisfies all of the security functional requirements stated in the NetApp Storage Encryption (NVE) Running ONTAP 9.16.1 Security Target, Version 1.8. The project underwent CCEVS Validator review. The evaluation was completed in February 2026. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11573-2026) prepared by CCEVS.
","environmental_strengths":"This section identifies the TOE’s logical boundaries:
\r\nThe TOE includes NIST CAVP-validated cryptographic algorithms supporting cryptographic functions. The TOE provides Key Wrapping, Key Derivation, and BEV Validation.
\r\nThe TOE supports management functions for forwarding requests to change the DEK to the 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 initiating TOE software updates using a command line interface.
\r\nThe TOE provides trusted firmware updates, protects Key and Key Material; and supports power saving states. The TOE runs a suite of self-tests during initial start-up (on power on).
\r\nThe list below identifies features or protocols that are not evaluated or must be disabled, and the rationale why. Note that this does not mean the features cannot be used in the evaluated configuration (unless explicitly stated so). It means that the features were not evaluated and/or validated by an independent third party and the functional correctness of the implementation is vendor assertion. Evaluated functionality is scoped exclusively to the security functional requirements specified in this Security Target. The features below are out of scope.
\r\n| \r\n Feature \r\n | \r\n\r\n Description \r\n | \r\n
| \r\n Networking protocols \r\n | \r\n\r\n Security functional requirements associated with networking protocols (NFS, SMB, etc.) are not evaluated and/or validated in the evaluated configuration. \r\n | \r\n
| \r\n High Availability \r\n | \r\n\r\n Security functional requirements associated with High Availability features provided by the TOE are not evaluated and/or validated in the evaluated configuration. \r\n | \r\n
| \r\n KMIP \r\n | \r\n\r\n KMIP client configurations provided by the TOE are not evaluated and/or validated in the evaluated configuration. \r\n | \r\n
| \r\n SnapLock \r\n | \r\n\r\n NetApp SnapLock is the WORM (write once, read many) compliance replication solution from NetApp. It provides integrated data protection for workloads that need to adhere to regulatory guidelines such as HIPAA, SEC 17a-4(f) rule, FINRA, and CFTC as well as national requirements for German-speaking countries (DACH). \r\nSnapLock was not included in the evaluation and was not tested in the evaluated configuration. \r\n | \r\n
| \r\n Trusted Platform Module (TPM) \r\n | \r\n\r\n The encryption keys for the onboard key manager (OKM) are not sealed by a physical TPM when running in Common Criteria mode. \r\n | \r\n
| \r\n MetroCluster \r\n | \r\n\r\n NetApp MetroCluster (MC) software is a solution that combines array-based clustering with synchronous replication to deliver continuous availability and zero data loss at the lowest cost. \r\nMetroCluster was not included in the evaluation and was not tested in the evaluated configuration. \r\n | \r\n
| \r\n System Manager GUI \r\n | \r\n\r\n The System Manager GUI is considered out of scope and all management is performed via the command line interface. \r\nNote: CLI management access excludes SSH access and is limited to serial console access only. \r\n | \r\n
| \r\n VMware Virtualization \r\n | \r\n\r\n VMware Virtualization was not included in the evaluation and was not tested in the evaluated configuration. \r\n | \r\n
| \r\n Cloud environments \r\n | \r\n\r\n ONTAP instances running within a cloud environment were not included in the evaluation and were not tested in the evaluated configuration. \r\n | \r\n