Cloud and SaaS
Google Cloud Security Assessment
Assess inherited Google Cloud permissions, service account trust and resource access. The review identifies indirect privilege paths that could affect data protection and operational control.
01 / Overview
Assessment objectives and control obligations
Google Cloud assessment reconstructs inherited authorisation across organisations, folders and projects, including conditional bindings and applicable restrictive policies. Service-account impersonation, key management, workload identity federation and policy-modification rights receive explicit review. Missing hierarchy visibility is recorded as an evidential limitation.
Deployment authority is analysed alongside runtime access to storage, datasets and secrets. Controlled operations establish whether indirect workload control confers access unavailable to the initiating user. Findings preserve both sides of the trust relationship and assign treatment responsibility to the relevant identity, platform or resource owner.
02 / Technical analysis
Failure mechanisms and security implications
A user unable to read a dataset directly may control a workload that can. We document both permissions so treatment addresses the deployment relationship as well as the resource grant.
03 / Scope
Technical coverage and authorisation boundaries
Coverage is agreed in writing before testing begins. The rows below describe what this service normally examines. Exclusions, testing windows and escalation contacts are recorded in the rules of engagement.
- Policy hierarchy
- Inherited grants, custom roles, conditions and restrictions.
- Service identities
- Keys, impersonation, federation and deployment authority.
- Data and audit
- Storage, dataset permissions, secrets and logging.
- Supporting tools
- Environment-appropriate instrumentation may include ScoutSuite, gcloud, Prowler, Security Command Center, Steampipe. Selection follows the investigative objective, compatibility requirements and approved operating constraints. Automated output requires corroboration against implementation evidence or observed execution before classification as a substantiated finding.
04 / Methodology
Investigation and validation methodology
Control review evaluates design adequacy and operating effectiveness against an explicit baseline. Sampling rationale, implementation evidence, exceptions and analytical limitations are retained to support traceable conclusions and proportionate remediation.
01
Objectives and evidence plan
Preparation
We agree the questions, applicable references and evidence sources, and authorise any sampling or active validation before collection.
02
Map inherited authority
Reconcile hierarchy and service identity relationships.
03
Check consequential access
Validate selected identity and resource relationships using approved operations.
04
Priorities and handover
Review completion
Factual reconciliation precedes delivery of a risk-treatment roadmap identifying accountable owners, implementation dependencies and measurable verification criteria.
05 / Assessment options
Access models and evidential confidence
Supplied access determines investigative reach, validation depth and evidential confidence. The proposal records the access model, supporting material and unresolved coverage limitations; no model implies unrestricted authority or exhaustive verification.
- Black box
- Testing starts without supplied credentials or internal design material. External exposure is examined, while authenticated workflows may remain inaccessible.
- Grey box
- Representative accounts and selected design information support direct comparison of roles, tenants and sensitive workflows.
- White box
- Source, configuration and design evidence support root cause analysis. Runtime and access limitations are still recorded.
06 / Deliverables
Decision-support and verification deliverables
Deliverables distinguish what was observed, what was concluded and where the evidence stops. The agreed scope states which evidence, review sessions and retesting are included.
Executive summary
The summary explains the demonstrated exposure, the business functions affected and the treatment decisions required, including material uncertainty.
Technical findings
Each confirmed issue records the affected assets, prerequisites, reproduction evidence and a specific remediation. Technical severity is presented separately from business priority.
Coverage and limitations
The record identifies the systems, identities and conditions tested, together with exclusions and assumptions that affect interpretation.
Treatment and retest status
Recommendations are sequenced by risk, dependency and ownership. Any agreed retest records resolved, partly resolved and unresolved issues without implying a new assessment.
Service specific evidence
Hierarchy bindings, service identity context and observed actions support accountable changes.
07 / References
Applicable technical references
References are selected for the technology and objective in scope, and the edition applied is recorded. A framework mapping supports review; it is not certification or proof of complete compliance.
- Google Cloud IAM allow policies
- Official guidance explains policy bindings and resource hierarchy inheritance. The review also considers applicable restrictive policies and service identity relationships.
- CIS Benchmarks
- Version and role specific configuration recommendations provide a baseline. Applicability, operational exceptions and effective deployment are recorded before interpreting a score.
08 / Safeguards
Operational safeguards and evidence governance
Active work is conditional on written authority from the appropriate asset owner and approved rules of engagement. The operating plan specifies permitted procedures, testing windows, prohibited actions, third-party restrictions and nominated stop authority. Unexpected instability or suspected genuine compromise triggers suspension of affected activity pending the client’s operational decision.
Evidence governance applies purpose limitation, data minimisation and access proportionality to collection, transfer, processing, retention and disposal. The signed terms define authorised recipients and any external processing arrangement. Publication, secondary use and disclosure of client material require the applicable written permission.
Conclusions distinguish substantiated exposure, untested consequence and residual uncertainty. Each material finding identifies the control obligation, causal mechanism, observed outcome and verification criteria for the proposed treatment. Technical severity informs analysis; prioritisation and acceptance of residual risk remain decisions for the client’s authorised risk owner.
Project level access may not expose all inherited policy; missing hierarchy evidence is disclosed.
09 / Suitability
Commissioning criteria
Use after organisation restructuring, workload federation or changes to service account administration.
Next step
Define the assessment you need
Tell us the business decision, the systems involved and any operational constraint. We will explain the coverage proposed, the access required and the evidence the engagement can provide.
- Confidentiality first
A mutual confidentiality agreement is signed before any technical detail is exchanged, so scope discussions can happen safely.
- Scope and cost in writing
Deliverables, access expectations, timeline and fee are confirmed before the engagement begins, and a scope change needs agreement.
- Answered by the delivery team
The consultants who scope an engagement are the consultants who perform it and explain the result to your team.
