As a vast majority of companies make the rapid shift to work-from-home to stem the spread of COVID-19, a significant percentage of IT and cloud professionals are concerned about maintaining the security of their cloud environments during the transition. The findings are a part of the State of Cloud Security survey conducted by Fugue, the company putting engineers in command of cloud security. The survey found that 96% of cloud engineering teams are now 100% distributed and working from home in response to the crisis, with 83% having completed the transition or in the process of doing so. Managing cloud infrastructure remotely Of those that are making the shift, 84% are concerned about new security vulnerabilities created during the swift adoption of new access policies, networks, and devices used for managing cloud infrastructure remotely. Knowing your cloud infrastructure is secure at all times is already a major challenge" “What our survey reveals is that cloud misconfiguration not only remains the number one cause of data breaches in the cloud, the rapid global shift to 100% distributed teams is creating new risks for organisations and opportunities for malicious actors,” said Phillip Merrick, CEO of Fugue. “Knowing your cloud infrastructure is secure at all times is already a major challenge for even the most sophisticated cloud customers, and the current crisis is compounding the problem.” Traditional security analysis tools Because cloud misconfiguration exploits can be so difficult to detect using traditional security analysis tools, even after the fact, 84% of IT professionals are concerned that their organisation has already suffered a major cloud breach that they have yet to discover (39.7% highly concerned; 44.3% somewhat concerned). 28% state that they’ve already suffered a critical cloud data breach that they are aware of. In addition, 92% are worried that their organisation is vulnerable to a major cloud misconfiguration-related data breach (47.3% highly concerned; 44.3% somewhat concerned). Over the next year, 33% believe cloud misconfigurations will increase and 43% believe the rate of misconfiguration will stay the same. Only 24% believe cloud misconfigurations will decrease at their organisation. Preventing cloud misconfiguration Preventing cloud misconfiguration remains a significant challenge for cloud engineering and security teams. Every team operating on cloud has a misconfiguration problem, with 73% citing more than 10 incidents per day, 36% experiencing more than 100 per day, and 10% suffering more than 500 per day. 3% had no idea what their misconfiguration rate is. The top causes of cloud misconfiguration cited are a lack of awareness of cloud security and policies The top causes of cloud misconfiguration cited are a lack of awareness of cloud security and policies (52%), a lack of adequate controls and oversight (49%), too many cloud APIs and interfaces to adequately govern (43%), and negligent insider behaviour (32%). Only 31% of teams are using open source policy-as-code tooling to prevent misconfiguration from happening, while 39% still rely on manual reviews before deployment. Identity and access management permissions Respondents cited a number of critical misconfiguration events they’ve suffered, including object storage breaches (32%), unauthorised traffic to a virtual server instance (28%), unauthorised access to database services (24%), overly-broad Identity and Access Management permissions (24%), unauthorised user logins (24%), and unauthorised API calls (25%). Cloud misconfiguration was also cited as the cause of system downtime events (39%) and compliance violation events (34%). While malicious actors use automation tools to scan the internet to find cloud misconfigurations within minutes of their inception, most cloud teams still rely on slow, manual processes to address the problem. 73% use manual remediation once alerting or log analysis tools identify potential issues, and only 39% have put some automated remediation in place. 40% of cloud teams conduct manual audits of cloud environments to identify misconfiguration. A reliance on manual approaches to managing cloud misconfiguration creates new problems, including human error in missing or miscategorising critical misconfigurations (46%) and when remediating them (45%). 43% cite difficulties in training team members to correctly identify and remediate misconfiguration, and 39% face challenges in hiring enough cloud security experts. Issues such as false positives (31%) and alert fatigue (27%) were also listed as problems teams have encountered. Effectiveness of cloud misconfiguration The metric for measuring the effectiveness of cloud misconfiguration management is MTTR The metric for measuring the effectiveness of cloud misconfiguration management is Mean Time to Remediation (MTTR), and 55% think their ideal MTTR should be under one hour, with 20% saying it should be under 15 minutes. However, 33% cited an actual MTTR of up to one day, and 15% said their MTTR is between one day and one week. 3% said their MTTR is longer than one week. With cloud misconfiguration rates at such high levels and a widespread reliance on manual processes to manage it, the costs are predictably high for cloud customers. 49% of cloud engineering and security teams are devoting more than 50 man hours per week managing cloud misconfiguration, with 20% investing more than 100 hours on the problem. Helping prioritise remediation efforts When asked what they need to more effectively and efficiently manage cloud misconfiguration, 95% said tooling to automatically detect and remediate misconfiguration events would be valuable (72% very valuable; 23% somewhat valuable). Others cited the need for better visibility into cloud infrastructure (30%), timely notifications on dangerous changes (i.e., “drift”) and misconfiguration (28%), and improved reporting to help prioritise remediation efforts (8%). Cloud security is about preventing the misconfiguration of cloud resources such as virtual servers, networks, and Identity and Access Management (IAM) services. Malicious actors exploit cloud misconfiguration to gain access to cloud environments, discover resources, and extract data. The National Security Agency states that “misconfiguration of cloud resources remains the most prevalent cloud vulnerability and can be exploited to access cloud data and services.” Potentially risky misconfigurations Fugue partnered with Propeller Insights to survey 300 IT, cloud, and security professionals With the cloud, there’s no perimeter that can be defended, exploits typically don’t traverse traditional networks, and legacy security tools generally aren’t effective. Because developers continuously build and modify their cloud infrastructure, the attack surface is highly fluid and expanding rapidly. Organisations widely recognised as cloud security pioneers can fall victim to their own cloud misconfiguration mistakes. With the Shared Responsibility Model, cloud providers such as Amazon Web Services, Microsoft Azure, and Google Cloud Platform are responsible for the ‘security of the cloud,’ and the customer is responsible for the ‘security in the cloud.’ While cloud providers can educate and alert their customers about potentially risky misconfigurations and good security practices, they can’t prevent their customers from making misconfiguration mistakes. Fugue partnered with Propeller Insights to survey 300 IT, cloud, and security professionals, including DevOps engineers, cloud architects, security engineers, site reliability engineers (SREs), DevSecOps engineers, and application developers. Professionals from companies representing a variety of industries that use Amazon Web Services, Microsoft Azure, and Google Cloud Platform for cloud computing were surveyed.
Fugue, the company delivering autonomous cloud infrastructure security and compliance, has announced the release of the Fugue Best Practices Framework to help cloud engineering and security teams identify and remediate dangerous cloud resource misconfigurations that aren’t addressed by common compliance frameworks. Users can deploy the Fugue Best Practices Framework within minutes to improve the security posture of their Amazon Web Service (AWS) cloud environments. Cloud misconfiguration, primary cause of data breaches Cloud misconfiguration is the number one cause of data breaches involving public cloud services Cloud misconfiguration is the number one cause of data breaches involving public cloud services such as those offered by AWS. The scale, complexity, and dynamic nature of cloud infrastructure environments often leads to significant misconfiguration events that traditional security analysis tools fail to prevent or detect. According to Neil MacDonald at Gartner, “Nearly all successful attacks on cloud services are the result of customer misconfiguration, mismanagement and mistakes.” While compliance frameworks such as the CIS Foundations Benchmarks address a number of cloud misconfiguration risks, recent major cloud-based data breaches were possible due to misconfigurations not necessarily covered by these standards. The Fugue Best Practices Framework is designed to complement standards such as the CIS Foundations Benchmark to provide additional protection against today’s advanced misconfiguration attacks. Fugue Best Practices Framework “Enterprise cloud and security teams are recognising that their current cloud security posture leaves them vulnerable to newer and more sophisticated misconfiguration attacks,” said Phillip Merrick, CEO of Fugue. “The Fugue Best Practices Framework gives cloud teams a simple tool to quickly identify these misconfigurations in their cloud environment and the most comprehensive security against cloud misconfiguration risk when used in combination with a framework like the CIS Foundations Benchmark.” The Fugue Best Practices Framework includes rules covering the following cloud vulnerabilities: Identity and Access Management (IAM) misconfigurations that can provide bad actors, including malicious insiders, with the ability to move laterally and discover resources to exploit S3 bucket policy misconfigurations that can be exploited in order to take data exfiltration actions VPC Security Group rule misconfigurations that can enable malicious access via Elasticsearch, etcd, and MongoDB services Enhancing cloud infrastructure security Fugue will continue to add new rules to the Fugue Best Practices FrameworkFugue will continue to add new rules to the Fugue Best Practices Framework as new misconfiguration attack vectors are identified. The Fugue Best Practices Framework joins a growing number of out-of-the-box cloud compliance frameworks Fugue provides, including CIS Foundations Benchmarks, GDPR, HIPAA, ISO 27001, NIST 800-53, PCI, and SOC2. Fugue also supports custom rules using Open Policy Agent, an open source policy as code engine, making it easy for enterprise cloud teams to create cloud infrastructure policies tailored to meet their specific use cases and security requirements. The Fugue Best Practices Framework is available now for all Fugue customers and can be used with a 30-day free trial.
Fugue, the company delivering autonomous cloud infrastructure security and compliance, has announced its support for Open Policy Agent (OPA), an open source general-purpose policy engine and language for cloud infrastructure. Fugue is leveraging OPA and Rego, OPA’s declarative policy language, for cloud infrastructure policy-as-code to provide customers with maximum flexibility when implementing their custom enterprise policies. The Cloud Native Computing Foundation (CNCF) accepted OPA as an incubation-level hosted project in April 2019. Focus of OPA has been on developing access policies for Kubernetes, while Fugue is driving the adoption of OPA Open Policy Agent on access policies While much of the focus of OPA has been on developing access policies for Kubernetes, Fugue is driving the adoption of OPA to address a wider variety of use cases for securing cloud environments on Amazon Web Services (AWS) and Microsoft Azure, including the application of common compliance frameworks to full cloud infrastructure stacks. The Fugue team has developed tools and enhancements to improve OPA’s developer experience. Fugue has provided many of these enhancements to the OPA open source project, and will continue to do so. Enhancing enterprise security Fugue has also added support to its product for customer-defined rules written using OPA and Rego. This sets Fugue apart from all other cloud infrastructure policy management solutions that rely on proprietary and inflexible rule languages that lock-in customers and are incompatible with other policy languages used elsewhere in the enterprise. Fugue also uses OPA to provide out-of-the-box support for commonly used compliance frameworks including CIS Foundations Benchmarks, GDPR, HIPAA, ISO 27001, NIST 800-53, PCI, and SOC 2. Cloud infrastructure policies Fugue has been developing policy-as-code solutions for some time, and now we’re offering an open source solution"“It’s very simple to build custom policies for our cloud infrastructure environments and validate those configurations pre-deployment using OPA and Fugue,” said Dave Williams, cloud architect and senior consultant at New Light Technologies. “Fugue simplifies the implementation and enforcement of custom cloud infrastructure policies we’ve written using OPA and helps us prove compliance at all times.” “Fugue has been developing policy-as-code solutions for some time, and now we’re offering an easy-to-use, open source solution for writing policies for cloud infrastructure,” said Phillip Merrick, CEO of Fugue. Cloud security He adds, “Our customers can use the same open language for defining their cloud infrastructure policies in Fugue that they are using for other enterprise policy needs. This eliminates the need to learn other vendors’ proprietary, inflexible policy languages.” Fugue’s custom rules capabilities that leverage OPA enable users to: Build and manage custom, user-defined cloud infrastructure rules in OPA Rego via the Fugue API, CLI, and web interface Validate and test custom rules while they are being written with helpful errors that save time Continuously validate and report on compliance for custom rules and out-of-the-box policy frameworks Security rule evaluations “Fugue is running millions of security rule evaluations every day using OPA, so we've put a lot of work into improving performance and developer tooling and will be contributing all of that back to the open source community,” said Josh Stella, co-founder and CTO of Fugue. Josh said, “OPA is a significant development for policy-as-code, and Fugue is fully committed to supporting and contributing to it.”