Case Study HUSPI: Security Assessment of Frontend and Backend Servers in Docker Containers

Client:

HUSPI — a software development company for healthcare and financial organizations

Industry:

Healthcare

Focus:

Protection of personal, medical, and corporate data within the company’s digital products

Main challenge:

Security assessment of servers in Docker containers to prevent unauthorized access and data leaks

Market:

Ukraine, Poland, Germany (international segment)

Services provided:

Comprehensive white-box penetration testing of two servers (frontend and backend) in Docker, including a full assessment of containerized environments and network interactions.

Key Takeaways

Conducted a white-box penetration test of servers and Docker containers

Reduced the risk of data leaks through inter-container interaction by 80–90%

Identified 9 vulnerabilities, including 2 critical ones (database access from other machines)

Provided a detailed report with recommendations for strengthening the infrastructure

Critical vulnerabilities were eliminated within 24 hours of reporting

24 hours

to fix the vulnerability

vulnerabilities detected

80–90%

lower risk of data breaches

Case Study HUSPI: Security Assessment of Frontend and Backend Servers in Docker Containers

May 10, 2025

14 min

Do Docker containers really guarantee isolation and security? The IT company HUSPI turned to Datami for a scheduled penetration test of its internal infrastructure. We performed white-box testing of Docker servers, identified critical vulnerabilities, and

HUSPI is a mid-sized IT company registered in Poland that develops software for the healthcare, financial, and real estate sectors. Thousands of users work with its web platforms and APIs every day.

HUSPI operates in regulated industries and complies with international security standards (including GDPR), making the protection of personal, medical, and corporate data critically important for the company.

Objectives and challenges

HUSPI initiated a scheduled security assessment due to the risks of unauthorized access to internal systems and potential data leaks from the containerized environment.

The goal of the project was to identify vulnerabilities and test the security of the internal infrastructure to ensure compliance with international security standards, including GDPR and healthcare requirements.

Conduct a white-box penetration test of internal servers and containers (frontend and backend).
Assess the isolation of Docker environments and network interactions, including the risks of container breakout.
Identify vulnerabilities, assess risks, and prepare a detailed report with recommendations.

Penetration testing

White-box testing of frontend and backend containers

Vulnerability detection

Identification and analysis of risks within the internal infrastructure

Reporting and recommendations

Detailed report on threats and security improvements

Datami methodology: HUSPI security assessment

Our approach

Datami assessed HUSPI’s internal infrastructure, including frontend and backend servers in Docker containers.

The primary method used was a white-box penetration test: the team had access to technical information for the most in-depth analysis.

We combined manual and automated testing methods, analyzed configurations, and examined inter-container interactions. SSH access enabled work in the live environment.

Despite a limited budget, the team identified critical vulnerabilities and provided effective recommendations.

White-box

The testing was carried out with full access to the internal infrastructure, allowing the team to simulate the most likely attack vectors and obtain an objective picture of the security posture.

Main project stages and solutions

During the project, Datami used specific scenarios to test Docker container isolation and adapted the workflow in response to access delays.

Analysis of the key components of the container environment enabled the team to cover priority risk areas and respond promptly to client requests.

Preparation:

Analysis and clarification of technical details, test planning, and identification of critical areas for assessment.
Penetration testing:

White-box pentest of two Docker servers, combining manual and automated approaches to detect vulnerabilities in network interactions and container isolation.
Analysis and reporting:

Preparation of a detailed report describing the identified risks, recommendations for remediation, and measures to improve security.

Results and recommendations

At the start of the project, HUSPI’s internal infrastructure faced high risks: lack of container audits and weak network segmentation posed threats to sensitive data.

During the white-box pentest, Datami discovered 9 vulnerabilities: 2 critical (including database access via inter-container communication), 3 medium, and 4 low.

HUSPI received clear recommendations to strengthen cybersecurity:

Regular audits of Docker configurations
Restriction of inter-container access
Implementation of a Zero Trust approach and updated logging

After implementing the recommendations, the risk level was reduced to medium: the likelihood of data loss due to inter-container communication decreased by 80–90%, helping to avoid over $50,000 in potential financial losses.

The project was completed in 2 weeks instead of the standard 3–4. Critical vulnerabilities were fixed by the client within 24 hours.

Key project outcomes

With Datami’s help, HUSPI improved its cybersecurity in just 2 weeks: the company gained a clear picture of potential risks, received an actionable roadmap, and strengthened its GDPR compliance. All project objectives were achieved.

This case proves that even companies specializing in complex digital solutions need regular penetration testing to avoid financial, legal, and reputational losses.

Aspect

Before the project

After implementation

Security status

High risk due to lack of container audits

Risk level reduced, 9 vulnerabilities found

Critical vulnerabilities

Possible unauthorized access to databases

2 critical issues found, fixed within 24 hours

Account compromise

Potential due to network isolation issues

Risk reduced after configuration improvements

Security compliance

Partial compliance with policies and GDPR

Improved alignment with standards

Timeline

Typically 3–4 weeks

Project completed in 2 weeks

Case Study HIDEEZ: Security Testing of Encryption and Authentication Before Product Release

Conducted a white-box pentest of cryptography and authentication mechanisms
Identified 6 vulnerabilities: 1 critical, 2 medium, 3 low

Services provided:

White-box penetration testing with source code analysis of encryption and authentication modules; static code analysis (SAST) and dynamic application security testing (DAST), aligned with OWASP ASVS best practices

May 10, 2025

Case Study: Comprehensive Security Assessment for a Large Financial Institution

Pentest and Code Review were conducted for digital services
106 vulnerabilities were identified, including a DoS attack threat targeting the call center.

Services provided:

Security Code Review, Penetration Testing (Black-box and Gray-box) of web portals, mobile applications, APIs, POS terminals, and parts of the internal network;

May 10, 2025

Case Study HUSPI: Security Assessment of Frontend and Backend Servers in Docker Containers

Conducted a white-box penetration test of servers and Docker containers
Reduced the risk of data leaks through inter-container interaction by 80–90%

Services provided:

Comprehensive white-box penetration testing of two servers (frontend and backend) in Docker, including a full assessment of containerized environments and network interactions.

May 10, 2025

Back to all cases

Datami articles

Internal Network Penetration Testing: Identify Vulnerabilities Before Attackers Do

Oleksandr Filipov: Security engineer at Datami, author of articles

Internal Network Penetration Testing: Identify Vulnerabilities Before Attackers Do

Learn what an Internal Network Penetration Test is and how to prepare for it. Discover the meaning, stages, and challenges of conducting an Internal Network Pen Testing.

May 8, 2025

Network Penetration Testing: What Is It?

Oleksandr Filipov: Security engineer at Datami, author of articles

Network Penetration Testing: What Is It?

What is network penetration testing? Learn more about the approaches and types of network pentests, the key stages, and the outcomes of a network penetration test.

May 1, 2025

Cybersecurity in healthcare: why hospitals have become a favorite target for hackers

Oleksandr Filipov: Security engineer at Datami, author of articles

Cybersecurity in healthcare: why hospitals have become a favorite target for hackers

Cybersecurity in healthcare is at risk: hospitals face more cyberattacks than banks. Learn how to protect medical data with expert tips from Datami.

Apr 24, 2025

Show all articles

On this page you will learn what cookies are and how and when we use them. Definition of the term Cookies Cookies are pieces of data that a web server generates and that a website stores on your user device (computer, smartphone, tablet, etc.). Each website or third-party service sends cookies to the browser installed on your device only if your browser allows it. This is possible if you have not set any restrictions in your browser settings to save cookies. Browsers are a very well thought out technology. They protect personal data and allow websites to access only cookies that were previously sent to them. Cookies are divided into: session cookies. They are stored in the memory of the browser only during your session, after leaving the site immediately removed. permanent. They are stored in the memory of the browser for a long time. Definition of the term “browser” A browser is an application for browsing websites. The most popular browsers are Chrome, Internet Explorer, Firefox and Safari. All listed browsers are safe. In the settings of these browsers, cookies can be easily disabled, as well as change the settings of their work. You can: accept all cookies; ask the browser to notify when cookies are used; do not accept cookies. Cookies on ak1-3.com.ua and how we use them We use cookies to: our site is more functional; to understand how you navigate on the site, what content you consume better, to develop the content strategy of the site; understand how many visits to the site were per day, month, year. Analyze the geographical identity of users of the site, the number of repeated visits and other data. Cookies that we use on our site. Third-party cookies. The buttons of social networks, videos and some other services of our site are the property of other companies. These companies may also use cookies on your device if you have used them on our site or have been previously registered with them. The privacy policy of the use of personal data by these services can be found on the websites of these services. Blocking cookies All browsers allow simple actions to disable cookies. To disable them, you must go to your browser settings and find cookies in them. But we must remember that blocking cookies can have a negative impact on the performance of many websites. How to delete files You can also always delete cookies that are stored on your computer. To do this, follow the instructions of your browser Again, deleting cookies can have a negative effect on the performance of many websites.