Track Common Adversary Tasks Performed Using Bad Rabbit

By Ashwin Venugopal -

 











To know more about it, you can go through my detailed document by clicking here










Overview

Bad Rabbit is a self-propagating ransomware, that mainly targets Ukrainian transportation sectors as well as Russian consumers. This ransomware locks up the victim's system or network from accessing any files, servers, or files until a ransom is paid (generally in Bitcoin).

How Does It Works?

Bad Rabbit appeared in 2017 and is very similar to the ransomwares like WannaCry and Petya. It spreads via drive-by downloads on a malicious or compromise website posing as a Adobe Flash Installer and when the victim clicks on the malicious link, the users files will be encrypted and a message like- "If you see this text, your files are no longer accessible. You might be looking for ways to recover them. Don't waste your time." After that a ransom in bitcoins is demanded along with a deadline to fulfill it, however, the payment does not always help in unlocking the encrypted files.

Remedy

If your system is infected with Bad Rabbit, then, you can follow these steps:
  • Contact law enforcements.
  • Disconnect from the other computers, networks, or servers connected to your system.
  • Use knowledge of threat intelligence to understand the situation.
  • Decide a proper response as ransomwares like screen-lockers are easier to remediate, while, the others might require proper file recovery from backup.
  • Free ransomware decryption tools might also help but they can't work for every type of ransomware.
  • Restore your files via backup.











To know more about it, you can go through my detailed document by clicking here
































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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more