Track Common Adversary Tasks Performed Using Anchor

By Ashwin Venugopal -

 




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






Overview

Anchor is a sophisticated backdoor malware, active since 2018, used with TrickBot installations, and generally targets high profile victims. As it is connected with TrickBot, many experts think that it's manufactured by the same developers.

Features

Some of the main features of Anchor are:
  • The TrickBot-Anchor Relation- As stated above, Anchor is somewhat connected with TrickBot, so, many organizations generally investigate its attacks against financial, manufacturing, and retail businesses, using this point-of-view.

  • Targets POS Systems- It generally targets POS systems stealing sensitive information from the victim's network.

  • Uses New Malware- There are many variants that are new or undocumented, extensively used, and are also related to TrickBot.

  • Uses Known Tools For Reconnaissance & Lateral Movement- Familiar tools such as, PowerShell, Meterpreter, Empire, Cobalt Strike, etc. are used for reconnaissance and lateral movement.  

  • Abuses the Trust of Certificate Authorities- Various payloads in the attacks are signed binaries, that abuses the trust of certificate authorities to bypass detection. 


Conclusion

Thus, the above statements depicts the general ways through which Anchor targets as well as attacks its victims successfully evading the security products like sandboxes, AV vendors, etc. However, as these types of malwares are focusing more on signed malware, the practice of the detection of signed malware must be improved and new rules must be set before giving any trust to signed binaries in general.







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