3 Recommendations For Cloud Security

11.20.18
Jackson Lucas
Cloud Tech Journalist

CONTACT US

Security is often cited as a concern for organizations who are migrating to the public cloud, but the belief that the public cloud is not secure is a myth. In fact, the leading public cloud service providers have built rigorous security capabilities to ensure that your applications, assets, and services are protected. That being said, security in the cloud isn’t guaranteed. The responsibility is split between the cloud provider, who is essentially responsible for the security of the cloud, and you and your organization, who are responsible for the security of what’s inside.

Cloud providers focus on the protection of infrastructure (e.g. hardware, software, facilities), while your organization must spend time developing and executing a strategy to maintain applications, service configuration, and identity and access management. This isn’t easy in a rapidly evolving multicloud environment, but your organization must keep up with changes that might impact your security.

We break down three core recommendations for cloud security across Amazon Web Service (AWS), Microsoft Azure, and Google Cloud Platform (GCP) to help you get started.

 
recommendations for cloud security

According to Gartner, through 2022, at least 95% of cloud security failures will be the customer’s fault, not the public cloud service provider.

The Center for Internet Security (CIS), a trusted non-profit organization that published standards and best practices for securing IT systems, created benchmarks for AWS Foundations, Microsoft Azure Foundations, and GCP Foundations. While these benchmarks do vary, they have three core recommendations in common: identity and access management, logging and monitoring, and networking.

Cloud security starts with properly managing access. Without the proper identity and access management, users can intentionally or unintentionally create security flaws with serious implications. Identity and access management controls take a proactive approach by validating that you have properly and securely configured access to your cloud environment.

The controls help you stay ahead of breaches and monitoring for leading indicators such as:

  • Misconfigured users (i.e., users not in a group)
  • Users with too broad of a span of control
  • Users with vulnerable accounts (i.e., multi-factor authentication disabled, etc.)
  • Inactive users (i.e., IAM user with access keys that are not being used, etc.)

While it’s best to catch security vulnerabilities before they are exploited, it’s prudent to also monitor for events that could turn into security incidents or lagging indicators.

 

To learn about the other two recommendations, logging and monitoring, and networking, download our cloud security eBook.

blog-security-rec.png