We work with global API providers to power our Continuous Control Monitoring capability.
For our Continuous Control Monitoring (CCM) capability, 6clicks partners with trusted third-party API providers to underpin and support seamless integrations with leading cloud security monitoring posture solutions (CSPM) and cloud providers. CCM data flows from these solutions and providers via our partners' APIs into 6clicks, with all credentials safely stored by 6clicks and our partners on a need-to-know basis only.
All credentials are stored within the same region as the 6clicks instance being used by the company, ensuring data sovereignty adherence.
Our trusted partners provide CCM integrations for the following CSPM solutions:
This article is designed to help our users to understand how data privacy and consent are handled when connecting 6clicks with CSPM solutions and walks you through the consent process.
Connecting to CSPM integrations
When an admin user initiates the CSPM integration by hitting the ‘Connect’ button, they are presented with a Data & Privacy consent dialog. The dialog highlights the privacy implications of connecting with cloud security solutions through our partner APIs.
There are two options:
- By clicking Continue, the admin user consents on behalf of the team for that specific integration, and the connection flow with the selected CSPM tool will be triggered.
- If the connection is successfully established, the consent will be saved and the integration will be active.
- If, for any reason, the connection fails, the consent will not be saved, and the integration will not be active.
- By clicking Cancel, the consent dialog will be closed, and the connection flow will not be initiated.
Disconnection and consent expiration
When a CSPM integration is disconnected, the previously saved consent is automatically marked as expired. If the admin user attempts to reconnect the integration, they will be presented with the consent dialog again.
Consent during integration disablement
In cases where the CSPM integration is disabled rather than disconnected, the consent remains active. This means that when the integration is enabled again, the admin user will not be presented with the consent dialog, as the previous consent is still valid.
Consent logs and auditing
Our platform maintains a log of all consents provided by admin users, ensuring a clear audit trail is available for compliance and security purposes.
For more information, refer to 6clicks Privacy Policy