Close today

Go to Top

Go to Top

Thumbnail for Solving Security Blind Spots
Thumbnail for Solving Security Blind Spots

Security Insights

Security Insights

Security Insights

What do security pros fear most today? Common factors and cures for breaches

What do security pros fear most today? Common factors and cures for breaches

What do security pros fear most today? Common factors and cures for breaches

EnkiWhiteHat

EnkiWhiteHat

Content

Content

Content

"Regular inspections were conducted, but basic threat items like web shells were excluded. The details regarding server or system operation and decommissioning were unclear. Equipment with no longer supported patch updates was neglected."

The Ministry of Science and ICT has documented this in the incident report of the security breach that shook the nation at our leading telecom company in April 2025. 

This pattern is not an issue of just one company. Similar issues are recurring in major security breaches that occurred this year. Security audits were performed, but only in formality, and vulnerability patches are delayed for 'later.'

In 2025, the survey conducted by NKI White Hat at the ISEC and CSK security conferences with 454 security practitioners reveals the essence of this problem. 37% of respondents identified 'unpatched vulnerabilities' as the biggest security threat, and while 60% performed regular penetration testing, many were limited to checklist-based formal reviews.

Even incidents that large corporations couldn't prevent indicate that our company could be the next target.

Let's explore the 'actual issues on the ground' revealed by 454 security practitioners and the 'effective response strategies' suggested by white hackers.



The ransomware that security professionals fear the most

랜섬웨어 설문조사 결과

What do domestic security officers worry about the most? According to our own survey, 38% of respondents identified ransomware as their main concern. Ransomware is malicious software that encrypts valuable data such as company files, documents, and images, then demands a ransom for their access return. Thus, when employees hear that their company is hit by ransomware, they feel stifled as it leads directly to 'operational paralysis' and 'customer data theft.' 

In fact, referring to KISA's "2024 Second Half Cyber Threat Trend Report," the damage from ransomware has increased about twofold since 2020. Particularly, there are clear statistics indicating that 94% of the victims are medium and small businesses, which have more difficulty in investing in security, so the worry about ransomware among practitioners is not a vague concern.

The Start of Hacking: 'Unpatched Vulnerabilities'

보안위협 우려 원인

So where does this anxiety about ransomware start for security personnel? 

37% of survey respondents identified 'unpatched vulnerabilities' as the biggest cause. While there is certainly fear of zero-day attacks, many are more concerned about breaches that occur because patches are available but not yet applied to systems. The delay of essential security updates due to work schedules, extensive testing burdens, and staff shortages is a reality that many responsible personnel resonate with.

Just as much as these concerns weigh on their minds, such security gaps become prime targets for attackers. Attackers can leverage vulnerabilities with publicly available PoCs (Proof of Concept) to easily infiltrate systems with minimal effort and time.

The Reality of Formal Penetration Testing

모의해킹 진행여부 확인

According to the survey results, 60% of companies conduct regular penetration tests, constituting a majority. While this seems positive on the surface, many of these tests are formal checks based on checklists. Such formal inspections often overlook the actual attacker's infiltration paths, leading to effectiveness issues. This happens because they fail to completely identify the security blind spots of the company that only attackers might know. 

Therefore, penetration testing and vulnerability assessments should not merely be a 'certification process' but rather a turning point for discovering the actual risks to our systems. It is advisable to recall the purpose of the assessment and execute the checks in a way that closely mimics real attackers.

Limits of Traditional Penetration Testing and Vulnerability Assessment

모의해킹 및 취약점 점검 불편한점

The biggest barrier to conducting vulnerability assessments and penetration testing more frequently and thoroughly was not technical performance but rather 'procedural inefficiency.' In the survey, 40% of respondents said 'the preparation procedures (draft, project adoption, etc.) are cumbersome.' Every time a quick assessment is needed, they have to go through complex internal approval and reporting processes, and for large-scale assessments, it was mostly done by posting business announcements.

7 Steps of Cyber Attacks Security Managers Must Know (Web Service Vulnerability Examples)

To prepare for security threats like the above, you need to understand how attackers create breaches. Typically, an attacker goes through a seven-step process to find a company's 'loophole' and achieve the final goal of data theft. Let's explore this process in detail using penetration through web service vulnerabilities as an example.

사이버 공격 과정 7단계

1) Initial Access

This is the first step of the attack. Penetration begins in various ways such as accessing exposed management pages, exploiting vulnerabilities that have a publicly available PoC (Proof of Concept), or exploiting web service vulnerabilities. At this stage, the attacker finds attack vectors in publicly exposed web services and gains a foothold in the system by uploading files (web shells) or executing remote commands.

  • Example: The attacker exploits a vulnerability in the 1:1 consultation feature of the web service where file extension checks are insufficient, uploads a malicious file (web shell), and prepares to execute commands.

2) Privilege Escalation

After initial access, the attacker needs to expand control beyond the limited authority they initially acquire. Methods include searching for credential-related files and exploiting LPE (Local Privilege Escalation) vulnerabilities with publicly available PoCs. Even if privilege escalation is not immediately possible, the attacker can proceed to the next step.

  • Example: By executing commands through the uploaded web shell, the attacker locates credential-related files like configuration files on the server and secures root access.

3) Malware Installation and Persistence

Next, the attacker sets up an environment to maintain access, even if existing vulnerabilities are patched or the system is rebooted. They accomplish this by creating new accounts, enabling SSH, generating auto-executing services for malware, or installing backdoors and rootkits to establish 'secret passages.'

  • Example: With root access, the attacker creates a new admin account and configures remote access (SSH) so they can access the system at any time.

4) Internal Reconnaissance

After securing continuous access to the system, it's time to look internally. The attacker surveys internal assets (those not accessible externally) connected to the compromised assets by exploring accessible internal assets, conducting port scans, and searching for vulnerable services to identify the next penetration points.

  • Example: The attacker identifies the internal IP range of the occupied assets, finds the reachable IPs, conducts port scans, and determines which services are running on those IPs.

5) Lateral Movement

Using the 'map' obtained from reconnaissance, the attacker attempts to penetrate other assets like the DMZ and internal network where key data might reside. Penetration methods include using acquired credentials for access, accessing exposed internal management pages, and exploiting vulnerabilities.

  • Example: When accessing the asset running the web service, the internal server management panel is fully exposed, allowing the attacker easy access to the internal systems.

6) Privilege Escalation and Persistence (Replication)

In an effort to get closer to the final target (e.g., DB server, backup server), the attacker repeats the steps of privilege escalation and persistence on the compromised assets. This gradually increases their control over the system.

  • Example: By accessing critical servers identified through the internal server management panel, the attacker escalates privileges and installs additional malware to recreate the persistence environment.

7) Goal Achievement

Finally, the attacker reaches the final objective and achieves their goal. At this stage, the company faces the most feared consequences, such as ransomware infections or theft of critical information.

  • Example: The attacker successfully accesses the DB server and steals a large amount of sensitive personal information, such as patient data and medical records.

Four Essential Security Tips for Ethical Hackers

To neutralize such deeply penetrating attack scenarios, simply adding a firewall or another security solution is not enough. Therefore, the following four defense strategies from an attacker's perspective must be implemented.

화이트해커의 4가지 핵심권고사항

1) Avoid Using Pirated Software

Strictly banning pirated software (so-called 'cracked' versions) in the enterprise is the most basic line of defense. However, in reality, as software costs are not cheap, many small and medium-sized enterprises do not always purchase and use genuine software. Yet, from document processors to specialized domain software, we cannot ignore that pirated files are highly likely to contain malware. Since such pirated software serves as a key entry path into an internal corporate network, clear internal policies must be established and followed to ensure all employees use only genuine software to protect valuable assets.

2) Build a Solid Backup Strategy

Ransomware has now evolved beyond simple file encryption to include data exfiltration or to target file theft directly. Accordingly, backup strategies must be designed to cover 'data breach response' beyond mere 'recovery.'

■ The 3-2-1-1-0 Rule

While the 3-2-1 rule is generally recommended for backups, we advise adopting a 3-2-1-1-0 strategy for stronger security.
- 3 copies of data
- 2 different media types
- 1 offsite location
- 1 immutable/offline copy
- 0 errors verified by regular recovery tests
In addition, to secure the backup system itself, the following measures are essential:
Backup server accounts must be completely isolated from production network accounts, strictly require MFA (Multi-Factor Authentication), and use the principle of least privilege.

  • Offline Management: Account credentials must not be saved in files but managed through offline methods.

  • Network Segregation: To prevent the backup server from being infected with malware, it must be managed in a network fully segregated from other assets.

  • Sensitive File Encryption: Considering potential leaks, sensitive files should be encrypted beforehand (e.g., password-protected zip folders) for management.

3) Minimize External Exposure of Unnecessary Assets

Paths through which attackers can attempt initial penetration must be fundamentally blocked. This means systematically managing the attack surfaces that an attacker might access. The key is minimizing the external exposure of assets that are unnecessary or poorly managed. Additionally, keep the following measures in mind for implementation:
Immediate Block & Access Control: Deprecated services, inactive assets, or admin panels must have external access blocked immediately upon discovery. If discovered, strictly tightening access control is critical.
Avoid Default Ports like SSH, RDP: Using default ports (e.g., SSH, RDP, etc.) should be avoided. If possible, disable these services, or if necessary, enforce strict access control to reduce unnecessary attack surfaces.

4) Run Penetration Tests Regularly

Penetration testing must be conducted regularly not only when launching new services but also on existing services. This involves applying real-world attack scenarios through an internal security team or an external professional agency. Through this, you should lower attack risks preemptively by identifying and patching potential vulnerabilities in advance. This is especially vital since the more familiar a system feels, the more likely you are to overlook existing vulnerabilities.

Enki WhiteHat's offer

Enki WhiteHat's OFFen Platform is designed to realistically solve these practical problems.

Key Values and Features Provided by the OFFen Platform

offen 대시보드

The OFFen platform offers key features that innovatively reduce administrative burdens while maximizing the real value of inspections as follows.

  1. Simple Request and Approval Workflow:

    • OFFen, as a subscription product, reduces the hassle of drafting and approval procedures, allowing the person in charge to request inspections with just a few clicks. It allows requests for various forms of inspections like Red Team, ASM, Offensive PT, Checklist PT to be made as needed, enhancing the tightness of vulnerability management.

  2. Real-time Attack Surface Visibility:

    • Domains, IPs, and cloud resources exposed externally are automatically collected and categorized through Enki White Hat's advanced ASM engine. This allows a clear view of Shadow IT, the hidden security blind spots. Additionally, the credibility of the collected assets is meticulously judged so that non-company related assets can be precisely classified. This allows for a clear identification of only the truly risky assets susceptible to attacks.

  3. Seamless Collaboration with Pentesters:

    • Many have experienced hesitance in asking simple questions to pentesters during a project. Now, you can freely question issues derived through commenting, lounge features. Moreover, during project progress, it's possible to receive the pentester's inspection schedule for transparent management.

  4. Simple Implementation Check:

    • Based on a created POC (Proof of Concept), you can conduct self-implementation checks with a one-click button. Furthermore, you can continuously request implementation checks from pentesters until no further vulnerabilities are detected.

Expected Effects from Introducing OFFen

Through the OFFen platform, companies can anticipate the following tangible security outcomes.

  • Reduced Administrative Burden via Subscription → Increase in Breach Prevention Rate
    With the subscription service, projects commence through purchased credits, greatly reducing cumbersome processes (proposals, approvals, etc.) and minimizing administrative burdens. As a result, it enables simultaneous securing of the inspection cycle (frequency) and depth, ultimately greatly increasing the breach prevention rate.

  • Accumulated Project History → Strengthened Internal Security Capability
    The accumulated vulnerability inspection project history within the OFFen service allows for smooth handovers even when there are changes in personnel. Moreover, the close communication established through multiple projects with white hackers complements the vulnerabilities of the internal blue team, practically enhancing security capabilities.

  • Combination of ASM and PTaaS → Integrated Security Management Possible
    Beyond managing the attack surface exposed to attackers (ASM), it is possible to manage penetration testing (PTaaS) based on these vulnerabilities from a single service. Thus, it realizes the most proactive and efficient integrated security from an attacker's perspective.

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

Subscribe

Find this content useful?
Subscribe to the Enki Letter!

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.