GCP Advanced Settings
Advanced Settings
Note
Advanced settings can either apply to all connections for this adapter, or to a specific connection. Refer to Advanced Configuration for Adapters.
- Email domain include list (optional) - Enter a comma-separated list of email domains to include in the fetch. If left empty, all connections for this adapter will fetch all users unless the Email domain exclude list is populated.
- Email domain exclude list (optional) - Enter a comma-separated list of email domains to exclude from the fetch when the Email domain include list is empty.
- Fetch Google Cloud Clusters - Select this option to fetch Cluster devices and display them in the Devices page.
- Fetch Google Cloud SQL database instances - Fetch all Google Cloud SQL instances.
- If enabled, all connections for this adapter will fetch Google Cloud SQL database instances.
- If disabled, all connections for this adapter will not fetch Google Cloud SQL database instances.
Note
Fetching Google Cloud SQL database instances also requires the following:
- Fetch Google Cloud Routers - Select to fetch Google Cloud routers.
- Fetch Google Instance Groups - Select to fetch Google Instance Groups as Compute Services.
- Fetch Google Cloud VPCs - Select whether to fetch VPCs from Google Cloud as assets.
- Fetch Subnets as assets - Split subnets of a VPC network into individual assets.
- Fetch Google Cloud Storage buckets Select to fetch all Google Cloud Storage buckets.
- If enabled (default), all connections for this adapter will fetch the GCP Storage buckets.
- If disabled, all connections for this adapter will not fetch the GCP Storage buckets.
Note
Fetch all Google Cloud Storage buckets also requires the following:
- Fetch Google Cloud Compute Images (Images, Snapshots and Templates) - Select whether to fetch all Google Cloud Compute Disk Images, Snapshots and Templates.
- Fetch Object metadata in Google Cloud Storage buckets (0: disabled, max supported: 1000) (optional, default: 0) - Fetch Object metadata in GCP Storage buckets that includes: name, size, and links to objects within each bucket.
- If supplied, all connections for this adapter will fetch 1000 objects or the specified number, the smallest of the two.
- If not supplied, all connections for this adapter will not fetch Object metadata in GCP Storage buckets.
Note
Fetch object metadata in GCP Storage buckets also requires the following:
- Fetch IAM permissions for users - Fetch IAM permissions and associate those to the users roles. This includes permissions for build-in roles as well as Subscription-level and Project-level custom defined roles.
- If enabled (default), all connections for this adapter will fetch IAM permissions and will associate those to the users roles. These permissions will be represented as the Role Details complex field. This must be enabled to use the Axonius - Send Email to Assets action to send emails to GCE account administrators.
- If disabled, all connections for this adapter will not fetch IAM permissions.
Note
Fetch IAM permissions and associate those to the users roles requires the following:
- Role Viewer
-
Only Fetch SCC Assets with associated SCC Findings - Select this option to only fetch SCC assets that have findings.
-
Fetch organizational tags - Select this option to enrich VM instances with organizational tags or project tags associated with them.
-
Fetch users (optional, default: true) - Unselect this option to exclude user data from the fetch.
-
Fetch Service Accounts (default: disabled) - Select this option to fetch Google Cloud service accounts as Users assets, including service accounts that have no role bindings. A service account is shown as disabled when Google Cloud reports it as disabled. The Email domain include list and Email domain exclude list settings also apply to service accounts. When you enable this, you can also enable the following optional settings:
- Fetch Service Account Keys (default: disabled) - Select this option to fetch the user-managed keys of each service account as Secrets assets (Asset Type: GCP Service Account Key). The adapter fetches only key metadata, not the private key. Each service account user also has a Service Account Keys field that lists the key IDs, each linking to its Secrets asset. Requires Fetch Service Accounts to be enabled. Secrets assets require the Cyber Assets product, like other Secrets assets. Without it, service accounts are still fetched as Users and the Service Account Keys field still lists the key IDs, but the IDs do not link to Secrets assets. When you enable this, you can also enable the following optional setting:
- Fetch Key Last Authenticated Time (default: disabled) - Select this option to add the last time each key authenticated to the Last Accessed Time field of its Secrets asset. Requires Fetch Service Account Keys to be enabled.
Note
To fetch service accounts and their keys:
- The Identity and Access Management (IAM) API must be enabled in the GCP projects you want to fetch from. To fetch the last authenticated time of keys, the Policy Analyzer API must also be enabled.
- The service account must have the
iam.serviceAccounts.listpermission to fetch service accounts, theiam.serviceAccountKeys.listpermission to fetch keys, and thepolicyanalyzer.serviceAccountKeyLastAuthenticationActivities.querypermission to fetch the last authenticated time of keys. The read-only predefined rolesroles/iam.serviceAccountViewer(service accounts and keys) androles/policyanalyzer.activityAnalysisViewer(last authenticated time) together provide these permissions. You can also create a custom role with only these permissions. - If a required API is not enabled in a project, the adapter skips that data for that project and continues the fetch. The same applies to a missing permission. Service accounts and keys are still fetched, and the Last Accessed Time field remains empty if the Policy Analyzer API is not enabled or its permission is missing.
- Fetch Service Account Keys (default: disabled) - Select this option to fetch the user-managed keys of each service account as Secrets assets (Asset Type: GCP Service Account Key). The adapter fetches only key metadata, not the private key. Each service account user also has a Service Account Keys field that lists the key IDs, each linking to its Secrets asset. Requires Fetch Service Accounts to be enabled. Secrets assets require the Cyber Assets product, like other Secrets assets. Without it, service accounts are still fetched as Users and the Service Account Keys field still lists the key IDs, but the IDs do not link to Secrets assets. When you enable this, you can also enable the following optional setting:
-
Security Command Center (SCC) Organizations (optional) - Specify a comma-separated list of organization IDs.
- If supplied, all connections for this adapter will fetch Security Command Center device assets and their associated vulnerabilities from the specified list of organization IDs.
- If not supplied, all connections for this adapter will not fetch any Security Command Center device assets.
Note
Fetch Security Command Center device assets and their associated vulnerabilities requires the following organization-level roles to each of the specified organizations:
Alternatively, Security Center Admin is required.
-
Fetch SCC findings from the last X days (0: disabled, max supported: 90) (optional, default: 90) - Specify the number of days SCC findings data is to be fetched.
- If supplied, all connections for this adapter will fetch SCC findings data gathered in the last number of days as specified.
- If not supplied, all connections for this adapter will fetch SCC findings data gathered in the last 90 days.
-
Custom filter expression for SCC findings (optional) - Specify an expression that defines the filter to apply across assets fetched from SCC.
- If supplied, all connections for this adapter will apply the specified filter when fetching SCC assets.
- If not supplied, all connections for this adapter will not apply any filter when fetching SCC assets.
-
Number of parallel connections (required, default: 20) - Specify the number of connections to be opened to control the performance of the data fetch.
-
Fetch only compute devices that are turned on - Select this option to not fetch compute devices that are turned on.
-
List of tags to parse as fields (optional, default: empty) - Specify a comma-separated list of tag keys to be parsed as device or user fields. Each tag is a key-value pair that is part of the Adapter Tags complex field.
- If supplied, all connections for this adapter will parse any of the listed tags that are associated with the fetched device or user as:
- Values of the Adapter Tags field.
- Designated field with the name of the tag key and the value of the tag value.
- If not supplied, all connections for this adapter will only parse all tags as values of the Adapter Tags field.
- If supplied, all connections for this adapter will parse any of the listed tags that are associated with the fetched device or user as:
-
Fetch Google Cloud Serverless Functions - Select this option to fetch Serverless Functions from the 'Cloud Functions' service using the Method: projects.locations.functions.list API.To fetch Google Cloud Serverless Functions the following permissions need to be granted:
- OAuth scope:
https://www.googleapis.com/auth/cloud-platform - IAM permission on the specified resource parent:
cloudfunctions.functions.list
- OAuth scope:
-
Fetch Google App Engine Instances - Select this option to fetch Google App Engine instances as Compute Services assets. Data retrieved about App Engine instances includes service name and ID, version, zone, VM liveness, memory usage, and more.
-
Fetch Google Cloud APIs - Select this option to fetch APIs from Apigee. To enable this, the following IAM permission on the specified resource parent is required:
apigee.proxies.list -
Fetch Google Cloud Run Services - Select this option to fetch Cloud Run Services and parse them as Compute Services.
-
Fetch Google Cloud Secret Manager Secrets - Select this option to fetch metadata from Google Cloud Secret Manager secrets across your GCP projects. When enabled, the adapter retrieves secret configuration details such as replication policies, rotation schedules, and expiration settings. The adapter fetches only secret metadata, not the actual secret values.
Note
To fetch Google Cloud Secret Manager secrets:
- The Secret Manager API must be enabled in the GCP projects you want to fetch secrets from.
- The service account must have permissions to list secrets (e.g., secretmanager.secrets.list and secretmanager.secrets.get). Refer to the Google Cloud Secret Manager IAM permissions documentation for details on granting the required permissions.
-
AI Fetch Settings - (available only for Security for AI)
- Fetch Google Gemini Enterprise Agents (available only for Security for AI) - Select this option to fetch Gemini Enterprise Agent Engine reasoning engines as AI Agent assets. (API endpoint called:
GET https://{location}-aiplatform.googleapis.com/v1/projects/{project_id}/locations/{location}/reasoningEngines) - Fetch Google Gemini Enterprise Agent Platform Models (available only for Security for AI) - Select this option to fetch Model Registry models as AI Models assets. (API endpoint called:
GET /v1/projects/{project_id}/locations/{location}/models) - Fetch Google Cloud Model Armor Templates (available only for Security for AI) - Select this option to fetch Google Cloud Model Armor templates as Guardrail assets. (API endpoint called:
GET /v1/projects/{project_id}/locations/{location}/templates) - Fetch Google Gemini Enterprise RAG Corpora (available only for Security for AI) - Select this option to fetch Gemini Enterprise Agent Platform RAG Engine corpora as Knowledge Source assets. The adapter creates one Knowledge Source asset for each RAG corpus, with the Hosting Platform set to Google Vertex AI. (API endpoint called:
GET https://{location}-aiplatform.googleapis.com/v1/projects/{project_id}/locations/{location}/ragCorpora) When enabled, the following setting becomes available:- Fetch RAG Corpus Files - Select this option to include the files of each fetched RAG corpus: file count, failed file count, and the source type and Google Cloud Storage URI of each file. (API endpoint called:
GET https://{location}-aiplatform.googleapis.com/v1/projects/{project_id}/locations/{location}/ragCorpora/{ragCorpus}/ragFiles)
Note
To fetch Google Gemini Enterprise RAG Corpora, enable the Vertex AI API (
aiplatform.googleapis.com) and provide the following access for the account used by the adapter:- OAuth scope:
https://www.googleapis.com/auth/cloud-platform - Role: Vertex AI Viewer (
roles/aiplatform.viewer) or Vertex AI User (roles/aiplatform.user) on the Google Cloud project.
- OAuth scope:
- Fetch RAG Corpus Files - Select this option to include the files of each fetched RAG corpus: file count, failed file count, and the source type and Google Cloud Storage URI of each file. (API endpoint called:
- Fetch Google Gemini Enterprise for CX Agent Studio Tools (available only for Security for AI) - Select this option to retrieve Gemini Enterprise for Customer Experience (CES) Agent Studio tools as AI Tool assets.
- Fetch Google Agent Registry Agents (available only for Security for AI) - Select this option to fetch Google Agent Registry agents as AI Agent assets. (API endpoint called:
GET /v1/projects/{project}/locations/{location}/agents)
Note
To fetch Google Agent Registry Agents, enable the Agent Registry API and provide the following access for the account used by the adapter:
- OAuth scope:
agentregistry.read-only - Permission:
agentregistry.agents.list- lists Agent Registry agents. - Permission:
agentregistry.bindings.list- retrieves bindings used to associate agents with MCP server targets.
- OAuth scope:
- Fetch Google Agent Registry MCP Servers (available only for Security for AI) - Select this option to fetch Google Agent Registry MCP servers as MCP Server assets, including the tools each server exposes. The adapter sets the Hosting Platform to Google Agent Registry. (API endpoint called:
GET /v1/projects/{project}/locations/{location}/mcpServers) When enabled, the following setting becomes available:- Fetch Associated Agents - Select this option to include the agents associated with each fetched MCP server. (API endpoint called:
GET /v1/projects/{project}/locations/{location}/bindings)
Note
To fetch Google Agent Registry MCP Servers, enable the Agent Registry API and provide the following access for the account used by the adapter:
- Permission:
agentregistry.mcpServers.list- lists Agent Registry MCP servers. - Permission:
agentregistry.mcpServers.get- retrieves the details of an MCP server. - Permission:
agentregistry.bindings.list- retrieves bindings used to associate agents with MCP servers. Required for Fetch Associated Agents.
Grant the service account the Agent Registry Viewer role (
roles/agentregistry.viewer), which includes these permissions. Grant it at the project level, or at the folder or organization level so that projects inherit it. The role cannot be granted at the location level. - Permission:
- Fetch Associated Agents - Select this option to include the agents associated with each fetched MCP server. (API endpoint called:
- Fetch Google Gemini Enterprise Agents (available only for Security for AI) - Select this option to fetch Gemini Enterprise Agent Engine reasoning engines as AI Agent assets. (API endpoint called:
-
Fetch Google Cloud Artifact Registry Repositories - Select this option to Select this option to fetch Google Cloud Artifact Registry repositories as Compute Services. Repository assets include Repository Format, Repository Mode, and Size In Bytes.
-
Fetch Google Firebase Hosting Sites - Select Enabled to fetch Firebase Hosting sites of each project as Compute Services assets (asset type: GCP Firebase Hosting Site). Not selected by default. Under this option you can also select:
- Fetch Firebase Hosting Custom Domains > Enabled to include the custom domains of each site (domain, host state, ownership state, certificate state).
- Fetch Firebase Hosting Live Channel > Enabled to include the live release of each site (release name, release time, release type, version status).
These two options take effect only when Fetch Google Firebase Hosting Sites is enabled.
Site fields include Site ID, Default URL, Site Type, Firebase App ID, Custom Domains (Domain, Host State, Ownership State, Certificate State), Live Release Name, Live Release Time, Live Release Type, and Live Version Status. Each site asset also shows the GCP project ID in Project ID and the project display name in Cloud Provider Account Name.
Note
The Firebase Hosting API must be enabled in each project, and the service account needs the
firebasehosting.sites.listandfirebasehosting.sites.getpermissions (included in the Firebase Hosting Viewer role). A project where the API is not enabled or the permission is missing does not stop the fetch. Axonius skips that project and logs a warning. -
Fetch Google Cloud Projects - Select this option to fetch Google Cloud Projects and parse them as Account/Tenants.
-
Fetch Google Cloud DNS Managed Zones - Select this option to fetch DNS Managed Zones from Google Cloud DNS as URL assets.
Note
To fetch DNS managed zones, the following IAM role is required:
- DNS Reader (
roles/dns.reader) - Allows read-only access to DNS managed zones and resource record sets.
Alternatively, you can create a custom role with the following permissions:
- dns.managedZones.list
- dns.managedZones.get
- dns.resourceRecordSets.list
Alternatively, you can create a custom role with these specific permissions:
dns.managedZones.listdns.managedZones.getdns.resourceRecordSets.list
- DNS Reader (
Note
For details on general advanced settings under the Adapter Configuration tab, see Adapter Advanced Settings.
Updated 6 days ago
