Storm-1133: A Gaza-based Threat Actor

By Ashwin Venugopal -

 






Introduction

Recently, Microsoft has unveiled a Gaza-based threat actor, primarily targeting the private-sector organizations of Israel. There main focus is on energy, defense, and telecommunications companies. This group works in the interests of Hamas, a Sunni militant organization, and attacks the organizations deemed hostile towards Hamas. They have also targeted Fatah, a Palestinian political party, located in the West Bank.

Characteristics

The attack strategy of Storm-1133 includes social engineering and the creation of fake profiles on LinkedIn. These fake profiles pose as the human resource managers, project coordinators, and software developers from Israel. They initiate communication with Israeli employees of various organizations by sending phishing messages, conducting reconnaissance, and then deliver malware. They also try to intrude third-party organizations with the help of links known to the employees of Israel. Through this intrusion, they try to create the backdoors and configure the command-and-control (C2) infrastructure hosted on Google Drive. This allows them to dynamically update their infrastructure.

Since Israeli-Palestinian conflicts, their attacks have shifted from destructive and disruptive operations to the long-term cyber espionage programs. 

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, Storm-1133 is mainly targeting organizations that are considered as hostile towards Hamas. They have extensively used phishing messages to lure their victims and compromise their network. Hence, a strong prevention strategy should be applied to prevent these attacks from compromising a network. 















































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