Track Common Adversary Tasks Performed Using Backdoor.Oldrea

By Ashwin Venugopal -

 




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









Overview

Backdoor.Oldrea, as the name suggests, is a backdoor used by Dragonfly to target energy companies since 2013. It spreads through supply chain compromise and also contains special modules to enumerate as well as map ICS-specific systems, processes, and protocols. It's a Remote Access Trojan (RAT) and can easily communicate with Command and Control (C2) server, that deploys payloads and offers additional functionality.

Techniques Used

Some of the techniques used by the malware are:
  • Automated Collection- Collects the information about the connected devices and send them to the server for the threat actors to analyze. 

  • Denial of Service- Sudden crash of the various OPC platforms may lead to the denial of service impact on the applications.

  • Spearphishing Attachment- The malware can easily spread via the emails containing the malicious links or attachments.

  • Point & Tag Identification- As the malware is capable of enumerating OPC tags, they can easily get information about the names and function of control devices. 

  • Supply Chain Compromise-The malware can also spread via malicious installers planted on compromised vendor sites. 

Remedy

The following methods may help in mitigating the threat:
  1. Use an Antivirus.
  2. Carefully download online files.
  3. Use a firewall.
  4. Use a password manager.
  5. Regular security updates/patches.














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

Deployment (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 3, please click  here Microsoft Sentinel Content Hub Content in Microsoft Sentinel includes any of the following types: Data connectors offer log ingestion from different sources into Microsoft Sentinel. Parsers give log formatting/transformation into ASIM formats, supporting usage across various Microsoft Sentinel content types and scenarios. Workbooks provide monitoring, visualization, and interactively with data in Microsoft Sentinel, highlighting meaningful insights for users.  Analytics rules give alerts that point to relevant SOC actions via incidents.  Hunting Queries are used by SOC teams to proactively hunt for threats in Microsoft Sentinel. Notebooks help SOC teams in using advanced hunting features in Jupyter and Azure Notebooks. Watchlists support the ingestion of specific data for enhanced threat detection and reduced alert fatigue.  Playbooks and Azure Logic Apps Custom Connectors provide featu...
Read more