Yesterday Fugue announced some new features that make it easier than ever to bring cloud infrastructure environments into compliance, make sure they stay that way, and demonstrate it at any time. Let’s take a look.
We're hearing a lot about “shifting left” these days in the industry, and like most popular terms the meaning can be hard to pin down, and some of the implications buried. This post will focus on how to shift security and compliance left in cloud computing. These two functions are closely related, but the operational aspect of each is quite different. However, before we get into specifics, it might be helpful to define what we mean by shifting left in general.
Today, Fugue added out-of-the-box support for Payment Card Industry Data Security Standards (PCI) to give enterprises full PCI compliance visibility and reporting across their entire cloud footprint. PCI joins HIPAA, NIST 800-53, GDPR, and AWS CIS Benchmark as part of Fugue’s turnkey solution for ensuring cloud infrastructure environments adhere to compliance standards.
All humans make mistakes and some of those mistakes could lead to security breaches. According to Gartner, through 2023 at least 99% of cloud security failures will be the customer’s fault. Many of these successful cyber-attacks will be a result of hackers preying on the vulnerabilities of human weakness to successfully gain access to an organization’s infrastructure and networks wreaking havoc and damage.
Infrastructure misconfiguration is the leading cause of data breaches in the cloud, and a big reason misconfiguration happens is infrastructure configuration “drift,” or change that occurs in a cloud environment post-provisioning. If you’re responsible for the security and compliance of cloud environments, you probably spend a lot of time focused on analyzing infrastructure drift events and remediating them. It’s easy to think of all drift as being bad or undesirable. And make no mistake, some of it is really bad. Ugly even! But some drift is good and desired, and understanding the differences between the good, the bad, and the ugly--and how to recognize them--can save you and your team a lot of frustration and wasted time.
In last week’s blog we discussed the Shared Responsibility Model and how it affects enterprises’ cloud security. Based on the Shared Responsibility Model, organizations are responsible for security in the cloud, which includes how they configure and use the resources provided by the cloud service providers. Falling within this realm are cloud resource configurations. Cloud configurations are complex and if not implemented correctly, can increase the risk of a data breach.
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.
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.
Enterprises operating at scale on clouds like Amazon Web Services (AWS) need assurance that their cloud infrastructure always adheres to compliance policy and never drifts. But unlike the datacenter, today’s cloud environments are API-driven and highly dynamic. When change is the only constant, enforcing continuous compliance is a major challenge. Failure here can result in costly fines, or worse—a critical data breach.
Since its founding, Fugue has set out to transform how cloud infrastructure is kept safe and secure. Today, we’re thrilled to announce our strategic partnership and development agreement withIn-Q-Tel (IQT)to help advance its mission for U.S. government agencies.