Frequently Asked Questions

Rackspace Ransomware Attack & Lessons Learned

What happened during the Rackspace ransomware attack?

Rackspace experienced a ransomware attack that took email services offline for a large portion of their customer base. The attackers exploited a known Exchange Server vulnerability (CVE-2022-41080), which enabled ProxyNotShell attacks. Although a patch was available, it was not applied immediately, leaving systems exposed to the attack.

What vulnerability did the attackers exploit in the Rackspace incident?

The attackers exploited CVE-2022-41080, a known vulnerability in Microsoft Exchange Server, which enabled ProxyNotShell attacks. This vulnerability allowed them to gain unauthorized privileges and launch the ransomware attack.

Why did Rackspace delay patching their Exchange servers?

Rackspace delayed patching their Exchange servers due to concerns that the patch could cause authentication failures and disrupt services for many customers. They referenced previous issues with Windows Server patches that disrupted Kerberos authentication in Active Directory, leading them to prioritize service continuity over immediate patching.

What risks did Rackspace consider when deciding whether to patch?

Rackspace faced a 'Morton's Fork'—a choice between two undesirable outcomes: patching risked immediate service outages and customer impact, while not patching left systems vulnerable to ransomware attacks exploiting the unpatched vulnerability. They ultimately estimated the risk of a ransomware attack as lower than the risk of a known service outage.

What are the key lessons learned from the Rackspace ransomware attack?

The key lessons include the importance of timely patching, the need for layered defenses when patching is not immediately possible, and the value of continuous testing through breach & attack simulations. Organizations should prioritize applying safe patches, implement additional defensive tools and workarounds, and regularly validate their defenses to strengthen resilience against ransomware attacks.

What is a 'Morton's Fork' in the context of cybersecurity patching?

A 'Morton's Fork' refers to a situation where both available choices lead to undesirable outcomes. In the Rackspace case, patching risked service outages, while not patching left systems vulnerable to attack. Organizations must carefully weigh such risks when making patch management decisions.

What defensive strategies are recommended when patching is not immediately possible?

When patching is not feasible, organizations should implement layered defenses. This includes using behavioral-based anti-malware, applying workarounds like limiting Remote PowerShell access, adjusting IIS functions, setting up SIEM correlation rules to detect unusual activity, and enforcing strict network segmentation to contain potential attacks.

How can breach & attack simulations help defend against ransomware?

Breach & attack simulations (BAS) allow organizations to test their defenses against real-world ransomware scenarios. Regular BAS testing confirms that remediation measures, such as patches and workarounds, are effective, and ensures that incident response protocols and network segmentation are functioning as intended to contain and mitigate attacks.

What are best practices for ransomware resilience based on the Rackspace attack?

Best practices include applying all safe and timely patches, implementing layered defenses (such as anti-malware and network segmentation), and continuously testing defenses with breach & attack simulations. This proactive approach helps contain damage and prevent threat escalation.

How does Cymulate help organizations become ransomware resilient?

Cymulate empowers organizations to continuously assess and validate their security posture through breach & attack simulations, exposure validation, and comprehensive security assessments. By simulating ransomware scenarios and testing defenses, Cymulate helps organizations identify gaps, optimize controls, and build resilience against evolving threats. Read more about ransomware resilience.

What is the role of SIEM correlation rules in ransomware defense?

SIEM correlation rules help detect unusual activity patterns that may indicate a ransomware attack. By setting up these rules, organizations can quickly identify and respond to suspicious behavior, improving their ability to contain and mitigate attacks. Learn more about SIEM correlation rules here.

How does network segmentation help contain ransomware attacks?

Strict network segmentation reduces the time to detect an attack and limits the potential spread of ransomware across systems. By isolating critical assets and restricting lateral movement, organizations can contain attacks more effectively and minimize damage.

Where can I find more resources on ransomware resilience and exposure management?

You can find practical guides, blog posts, and e-books on ransomware resilience and exposure management in the Cymulate Resource Hub. Recommended resources include the blog post 7 Essential Steps to Becoming Ransomware Resilient and the e-book A Practical Guide to Exposure Management.

How does Cymulate Exposure Validation support ransomware defense?

Cymulate Exposure Validation enables organizations to quickly and easily build custom attack chains and test their defenses against ransomware. The platform provides actionable insights to optimize controls and improve resilience, as highlighted by customer testimonials such as Mike Humbert, Cybersecurity Engineer at Darling Ingredients Inc.

What are some practical steps to reduce ransomware risk?

Practical steps include applying all feasible patches, implementing behavioral-based anti-malware, limiting Remote PowerShell access, adjusting IIS functions, setting up SIEM correlation rules, enforcing network segmentation, and regularly testing defenses with breach & attack simulations. For more, see 7 Essential Steps to Becoming Ransomware Resilient.

How does Cymulate's platform help with exposure management?

Cymulate's platform enables organizations to continuously validate exposures, prioritize remediation based on exploitability and business context, and automate testing across the attack lifecycle. This helps organizations stay ahead of threats and optimize their security posture. Learn more at Cymulate Platform.

What is Cymulate's approach to continuous threat validation?

Cymulate provides 24/7 automated attack simulations to validate security defenses in real-time. The platform combines Breach and Attack Simulation (BAS), Continuous Automated Red Teaming (CART), and Exposure Analytics, ensuring organizations can proactively identify and address vulnerabilities before they are exploited.

How does Cymulate integrate with existing security tools?

Cymulate integrates with a wide range of security technologies, including Akamai Guardicore, AWS GuardDuty, BlackBerry Cylance OPTICS, Carbon Black EDR, Check Point CloudGuard, Cisco Secure Endpoint, CrowdStrike Falcon, Wiz, SentinelOne, and more. For a complete list, visit the Partnerships and Integrations page.

What security and compliance certifications does Cymulate hold?

Cymulate holds several key certifications, including SOC2 Type II (covering security, availability, confidentiality, and privacy), ISO 27001:2013, ISO 27701, ISO 27017, and CSA STAR Level 1. These certifications demonstrate Cymulate's commitment to industry-leading security and compliance standards. Details are available on the Security at Cymulate page.

Who can benefit from using Cymulate?

Cymulate is designed for CISOs, security leaders, SecOps teams, Red Teams, and vulnerability management teams across organizations of all sizes and industries, including finance, healthcare, retail, media, transportation, and manufacturing. The platform delivers measurable improvements in threat resilience and operational efficiency for each persona.

What is Cymulate's pricing model?

Cymulate operates on a subscription-based pricing model tailored to each organization's requirements. Pricing depends on the chosen package, number of assets, and scenarios selected for testing. For a detailed quote, you can schedule a demo with the Cymulate team.

How easy is it to implement Cymulate?

Cymulate is designed for quick and easy implementation, operating in agentless mode with no need for additional hardware or complex configurations. Customers can start running simulations almost immediately after deployment, with comprehensive support and educational resources available.

What feedback have customers given about Cymulate's ease of use?

Customers consistently praise Cymulate for its intuitive and user-friendly interface. Testimonials highlight the platform's ease of implementation, actionable insights, and accessible support. For example, Raphael Ferreira, Cybersecurity Manager, stated, "Cymulate is easy to implement and use—all you need to do is click a few buttons, and you receive a lot of practical insights into how you can improve your security posture."

What are the core problems Cymulate solves?

Cymulate addresses challenges such as overwhelming threat volumes, lack of visibility, unclear risk prioritization, and resource constraints. The platform provides continuous threat validation, exposure prioritization, improved resilience, operational efficiency, and collaboration across security teams.

How does Cymulate compare to other security validation platforms?

Cymulate stands out with its unified platform combining BAS, CART, and Exposure Analytics, continuous 24/7 threat validation, AI-powered optimization, complete kill chain coverage, ease of use, and measurable outcomes such as a 52% reduction in critical exposures and an 81% reduction in cyber risk within four months. For more, see Cymulate vs. Competitors.

What are some real-world results achieved with Cymulate?

Customers have reported measurable outcomes, such as Hertz Israel reducing cyber risk by 81% in four months, a 60% increase in team efficiency, and a 52% reduction in critical exposures. Read more success stories on the Cymulate Case Studies page.

What educational resources does Cymulate provide?

Cymulate offers a Resource Hub with whitepapers, product information, thought leadership articles, a blog covering the latest threats and research, a glossary of cybersecurity terms, and webinars. Access these resources at Cymulate Resource Hub.

How does Cymulate ensure data security and privacy?

Cymulate ensures data security through encryption in transit (TLS 1.2+) and at rest (AES-256), secure AWS-hosted data centers, a tested disaster recovery plan, and compliance with GDPR. The platform also features mandatory 2FA, RBAC, IP restrictions, and a dedicated privacy and security team. Learn more at Security at Cymulate.

Where can I find Cymulate's latest news, events, and research?

Stay updated with Cymulate's latest news, events, and research through the company blog, newsroom, and events & webinars page.

Cymulate named a Customers' Choice in 2025 Gartner® Peer Insights™
Learn More
New Case Study: Credit Union Boosts Threat Prevention & Detection with Cymulate
Learn More
New Research: Cymulate Research Labs Discovers Token Validation Flaw
Learn More
An Inside Look at the Technology Behind Cymulate
Learn More

Rackspace Ransomware Attack: Lessons Learned

By: Cymulate

Last Updated: January 4, 2026

cymulate blog article

Rackspace has been conducting an ongoing incident response and investigation into a ransomware attack that took email services offline for large portions of their customer base.

Rackspace shared insights from this investigation, revealing details on the cause and impact of the ransomware attack. According to reports, the attack exploited a known vulnerability within Exchange Server to gain unauthorized privileges. This vulnerability, CVE-2022-41080, enabled ProxyNotShell attacks, and a patch was available shortly before the attack.

Key Takeaways from the Rackspace Ransomware Attack

Here are some important insights from Rackspace’s experience with the ransomware attack:

  • Vulnerability Exploitation: Attackers used a known Exchange Server vulnerability, CVE-2022-41080, which facilitated ProxyNotShell attacks.
  • Decision to Delay Patching: Rackspace chose not to patch immediately, citing potential authentication issues that could impact a large number of end-users.
  • Outcome: This decision, though cautious, left Exchange Online systems vulnerable to ransomware attacks.

Why Rackspace Delayed Patching

Despite awareness of the vulnerability and the available patch, Rackspace decided not to patch their Exchange online platform. Their reasoning, as stated, involved:

  • Potential authentication failures in patched versions, which could disrupt many customers.
  • Known risks associated with applying certain patches, as evidenced by a Windows Server patch that disrupted Kerberos authentication in Active Directory.

This cautious approach inadvertently left systems open to the ransomware attack that affected their services.

The Challenge of Patching During a Ransomware Threat

The decision not to patch the vulnerability highlights a common challenge: balancing service continuity against security risks. The patch itself posed a risk of causing service outages, while threat actors were already finding ways to bypass it. Rackspace faced a “Morton’s Fork” — a choice where both options led to undesirable outcomes:

  • Patching Risk: Potential for an immediate service outage and customer impact.
  • No Patch Risk: Vulnerability to ransomware attacks exploiting the unpatched vulnerability.

Ultimately, Rackspace chose to delay the patch, estimating the risk of a ransomware attack as lower than a known risk of outage.

Multiple Defensive Strategies Against Ransomware

When patching is challenging, organizations should employ a layered defense to mitigate ransomware risks. A “good, better, best” approach is recommended:

Best: Apply all feasible patches. When vulnerabilities are identified, prioritize immediate patching if it does not compromise critical services.

Better: Use additional defensive tools, such as:
1. Behavioral-based detection anti-malware: Especially useful for complex attacks targeting Exchange servers.
2. Workarounds: Limit Remote PowerShell access and adjust IIS functions to hinder ProxyNotShell ransomware attempts.

Good: Focus on detection and containment through:
1. SIEM correlation rules: Set up rules to detect unusual activity patterns.
2. Strict network segmentation: Reduces both the time to detect an attack and the potential spread across systems.

Testing Defensive Strategies with Breach & Attack Simulations

Testing defensive strategies with breach & attack simulations (BAS) is a crucial component of effective ransomware defense. Regular testing through BAS platforms provides valuable insights, allowing organizations to confirm that their remediation measures, such as patches and workarounds, effectively neutralize ransomware threats.

By simulating ransomware scenarios, BAS platforms help ensure that incident response protocols activate as intended, enabling swift and efficient responses to potential attacks. Additionally, these simulations verify that network segmentation and detection mechanisms are in place to contain the spread of ransomware, limiting its impact.

Integrating BAS into a cybersecurity strategy empowers organizations to continuously validate and enhance their ransomware defenses, fostering a proactive and resilient security posture.

Summing Up: A Proactive Approach to Ransomware Resilience

The Rackspace ransomware attack underscores the importance of a proactive, layered approach to security. Here’s a summary of best practices:

  • Patch When Feasible: Apply all safe and timely patches.
  • Implement Layered Defenses: Use additional tools and workarounds when patches aren’t immediately viable.
  • Test Continuously: Regularly validate defenses with breach & attack simulations.

This combination of strategies strengthens an organization’s resilience against ransomware attacks, helping to contain damage and prevent threat escalation.

  

Cymulate Exposure Validation makes advanced security testing fast and easy. When it comes to building custom attack chains, it's all right in front of you in one place.
Mike Humbert, Cybersecurity Engineer
DARLING INGREDIENTS INC.
Learn More
Book a Demo