A Ransomware That Is Royal

By Ashwin Venugopal -

 







Overview

First discovered in September 2022, Royal ransomware is a group of threat actors that had targeted more than 350 million known victims worldwide, and their ransom demand have exceeded 275 USD till now. Previously, this ransomware was linked to another ransomware family, Zeon, that started in January 2022. 

Interestingly, they do not hire affiliates to promote their Ransomware-as-a-Service (RaaS) model. This group is mainly made up of the former members of Conti ransomware group. This fact give them experience and a solid base to carry out their extorting activities across the globe. They threatened certain critical infrastructure sectors like, manufacturing, healthcare, and education industry.

Methodology

This ransomware group uses following multiple initial access vectors to secure access into vulnerable systems:
  1. Callback phishing
  2. SEO poisoning 
  3. Exposed Remote Desktop Protocol (RDP) accounts
  4. Compromised credentials

They make use of the unique partial encryption approach allowing the threat actor to choose a specific percentage of data in a file to encrypt. It helps the ransomware to evade detection and save the encryption percentage for larger files. Besides, they also go for double extortion tactics publicly threatening the release of encrypted data if the victim does not pay the ransom. 

Prevention

General methods to combat a ransomware attack are as follows-
  • Mandatory strong password policies and multi-factor authentication for all critical services.
  • Use updated or modern Identity and Access Management (IAM) tools.
  • Employ advanced endpoint security products on all endpoints.
  • Regularly update all the software and operating systems. 
  • Have the least privilege approach to security, including the removal of all the unnecessary access to administrative shares and other services.
  • Administer a solid backup strategy including offline, encrypted, and immutable backup of data.


Conclusion

Royal ransomware has been widely active since few years and still using a variety of tools to aggressively target critical infrastructure organizations. The best security practices should be implemented and organizations must be wary of this ongoing ransomware. 























































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more