CBOM Documentation

CBOM Secure

  • Product Overview
    • Overview
    • Dashboard Interface
    • Dashboard Operations
    • Data Visualization
    • Overview
    • Host
    • Template
      • Networked Deployments
      • Cloud Deployments
      • Off-Grid Deployments
    • Discovery History
      • Tags
      • Tag Scope
      • Integrations
      • Cloud Servers
      • CycloneDX Export
    • Sensors Reference
    • Overview
    • Summary Report
    • PQC Report
    • AI Services
    • Source Code Visualizer
    • Key
    • Certificate
    • CipherSuites
    • Analysis
    • Policy Management
    • User Policy
    • Standard Policy
    • Overview
    • Cases
    • Criteria
    • Notification Format
    • Rules
      • Connections
      • Health
    • User Management
    • Roles & Permissions
    • Audit Trail
    • System Logs
    • Top Bar and User Menu
    • System Configuration
  • Login and Authentication
    • Introduction
      • Components
      • Data Flows
      • Execution Models
      • Incremental Scanning
      • Security Model
      • Topologies
      • Sizing Guide
      • HA and Scaling
      • Ports and Firewall
      • Prerequisites
      • Docker Compose
      • Native on Linux
      • Deployment Server
      • Install Troubleshooting
      • Validation Checklist
      • Managing Services
      • Logging
      • Certificates
      • Configuration
      • Backup and Recovery
      • Ops Troubleshooting
      • Methods
      • SAML 2.0 SSO
      • OIDC and Entra ID
      • Token Authentication
      • Password Policy
      • Sensor vs Connector
      • Sensor Guide Structure
      • Capability Matrix
      • GitHub Sensor
        • AWS
        • Azure
        • Google Cloud
        • Active Directory
        • LDAP Directories
        • AD CS
        • Thales Luna HSM
        • Entrust nShield HSM
        • HashiCorp Vault KMIP
        • Windows Cert Store
        • Linux Trust Store
        • MSSQL TDE
      • Roadmap
      • Integration Model
      • CrowdStrike
      • ServiceNow
      • ServiceNow and Jira Setup
      • Notification Engine
  • Administrative Guide
    • Glossary
    • Configuration Reference
    • Data Model Reference
    • API Reference
    • API Authentication
    • CycloneDX Export Specification
    • Risk and PQC Scoring
    • Built-in Standards
    • Widget Catalogue
    • AI Services Data Handling

Google Cloud KMS Setup Guide for CBOM GCP Discovery Sensor

PART 1: GCP SETUP (From scratch)

1.1. Create a GCP Project
  1. Go to https://console.cloud.google.com/

  2. At the top, click the project selector dropdown.

  3. Click "New Project".

  4. Enter: Project name: cbom Billing account: Must be set up (free tier is fine)

  5. Click Create.

  6. Once created, select the new project.

1.2. Enable APIs

Navigate to: https://console.cloud.google.com/apis/library

Enable the following APIs for the project:

API NameDescription
Cloud KMS APIRequired for key management
IAM APIRequired to manage service roles

Click “Enable” on each.

1.3. Create a Key Ring & Key

In GCP Console or with gcloud:

Using GCP Console:
  1. Go to: Security > Key Management > Key Rings

  2. Click "Create Key Ring" Name: test-key-ring Location: global

  3. Click "Create Key" Name: test-asym-key Key Purpose: Asymmetric Sign Algorithm: RSA_SIGN_PKCS1_2048_SHA256 Protection Level: Software (or HSM if available)

Alternatively, via gcloud CLI:
gcloud kms keyrings create test-key-ring --location global

gcloud kms keys create test-asym-key \
  --location global \
  --keyring test-key-ring \
  --purpose asymmetric-signing \
  --default-algorithm rsa-sign-pkcs1-2048-sha256

PART 2: IAM & AUTHENTICATION

2.1. Create a Service Account
  1. Go to: IAM & Admin > Service Accounts

  2. Click “Create Service Account” Name: cbom-kms-reader ID: auto-filled * Description: Used for CBOM GCP discovery

  3. Click Create and Continue

  4. Grant roles: Cloud KMS Viewer (optional) Secret Manager Viewer if you want to add certs later

  5. Click Done

2.2. Create & Download JSON Key
  1. In the service account list, click the 3 dots → Manage keys

  2. Click “Add Key” → “Create new key”

  3. Select JSON and click Create

  4. Save the key file (e.g. cbom-sa-key.json) securely

PART 3: LOCAL PYTHON SETUP

3.1. Install Python Packages
pip install google-cloud-kms cryptography
3.2. Prepare Your CBOM Config

ConfigExample.yaml:

ExtName: Discover_GCPKMS
project_id: "cbom-468113"
location_id: "global"          
key_ring_id: "test-key-ring"  
Use GOOGLE_APPLICATION_CREDENTIALS environment variable (Recommended)
  1. Locate your downloaded service account JSON key — e.g.:

    C:\CBOM-Services\creds\cbom-468113-5dd33f609a00.json
  2. Open Command Prompt (or PowerShell) and run: #### For Command Prompt:

    set GOOGLE_APPLICATION_CREDENTIALS=C:\CBOM-Services\creds\cbom-468113-5dd33f609a00.json

    #### For PowerShell:

    $env:GOOGLE_APPLICATION_CREDENTIALS="C:\CBOM-Services\creds\cbom-468113-5dd33f609a00.json"
  3. Then rerun your CBOM discovery task.

This environment variable must be set in the same session that runs your Python or CBOM task, unless you persist it.

Optional: Persist environment variable (Windows)

If you want to make it permanent:

  1. Search for Environment Variables in the Start Menu.

  2. Under System Properties > Environment Variables: Click New (in User or System variables) Name: GOOGLE_APPLICATION_CREDENTIALS * Value: C:\CBOM-Services\creds\cbom-sa-key.json

  3. Click OK, apply changes.

  4. Restart your Command Prompt or system.

On this Page:
Support Privacy Policy Terms of Service

Copyright 2026 Encryption Consulting LLC. All rights reserved.