Go to the docs for the latest release.
Disabling Cloud Compliance
If you need to, you can stop Cloud Compliance from scanning one or more working environments or databases. You can also delete the Cloud Compliance instance if you no longer want to use Cloud Compliance with your working environments.
Deactivating compliance scans for a working environment
When you deactivate scans, Cloud Compliance no longer scans the data on the system and it removes the indexed compliance insights from the Cloud Compliance instance (the data from the working environment or database itself isn’t deleted).
From the Scan Configuration page, click the button in the row for the working environment, and then click Deactivate Compliance.
|You can also disable compliance scans for a working environment from the Services panel when you select the working environment.|
Deleting the Cloud Compliance instance
You can delete the Cloud Compliance instance if you no longer want to use Cloud Compliance. Deleting the instance also deletes the associated disks where the indexed data resides.
Go to your cloud provider’s console and delete the Cloud Compliance instance.
The instance is named CloudCompliance with a generated hash (UUID) concatenated to it. For example: CloudCompliance-16bb6564-38ad-4080-9a92-36f5fd2f71c7