Getting started with Cloud Compliance
Complete a few steps to get started with Cloud Compliance for Cloud Volumes ONTAP or Azure NetApp Files.
Get started quickly by following these steps or scroll down to the remaining sections for full details.
Ensure that your cloud environment can meet the prerequisites, which includes 16 vCPUs for the Cloud Compliance instance, outbound internet access for the instance, connectivity between Cloud Manager and Cloud Compliance over port 80, and more. See the complete list.
Enable Cloud Compliance
New working environments: Be sure to keep Cloud Compliance enabled when you create the working environment (it’s enabled by default).
Existing working environments: Click Compliance, optionally edit the list of working environments, and click Show Compliance Dashboard.
Ensure access to volumes
Now that Cloud Compliance is enabled, ensure that it can access volumes.
The Cloud Compliance instance needs a network connection to each Cloud Volumes ONTAP subnet or Azure NetApp Files subnet.
Security groups for Cloud Volumes ONTAP must allow inbound connections from the Cloud Compliance instance.
NFS Volume export policies must allow access from the Cloud Compliance instance.
Cloud Compliance needs Active Directory credentials to scan CIFS volumes.
Click Compliance > Scan Status > Edit CIFS Credentials and provide the credentials. The credentials can be read-only, but providing admin credentials ensures that Cloud Compliance can read data that requires elevated permissions.
Review the following prerequisites to make sure that you have a supported configuration before you enable Cloud Compliance. You’ll need to ensure connectivity to volumes after you enable Cloud Compliance. That’s covered below.
- Enable outbound internet access
Cloud Compliance requires outbound internet access. If your virtual network uses a proxy server for internet access, ensure that the Cloud Compliance instance has outbound internet access to contact the following endpoints. Note that Cloud Manager deploys the Cloud Compliance instance in the same subnet as Cloud Manager.
Communication with the Cloud Manager service, which includes Cloud Central accounts.
Communication with NetApp Cloud Central for centralized user authentication.
Provides access to software images, manifests, and templates.
Enables NetApp to stream data from audit records.
Enables Cloud Compliance to access and download manifests and templates, and to send logs and metrics.
- Ensure that Cloud Manager has the required permissions
Ensure that Cloud Manager has permissions to deploy resources and create security groups for the Cloud Compliance instance. You can find the latest Cloud Manager permissions in the policies provided by NetApp.
- Check your vCPU limits
Ensure that your cloud provider’s vCPU limit allows for the deployment of an instance with 16 cores. You’ll need to verify the vCPU limit for the relevant instance family in the region where Cloud Manager is running.
In AWS, the instance family is On-Demand Standard instances. In Azure, the instance family is Standard DSv3 Family.
For more details on vCPU limits, see the following:
- Ensure that Cloud Manager can access Cloud Compliance
Ensure connectivity between Cloud Manager and the Cloud Compliance instance:
The security group for Cloud Manager must allow inbound and outbound traffic over port 80 to and from the Cloud Compliance instance.
This connection enables deployment of the Cloud Compliance instance and enables you to view information in the Compliance tab.
If your AWS network doesn’t use a NAT or proxy for internet access, modify the security group for Cloud Manager to allow inbound traffic over TCP port 3128 from the Cloud Compliance instance.
This is required because the Cloud Compliance instance uses Cloud Manager as a proxy to access the internet.
This port is open by default on all new Cloud Manager instances, starting with version 3.7.5. It’s not open on Cloud Manager instances created prior to that.
- Set up discovery of Azure NetApp Files
Before you can scan volumes for Azure NetApp Files, Cloud Manager must be set up to discover the configuration.
- Ensure that you can keep Cloud Compliance running
The Cloud Compliance instance needs to stay on to continuously scan your data.
- Ensure web browser connectivity to Cloud Compliance
After Cloud Compliance is enabled, ensure that users access the Cloud Manager interface from a host that has a connection to the Cloud Compliance instance.
The Cloud Compliance instance uses a private IP address to ensure that the indexed data isn’t accessible to the internet. As a result, the web browser that you use to access Cloud Manager must have a connection to that private IP address. That connection can come from a direct connection to AWS or Azure (for example, a VPN), or from a host that’s inside the same network as the Cloud Compliance instance.
If you’re accessing Cloud Manager from a public IP address, then your web browser probably isn’t running on a host inside the network.
Enabling Cloud Compliance on a new working environment
Cloud Compliance is enabled by default in the Cloud Volumes ONTAP working environment wizard. Be sure to keep the option enabled.
Click Create Cloud Volumes ONTAP.
Select Amazon Web Services or Microsoft Azure as the cloud provider and then choose a single node or HA system.
Fill out the Details & Credentials page.
On the Services page, leave Cloud Compliance enabled and click Continue.
Complete the pages in the wizard to deploy the system.
Cloud Compliance is enabled on the Cloud Volumes ONTAP system. If this the first time that you enabled Cloud Compliance, Cloud Manager deploys the Cloud Compliance instance in your cloud provider. As soon as the instance is available, it starts scanning data as its written to each volume that you create.
Enabling Cloud Compliance on existing working environments
If you haven’t enabled Cloud Compliance yet, enable it on existing Cloud Volumes ONTAP or Azure NetApp Files working environments from the Compliance tab in Cloud Manager.
Another option is to enable Cloud Compliance from the Working Environments tab by selecting each working environment individually.
At the top of Cloud Manager, click Compliance.
If you want to enable Cloud Compliance on specific working environments, click the edit icon.
Otherwise, Cloud Manager is set to enable Cloud Compliance on all working environments to which you have access.
Click Show Compliance Dashboard.
At the top of Cloud Manager, click Working Environments.
Select a working environment.
In the pane on the right, click Enable Compliance.
If this the first time that you enabled Cloud Compliance, Cloud Manager deploys the Cloud Compliance instance in your cloud provider.
Cloud Compliance starts scanning the data on each working environment. Data will be available in the Compliance dashboard as soon as Cloud Compliance finishes the initial scans. The time that it takes depends on the amount of data—it could be a few minutes or hours.
Verifying that Cloud Compliance has access to volumes
Make sure that Cloud Compliance can access volumes by checking your networking, security groups, and export policies. You’ll need to provide Cloud Compliance with CIFS credentials so it can access CIFS volumes.
Make sure that there’s a network connection between the Cloud Compliance instance and each network that includes volumes for Cloud Volumes ONTAP or Azure NetApp Files.
For Azure NetApp Files, Cloud Compliance can only scan volumes that are in the same region as Cloud Manager.
Ensure that the security group for Cloud Volumes ONTAP allows inbound traffic from the Cloud Compliance instance.
You can either open the security group for traffic from the IP address of the Cloud Compliance instance, or you can open the security group for all traffic from inside the virtual network.
Ensure that NFS volume export policies include the IP address of the Cloud Compliance instance so it can access the data on each volume.
If you use CIFS, provide Cloud Compliance with Active Directory credentials so it can scan CIFS volumes.
At the top of Cloud Manager, click Compliance.
In the top right, click Scan Status.
For each working environment, click Edit CIFS Credentials and enter the user name and password that Cloud Compliance needs to access CIFS volumes on the system.
The credentials can be read-only, but providing admin credentials ensures that Cloud Compliance can read any data that requires elevated permissions. The credentials are stored on the Cloud Compliance instance.
After you enter the credentials, you should see a message that all CIFS volumes were authenticated successfully.
On the Scan Status page, click View Details to review the scan status for each CIFS and NFS volume and correct any errors.
For example, the following image shows three volumes that Cloud Compliance can’t scan due to network connectivity issues between the Cloud Compliance instance and the volumes.