Ebook Ransomware Oct12023
Ebook Ransomware Oct12023
Acknowledgements
Author
Charles lheagwara, Principal Program Manager
Contributors
Mark Simos, Lead Cybersecurity Architect
Table of Contents
Executive Summary 1
Responding to Ransomware Attacks: Increase effectiveness with practiced incident response teams 33
Conclusion 36
Executive Summary
Ransomware and extortion attacks are a high profit, low-cost attacker
business model that have a debilitating impact on targeted organizations,
national security, economic security, and public health and safety. What
started as simple single-PC ransomware has grown to include a variety of
extortion techniques directed at all types of organizations and platforms.
This eBook helps guide you on Azure native capabilities and defenses for
ransomware attacks you can proactively leverage these to protect your
assets on Azure cloud.
Introduction
Ransomware explained
1. Exposure is where attackers look for 2. Attackers will try to exploit an 3. During the lateral movement stage, attackers 4. The actions an attacker takes after
opportunities to gain access to your exposure to gain access to your discover what resources they have access to lateral movement, are largely dependent
infrastructure. For example, attackers public cloud infrastructure. This can and what the scope of that access is. Successful on the resources they were able to gain
know customer-facing applications must be done through compromised user attacks on instances give attackers access to access to during the lateral movement
be open for legitimate users to access credentials, compromised instances, storage, databases and other sensitive phase. Attackers can take actions that
them. Those applications are exposed to or misconfigured resources. information. The attacker then searches for cause data exfiltration, data loss or launch
the Internet and therefore susceptible to additional credentials. Our Microsoft Defender other attacks. For enterprises, the average
attacks. Microsoft Defender External for Cloud data shows that without a security financial impact of data loss is now
Attack Surface Management discovers tool to quickly notify you of the attack, it takes reaching $1.23 million.
and maps your externally-facing attack organizations on average 101 days to discover
surface to provide insight about your 1st a breach. Meanwhile, in just 24-48 hours after a
& 3rd party online infrastructure that is breach, the attacker will usually have complete
accessible to the open Internet. control of the network.
• The attack surface has increased as more and more businesses offer more services
through digital outlets
• There is a considerable ease of obtaining off-the-shelf malware, Ransomware-as-a-
Service (RaaS)
• With the above, the option to use cryptocurrency for blackmail payments has
opened new avenues for exploit
• Expansion of computers and their usage in different workplaces (local school
districts, police departments, police squad cars, etc.) each of which is a potential
access point for malware, resulting in potential attack surface
• Prevalence of old, outdated, and antiquated infrastructure systems and software.
• Poor patch management regimen
• Outdated or very old operating systems that are close to or have gone beyond end-
of-support dates
• Lack of resources to modernize the IT footprint
• Knowledge gap
• Lack of skilled staff and key personnel overdependency
• Poor security architecture
Figure 3: Ransomware Compromise Techniques
While you may ultimately be forced into a difficult position where paying seems to be the best option,
you should never plan to pay the ransom ahead of time. Paying the ransom doesn't immediately
restore services, it often requires tools that are prone to failure and require manual restore steps on
each device. It also marks your organization as “willing to pay” to the criminal underground, provides
attack groups with funding to buy more advanced tools, and carries the risk of funding criminal
and/or terrorist activity (which is explicitly outlawed in some jurisdictions).
You may find yourself a victim of an intentional destruction attack where there is no recovery key
available (such as in the case of NotPetya and some recent attacks related to Ukraine).
In the end, the best way to prevent paying ransom is not to fall victim by implementing preventive
measures and having tool saturation to protect your organization from every step that an attacker
takes wholly or incrementally to hack into your system. In addition, having the ability to recover
impacted assets will ensure restoration of business operations in a timely fashion. Azure Cloud has a
robust set of tools to guide you all the way.
• Financial loss
Colonial Pipeline paid about $4.4 Million in ransom to have their data
released. This does not include the cost of downtime, lost productivity, lost
sales and the cost of restoring services. More broadly, a significant impact is
Figure 4: Impact of Ransomware Attack to Business
the “knock-on effect” of impacting high numbers of businesses and
organizations of all kinds including towns and cities in their local areas. The
financial impact is also staggering. According to Microsoft, the global cost
associated with ransomware recovery was projected to exceed $20 billion in
2021 and is expected to grow year to year as both the number and scope of
attacks continue to increase.
Azure Firewall Premium TI and IDPS signatures can identify, and block
command-and-control activity and other operations used by Figure 6: Detecting and Preventing Ransomware with Azure Firewall
ransomware at the network layer to enable early
detection, comprehensive attack prevention or lower their impact
to resources.
Defender for Cloud has different plans to help protect your hybrid workloads, cloud
native services, and servers from ransomware and other threats; it integrates with
your existing security workflows like your SIEM solution and Microsoft’s vast threat
intelligence to streamline threat mitigation.
Defender for Cloud has a built-in Ransomware workbook that maps security
recommendations to MITRE ATT&CK framework, facilitating the prioritization of
remediations to help prevent successful attacks.
Defender for Cloud helps you to incorporate good security practices early during the
software development process, or DevSecOps. You can protect your code
management environments and your code pipelines and get insights into your
development environment security posture from a single location. In addition,
Defender for Cloud extends protection to on-premises and multi-cloud workloads, Figure 7: Defender for Cloud
including Containers and SQL databases using Azure Arc.
With Sentinel you can connect to any of your security sources using built-
Microsoft Sentinel helps to create in connectors and industry standards and then take advantage of artificial
intelligence to correlate multiple low fidelity signals spanning multiple sources
Microsoft Sentinel is your birds-eye view across the enterprise alleviating the
stress of increasingly sophisticated attacks, increasing volumes of alerts, and
Microsoft Sentinel
long resolution time frames.
Optimize security operations with cloud-native SIEM powered by AI and automation
• Harness the scale of the cloud eliminating infrastructure setup and
maintenance and collecting data across your entire organization.
has capabilities to detect and Microsoft Defender for Cloud is a cloud-native application protection
platform (CNAPP) with a set of security measures and practices designed to
and threats against your you can take to prevent breaches and a cloud workload protection platform
(CWPP).
workloads in Azure Microsoft Defender for Cloud's threat protection enables you to detect and
prevent threats at the IaaS and PaaS layers in Azure, as well as in non-Azure
servers.
Microsoft Defender for Cloud has different plans that offer tailored threat
detection and alert correlation with the fusion. This capability automatically
correlates alerts in your environment based on cyber kill-chain analysis, to
help you better understand the full story of an attack campaign, where it
started and what kind of impact it had on your resources.
Azure Backup Azure Site Recovery Built-in Security and Management in Azure
Azure Backup, part of Azure Business Continuity and With disaster recovery from on-prem to the cloud, To be successful in the Cloud era, enterprises must have
Disaster Recovery (BCDR) services, provides simple, or from one location to another, you can avoid visibility/metrics and controls on every component to
secure, and cost-effective solution to back up your downtime and keep your applications up and pinpoint issues efficiently, optimize and scale effectively,
Azure VMs, on-prem servers, databases running in running. Azure Site Recovery, also part of Azure while having the assurance the security, compliance and
Azure VMs, and other Azure resources. Additionally, BCDR, can help accomplish this. polices are in place to ensure the velocity.
several Azure resources also provide their own built-
in backup solutions. Azure Backup also provides
several enhanced protection features like
immutability, MUA and soft delete to help protect
better against threats like ransomware.
Key Features:
• Azure comes with Locally Redundant Storage (LRS), where data is stored locally, as well as Geo
Redundant Storage (GRS) in a second region
• All data stored on Azure is protected by an advanced encryption process, and all Microsoft’s data
centers have two-tier authentication, proxy card access readers, biometric scanners
• Azure has more certifications than any other public cloud provider on the market, including ISO
27001, HIPAA, FedRAMP, SOC 1, SOC 2, and many international specifications
Guaranteed: - Microsoft offers 99.5-99.9% uptime on their services. Read the full SLA for more details.
All of the above are some very good reasons to trust Microsoft—and Azure—with your data.
Ultimately, the Framework is aimed at reducing and better managing cybersecurity risks Logging and Threat Detection (LT)
1 2 3
Prepare your recovery plan Limit the scope of damage Make it hard to get in
Recover without paying Protect privileged roles Incrementally remove risks
Based on our experience with ransomware attacks, we’ve found that prioritization should focus on:
This may seem counterintuitive, since most people want to simply prevent attacks first. But the unfortunate truth is that we must assume breach (a key Zero Trust
principle) and focus on reliably mitigating the most damage first. This prioritization is critical because of the high likelihood of a worst-case scenario with
ransomware/extortion attacks.
While it’s not a pleasant truth to accept, we face creative and motivated human attackers who are skilled at finding ways to control the complex environments we
operate. Against that reality, it’s important to prepare for the worst and establish frameworks to contain and prevent attackers’ ability to get what they’re after.
While these priorities should govern what to do first, we encourage organizations to run as many steps in parallel as
possible (including pulling quick wins forward from steps 2 and 3 whenever you can).
Note: The attackers may still attempt to extort the organization through data disclosure or
abusing/selling the stolen data, but this gives them less leverage than if they have the only
access path to your data and systems.
1. Register Risk - Add ransomware to risk register as high likelihood and high impact scenario. Track mitigation status via
Enterprise Risk Management (ERM) assessment cycle.
2. Define and Backup Critical Business Assets – Define systems required for critical business operations and automatically
back them up on a regular schedule (including correct backup of critical dependencies like Active Directory).
3. Protect backups and supporting documents/systems (CMDB, network diagrams, etc.) against deliberate erasure and
encryption. This could use immutable backups, traditional offline/isolated backups, soft delete, and/or out of band steps
(MFA, MUA or PIN) before modifying/erasing online backups.
4. Test ‘Recover from Zero’ Scenario – test to ensure your business continuity / disaster recovery (BC/DR) can rapidly bring
critical business operations online from zero functionality (all systems down). Conduct practice exercise(s) to validate
cross-team processes and technical procedures, including out-of-band employee and customer communications (assume
all email/chat/etc. is down).
IMPORTANT: Protect (or print) supporting documents and systems required for recovery including restoration
procedure documents, CMDBs, network diagrams, SolarWinds instances, etc. Attackers destroy these regularly.
5. Reduce on-premises exposure – by moving data to cloud services with automatic backup & self-service rollback.
Step 2 –
Limit Scope of Damage:
Protect Privileged Roles
(starting with IT Admins)
Ensure you have strong controls (prevent, detect, respond) for
privileged accounts like IT Admins and other roles with
control of business-critical systems. This slows and/or blocks Figure 9: Complete End-to-end Approach
attackers from gaining complete access to your resources to
steal and encrypt them. Taking away the attackers’ ability to See Microsoft’s recommended roadmap at aka.ms/spa that describes how to establish:
use IT Admin accounts as a shortcut to resources, will
• End to End Session Security (including multifactor authentication (MFA) for admins)
drastically lower the chances they are successful at attacking
you and demanding payment / profiting. • Protection and Monitoring Identity Systems
Organizations should have elevated security for privileged • Mitigating Lateral Traversal attacks
accounts (tightly protect, closely monitor, and rapidly respond
• Establishing Rapid Threat Response
to incidents related to these roles).
Step 3 –
Make it harder to get in:
incrementally remove risks Microsoft recommends organizations follow the principles outlined
in the Zero Trust strategy here. Specifically, against Ransomware,
Prevent a ransomware attacker from entering your environment and organizations should prioritize:
rapidly respond to incidents to remove attacker access before they
can steal and encrypt data. This will cause attackers to fail earlier
and more often, undermining the profit of their attacks. While a. Ransomware-specific features of detection and prevention
prevention is the preferred outcome, it is a continuous journey and tools. While these won’t block all attacks, these will quickly
may not be possible to achieve 100% prevention and rapid response mitigate risks specific to attack techniques currently popular
across a real-world organization’s complex multi-platform and with these attackers.
multi-cloud estate with distributed IT responsibilities.
b. Improving security hygiene by focusing efforts on attack
surface reduction and threat and vulnerability management for
To achieve this, organizations should identify and execute quick
assets in their estate.
wins to strengthen security controls to prevent entry and rapidly
detect/evict attackers while implementing a sustained program that c. Implementing Protection, Detection and Response
helps them stay secure. controls for their digital assets that can protect against
commodity and advanced threats, provide visibility and alerting
. on attacker activity, and respond to active threats.
Educate end-users on the dangers of ransomware Educate security operations center (SOC) analysts and
others on how to respond to ransomware incidents
As most ransomware variants rely on end-users to install the
ransomware or connect to compromised Web sites, all end-
SOC analysts and others involved in ransomware incidents should
users should be educated about the dangers. This would
know the fundamentals of malicious software and ransomware
typically be part of annual security awareness training as well as
specifically. They should be aware of major variants/families of
ad hoc training available through the company’s learning
ransomware, along with some of their typical characteristics.
management systems. The awareness training should also
Customer call center staff should also be aware of how to handle
extend to the company’s customers via the company’s portals
ransomware reports from the company’s end-users and customers.
or other appropriate channels.
• Static and dynamic malware analysis tools • Active Directory and other authentication systems
(and related logs)
• Digital forensics software and hardware
• Internal Configuration Management Databases (CMDBs)
• Non- Organizational Internet access (e.g. 4G dongle) containing endpoint device information
• Designate Protected Folders – to make it more difficult for • Backup all critical systems automatically on a regular schedule.
unauthorized applications to modify the data in these folders.
• Ensure Rapid Recovery of business operations by regularly exercising
• Review Permissions – to reduce risk from broad access business continuity / disaster recovery (BC/DR) plan.
enabling ransomware
• Protect backups against deliberate erasure and encryption
• Discover broad write/delete permissions on fileshares,
SharePoint, and other solutions • Strong Protection – Require out of band steps (MFA or PIN) before
allowing access to online backups, such as Azure Backup security
• Reduce broad permissions while meeting business features and Azure Role Based Access (RBAC) model
collaboration requirements
• Strongest Protection – Store backups in online immutable storage
• Audit and monitor to ensure broad permissions (Azure Blob info) and/or fully offline/off-site
don’t reappear
• Protect supporting documents required for recovery such as restoration
procedure documents, CMDB, and network diagrams.
1. Preparation: This stage describes the various measures that should be put into
place prior to an incident. This may include both technical preparations (such as the
Preparing for Ransomware Attacks: Stay ahead of attackers implementation of suitable security controls and other technologies) and non-
technical preparations (such as the preparation of processes and procedures).
Establish an incident
2. Triggers / Detection: This stage describes how this type of incident may be
detected and what triggers may be available that should be used to initiate either
handling process
further investigation or the declaration of an incident. These are generally separated
into high-confidence and low-confidence triggers.
5. Containment / Mitigation: This stage covers the steps that may be taken either by
the Security Operations Center (SOC), or by others, to contain or mitigate (stop) the
incident from continuing to occur or limiting the effect of the incident using
available tools, techniques and procedures.
6. Remediation / Recovery: This stage covers the steps that may be taken to
remediate or recover from damage that was caused by the incident before it was
contained and mitigated.
7. Post-Incident Activity: This stage covers the activities that should be performed
Figure 10: NIST SP 800-61r2 Incident Response Lifecycle
once the incident has been closed. This can include capturing the final narrative
associated with the incident as well as identifying lessons learned.
Once a successful ransomware infection has been confirmed, the analyst should verify that 1. Engage antimalware vendors through standard support processes
this represents a new incident or that it is related to an existing incident. Look for
2. Manually add hashes and other information associated with malware to
currently-open tickets that indicate similar incidents. If so, update the current incident
antimalware systems
ticket with new information in the ticketing system. If this is a new incident, an incident
should be declared in the relevant ticketing system and escalated to the appropriate teams
3. Apply antimalware vendor updates
or providers to contain and mitigate the incident. Be mindful that managing ransomware
incidents may require actions taken by multiple IT and security teams. Where possible, 4. Contain affected systems until they can be remediated
ensure that the ticket is clearly identified as a ransomware incident to guide workflow.
5. Disable compromised accounts
Conclusion
Microsoft focuses heavily on both security of our cloud and providing
you the security controls you need to protect your cloud workloads. As
a leader in cybersecurity, we embrace our responsibility to make the
world a safer place. This is reflected in our comprehensive approach to
ransomware prevention and detection in our security framework,
designs, products, legal efforts, industry partnerships, and services.
Additional Resources
Microsoft Cloud Adoption Framework for Azure Azure Security Control – Incident Response
Build great solutions with the Microsoft Azure Well- Zero Trust Guidance Center
Architected Framework
Azure Web Application Firewall
www.microsoft.com/services
Thank you!