ELECTRUM: A SANDWORM APT

By Ashwin Venugopal -

 





Introduction

ELECTRUM has been associated with the SANDSTORM Advanced Persistent Threat. It was responsible for the power outage in, Kiev, Ukraine, in December 2016. They blacked out some part of the city's electricity for about an hour. This was done via ICS malware CRASHOVERRIDE. They have been active since 2009 and mostly targets Ukraine. 

Characteristics

ELECTRUM has entered into both developmental and operational role after the power outage incident. It does not depend on exploits or zero-day vulnerabilities. However, it leverages common exploitation behaviors and methodology. It also uses Microsoft SQL database servers as gateways to bridge both the industrial and business control networks. In this way, they can successfully compromise industrial control systems where they can use stolen credentials to execute code. 

ELECTRUM is still active but evidence shows that it is not targeting Ukraine exclusively. It is considered as one of the most competitive and sophisticated threat activity groups present in the ICS industry. 

Detection & Mitigation

Some of the prevention and mitigation techniques are as follows:
  • Network and host hardening to reduce exposure to threats.
  • Vulnerability management to reduce the security weakness in the exposed services. 
  • Using strong data encryption will reduce its usefulness even if it is stolen.
  • Make use of Data Loss Prevention (DLP) and Endpoint Security to protect the sensitive data from leaking via the network or end-user devices. 
  • Use network and application-level firewalls to stop unwanted traffic from entering.

Conclusion

Nowadays, ELECTRUM is also targeting the organizations other than Ukraine's. It extensively uses common exploitation methods to attack their victims and compromise their network. Hence, a strong prevention strategy should be applied to prevent these attacks from compromising a network. 




To know more, read- ELECTRUM















































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