Ransomware WannaCry

By Ashwin Venugopal -

 





Introduction

The WannaCry Ransomware attacked worldwide in May, 2017. It used the WannaCry ransomware cryptoworm, and targeted the computers running on the Microsoft Windows Operating System. It encrypted the data and demanded ransom payments in the Bitcoin cryptocurrency. It exploited EternalBlue. developed by the United States National Security Agency, which was stolen and leaked by The Shadow Brokers one month before the attack occurred. 

Countries like the U.S.A. and U.K. formally confirmed that the attack was originated from North Korea. However, North Korea denied any involvement in the attack. It is estimated that the attack affected more than 300,000 computers of about 150 countries. 

Characteristics

The WannaCry Ransomware cryptoworm is also known as WannaCrypt, Wanna Decrypt0r 2.0, and Wanna Decryptor. It is a network worm laced with a transport mechanism to automatically spread itself. The transport code scans the vulnerable systems and gain access using the EternalBlue exploit. After that the DoublePulsar backdoor tool is used to install and execute a copy of the ransomware. 

When the execution is done successfully, this malware checks the kill switch domain name before anything, and if it is not there then the ransomware starts encrypting the data. It also try to exploit the SMB vulnerability spreading itself to the other computers via internet and laterally to the computers present on the same network. 

 Impact

Kaspersky Lab asserted that the countries like India, Russia, Ukraine, and Taiwan were the most affected countries among the others. The other organizations targeted by this ransomware were the National Health Service Hospitals of England and Scotland, Nissan Motor Manufacturing in UK, Spain's Telefonica, FedEx, and Deutsche Bahn, etc. 

However, the attack done by WannaCry was relatively less as compared to the other potential attacks of same types. It should be noted that its attacks might be much worse if Hutchins had not discovered the in-built kill switch created by its creators, or if it targeted much critical infrastructures like the railways, Nuclear power plants, dams, etc. 

Conclusion

WannaCry ransomware had targeted many organizations, that have been identified publicly. Hence, the information available about their pattern and everything is sufficient enough to successfully protect a network from its attack and/or mitigate its adverse effects. 





















































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