Mitiga Appoints Charlie Thomas as CEO READ THE RELEASE

Mitiga Announces $30M Series B Led by SYN Ventures READ THE NEWS

More and more, companies look to the cloud for increased scalability, business continuity and cost-efficiency. In fact, it’s estimated that in 2021, 94% of the Internet workload will be processed in the cloud.

Moving to the cloud is driven by many goals, including security and data protection, and modernization, but cloud technology doesn’t come without concerns.

In a recent survey:

  • Nearly 4 of every 5 companies experienced at least one cloud data breach between December 2018 and May 2020
  • More than 2 out of 5 said they had experienced 10 or more cloud security breaches in that time
  • More than 7 out of every 10 companies cited security configuration management as a top cloud security priority

Enterprises moving to the cloud from legacy data centers face many security challenges in making that transition, most notably the following:

1. Lack of Architectural and Organizational Alignment

Be prepared for a move to the cloud to impact nearly every part of your organization. Security controls, governance models, and org charts must adapt to new ways of working as enterprises move systems to the cloud. Applications suddenly operate as rapidly changing distributed systems, having little in common with the stateful nature of most legacy applications. Security teams must collaborate across organizational and functional boundaries, standing the insular nature of most security organizations on its head. These cultural and technical asymmetries undermine security posture and incident response efforts.

2. Lack of Cloud Experience

Security teams experienced in managing an internal data center usually lack the skills necessary to ensure the security around cloud systems. Cloud security assessments are very different from traditional data center assessments, for example. Organizations must also work out the specific responsibilities between the cloud provider and the organization, and inexperience often leads to fundamental misconfiguration problems that can create serious security issues. If security teams apply traditional security controls and techniques to the cloud, avoidable failures are inevitable.

3. Speed of Change

One of the primary business benefits of cloud services is the ease with which new features (including security settings) can roll out. But that benefit can put the security team behind the curve if it doesn’t have enough people to keep up with rapidly changing systems. Understanding how changing feature sets, configuration settings, and security controls affect security posture is essential.

4. Higher and New Levels of Complexity

Cloud vendors typically provide deep logging capabilities. But security teams face significant challenges getting up to speed on those logs and understanding how to monitor them in near real-time. The need to define the right queries and metrics based on the organization’s specific business lines, threat models and risk profiles is even more challenging. Integrating these functions with legacy infrastructure and an existing SOC are obstacles to a successful transition to the cloud, compromising readiness, and response.

Is Your Enterprise Prepared for Cloud Security Incidents?

If you can recognize or relate to any of these four challenges, it’s time to take action before your enterprise experiences a disabling or dangerous breach.

The transition to the cloud challenges traditional information security models in fundamental ways, compromising both readiness and response. Speedy investigation, response (including situational awareness), and recovery are crucial for returning to business as usual, particularly during incidents that require rapid response.

Whitepaper: The 9 Fundamental Ways Incident Response Is Different in the Cloud

LAST UPDATED:

May 3, 2024

Don't miss these stories:

Can vulnerabilities in on-prem resources reach my cloud environment?

What risk does this Zoho password manager vulnerability present, and could this on-prem vulnerability impact cloud environments as well?

Log4Shell - identify vulnerable external-facing workloads in AWS

Cloud-based systems should be thoroughly searched for the new Log4j vulnerability (CVE-2021-44228). But this is a daunting task, since you need to search each and every compute instance, from the biggest EC2 instance to the smallest Lambda function. This is where Mitiga can help.

How Transit Gateway VPC Flow Logs Help Incident & Response Readiness

In this blog, we will focus on the security and forensic aspects of Transit Gateway VPC flow logs and expand the way they can be used by organizations to respond to cloud incidents.

Uber Cybersecurity Incident: Which Logs Do IR Teams Need to Focus On?

On September the 16th, Uber announced they experienced a major breach in their organization in which malicious actor was able to log in and take over multiple services and internal tools used at Uber. What are some of the logs that IR teams should be focusing on in their investigation?

Viral Outbreaks: Thinking of Microsoft’s New Wormable Vulnerability in a Coronavirus Context

But today, in the midst of a pandemic outbreak of Coronavirus (COVID-19) and while governments and global organizations work to contain and eradicate the virus, we’re hearing of a new wormable vulnerability in Microsoft’s SMBv3 protocol.How can we learn from these unfortunate events to provide us with a different context and an opportunity to rethink our level of readiness for unexpected, viral cyber events?

Unlocking Cloud Security with Managed Detection and Response

See how Mitiga’s Cloud Managed Detection and Response tackles complex cyber threats with proactive threat management and advanced automation at scale.