Understanding Attacks Linked to Blind Eagle APT-C-36

By Ashwin Venugopal -

 




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





Overview

APT-C-36 also known as Blind Eagle active since 2018, is an espionage group suspected to be originated from South America and mainly targets Colombian government institutions along with the other important corporations of financial sector, petroleum industry, professional manufacturing, etc.

Types of Attack

  • It can use fraudulent emails posing as Colombian government offices.

  • All these emails may state that a government order has been issued along with all the details in the attachment (in which the information is protected with a password).

  • Other spam emails may also claim to provide an Id proof with photo urging the recipient to open it with the password given by the hackers.

  • The sender's email address is generally disguised as a fake profile.

  • These emails also use DOCX/PDF files with a link and when clicked the recipient is taken to a file hosting site that can automatically download a BitRat laden archive. 

Remediation

  • By blocking all the threat indicators at your respective controls.
  • By looking out for all the IOCs in your environment.

Conclusion

As it is known worldwide, APT-C-36 has become more efficient with time and improved its techniques of spreading malware while also avoiding any kind of detection. Hence, one have to keep an eye on this threat group in order to avoid any unpleasant surprises.






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