Track Common Adversary Tasks Performed Using Agent.btz

By Ashwin Venugopal -

 




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




Overview

Agent.BTZ or Autorun is a worm that generally spreads through USBs. Although, it was initially thought to be related with China but, it's still not clear if it is really related to China or Russia. This worm has attacked a US military base at Middle-East via an infected USB attached to a laptop linked with the United States Central Command which took nearly 14 months to clear from the military networks. 

Tactics

Whenever the operators of Agent.BTZ recognize their targets, such as, military networks, they quickly take action by gaining remote control and installing other malicious tools to steal important documents.

Characteristics

Some of its main characteristics are:
  • It is used to steal or exfiltrate sensitive information or documents.

  • It is deployed with the help of access methods like PowerStallion, PowerShell backdoor, etc. 

  • It can perform so many actions on a compromised computer, like, executing additional programs, stealing files, etc.

Prevention

In order to protect against this kind of cyberthreat you can follow the steps given below:
  • Security Training- Security awareness training of the employees is the most inevitable part to secure your network's environment from these type of cyberthreats which makes the employees vigilant so that, they won't compromise the network's security unintentionally.

  • Strict Access Control Procedures- It allows you to restrict the fallouts from the compromised credentials.

  • Secure Remote Access Solutions- Organizations must use either secure connections via Virtual Private Networks (VPNs) for remote access or tightly secured gateways to restrict the attack surface.

  • Zero-Trust Security Technologies- This approach allows granular over lateral movements, which is vital as many RAT attacks uses lateral movements to infect a system.








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