Skip to content

Read the cloud you actually run

Cloud Security
Assessment

We review how your cloud is really configured: who can do what, what faces the internet, where data sits and what gets logged. Findings are checked against the provider's own CIS Benchmark and confirmed by a senior practitioner, so you learn which settings would let an attacker in and which can wait.

Six places clouds break

Where misconfiguration
turns into a breach.

We work read only, through an audit role or a guest account you create, and score every account, subscription and project against the CIS Benchmark for that provider and the CSA Cloud Controls Matrix. Automated checks with Prowler find candidates. A senior practitioner confirms each one before it counts.

What we examine

Identity & access

Find out who can really change production.

A list of identities with more power than their job needs, including the paths that chain into admin.

  • Human users, roles and service identities enumerated across every account.
  • Admin rights, wildcard permissions and unused credentials flagged.
  • MFA and federation from your identity provider checked.

Internet exposure

See what anyone on the internet can reach.

Every public endpoint, open firewall rule and exposed storage bucket, ranked by what sits behind it.

  • Security groups, firewall rules and load balancers reviewed for open inbound access.
  • Public IPs, storage and snapshots matched to their owners.
  • Management ports and admin consoles open to the internet called out.

Data protection

Check where sensitive data lives and how it is encrypted.

A map of sensitive data stores with their encryption, sharing and backup settings, and the gaps between them.

  • Storage, databases and snapshots checked for public or cross tenant sharing.
  • Encryption settings reviewed along with who is allowed to decrypt.
  • Backups checked for isolation from the accounts they protect.

Logging & detection

Confirm you would see an attack in progress.

Which actions are logged, where the logs go, and which attacker moves would pass without an alert.

  • Audit logging coverage checked in every region and account.
  • Log storage reviewed for tamper resistance and retention.
  • Native threat detection settings and alert routing reviewed.

Workloads

Look inside the compute that runs your business.

Weak spots in virtual machines, containers and serverless functions, with the fix for each.

  • Instance metadata settings and patch state checked.
  • Kubernetes clusters reviewed against the CIS Kubernetes Benchmark.
  • Secrets found in code, environment variables and templates.

Governance

Test whether guardrails stop mistakes before they ship.

Which preventive guardrails exist across the estate and where a single engineer can bypass them.

  • Account, subscription and project structure reviewed.
  • Organization level policies and their exceptions read line by line.
  • Infrastructure as code checked for the same mistakes found live.

Key benefits

Fix the settings attackers look for first.

One view across every cloud

AWS, Microsoft Azure and Google Cloud reviewed by the same senior team with one scoring method, so you can compare risk across providers instead of reading unrelated reports.

Scored against the provider's benchmark

Each finding maps to the CIS Benchmark for that platform. Your auditors, customers and insurers recognize the reference, and your engineers get the exact setting to change.

Fixes ranked by exposure

A public bucket of customer records outranks a missing tag. We order findings by what an attacker could reach from them, so the first fixes your team makes remove the most risk.

What you get

What lands on
your desk.

One piece for leadership and auditors, one for the engineers who change settings, and a conversation to agree what happens next.

The document

The cloud assessment report

Executive summary, scope by account and subscription, benchmark scores, and every confirmed finding with evidence, affected resources and the exact configuration change that fixes it.

The working file

The configuration tracker

One row per finding with the resource ID, benchmark reference, severity, owner and status. Import it into your ticketing system or work straight from the sheet.

The conversation

The cloud readout

A working session with the practitioner who did the review and your cloud engineers. We walk the top exposures, settle owners, and agree which fixes are quick and which need a project.

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.

Before we connect

Asked about
every cloud.

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

Read only access. In AWS that is an audit role, in Azure a Reader assignment, in Google Cloud a Viewer role at the organization level. We send the exact permissions in scoping, and nothing we use can change a resource.

No. This assessment reviews several providers in one engagement. If one platform carries most of your risk, our AWS, Microsoft and Google Cloud assessments go deeper on that provider's own services and benchmarks.

We make no changes. Configuration and logs are read through the provider's APIs, calls are paced to stay under rate limits, and we tell your team before we start so the activity is expected.

Findings reference the CIS Benchmarks, which auditors know. The report shows that cloud configuration was independently reviewed, and the tracker records remediation over time, which is what an auditor asks to see after a finding.

The senior practitioner who scoped the engagement runs it, from the first read of your accounts to the readout. No junior analyst runs the tools and passes you their output.

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.