Google Cloud Platform Setup Guide

Google Cloud Platform Setup Guide

Google Cloud Platform Setup Guide

Google Cloud Platform Setup Guide

Google Cloud Platform Setup Guide

Google Cloud Platform Setup Guide

This guide walks you through connecting a Google Cloud Platform (GCP) project to Swise for cloud security scanning.

Prerequisites

Before you begin, ensure you have:

  • A Google Cloud project with Owner or Project IAM Admin privileges

  • Access to the GCP Console or Cloud Shell

Step 1: Project Details Configuration

  1. Go to the GCP Console, locate your Project ID on the welcome screen (e.g., inlaid-joy-468000-r8). Note down this Project ID as you'll need it for Swise configuration.

  2. Navigate to Integrations → Cloud Security → Google Cloud Platform in the Swise app and click Connect.

  3. In the Project Details tab:

    • Project IDs: Enter one or more GCP Project identifiers (6–63 characters, lowercase letters, numbers, and hyphens; must start and end with a letter or number).

    • Project Alias: Provide a descriptive name for your environment (e.g., Production env)

  4. Click Credentials → to proceed.

Step 2: Retrieve credentials from Google Cloud

Using Google Cloud Shell:

  1. In the GCP Console, click on Activate Cloud Shell

  2. Click Authorise Cloud Shell when prompted

  3. Run the following command in Cloud Shell:

    bash

    gcloud auth application-default login --no-launch-browser

  4. Type Y when prompted to continue

  5. Copy the authentication URL provided and open it in a new browser tab

  6. Select your Google account and follow the authorisation steps

  7. Copy the authentication code provided

  8. Paste the authentication code back in Cloud Shell

  9. Once completed, run:

    bash

    cat ~/.config/gcloud/application_default_credentials.json

  10. Extract the following values from the output:

    • client_id

    • client_secret

    • refresh_token

Step 3: Enter Credentials in Swise

  1. Back in the Swise UI, in the Credentials tab enter your GCP service account credentials:

    1. Client ID: Your OAuth 2.0 client ID from the credentials file

    2. Client Secret: The corresponding client secret from the credentials file

    3. Refresh Token: The refresh token for maintaining authentication

    Note: All credential fields are required for successful connection.

  2. Click Compliance Standards → to proceed.


Step 4: Select Compliance Standards

In the Compliance Standards tab, choose which frameworks to evaluate against:

  • Your Security Compliance Project e.g. ISO 27001 (auto-selected if your Security Compliance project is set to ISO 27001)

  • CIS Controls V8 (optional)

Check any additional standards you’d like to monitor. Each standard’s description appears below its checkbox. When ready, click Connect.

What Happens Next

After clicking Connect, Swise will authenticate using your credentials, perform read-only API scans across your GCP project’s resources and regions, evaluate findings against your selected compliance standards. Scan results and compliance gaps will appear in the Cloud Security dashboard shortly.

© Copyright 2025 Swise Limited • All rights reserved.

© Copyright 2025 Swise Limited • All rights reserved.

© Copyright 2025 Swise Limited • All rights reserved.