Skip to content

From org policy to Workspace

Google Cloud
Security Assessment

We review your Google Cloud organization and Google Workspace together: IAM bindings and service account use, VPC Service Controls perimeters, Security Command Center coverage and Workspace admin settings. Findings are scored against the CIS Google Cloud Platform Foundation Benchmark and checked by a senior practitioner, so you see which gaps open a path to your data.

Projects, folders, perimeters

Where Google Cloud
access gets loose.

We use read only roles granted at the organization level and score every project against the CIS Google Cloud Platform Foundation Benchmark and the CIS Google Workspace Foundations Benchmark. Security Command Center findings are a starting point. We confirm each one and trace how IAM inheritance spreads access.

What we examine

IAM & service accounts

Follow inherited access down the resource tree.

Principals with more access than they need, including service accounts that can impersonate others.

  • Bindings at organization, folder and project level traced through inheritance.
  • Basic roles such as Owner and Editor flagged for replacement.
  • User managed service account credentials and impersonation rights reviewed.
  • Workload Identity Federation checked where outside systems connect.

VPC Service Controls

Test whether your perimeters really keep data in.

Which sensitive projects sit inside a perimeter, and which ingress and egress rules open holes in it.

  • Perimeter membership compared to where sensitive data lives.
  • Ingress and egress rules and access levels reviewed.
  • Dry run mode results read for violations nobody followed up.

Detection & logging

Check that Security Command Center sees what matters.

Detection coverage by project, with the gaps in audit logging and the alerts no one receives.

  • Security Command Center tier and enabled services reviewed.
  • Cloud Audit Logs, including Data Access logs, checked on sensitive services.
  • Log sinks and retention reviewed for tamper resistance.

Org policies

Find the guardrails that were never set.

Organization policy constraints in force, the ones missing, and the projects exempted from them.

  • Constraints on external IPs and service account credential creation checked.
  • Domain restricted sharing reviewed.
  • Exceptions at folder and project level listed with their owners.

Network & exposure

See what Google Cloud exposes to the internet.

Public endpoints by project, with the firewall rules and load balancers that make them reachable.

  • VPC firewall rules read for open management ports.
  • Public Cloud Storage buckets and BigQuery datasets found.
  • External IPs and Cloud Run ingress settings reviewed.

Google Workspace

Close the Workspace settings attackers use first.

Workspace admin, login and sharing settings compared to the CIS benchmark, with the takeover paths marked.

  • Super admin accounts and 2SV enforcement reviewed.
  • Third party app access and OAuth grants checked.
  • Drive external sharing and Gmail forwarding settings read.

Key benefits

Find the Google Cloud gaps before attackers do.

Inheritance made visible

A role granted at a folder quietly applies to every project beneath it. We trace those grants, so you see who really holds access and where one binding opens a whole business unit.

Benchmarks your auditor knows

Results map to the CIS Google Cloud Platform Foundation Benchmark and the CIS Google Workspace Foundations Benchmark, giving you evidence for SOC 2, ISO/IEC 27001 and customer security reviews.

Perimeters that match your data

VPC Service Controls only protect what sits inside them. We compare your perimeters to where sensitive data actually lives and show the projects and rules that leave it exposed.

What you get

What lands on
your desk.

Each piece names the project, the binding or setting at fault, and the change that fixes it.

The document

The Google Cloud assessment report

Executive summary, the organization and folder structure reviewed, benchmark results for Google Cloud and Workspace, and each confirmed finding with evidence, affected projects and the fix.

The working file

The IAM and settings tracker

One row per finding with project ID, resource, benchmark reference, severity, owner and status. A separate tab lists every IAM binding we recommend removing or narrowing.

The conversation

The platform readout

A session with your platform team and Workspace admins. We walk the inherited access we found, agree which org policies to enforce first, and plan the perimeter changes that need testing.

Client case studies

Real engagements.
Documented outcomes.

YHB | CPAs & Consultants testimonial

In their words

"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."

Cyrus Kapadia
Chief Technology & Information Officer, YHB | CPAs & Consultants

Trusted by industry leaders.

Google Cloud questions

Asked by
platform teams.

Straight answers from the practitioners who do the work. If yours is not here, ask us directly.

Read only roles at the organization level, such as Viewer, Security Reviewer and Organization Policy Viewer, plus a Workspace admin role limited to reading settings. We send the exact list in scoping, and none of it can change a resource.

Yes. Each can be scoped on its own. Reviewing them together shows where a Workspace super admin can also reach Google Cloud resources, which is a path attackers look for.

No. We read perimeter configuration and dry run logs. We do not change perimeters or send traffic meant to trip them unless you ask for that in scope, and then only against projects you name.

It finds misconfigurations one resource at a time. It does not decide which of them matter in your organization or how they combine. We start from its output and add the judgement.

Ready?

Bring us
the problem.

One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.