Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Cloud misconfiguration is a state in which wrong public-range or permission settings have become a hole. With one setting on a screen, the cloud can open something to the whole world or limit it to particular people. If that switch is set wrongly, the data becomes visible without any attack.
How does cloud misconfiguration work?
It is like renting a storage unit, locking the door, and finding that some doors have been left ajar. Even if the provider protects the building, how to close the door is decided by the tenant. A misconfiguration is a problem close to that failure to close.
In the 2021 edition of the OWASP Top 10, security misconfiguration (A05) ranks fifth, up from sixth in the previous edition. Among the ways an app can be vulnerable, A05 lists wrongly set permissions on cloud services. Its countermeasures also include reviewing the permissions of cloud storage, such as S3 bucket permissions.
An example is attached. It is a scene where a cloud provider's default sharing settings are open to other users on the internet, and confidential data in the storage can be reached. MITRE's CWE-732 says that if storage is open to public or anonymous access, outside people can read or rewrite its contents.
Review of settings does not end in one pass. OWASP recommends setting up development, testing, and production alike, and repeating the check automatically. CISA's material also touches on the role of mechanisms that monitor continuously and find and prevent misconfigurations that lead to data leaks.
A concrete way of looking is in public cloud storage misconfiguration. The free URL check gives a first look at the outside of your site.
Why does cloud misconfiguration matter?
The appeal of the cloud is the freedom to decide your own settings. For the same reason, responsibility for the settings stays with you. At small companies, the person who set it up moves on, or a production firm sets it and the handover is missed, so that nobody sees the whole.
Damage does not end with data being visible. CWE-732 lists the chance that credentials and configuration files leak by being read, the chance of gaining permissions from rewritten executables, and the chance of data being destroyed.
An option for having an expert check your settings is the cloud configuration assessment (AWS, Google Cloud, Azure). It is from JPY 98,000 (excl. tax) per account, and the cost rises as the number of accounts assessed grows. The thinking on assessment is on the cloud assessment page. To talk it over, contact us.
Related terms
- Public cloud storage: a state in which data in cloud storage can be seen by anyone
- Security misconfiguration: the general state in which wrong settings become holes, beyond the cloud
- IAM: the mechanism that decides who may do what in the cloud
- CSPM: a mechanism that finds cloud misconfigurations automatically
- Shared responsibility model: the idea of dividing the range of protection between provider and user
Frequently asked questions
Isn't a cloud misconfiguration the cloud provider's responsibility?
The content of settings is, in many cases, decided by the user. How far the provider protects and where the user's protection begins changes with the form of the service. For how responsibility is divided, see the explanation of the shared responsibility model.
If I fix it once, will misconfiguration stop happening?
It cannot be said it will stop. OWASP recommends repeating checks of settings automatically in all environments: development, testing, and production. Settings move every time the person in charge or the configuration changes.
Next step
First list in the admin screen whether any storage is set to public. A concrete way of looking is in public cloud storage misconfiguration, and the content of an assessment is in cloud assessment. The free URL check shows only what is visible from outside, and for a review of settings, contact us.
Frequently asked questions
Isn't a cloud misconfiguration the cloud provider's responsibility?
The content of settings is, in many cases, decided by the user. How far the provider protects and where the user's protection begins changes with the form of the service. For how responsibility is divided, see the explanation of the shared responsibility model.
If I fix it once, will misconfiguration stop happening?
It cannot be said it will stop. OWASP recommends repeating checks of settings automatically in all environments: development, testing, and production. Settings move every time the person in charge or the configuration changes.