Thick-Client & Wireless Testing
Thick-client penetration testing for the desktop applications your business runs on: trading, banking, ERP and custom in-house software on Windows, macOS and Linux. We test the application on the device, the data it stores and how it talks to your servers, then show you how to fix what we find.
- Windows, macOS and Linux apps
- Client, traffic and backend tested
- Free retest and attestation letter




- CREST-accredited testing partner, globally recognised standards

-
Desktop apps Windows, macOS, Linux
-
Local data Files, registry, memory
-
Traffic App to server calls
-
Free retest Plus an attestation letter
When do you need thick-client penetration testing?
Desktop applications often hold privileged access to core systems, yet are rarely tested. These are the moments to change that.
A regulator or auditor asks
MAS TRM or a client audit expects every critical application to be tested, not just the websites.
Custom or legacy software
An in-house or older application handles sensitive data and has never had a security test.
A new release or vendor product
You are rolling out a new desktop application or a major update to staff or customers.
Insider and endpoint risk
Staff, contractors or a compromised laptop could use the app to reach data they should not.
What is thick-client penetration testing?
Thick-client penetration testing is an authorised security test of an application installed on a user’s computer that talks to backend servers, such as a trading platform, banking terminal or ERP client. Testers examine the application itself, the data it keeps on the device and its communication with the server, then report what needs fixing and how.
Thick clients do much of their work on the device, so they can expose things a web application never would: passwords and keys stored locally, security checks that only happen in the client, and direct connections to databases or internal APIs. We test by hand as well as with tools, because most serious issues sit in how the application trusts its own user.
How it works
-
1
Analyse
Reverse engineer the app and its files.
-
2
Attack
Client, traffic and backend.
-
3
Fix
Developer-ready fixes, then retest.
What our thick-client testing covers
We follow OWASP guidance for desktop applications and test the places attackers look first.
Authentication and authorisation
Whether sign-in and permission checks happen on the server, or only in the client where they can be bypassed.
- Login bypass
- Role checks
- Licence checks
Local data storage
Passwords, keys, tokens and customer data left in files, the registry, logs or memory.
- Config files
- Registry
- Memory
Client-server communication
Unencrypted or tamperable traffic between the app and your servers, including replay attacks.
- HTTP and sockets
- SOAP and gRPC
- Replay
Backend APIs and databases
Services and direct database connections the client uses, called without the client in the way.
- Internal APIs
- SQL injection
- Exposed services
Binary and code analysis
Reverse engineering the application to find hard-coded secrets and hidden functions.
- Decompilation
- Hard-coded secrets
- Debug code
Operating system interaction
Ways the app could let an attacker run code or gain higher privileges on the computer.
- DLL hijacking
- File permissions
- Privilege escalation
How our thick-client penetration testing process works
Five steps from installer to retest.
-
01
Scope and quote
- You:
- Share the app, roles and backend.
- We:
- Send a fixed quote and plan.
-
02
Set-up and analysis
- You:
- Provide installers and test accounts.
- We:
- Install, map and reverse engineer.
-
03
Testing
- You:
- Keep the test backend up.
- We:
- Attack client, traffic and backend.
-
04
Report
- You:
- Join with your developers.
- We:
- Explain findings and fixes.
-
05
Retest
- You:
- Ship the fixes.
- We:
- Retest and attest.
Typical timeline: a quote within 24 hours, testing in 4 to 7 working days per application and your report 3 to 5 days later.
Get a thick-client pentest quoteWhat you receive
Findings your developers and IT team can act on, with proof of each issue.
- Executive summary Business risk in plain English for management.
- Technical findings Each issue risk-rated, with the component affected.
- Proof of concept Steps and evidence so your team can reproduce it.
- Fix guidance Developer and configuration advice for each finding.
- Walkthrough call Your developers talk to the testers.
- Retest letter Attestation for auditors and clients.
Standards and regulations we help you meet
-
OWASP
Testing aligned with OWASP guidance, including the OWASP Desktop App Security Top 10.
-
MAS TRM
Supports independent security testing of the critical applications financial institutions run.
-
PDPA
Shows reasonable security arrangements protect personal data stored and processed by the application.
We help you meet these requirements; certification itself is issued by the relevant body.
Why choose Genic Solutions for thick-client penetration testing
A Singapore team on your time zone
Your thick-client pentest is scoped, run and debriefed by people based here, who understand MAS TRM, PDPA and local procurement.
Ubi Techpark, Singapore
A CREST-accredited partner
Testing is delivered with a CREST-accredited partner, to the standard auditors, regulators and enterprise clients ask for by name.
CREST-accredited partner
Named testers
You know who is testing your systems before the work starts.
Named lead tester
A fixed quote within one working day
Send us the scope and get a fixed price, a test window and a report date, with no open-ended billing.
Quote within 24 hours
Free retest after you fix
Once your team has fixed the findings, we retest them and issue an attestation letter at no extra cost.
Retest included
Plain-English executive summary
Management gets a short summary of business risk; engineers get technical detail and step-by-step fixes.
Two audiences, one report
How much does thick-client penetration testing cost?
The price depends on the application and how much of the backend is in scope. You get a fixed quote before any work starts.
- Applications and platforms How many applications are in scope, and on which operating systems.
- Roles and complexity Testing across several user roles or complex business workflows takes longer.
- Backend in scope Whether the servers, APIs and databases the client uses are tested too.
- Retests and timing One free retest is included. On-site work or urgent start dates can change the price.
Thanks, .
A security advisor will contact you within one working day to arrange your free consultation.
Thick-client penetration testing FAQs
Still unsure? Ask us directly on a free call.
-
It is software installed on a user’s computer that does much of its processing locally and connects to backend servers, such as a trading terminal, ERP client or custom in-house tool. A web application, by contrast, runs in the browser.
-
Windows, macOS and Linux applications, including those built with .NET, Java, Electron, Python and C or C++.
-
Yes. Custom and older applications are often the most at risk because they were never tested. We offer black-box testing and, with access to source code, white-box testing.
-
No. We test in a test environment or in agreed windows, coordinated with your IT team, so live users are not disrupted.
-
Yes. Wireless testing, including rogue access points and Wi-Fi encryption, is part of our network penetration testing service.
Thanks, .
We will reply with a fixed thick-client pentest quote within one working day.