Track Common Adversary Tasks Performed Using BBSRAT

By Ashwin Venugopal -

 









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













Overview

BBSRAT is a type of malware that allows the attackers remotely access the compromised system and execute remote commands, codes, or deploy additional malware in the system. The threat actors behind it are called 'Roaming Tiger' and they are known to specifically target Russia or Russian speaking countries via phishing emails written exclusively in Russian.

Capabilities

Once it's inside your system, the BBSRAT can perform following task:

  1. Execute remote commands and transfer the response to the control server.
  2. Delete all the files related to its activity.
  3. List running processes and cancel the specific ones. 
  4. Receive directory structure and a list of files.
  5. Read, edit, or delete files.
  6. Upload more files from the control server.   



Defensive Measures:

  • Training- As humans tend to make mistakes in an IT industry, a regular social engineering awareness training is recommended, so that, they can become the primary firewall to defend against social engineering attacks.

  • Defense in Depth- An in-depth defense strategy can be applied, that instead of preventing the attack, slows down the progression of the attack just enough, so that the defenders can take action in the meantime. 

  • Intrusion Detection systems- They can be used in order to detect various attacks like buffer overflows, CGI attacks, SMB probes, OS fingerprinting, etc.

  • System Integrity Verifiers (SIV)- Any changes in the system components can be detected while also comparing the snapshots of file systems with the pre-existing baseline snapshots in order to secure against any kind of system intrusion.

  • Multihomed Firewalling- This technique can be used in which firewalls having more than one interfaces to further subdivide the network are required, in order to minimize the amount of damage done by an attacker on a private network.

  • Honeypot- This method is used to attract or trap the attackers trying to gain unauthorized access, in order to learn more about their motives and objectives.

  • Patch Management- The defender must have up-to-date software and firmware patches, so that they can be deployed whenever needed.









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 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