Security and compliance are priorities for companies in the cloud. However, cloud security and compliance is not the responsibility of any single entity alone and determining the demarcation line can lead to confusion. Security and compliance in the cloud is a shared responsibility between the cloud service providers (CSP) and their customers.
Whenever there's talk of the cloud, misconfiguration and the security risk it brings inevitably becomes a part of the conversation. And of course, once you start talking about cloud misconfiguration, “auto-remediation” often creeps into the conversation. But what does “auto-remediation” really mean? The concept of “auto-remediation” is that the solution finds problems or policy violations in your cloud infrastructure and automatically fixes them.
As organizations adopt cloud technology to modernize their businesses and increase agility, employing security automation to identify and correct cloud infrastructure misconfiguration has become a necessity. Cloud misconfiguration is one of the most common and significant security risks facing organizations today, yet it is also preventable.
We are thrilled to announce that the Fugue Compliance Suite is available today. The Compliance Suite is a set of validation libraries for provisioning and orchestrating infrastructure with Fugue. The prepackaged libraries help to enforce security and regulatory controls specified in compliance frameworks such as NIST 800-53, HIPAA, and GDPR, as well as best practices such as the AWS CIS Benchmarks.
As more organizations accelerate adoption of cloud infrastructure for increased efficiencies and scalability, they are faced with the challenge of identifying and correcting misconfiguration. Cloud infrastructure misconfiguration can occur anywhere in your infrastructure. If not corrected immediately after discovery, it can expose organizations to unforeseen risks. The longer misconfiguration is left unattended, the higher the risk of a critical security breach. Below are some of the most common kinds of cloud infrastructure misconfiguration and the resulting data breaches. Download the Cloud Infrastructure Misconfiguration ebook for more detailed information on misconfiguration and best practices on how to prevent it. Related Posts Cloud Infrastructure...
In last week’s blog post, we discussed the seriousness of cloud misconfigurations and the impact they can have on organizations as they move to the cloud. The fallout from cloud misconfigurations can be severe: steep regulatory fines, loss of customer data, damage to your reputation, or loss of customer trust. In this post, we address some of the most common cloud infrastructure misconfigurations and consequences resulting from the misconfiguration. AWS Security Group Misconfigurations AWS security groups are associated with EC2 server instances and provide security at the port and protocol access level. A security group misconfiguration can allow an attacker to access your cloud-based servers and exfiltrate data. A common security group misconfiguration is to make a server...
Cloud infrastructure misconfiguration is preventable, yet remains one of the most common security concerns for organizations moving to the cloud. A recent report from IBM X-Force revealed that there was a 424% increase in data breaches due to cloud misconfigurations that were caused by human error. Configuration drift that leads to misconfigurations can easily be exploited to gain unauthorized access to data, thus exposing organizations to unforeseen risks. Why has there been such a huge increase in misconfigurations and why are these breaches so damaging? Infrastructure misconfiguration has become increasingly likely as companies migrate more of their workloads to the cloud. Being on cloud means being dynamic and agile, and the security solutions used to protect data centers are...
We are thrilled to announce that the Fugue Compliance Suite is available today. The Compliance Suite is a set of validation libraries for provisioning and orchestrating infrastructure with Fugue. The prepackaged libraries help to enforce security and regulatory controls specified in compliance frameworks such as NIST 800-53, HIPAA, and GDPR, as well as best practices such as the AWS CIS Benchmarks. As a reminder, a validation is a type of “policy as code” that tests your infrastructure. If a validation fails, such as determining that an S3 bucket has been defined in an unpermitted AWS region, then the infrastructure code will not compile and cannot be deployed. Our Compliance Suite validations ensure that infrastructure does not violate controls specified in a compliance framework. For...