Have your security team members ever made a mistake in the cloud? Human error happens and it can take on many forms. But, none are as serious as failing to understand the way cloud defenses work.
If a mistake does come to mind, be reassured you’re not alone.
Seven in 10 organizations suffered a public cloud security incident between July 2019 and July 2020, reports Help Net Security. Of those cloud computing security incidents, 66% involved the exposure of cloud-based data as the result of an exploited misconfiguration.
How can you be sure you’re getting the right type and level of protection? Let’s take a look at what you need to know about protecting your cloud security when using the Amazon Web Services (AWS) shared responsibility model.
Why a Cloud Shared Responsibly Model Makes Sense
For many, security goes hand-in-hand with control. One can’t secure something unless one has control over it, the logic goes. It takes a cue from the perimeter-based model. The holder of the data needs to not only own the apps and data but also the base infrastructure itself.
Not so in the cloud. This approach follows the AWS shared responsibility model. In this model, the data holder shares security duties with their cloud service provider (CSP). The latter is always in charge of physically securing the infrastructure. From there, the balance shifts depending on the cloud deployment model in use.
There are a few options when it comes to ..
Support the originator by clicking the read the rest link below.
