Today we released the Fugue Best Practices Framework to help software engineering teams identify and remediate the kinds of dangerous cloud resource misconfigurations used in recent data breaches that aren’t addressed by common compliance frameworks (see A Technical Analysis of the Capital One Cloud Misconfiguration Breach).
Just like the challenges of managing large cloud infrastructure operations led to the development of infrastructure as code, ensuring the security and compliance of those environments led to policy as code. Cloud infrastructure environments are simply too vast, complex and dynamic to address with traditional security approaches such as manual audits and checklists.
Today we announced that Fugue now supports Microsoft Azure, in addition to Amazon Web Services (AWS). Our customers increasingly use multiple Cloud Service Providers (CSPs), and they want a single Cloud Security Posture Management (CSPM) solution that spans multiple CSPs. Now Fugue for Microsoft Azure is now generally available, and we’re thrilled to deliver that to our customers.
We’re thrilled that DeveloperWeek NYC has awarded Fugue a DevProject Award for the work our amazing engineering and product teams delivered to bring our Software as a Service (SaaS) solution for cloud security and compliance to market.
Fugue is excited to announce support for AWS GovCloud. This enables public sector customers to leverage public cloud resources while remaining compliant. Our product supports AWS GovCloud regions which meets specific regulatory and compliance requirements for US government agencies such FedRAMP High and ITAR.
As organizations increase their cloud footprint, gaining visibility into their cloud resources becomes an arduous but essential task. It is critical to understand how your cloud resources are provisioned and configured as well as identifying any misconfigurations. Many security and compliance teams address these needs by working with system architects to manually create architecture diagrams for reporting based on cloud console configuration settings, log records, and AWS Config data. This process is tedious and time consuming and not scalable for enterprises with large cloud workloads.
At Fugue, we are obsessed with infrastructure baselines and especially with how they are utilized to correct cloud resource misconfiguration and drift—the leading cause of cloud-based data breaches. Baselines are a relatively new concept, so we thought an informative blog post about baselines, what they are, why organizations need them, and how organizations can get started with baselines, would be a great introduction to baselines. So let’s get started.
Since AWS re:Invent 2018, Fugue has supported two different products: the self-hosted Fugue Platform and the newer Software as a Service (SaaS) Fugue Risk Manager product. Today, we’re thrilled to announce that we have merged capabilities from the two products into a single, unified SaaS solution for autonomous cloud infrastructure security and compliance. Our product is now simply called Fugue.
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.