Fortanix DSM with NetApp ONTAP Using NAE

Prev Next

1.0 Introduction

This article describes the process of integrating Fortanix-Data-Security-Manager (DSM) with NetApp ONTAP using NetApp Aggregate Encryption (NAE) to centrally manage keys. It explains how to configure Fortanix DSM as an external Key Management Interoperability Protocol (KMIP) key manager, create an NAE-enabled aggregate, and create and verify an encrypted volume that uses the aggregate's encryption.

2.0 Product Tested Version

The following product versions were tested:

  • Fortanix DSM version 5.11

  • NetApp ONTAP version 9.19.1P2

3.0 Prerequisites

Ensure the following:

  • NetApp ONTAP version 9 is installed on the system along with Volume Encryption (VE) license applied.

  • Fortanix DSM cluster is running a tested version.

4.0 Architecture Workflow

Figure 1: Architecture diagram

This architecture diagram illustrates how NetApp ONTAP integrates with Fortanix DSM using the KMIP for secure encryption key management.

NetApp ONTAP uses NetApp Aggregate Encryption (NAE) to encrypt data at the aggregate level. Volumes created on an NAE-enabled aggregate inherit the aggregate's encryption. Fortanix DSM manages the encryption keys separately from the storage system. ONTAP communicates with Fortanix DSM over KMIP to access the encryption keys required for data encryption and decryption.

KMIP standardizes the communication between NetApp ONTAP and Fortanix DSM, enabling secure retrieval and centralized management of encryption keys. Fortanix DSM serves as the external key manager, while ONTAP uses the managed keys to encrypt and decrypt data stored in NAE-enabled aggregates.

Fortanix DSM enforces authentication for users, applications, and systems before granting access to encryption keys, preventing unauthorized decryption. Even if NetApp ONTAP storage is compromised, the encrypted data remains secure since the keys are centrally managed within DSM through KMIP, maintaining strong access control and compliance with security standards.

5.0 Configure Fortanix DSM

A Fortanix DSM service must be configured, and the URL must be accessible. To create a Fortanix DSM account and group, refer to the following sections:

5.1 Signing Up

To get started with the Fortanix DSM cloud service, you must register an account at <Your_DSM_Service_URL>. For example, https://amer.smartkey.io. On-premises customers use the KMS URL, and the SaaS customers can use the URLs as listed here based on the application region.

For more information on how to set up the Fortanix DSM, refer to Sign Up for Fortanix Data Security Manager SaaS.

5.2 Creating an Account

Access <Your_DSM_Service_URL> in a web browser and enter your credentials to log in to Fortanix DSM.

Figure 2: Logging in

For more information on how to set up an account in Fortanix DSM, refer to Getting Started with Fortanix Data Security Manager - UI.

5.3 Creating a Group

Perform the following steps to create a group in the Fortanix DSM:

  1. In the DSM left navigation panel, click the Groups menu item, and then click ADD GROUP to create a new group.

    Figure 3: Add groups

  2. On the Adding new group page:

    1. Title: Enter a name for your group.

    2. Description (optional): Enter a short description of the group.

  3. Click SAVE to create the new group.

For more information about groups, refer to Definitions.

TIP

It is recommended to configure a Key undo policy for groups for the cryptographic keys used by the application before creating or using the keys. Without a configured Key undo policy, key deletion is permanent and the deleted key cannot be recovered. Deleting an encryption key may result in permanent loss of access to the protected data and service disruption for applications that depend on the deleted key. For detailed steps, refer to Key Undo Policy.

5.4 Creating an Application

Perform the following steps to create an application (app) in the Fortanix DSM:

  1. In the DSM left navigation panel, click the Apps menu item, and then click ADD APP to create a new app.

    Figure 4: Add application

  2. On the Adding new app page:

    1. App name: Enter the name for your application.

    2. ADD DESCRIPTION (optional): Enter a short description of the application.

    3. Authentication method: Select the default API Key as the authentication method from the drop down menu. For more information on these authentication methods, refer to Authentication.

    4. Assigning the new app to groups: Select the group created in Section 5.3: Creating a Groupfrom the list.

  3. Click SAVE to add the new application.

For more information about applications, refer to Definitions.

5.5 Copying the App UUID

Perform the following steps to copy the app UUID from the Fortanix DSM:

  1. In the DSM left navigation panel, click the Apps menu item, and then click the app created in Section 5.4: Creating an Application to go to the detailed view of the app.

  2. From the top of the app’s page, click the copy icon next to the app UUID to copy it to use in Section 5.6: Generating a Certificate.

5.6 Generating a Certificate

A certificate must be generated to identify the application through which KMIP keys will be generated and retrieved by ONTAP.

Two methods are available for generating this certificate:

5.6.1 Creating a CSR for Certificate Issuance from a Trusted CA (Production Environment)

Perform the following steps to create a Certificate Signing Request (CSR) for certificate issuance from a Trusted Certificate Authority (CA):

  1. Use the following command to create a CSR:

    openssl req -out cert.pem -new -newkey rsa:2048 -nodes -keyout key.pem
  2. Fill out the certificate request fields according to your organization's standards. Ensure that the Common Name (CN) field is set to the Fortanix DSM app UUID as copied in Section 5.5: Copying the App UUID.

  3. Submit the cert.pem file to your local Certificate Authority (CA) for issuance.

  4. Download the issued certificate as cert.pem from the CA, ensuring it is stored in PEM format.

  5. Obtain copies of the Root CA and Intermediate CA certificates in PEM format. Save them in file Fortanix_DSM_CA.cer.

    Figure 5: Example command for certificate request

5.6.2 Creating Self-Signed Certificate (Lab Environment)

Run the following command to generate a self-signed certificate:

openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days 365 -subj "/CN={Fortanix DSM App UUID}" 

Replace the {Fortanix DSM app UUID} with the actual app UUID copied in Section 5.5: Copying the App UUID.

5.7 Updating the Authentication Method

Perform the following steps to change the authentication method:

  1. Go to the detailed view of the app created in Section 5.4: Creating an Application. Click Change authentication method, and select the Certificate option to change the authentication method to Certificate.

  2. Click SAVE.

  3. On the Add certificate dialog box, click UPLOAD NEW CERTIFICATE to upload the certificate file or paste the content of the cert.pem certificate generated in Section 5.6: Generating a Certificate.

  4. Select both check boxes to confirm your understanding of the action.

  5. Click UPDATE to save the changes.

6.0 Configuration on NetApp ONTAP

The following section describes the procedures to add a Key Management Server (KMS) and to set up volume encryption to enhance the security of your data storage environment:

6.1 Installing the Client and Server CA Certificates

Perform the following steps to add a Key Management Server (KMS) to NetApp ONTAP:

  1. Run the following command to update the certificate and key for the client:

    security certificate install -type client

    Copy and paste the output of the certificate and key generated in Section 5.6: Generating a Certificate when prompted.

  2. When asked, Do you want to continue entering root and/or intermediate certificates?, type n:

    Do you want to continue entering root and/or intermediate certificates: n
  3. If your Issuing CA for the KMIP certificate is a public CA that is kept current with ca-certificates, then proceed to Step 6.

  4. Open the Fortanix DSM root CA certificate, Fortanix_DSM_CA.cer, saved previously with a text editor and copy the certificate value.

  5. Run the following command to update the certificate and key for the server:

    security certificate install -type server-ca

    Paste the output of the certificate from Step 4 when prompted.

  6. Run the following command to confirm the name of the imported Client and Server-CA Certificates:

    security certificate show-user-installed

    NetApp_ConfirmName.png

    Figure 6: Confirm name of imported certificate

Note the unique names of the installed client and server CA certificates from the command output. You will need these names when enabling the external key manager in the next section.

6.2 Enabling Fortanix DSM as the External Key Manager

This section describes how to configure Fortanix DSM as the external key manager on the ONTAP cluster and verify the KMIP connection.

Perform the following steps:

  1. Run the following command to specify the Fortanix DSM KMIP server, the client certificate, and the server CA certificate:

    security key-manager external enable -vserver <vserver-name> \ 
      -key-servers <dsm-kmip-server-ip>:5696 \ 
      -client-cert <client-certificate-name> \ 
      -server-ca-certs <server-ca-certificate-name> 

    Where,  

    • <vserver-name>: The name of the cluster storage virtual machine (SVM) on which to enable the external key manager.

    • <dsm-kmip-server-ip>: The IP address of the Fortanix DSM KMIP server.

    • <client-certificate-name>: The unique name of the client certificate installed on the ONTAP cluster for authentication with Fortanix DSM.

    • <server-ca-certificate-name>: The unique name of the server CA certificate installed on the ONTAP cluster to verify the Fortanix DSM server certificate.

  2. Run the following command to verify the external key manager configuration:

    security key-manager external show 

    Output:

    The output shows Enabled: true and lists the Fortanix DSM KMIP server as the primary key server.

  3. Run the following command to verify the status of the key server:

    security key-manager external show-status 

    Output:

    The output shows KMIP is operational: true and a server status of available, indicating that ONTAP can communicate with the Fortanix DSM KMIP server.  

7.0 Configure an Aggregate with NAE

This section describes how to create a new aggregate with NAE or enable NAE on an existing aggregate. It also explains how to encrypt existing volumes, migrate NVE-encrypted volumes to NAE, and verify that new volumes use NAE by default.

7.1 Enable NAE on an Existing Aggregate

To enable NAE on an existing aggregate, first verify the encryption status of its volumes. All volumes must be encrypted before you enable aggregate-level encryption. Plaintext volumes must first be encrypted using NVE. After enabling aggregate-level encryption, migrate the existing NVE-encrypted volumes to NAE.

7.1.1 Verify the Existing Aggregate and Volume Encryption Status

Before enabling NAE, identify the existing aggregates and verify their encryption status. Also, identify any plaintext volumes that require encryption.

Perform the following steps:

  1. Run the following command to view the existing aggregates in the ONTAP cluster:

    storage aggregate show

    Output:

  2. Run the following command to check whether aggregate-level encryption is enabled:

    storage aggregate show –fields encrypt-with-aggr-key

    Output:

    Where, the encrypt-with-aggr-key field indicates the aggregate encryption status:

    • true: Aggregate-level encryption is enabled.

    • false: Aggregate-level encryption is not enabled.

    Output:

  3. Run the following command to list all encrypted volumes:

    volume show -is-encrypted true

    Output:

  4. Run the following command to view the encryption status and encryption type of the volumes in the aggregate:

    volume show -aggregate <aggregate-name> -fields volume,is-encrypted,encryption-type

    Where, <aggregate-name> is the name of the aggregate to verify identify the volumes that are not encrypted and report the following values:

    • encryption-type = none

    • is-encrypted = false

    For example:

    volume show -aggregate NetApp_Test_aggregate -fields volume,is-encrypted,encryption-type

    Output:

    NOTE

    All volumes in an existing aggregate must be encrypted before the aggregate can be configured for NAE. Encrypt plaintext volumes using NVE before enabling aggregate-level encryption.

7.1.2 Encrypt Plaintext Volumes Using NVE

ONTAP provides the volume encryption conversion start command to encrypt an existing volume in place without relocating it to another aggregate.

During this operation:

  • ONTAP creates an individual encryption key for the volume.

  • The encryption key is managed through the configured external key management infrastructure.

  • ONTAP encrypts the existing volume data.

  • The volume transitions from plaintext to an NVE-encrypted volume.

  • The volume remains on its existing aggregate.

  • This operation does not enable NAE on the aggregate.

Perform the following steps for each plaintext volume identified in the previous section:

  1. Run the following command to initiate in-place encryption conversion:

    volume encryption conversion start -vserver <svm-name> -volume <volume-name>

    Where,

    • <svm-name>: The name of the SVM that contains the volume.

    • <volume-name>: The name of the plaintext volume to encrypt.

    Output:

  2. Run the following command to monitor the encryption conversion:

    volume encryption conversion show

    Output:

    Monitor the conversion until it completes.

  3. After the conversion completes, run the following command to verify the volume encryption status:

    volume show -vserver <svm-name> -volume <volume-name> -fields aggregate,state,encryption-type,is-encrypted

    Where,

    • <svm-name>: The name of the SVM that contains the volume.

    • <volume-name>: The name of the plaintext volume to encrypt.

    Output:

  4. Verify that the volume reports encryption-type = volume and is-encrypted = true. This confirms that the volume has transitioned from plaintext to an NVE-encrypted volume.

  5. Repeat these steps for all plaintext volumes identified in the previous section.

NOTE

  • NVE conversion is an intermediate operation for plaintext volumes only.

  • Do not initiate another in-place encryption conversion for volumes that are already encrypted using NVE.

  • After all plaintext volumes have been successfully encrypted using NVE, the aggregate is ready for NAE enablement.

7.1.3 Enable Aggregate-Level Encryption on the Existing Aggregate

After encrypting all plaintext volumes using NVE, enable aggregate-level encryption on the existing aggregate.

This operation updates the aggregate's encryption configuration and establishes the aggregate-level encryption capability required for NAE volumes.

Perform the following steps:

  1. Run the following command to verify that all volumes in the aggregate are encrypted:

    volume show -aggregate <aggregate-name> -fields volume,state,encryption-type,is-encrypted

    Where, <aggregate-name> is the name of the aggregate.

  2. Review the output and confirm that no plaintext volumes remain in the aggregate.

  3. Run the following command to check whether aggregate-level encryption is enabled:

    storage aggregate show -aggregate <aggregate-name> -fields encrypt-with-aggr-key

    Output:

  4. Run the following command to enable aggregate-level encryption:

    storage aggregate modify -aggregate <aggregate-name> -node <node-name> -encrypt-with-aggr-key true

    Where,

    • <aggregate-name>: The name of the aggregate.

    • <node-name>: The name of the node hosting the aggregate.

    Output:

  5. Enabling aggregate-level encryption has the following effects:

    • The aggregate becomes an NAE-enabled aggregate.

    • Aggregate-level encryption key management is established.

    • Existing NVE-encrypted volumes remain NVE-encrypted.

    • Existing NAE-encrypted volumes remain NAE-encrypted.

    • New volumes created in the aggregate use NAE by default.

    • Plaintext volumes are not permitted in the NAE-enabled aggregate.

    NOTE

    Enabling aggregate-level encryption does not automatically convert existing volumes to NAE. Existing NVE-encrypted volumes continue to use NVE, while plaintext volumes remain unencrypted. If you want existing volumes to use NAE, plaintext volumes must first be encrypted using NVE, and then migrated to the NAE-enabled aggregate. Migration is not required if you want existing NVE-encrypted volumes to retain volume-level encryption.

Perform the following steps:

  1. Run the following command to verify that aggregate-level encryption is enabled:

    storage aggregate show -aggregate <aggregate-name> -fields encrypt-with-aggr-key

    Review the output and confirm that the encrypt-with-aggr-key field is set to true.

  2. Run the following command to review the encryption status of the volumes in the aggregate:

    volume show -aggregate <aggregate-name> -fields volume,state,encryption-type,is-encrypted

    For example:

    volume show -aggregate NetApp_Test_aggregate -fields volume,state,encryption-type,is-encrypted
  3. Review the output. Existing NVE-encrypted volumes may still report:

    encryption-type = volume

    This is the expected output. The aggregate is NAE-enabled, but the existing NVE-encrypted volumes have not yet been converted to NAE.

After confirming that aggregate-level encryption is enabled, you can migrate the existing NVE-encrypted volumes to NAE if you want them to use aggregate-level encryption.

7.1.4 Migrate Existing Volumes to NAE (Optional)

If you want existing volumes to use aggregate-level encryption (NAE), you must migrate them to the NAE-enabled aggregate. Existing NVE-encrypted volumes must be moved to the NAE-enabled aggregate, while plaintext volumes must first be encrypted using NVE before they can be migrated.

Perform the following steps to migrate the existing volumes to NAE:

  1. Run the following command to migrate an NVE-encrypted volume to the NAE-enabled aggregate:

    volume move start -vserver <svm-name> -volume <volume-name> -destination-aggregate <aggregate-name> -encrypt-with-aggr-key true

    Where,

    • <svm-name>: The name of the SVM containing the volume.

    • <volume-name>: The name of the NVE-encrypted volume.

    • <aggregate-name>: The name of the NAE-enabled destination aggregate.

    For example:

    volume move start -vserver svm_poc -volume NAE_VOL_01 -destination-aggregate NetApp_Test_aggregate -encrypt-with-aggr-key true

    The -encrypt-with-aggr-key true parameter configures the destination volume to use aggregate-level encryption. You do not need to decrypt the source volume before starting the migration or perform another in-place NVE conversion.

  2. Review the command response and note the generated job ID.

    [Job 42] Job queued: Move "NAE_VOL_01"
    in Vserver "svm_poc" to aggregate
    "NetApp_Test_aggregate".
    Use the "volume move show -vserver svm_poc
    -volume NAE_VOL_01" command to view the
    status of this operation.
  3. Run the following command to monitor the volume move operation:

    volume move show

    Output:

  4. Run the following command to check the migration status of a specific volume:

    volume move show -vserver <svm-name> -volume <volume-name>
  5. Monitor the operation until the volume move completes successfully.

    The volume move process performs the required data relocation and cutover operations. It can involve the following stages:

    • Destination preparation.

    • Initial data replication.

    • Incremental data synchronization.

    • Replication of changes occurring during migration.

    • Cutover preparation.

    • Final synchronization and cutover.

    • Completion of the volume move.

    The volume move operation is designed to maintain volume availability during most of the migration process. However, a brief I/O interruption may occur during the final cutover.

    The actual migration duration depends on the volume size, workload activity, available system resources, and migration conditions.

  6. After the volume move completes, run the following command to verify the volume's aggregate and encryption status:

    volume show -vserver <svm-name> -volume <volume-name> -fields aggregate,state,is-encrypted,encryption-type

    For example:

    volume show -vserver svm_poc -volume NAE_VOL_01 -fields aggregate,state,is-encrypted,encryption-type

    Output:

  7. Verify that the volume is in the ‘online’ code fon state (available for read and write operations), ‘is-encrypted’ is ‘true’, and ‘encryption-type’ is ‘aggregate’. Also confirm that the volume is located on the intended NAE-enabled aggregate.

  8. After validating the first volume, repeat the migration procedure for the remaining NVE-encrypted volumes. Perform the migration in controlled batches based on workload criticality and available system resources.

NOTE

For each volume:

  • Verify the current encryption type of each volume.

  • Verify that the destination aggregate has aggregate-level encryption enabled.

  • Ensure that no other volume move operation is active for the volume.

  • Record the generated job ID.

  • Monitor the replication phase.

  • Verify that the volume move completes successfully.

  • Validate the final encryption type.

  • Confirm that the volume remains online.

  • Record the migration result in the implementation log.

  • Validate each volume independently. Do not assume that all volumes use NAE just because the aggregate has NAE enabled.

7.1.5 Verify the NAE Conversion

Perform the following steps:

  1. Monitor the volume move operation until it completes successfully.

  2. Run the following command to verify the migrated volume:

    volume show -vserver <svm-name> -volume <volume-name> -fields aggregate,state,is-encrypted,encryption-type

    Where,

    • <svm-name>: The name of the SVM that contains the volume.

    • <volume-name>: The name of the plaintext volume to encrypt.

    For example:

    volume show -vserver svm_poc -volume NAE_VOL_01 -fields aggregate,state,is-encrypted,encryption-type
  3. Review the output and verify the final aggregate, volume state, encryption status, and encryption type.

  4. After validating the first volume, repeat the migration procedure for the remaining NVE-encrypted volumes.

  5. Perform the migration in controlled batches based on workload criticality and available system resources.

  6. Run the following command to check the migration status of a specific volume, if required:

    volume move show -vserver <svm-name> -volume <volume-name>

    Where,

    • <svm-name>: The name of the SVM that contains the volume.

    • <volume-name>: The name of the plaintext volume to encrypt.

    Output:

After encrypting all volumes using NVE, check the Fortanix DSM application audit logs to confirm the encryption operations.

Figure 7: App page

Figure 8: Security objects page

7.1.6 Create a New Volume in an NAE-enabled Aggregate

After migrating all existing NVE-encrypted volumes, verify that each volume uses NAE.

Perform the following steps:

  1. Run the following command to create a new volume in the NAE-enabled aggregate:

    volume create -vserver <svm-name> -volume <volume-name> -aggregate NetApp_Test_aggregate -size 20MB

    Where,

    • <svm-name>: The name of the SVM that contains the volume.

    • <volume-name>: The name of the plaintext volume to encrypt.

  2. Run the following command to verify the new volume's encryption status:

    volume show -vserver <svm-name> -volume <volume-name> -fields aggregate,state,is-encrypted,encryption-type

    Where,

    • <svm-name>: The name of the SVM that contains the volume.

    • <volume-name>: The name of the plaintext volume to encrypt.

    Output:

  3. Verify that the new volume is automatically encrypted using NAE.

    Monitor the operation until the volume move completes successfully.

7.2 Create a New Aggregate with NAE

This section describes how to create a new aggregate and verify that aggregate-level encryption (NAE) is enabled on it. After creating the aggregate, review the proposed aggregate layout and confirm its creation. Then, verify the NAE configuration using the ONTAP CLI.

Perform the following steps:

  1. Run the following command to create a new volume in the NAE-enabled aggregate:

    storage aggregate create -aggregate <aggregate-name> \ 
      -node <node-name> -diskcount 5 

    Where,  

    • <aggregate-name>: The name to assign to the new aggregate.

    • <node-name>: The name of the ONTAP node on which to create the aggregate.

    ONTAP displays the proposed aggregate layout. Enter y at the prompt to continue:

    Output:

    Info: The layout for aggregate "Fortanix_NAE_Aggr" on node "Fortanix-NetApp-Cluster-01" would be: 
    Usable Physical 
              Position   Disk                      Type           Size     Size 
              ---------- ------------------------- ---------- -------- -------- 
              dparity    NET-1.14                  FCAL              -   1.00GB 
              parity     NET-1.22                  FCAL              -   1.00GB 
              data       NET-1.23                  FCAL         1000MB   1.00GB 
              data       NET-1.24                  FCAL         1000MB   1.00GB 
              data       NET-1.25                  FCAL         1000MB   1.00GB 
     
          Aggregate capacity available for volume use would be 2.64GB. 
     
    Do you want to continue? {y|n}: y 
    [Job 28] Job succeeded: DONE 
  2. Run the following command to verify that the aggregate uses NAE:

    storage aggregate show -aggregate <aggregate-name> -fields encrypt-with-aggr-key 

    Where, <aggregate-name> is the name of the aggregate to verify.

    Output:

    aggregate         encrypt-with-aggr-key 
    ----------------- --------------------- 
    Fortanix_NAE_Aggr true 

    The value true in the encrypt-with-aggr-key field confirms that the aggregate uses NAE.

  3. Review the output and verify that the new volume is online, encrypted, and uses NAE.

8.0 Create and Verify an Encrypted Volume

Volumes created in an aggregate with NAE enabled automatically inherit aggregate-level encryption. You do not need to specify the ‘-encrypt true’ parameter when creating the volume. This section describes how to create a volume in an NAE-enabled aggregate and verify the volume encryption.

  1. Run the following command to create a volume on the NAE aggregate:

    volume create -vserver <data-vserver-name> -volume <volume-name> \
    -aggregate <aggregate-name> -size 20MB

    Where,

    • <data-vserver-name>: The name of the data SVM on which to create the volume.

    • <volume-name>: The name to assign to the new volume.

    • <aggregate-name>: The name of the aggregate on which to create the volume.

    NOTE

    The volume creation command above does not use the -encrypt true parameter because the volume inherits encryption from the NAE-enabled aggregate.

    Output:

    [Job 31] Job succeeded: Successful
  2. Run the following command to verify the volume encryption:

    volume show -vserver <data-vserver-name> -volume <volume-name> \
    -fields state,is-encrypted,encryption-type,aggregate

    Where,

    • <data-vserver-name>: The name of the data SVM that contains the volume.

    • <volume-name>: The name of the volume to verify.

    Output:

    vserver volume aggregate encryption-type state is-encrypted
    ------------------- ----------------------- ----------------- --------------- ------ ------------
    test_vserver_netapp Fortanix_NAE_Test_Vol_1 Fortanix_NAE_Aggr aggregate online true

    The encryption-type field shows ‘aggregate’, indicating that the volume inherits encryption from the NAE-enabled aggregate and the is-encrypted field shows true. This confirms that the volume uses aggregate-level encryption inherited from the NAE-enabled aggregate.

9.0 Verify the Keys

9.1 Verify Keys Using NetApp ONTAP CLI

This section describes how to query the keys that Fortanix DSM provides to ONTAP.

Run the following command to query the encryption keys managed by Fortanix DSM for NetApp ONTAP:

security key-manager key query

Output (trimmed):

The output lists the key manager as <dsm-kmip-server-ip>:5696 with the type KMIP. Each key has the key type AEK and the encryption XTS-AES-256, and the Restored field shows true.

9.2 Verify Keys in Fortanix DSM

You can also verify that the keys generated by NetApp ONTAP are available in Fortanix DSM.

Perform the following steps:

  1. In the DSM left navigation panel, click the Security Objects menu item.

  2. On the Security Objects page, locate the keys associated with the group configured for the NetApp ONTAP integration.

    Figure 9: Keys created in DSM

    Verify that the keys associated with the NetApp ONTAP integration group are listed in DSM. The SOURCE field identifies keys created externally and made available to DSM through the KMIP integration.

Fortanix-logo

4.6

star-ratings

As of August 2025