Shared Responsibility on Cloud

Shared Responsibility On Cloud

Shared Responsibility on Cloud

Figure 2  Summary of the shared responsibility 

The Amazon Web Service (AWS) security model claims responsibility for “protecting the hardware, software, networking, and facilities that run on AWS Cloud services”. On the other hand, Microsoft Azure claims security ownership of “physical hosts, networks, and data centers.” Both the cloud giants state that your retained security responsibilities depend upon which services you select.

You are responsible for all facets of your identity and access management (IAM), including authentication and authorization mechanisms, single sign-on (SSO), multi-factor authentication (MFA), access keys, certificates, user creation processes, and password management.

You are responsible for ensuring a regular check on your cloud health. Locuz’ Cloud Security Posture Management routinely and constantly checks for misconfigurations that can lead to data breaches and leaks, while recommending any necessary changes on a continuous, ongoing basis. 

Application Developers and CIOs should consider the implications of shared responsibility and ensure that there are no security blind spots, where one thinks that the other is taking care of security. The best practice would be to schedule regular security audits across all areas. Locuz has provided these services such as Security Posture Assessment to clients that have benefited tremendously and have been able to plug vulnerabilities before any mishap.

Application Security in a Cloud First World

Bridging the Visibility Gap on Cloud

Future of Networking – ZTNA (Zero Trust Network Access)

Share this post