Go to Top

Go to Top

The sure solution Software supply chain attacks
The sure solution Software supply chain attacks
The sure solution Software supply chain attacks
The sure solution Software supply chain attacks

Security Insights

Security Insights

Security Insights

Is there a security solution for software supply chain attacks? A response strategy from the attacker's perspective

Is there a security solution for software supply chain attacks? A response strategy from the attacker's perspective

Is there a security solution for software supply chain attacks? A response strategy from the attacker's perspective

EnkiWhiteHat

EnkiWhiteHat

Friday, November 29, 2024

Friday, November 29, 2024

Friday, November 29, 2024

Content

Content

Content

Introduction

Recently, we often encounter the term 'SW supply chain attack' in the news. We know something significant has occurred, but what exactly is the 'SW supply chain,' and why are so many people concerned? In this article, we aim to explore SW supply chain attacks and discuss how we can protect ourselves from such threats. While it may be a somewhat serious topic, we'll strive to make it as understandable and engaging as possible.


What is a SW supply chain?

The software supply chain includes all the stages and various elements involved in making and distributing software. Simply put, it refers to the entire journey of software reaching us. This includes developers, external libraries, packages, and even the distribution paths to deliver the software to the end user. Because each element of the supply chain is interconnected, a problem in any part can threaten the entire software, reminiscent of dominoes!

Rising SW supply chain attacks

There has been a sharp increase in attacks targeting the software supply chain in recent years. A prominent example is the 2020 SolarWinds incident. SolarWinds' network management software, Orion, was infected with malware by attackers, exposing numerous companies and government agencies using it to significant security threats. It was like handing over the keys to a thief.

  • SolarWinds Backdoor (2020.3)

  • MS Exchange Vulnerability Attack (2021.3)

  • CodeCov CI/CD Manipulation (2021.4)

  • Kaseya Remote Management Solution Hacking (2021.7)

  • Log4j Vulnerability Attack (2021.12)

  • PyTorch Malicious Package Registration (2022.12)

  • 3CX Malware Insertion (2023.3)

  • Inisafe Security Authentication Software (2023.3)

  • JetBrains Supply Chain Attack (2023.9)

  • Okta Supply Chain Attack (2023.10)

Another example is the NotPetya attack in 2017. Malicious code was secretly inserted during the update process of Ukrainian accounting software, causing massive global damage. Such attacks on the supply chain have extensive damage scopes, and once breached, they can have a significant impact.

Why it's difficult to prevent and respond to software supply chain attacks

There are several reasons why it is difficult to prevent, detect, and respond to software supply chain attacks. First, because numerous external libraries and modules are used in the software development process, it is not easy to completely control the entire supply chain. If there is malicious code hidden in the imported code from outside, it is also very difficult to identify it.

Additionally, it is always challenging to verify that software updates are being conducted properly. More than anything, attackers operate very cunningly and can remain dormant in the system for a long time before the security team notices. Ultimately, security is bound to become vulnerable at each stage of the supply chain, and this complexity and multi-staged nature provide opportunities for attackers.

As such, the traditional 'perimeter security' has limitations in responding to software supply chain attacks. Due to these limitations, the concepts of 'SBOM' (Software Bill of Materials), which is used to quickly identify and patch threats, and 'Zero Trust', which is contrary to perimeter security, have emerged.

However, there are several challenges associated with SBOMs. It is not easy to manage and operate SBOMs of numerous software, and there are limitations in verifying and applying the reliability of VDR and VEX. Also, there are problems such as difficulty in responding to zero-day vulnerabilities and being unable to respond to attacks due to incorrect settings and configurations.

In the case of zero trust, its actual implementation is very challenging. Transitioning from existing systems to zero trust requires identification and evaluation of each part, and setting the minimum standards for the level of additional authentication is a significant challenge. In this respect, the introduction of zero trust is also not an easy task.

The Need for Security Response from an Attacker's Perspective

Effectively responding to such sophisticated supply chain attacks requires more than just a defensive approach. Sometimes, it's necessary to think from the attacker's perspective. This means understanding how attackers might infiltrate and exploit the system. By doing so, we can anticipate and respond to which points in the supply chain they are likely to target and how they might infiltrate them in advance.

In the future, for corporate and organizational security, it will be essential to think from the attacker's point of view and understand how they can infiltrate and exploit the system. To this end, an approach that acts like an actual attacker is necessary, such as finding vulnerabilities in a corporate system through Penetration Testing. Penetration testing allows for a realistic assessment of an organization's security state by simulating various paths attackers might take.

Scenario-based supply chain attack training is also important. This training aims to practice how the internal security team can respond based on actual supply chain attack scenarios. Teams that are trained this way can respond more quickly and accurately in real attack situations. Just as a soccer team formulates strategies in pre-matches, it involves being well-prepared before the real deal.

Email APT (Advanced Persistent Threat) training cannot be overlooked. APT attacks often start with highly sophisticated phishing emails. Regular training exercises for internal staff to identify and respond to APT emails can neutralize attackers' initial attempts, no matter how cunningly they disguise their emails.

Software supply chain attacks are not just a single enterprise's problem. They are severe threats that can significantly impact all organizations using the software. Although protecting a complex, multi-layered supply chain perfectly is challenging, thinking and responding from an attacker's perspective can be the solution. By understanding the attackers and anticipating the points they are likely to target, a more robust and practical security system can be established.

There is a saying, 'The proof of the pudding is in the eating.' Similarly, in Eastern culture, we say '百聞不如一見, seeing once is better than hearing a hundred times.' The same holds true for security. Directly experiencing and experimenting is the way to truly grasp its value. Ultimately, we must stay one step ahead in this battle. When attackers come, we should already be waiting for them.

EnkiWhiteHat

EnkiWhiteHat

ENKI Whitehat
ENKI Whitehat

Offensive security experts delivering deeper security through an attacker's perspective.

Offensive security experts delivering deeper security through an attacker's perspective.

The Beginning of Flawless Security System, From the Expertise of the No.1 White Hacker

Prepare Before a Security Incident Occurs

The Beginning of Flawless Security System, From the Expertise of the No.1 White Hacker

Prepare Before a Security Incident Occurs

The Beginning of Flawless Security System, From the Expertise of the No.1 White Hacker

Prepare Before a Security Incident Occurs

Copyright © 2025. ENKI WhiteHat Co., Ltd. All rights reserved.

Copyright © 2025. ENKI WhiteHat Co., Ltd. All rights reserved.

Copyright © 2025. ENKI WhiteHat Co., Ltd. All rights reserved.