Cloud security assessment: scope, cost and process for AWS, Google Cloud and Azure

A cloud security assessment reviews public settings, permissions, keys and logging in AWS, Google Cloud and Azure, from JPY 98,000 (excl. tax) per account.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

A cloud security assessment inspects what is inside your AWS, Google Cloud or Azure account. It asks four things. Is anything public that should not be? Are permissions wider than they need to be? Are keys protected? Is activity being recorded? It is meant for companies that run their sites or systems in the cloud. Start by confirming which clouds you use and how many accounts you have.

Cyber Shield uses a broad tool-based listing of settings, followed by manual review by an analyst. The price starts from JPY 98,000 (excl. tax, one account). The sections below cover who protects what, what we examine, what remains with you afterwards and what it costs.

Who is responsible for protecting what in the cloud?

A cloud provider protects the base: data centers and server equipment. What you place on top, and who you allow to do what, is set by the customer. This split is called the shared responsibility model.

All three major providers publish the same idea. In AWS's explanation, even with a service such as S3, handling your data and setting permissions through IAM (the system that decides who may do what) are the customer's tasks. Azure says that for every type of service, data, accounts and identities, and configuration stay on the customer's side. Google Cloud's material likewise puts access policy and data with the customer.

In Japan, the Ministry of Internal Affairs and Communications published guidelines on appropriate settings when using and providing cloud services in October 2022. In April 2024 it released the Guidebook on Preventing Cloud Misconfiguration, a plainer summary. Its aim is to prevent setting mistakes, because a wrong setting can lead to incidents such as information leaks.

What does a cloud security assessment examine?

We look at four areas where an overlooked setting most often becomes an incident. The table puts them in plain words.

Viewpoint In plain words What can happen
Public settings Is storage or a similar service readable by anyone on the internet? Customer data or backups can be seen from outside
Permissions (IAM) Do people and systems hold more rights than they need? If one entry point is taken over, the damage spreads across the whole account
Access keys Are the keys that systems use to talk to each other left in a public place, or never rotated? Whoever holds the key can act as a legitimate user
Logs and monitoring Is a record kept of who did what and when, and are settings in place to notice something odd? Misuse is noticed late and the cause cannot be traced

The mechanism and the fix for each are in our explainers on public cloud storage, excessive IAM permissions, leaked access keys and weak cloud logging and monitoring. The damage that follows is laid out in the information leak measures.

Names differ by cloud. Storage is S3 in AWS, Cloud Storage in Google Cloud and Azure Storage in Azure. We check against each console and its own terms.

For checking your own account, the CIS Benchmarks can serve as a yardstick. They are recommended settings compiled by the Center for Internet Security through expert consensus. Editions covering the basic settings of AWS, Google Cloud and Azure are each published.

What this assessment leaves out

The base that the provider protects is not something the customer inspects. The inside of a site or app running in your account belongs to the web application assessment.

The settings of the virtual servers themselves and of network devices are handled by the server and network assessment. An account run by another company cannot be assessed without its operator's permission.

How do tools and people share the work?

An assessment has two stages: a tool lists the settings, and a person reviews them. In the cloud, simply reading the values tells you a great deal, and that is where the tool comes in.

A tool is strong at turning a huge number of settings into a list and matching them against public standards. The more an account grows, the more settings it holds, yet every one is held to the same standard.

What a tool cannot do is decide whether a given public setting was meant. A storage bucket that holds your company brochure images should be public. One that holds customer documents must be fixed at once if it is public. The same setting means different things depending on what is stored and how it is used.

So an analyst reads each finding and sorts it into a setting your operations need or a hole to be fixed. False positives are removed at that point.

The assessment centers on reviewing settings. We never rewrite settings in your cloud. Fixing a hole comes after a quotation and your order. The consent form records the target account, the period and the methods before work starts. Which permissions you share with us, and for how long, is agreed in the consent form and the free consultation.

What do you keep after the assessment?

What you keep is a report. It has an executive summary, a technical section and a ranked list of fixes. Leaders get the overall rating and the first things to fix. Operations and development staff read which setting in which account to change, and how.

After the fixes, we run one re-assessment at no charge. It checks that the settings you changed have not slipped back, and the result goes into the report.

What does it cost, and what changes the amount?

The base for the price is the number of accounts assessed. All amounts exclude tax.

Item Price Range Included
Cloud configuration assessment (AWS, Google Cloud, Azure) from JPY 98,000 (excl. tax) one account Tool scan and a person's review, a report, one free re-assessment after fixes
Individual vulnerability fix from JPY 10,000 per item (excl. tax) Holes found in the assessment Quoted by content
Free assessment JPY 0 After the NDA and the consent form A quick tool scan plus a person's review, with an issue report

With several accounts, or with more than one cloud, we look at your list and quote. The more kinds of service you use, the more settings there are to check, and the quote reflects that.

A formal quotation follows the free assessment. All prices are on the pricing page. The free URL check cannot look inside a cloud account, because it reads only what a visitor could see. Run it for the outside view of your public site, then contact us to agree how many accounts and which clouds an assessment should cover.

What is the path from first contact to delivery?

Our standard flow from first contact to after-delivery support applies here too. Only the stages that touch the assessment appear below.

  1. In the free consultation we ask which cloud you use, how many accounts you have and what they are mainly for.
  2. Before work begins, we sign a non-disclosure agreement (NDA) without charge.
  3. After you sign the consent form, we run the free assessment and give you an issue report.
  4. We present the cost of fixing the issues as a quotation.
  5. Once you order, we assess every item and close the holes in the settings.
  6. We share a PDF of what was fixed and how before delivery.
  7. You check the real environment, and we deliver. Free support covers the month after delivery.

If you want ongoing monitoring once the assessment is over, a maintenance and advisory plan or our AI monitoring service, Guard, can carry it on.

Is a small cloud setup worth assessing?

Setting mistakes happen at any scale. Making a single storage bucket public is enough to make its contents readable from outside. In a small setup we use the same viewpoints for public settings and permissions.

If it fits within the base of one account, the price is from JPY 98,000 (excl. tax). A formal quotation follows the free assessment.

Frequently asked questions

What is a cloud security assessment?

It is a review of your AWS, Google Cloud or Azure account for gaps in public settings, permissions, access keys and logging. Tools list the settings broadly. Then a person asks whether each setting was intended, and the results go into a report.

How much does it cost?

It is from JPY 98,000 (excl. tax, one account). With several accounts, or with more than one cloud, we look at your list and quote. An individual vulnerability fix is from JPY 10,000 per item (excl. tax), quoted by content, and one re-assessment after the fixes is free.

The cloud provider protects us, so why do we need an assessment?

The provider protects the base: data centers and equipment. Data, accounts, and the settings for permissions and public access are organized as the customer's responsibility. However sturdy the base, a gap in your settings lets information out.

Could the assessment stop our services or change our settings?

The assessment is mainly a review of settings, and we never rewrite them ourselves. Fixing the holes found happens only after a quotation and your order. The targets and methods are put in writing in the consent form before we begin.

Does an assessment prove the cloud setup is safe?

No. An assessment is a way to confirm settings as they stood at that moment. Cloud settings can be changed every day, so each change can create a new hole. We suggest treating fixes, re-assessment and maintenance as one continuous effort.

Next step

If you would like to see how your public site looks from outside before an assessment, the free URL check will show it. Enter a single URL and it reads only what anyone can see. It does not run attacks.

When the number of accounts or the clouds you use are unclear, contact us by form, phone or online meeting. The NDA is free and comes before the assessment.

Written by Mio Kanzaki (AI security analyst). Supervised by 千葉圭介. Updated 19 November 2026.

Frequently asked questions

What is a cloud security assessment?

It is a review of your AWS, Google Cloud or Azure account for gaps in public settings, permissions, access keys and logging. Tools list the settings broadly. Then a person asks whether each setting was intended, and the results go into a report.

How much does it cost?

It is from JPY 98,000 (excl. tax, one account). With several accounts, or with more than one cloud, we look at your list and quote. An individual vulnerability fix is from JPY 10,000 per item (excl. tax), quoted by content, and one re-assessment after the fixes is free.

The cloud provider protects us, so why do we need an assessment?

The provider protects the base: data centers and equipment. Data, accounts, and the settings for permissions and public access are organized as the customer's responsibility. However sturdy the base, a gap in your settings lets information out.

Could the assessment stop our services or change our settings?

The assessment is mainly a review of settings, and we never rewrite them ourselves. Fixing the holes found happens only after a quotation and your order. The targets and methods are put in writing in the consent form before we begin.

Does an assessment prove the cloud setup is safe?

No. An assessment is a way to confirm settings as they stood at that moment. Cloud settings can be changed every day, so each change can create a new hole. We suggest treating fixes, re-assessment and maintenance as one continuous effort.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.