Skip to main content
BlueXP classification

Scan Cloud Volumes ONTAP and on-premises ONTAP volumes with BlueXP classification

Contributors netapp-tonacki amgrissino netapp-ahibbard netapp-bcammett

Complete a few steps to start scanning your Cloud Volumes ONTAP and on-premises ONTAP volumes using BlueXP classification.

Prerequisites

Before you enable BlueXP classification, make sure you have a supported configuration.

Enable BlueXP classification scanning in your working environments

You can enable BlueXP classification scanning on Cloud Volumes ONTAP systems in any supported cloud provider, and on on-premises ONTAP clusters.

Steps
  1. From the BlueXP left navigation menu, select Governance > Classification.

  2. From the BlueXP classification menu, select Configuration.

    The Configuration page shows multiple working environments.

    A screenshot of the Configuration tab showing a Cloud Volumes ONTAP working environment.

  3. Choose a working environment and select Configuration.

    A screenshot of the Configuration tab showing the options for mapping and classifying repositories.

  4. If you don't care if the last access time is reset, turn the Scan when missing "write attributes" permissions switch ON and all files are scanned regardless of the permissions.

    The switch at the top of the page for Scan when missing "write attributes" permissions is disabled by default. This means that if BlueXP classification doesn't have write attributes permissions in CIFS, or write permissions in NFS, that the system won't classify the files because BlueXP classification can't revert the "last access time" to the original timestamp. Learn more.

  5. Select how you want to scan the volumes in each working environment. Learn about mapping and classification scans:

    • To map all volumes, select Map.

    • To map and classify all volumes, select Map & Classify.

    • To customize scanning for each volume, select Custom, and then choose the volumes you want to map and/or classify.

  6. In the confirmation dialog box, select Approve to have BlueXP classification start scanning your volumes.

Result

BlueXP classification starts scanning the volumes you selected in the working environment. Results start to appear in the Compliance dashboard as soon as BlueXP classification starts the scan. The time that it takes to complete depends on the amount of data—​it could be a few minutes or hours.

Note BlueXP classification scans only one file share under a volume. If you have multiple shares in your volumes, you'll need to scan those other shares separately as a shares group. See more details about this BlueXP classification limitation.

Verify that BlueXP classification has access to volumes

Make sure that BlueXP classification can access volumes by checking your networking, security groups, and export policies. You'll need to provide BlueXP classification with CIFS credentials so it can access CIFS volumes.

Steps
  1. Make sure that there's a network connection between the BlueXP classification instance and each network that includes volumes for Cloud Volumes ONTAP or on-prem ONTAP clusters.

  2. Ensure that the security group for Cloud Volumes ONTAP allows inbound traffic from the BlueXP classification instance.

    You can either open the security group for traffic from the IP address of the BlueXP classification instance, or you can open the security group for all traffic from inside the virtual network.

  3. Ensure that NFS volume export policies include the IP address of the BlueXP classification instance so it can access the data on each volume.

  4. If you use CIFS, provide BlueXP classification with Active Directory credentials so it can scan CIFS volumes.

    1. From the BlueXP left navigation menu, select Governance > Classification.

    2. From the BlueXP classification menu, select Configuration.

      A screenshot of the Configuration tab showing the options for mapping and classifying repositories.

    3. For each working environment, select Edit CIFS Credentials and enter the user name and password that BlueXP classification needs to access CIFS volumes on the system.

      The credentials can be read-only, but providing admin credentials ensures that BlueXP classification can read any data that requires elevated permissions. The credentials are stored on the BlueXP classification instance.

      If you want to make sure your files "last accessed times" are unchanged by BlueXP classification scans, it's recommended the user has Write Attributes permissions in CIFS or write permissions in NFS. If possible, configure the Active Directory user as part of a parent group in the organization which has permissions to all files.

      After you enter the credentials, you should see a message that all CIFS volumes were authenticated successfully.

  5. On the Configuration page, select Configuration to review the status for each CIFS and NFS volume and correct any errors.

Disable compliance scans on volumes

You can start or stop mapping-only scans, or mapping and classification scans, in a working environment at any time from the Configuration page. You can also change from mapping-only scans to mapping and classification scans, and vice-versa. We recommend that you scan all volumes.

Note New volumes added to the working environment are automatically scanned only when you have set the Map or Map & Classify setting in the heading area. When the option is set to Custom or Off in the heading area, you'll need to activate mapping and/or full scanning on each new volume you add in the working environment.
Steps
  1. From the BlueXP classification menu, select Configuration.

  2. Select the Configuration button for the working environment that you want to change.

    A screenshot of the Configuration tab showing the options for mapping and classifying repositories.

  3. Do one of the following:

    • To disable scanning on a volume, in the volume area, select Off.

    • To disable scanning on all volumes, in the heading area, select Off.