When you register apps in Azure or add service accounts in Google Cloud for SCA and Cloud Visibility, these platforms provide the apps/service accounts with secrets so that they can get permissions to perform necessary activities.
This document describes how SCA and Cloud Visibility handle secret rotation, and how you can manually rotate or regenerate a secret if it expires, becomes invalid, or becomes compromised.

Steps
Solution
This section describes how to manually rotate or regenerate secrets for your Azure apps or Google Cloud service accounts.
|
Cloud Provider
|
Solution
|
|
Azure
|
- Cloud Visibility - When you register Cloud Visibility in Azure, we recommend that you create a secret that is valid for 24 months.
When the secret expires or if it becomes invalid, Cloud Visibility displays an error. Click the error to get online instructions for creating a new secret in Azure and updating it in Cloud Visibility.
If the secret is compromised, delete it manually from Azure. Cloud Visibility detects that the secret is missing and displays an error. Click the error to get online instructions for creating a new secret in Azure and updating it in Cloud Visibility.
For more information, see the Cloud Visibility docs.
- SCA - When you register SCA in Azure, we recommend that you create a secret that is valid for 60 days. SCA automatically rotates this secret every 30 days.
If you want to manually generate a new secret before the scheduled automatic rotation, please open a support case with Idira Customer Support.
|
|
GCP
|
- Secrets for Cloud Visibility and SCA service accounts are created with no expiration date. If you want to manually generate a new secret, see the instructions in our Cloud Visbility (CV) docs here.
|