Track Common Adversary Tasks Performed Using ACAD/Medre.A

By Ashwin Venugopal -

 









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






Overview

ACAD/Medre.A is basically a worm written in AutoLISP (a dialect used in AutoCAD) capable of stealing operational information via collecting AutoCAD files with drawings. This worm has an immense capacity to be used as an industrial espionage. For example the attack of this worm may result in automatic sending of all the new designs or files to the operator of this malware leading a lot of money loss to the legitimate owner as the cybercriminals have the designs even before they are introduced in the market.

Functions

This worm performs following key functions:
  • It can copy itself to various locations so that it can install and spread quickly throughout the system.
  • It steals AutoCAD drawings from the infected systems.

Tactics

The ACAD/Medre.A spreads rapidly through your system or network and uses following tactics to carry out its attack:
  • It can detect all AutoCAD files with the DWG extension and then send them to a remote server by email.

  • It can steal email information from Outlook or Thunderbird so that it can attack in future.

  • It can also create a RAR archive containing all the stolen data and its code.

Remedy

As generally ACAD/Medre.A spreads through malicious email attachment, it is advised to scan all the AutoCAD files via an updated antimalware program before it can affect your system. However, those who don't use AutoCAD files are not affected by this attack, it is a matter of serious concern for those who uses these files.








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