Optimize the security of your assets on Google Cloud with our industry-leading data scan addon, offering advanced protection, complete visibility and foolproof compliance to ensure your data remains secure in the cloud.
Report Bug
·
Request Feature
For each of your environments, the following keys are mandatory:
- "rules": This refers to the set of rules files you want to apply to this environment.
- "prefix": the prefix is the particle to be placed in front of the environment variables to be quoted here.
The following keys are recommended to ensure better readability when re-reading the configuration:
- "name": The name refers to the environment concerned by one or more keywords.
- "description": the description helps to clarify the name and avoid any possible confusion about the environment concerned
You can also specify the regions you want to scan, this can be used to avoid scanning all regions and reduce execution time. Without specifying this, all regions will be scan.
- "regions": The list of the regions name you want to scan, refer to AWS regions name
Here is the GCP regions official documentation :
Example config for 2 environments:
There are several ways to identify yourself in an Google Cloud environment. Obviously, you can only scan the environment for which you are at least a "reader":
GOOGLE_PROJECT_ID=XXXXXXXXXX ( the google project id )
GOOGLE_APPLICATION_CREDENTIALS=XXXXXXXX ( the credentials.json content )