Track Common Adversary Tasks Performed Using Agent Tesla

By Ashwin Venugopal -

 









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










Overview

Agent Tesla is an advanced spyware Remote Access Trojan (RAT) written for the .NET framework and has been active seen 2014. It can easily steal sensitive information from an infected machine and collect data like keystrokes as well as login credentials used in various browsers while also mailing clients linked with the victim's machine. 

Tactics & Techniques

As stated above, this malware spreads through phishing emails and once it enters into the system, it hides itself with the help of various techniques which makes it difficult to detect it before any damage. After the successful breach, Agent Tesla extracts all the information related to search engines like login credentials, keystrokes, screenshots, etc. in order to compromise the users' accounts. It main targets are the industries related to energy, logistics, finance, government sector, etc.

Prevention

In order to mitigate the risks related to Agent Tesla, we can perform following steps:
  • Anti-Phishing Protection- As this malware attacks via phishing emails, we can apply anti-phishing solutions that can analyze as well as detect the malicious contents within an isolated environment.

  • Content Disarm & Reconstruction (CDR)- This one basically filters or sanitize the files before allowing them to enter the user's inbox, thus protecting it against any malfunctions.

  • Endpoint Detection & Response- Since it is very difficult to identify this malware before it reveal itself, the endpoint security solutions can easily destroy the malware once it is revealed.

  • Multi-Factor Authentication (MFA)- As we all know by now, MFA makes it nearly impossible for threat actors to make use of any stolen credentials. 

  • Zero Trust Access Management- This one can successfully limit the damage done by the malware via an infected account.

  • User Behavior Monitoring- Regular monitoring of an account's behavior will significantly help in identifying a compromised user account.

  • Employee Security Training- It is very crucial to make cybersecurity awareness training essential for the employees to identify and respond accordingly during a breach situation in order to minimize the risks related to these attacks. 












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