Volt Typhoon

By Ashwin Venugopal -

 







About

Volt Typhoon is a Chinese-backed cyber espionage group, targeting legacy Cisco devices and expanded its attack infrastructure in a sophisticated and systematic campaign. As of now, it has compromised about 30% of the Cisco legacy routers on a SOHO botnet, used by multiple threat groups.

They targets the critical infrastructure via the exploitation of the target's vulnerabilities and insert themselves into the victims' devices to take control of everything.

Targets

Volt Typhoon has successfully entered into the US critical infrastructure organizations, thus indicating a potential future disruption. The targeted attacks includes water utilities, power suppliers, transportation, and communication systems of the countries like the US, UK, and Australia. 

How does Volt Typhoon works?

The initial access is achieved via internet-facing Fortinet FortiGuard Devices. They leverage any type of privileges offered by these devices to extract credentials to an Active Directory account and then try to authenticate the other devices on the network with the help of those credentials. 

After that, Volt Typhoon proxies all its network traffic to its targets through compromised SOHO network edge devices. Proxying of these devices allows them to enhance the stealth of their operations and lowers overhead costs for acquiring infrastructure. 

Volt Typhoon rarely uses malware in their post-compromise activity. They generally rely on living-off-the-land commands to find information, discover additional devices on the network, and exfiltrate data.

Protection

  • Owners of the network edge devices should ensure that management interfaces are not exposed to the public internet to reduce their attack surface.

  • Enforce strong multi-factor authentication (MFA) policies with the help of hardware security keys or Microsoft Authenticator. 

  • Reduce the attack surface by turning on the attack surface reduction rules to block or audit some observed activity associated with this threat.

  • Turn-on cloud-delivered protection in Microsoft Defender Antivirus to cover rapidly evolving attacker tools, techniques, and behaviors.

  • Run Endpoint Detection and Response (EDR) in block mode. In this way, Microsoft Defender for Endpoint can block malicious artifacts that are detected post-compromise.

















































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