Understanding Attacks Linked to APT38

By Ashwin Venugopal -








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









Overview

APT38 is a North Korean backed cyber threat group, that has actively targeted banks, financial institutions, casinos, cryptocurrency exchanges, SWIFT system endpoints, ATMs, etc. in various countries since 2014.

Some of their significant as well as destructive attacks include the Bank of Bangladesh heist of 2016 which resulted in stolen $81 million, the attack on Bancomext and Banco de Chile in 2018, etc. 

Targeting Pattern

This cyber threat group has targeted more than 16 organizations in at least 13 countries which indicates that the group is very large and laced with extensive resources. Some of their target details are as follows:
  • The total number of targeted organizations may be higher due to the low incident reporting rate from the affected organization.

  • Their attacks are always planned, they are subtle in their operations with mixed operating system environments, they always use custom-made tools, and completely destroys all the compromised machines afterwards.

  • Their attacks are very calculated and careful with aspiration of longer access to the victim's environment in order to understand the network layout, technology, and required permissions to be successful in their goals.

Impact

  • Loss as well as compromise of sensitive user information and high-value user accounts.
  • Its illicit transactions via victim's infrastructure may lead to loss of monetary funds.
  • A successful compromise may lead to regulatory fines like GDPR, or PCI DSS penalties if gross negligence is discovered. 

Remedy

It is highly recommended to patch your public-facing network and use Mimikatz defense guide along with the other defensive techniques in order to improve your defensive stance as well as minimize its impact to your business operations. 











 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