Black Friday Our software, PenTest Project: Slate Enterprise at €53 instead of €173 per user a month, and Flint free for 12 months. Until 30 November. See the offer →
PenTest Hub logo

Desktop · Client-server · Installed software

Thick Client Penetration Testing

Desktop and client-server applications run on machines you do not fully control. We test what they store, how they talk to their servers and whether they can be used to take over the computer they run on.

  • Static and dynamic analysis
  • Client and server tested together
  • Local privilege escalation
Sample findings · Thick client testSample
CRITICALDatabase password hard-coded in the clientGives direct access to the production database
HIGHAny user can gain administrator rightsThe update service loads files from a writable folder
HIGHClient-side permission checks onlyHidden functions unlocked by editing memory
MEDIUMUnencrypted protocol to the application serverCredentials visible on the network
Each finding with evidence, a risk rating and a fixSample findings

In one sentence

What is thick client penetration testing?

Thick client penetration testing examines desktop and client-server applications, the data they keep on the computer, the protocols they use to reach their servers, and the services they install, to find weaknesses an attacker or a malicious user could exploit.

Unlike a web application, a thick client hands much of its logic to the user's machine. Anything it stores or checks locally can be read and changed, so we test with both static and dynamic techniques.

Typical thick clients

  • Trading, banking and finance desktop applications
  • Healthcare and laboratory software
  • Industrial and engineering tools
  • Line-of-business applications installed on employee laptops

Scope

What we test

The client, the machine it runs on, and the server it talks to.

Local data and secrets

Configuration files, caches, logs and the registry: credentials, keys and personal data left on the machine.

  • Config files
  • Credentials
  • Registry

Network traffic and protocols

How the client talks to its servers, including custom and legacy protocols, and what can be intercepted or replayed.

  • Custom protocols
  • Interception
  • Replay

Memory and runtime manipulation

Changing values and logic while the application runs, to bypass checks or unlock functions.

  • Memory editing
  • Runtime hooks
  • Logic bypass

Local privilege escalation

Installers, services, update mechanisms and file permissions that could give a user administrator rights.

  • Services
  • DLL loading
  • Updaters

Server-side checks

Whether the server enforces the rules, or trusts whatever the client sends.

  • Authorisation
  • Input validation
  • Trust

Authentication

Login, single sign-on integration and how sessions are kept and protected.

  • Login
  • SSO
  • Sessions

Approach

Testing approaches based on access

Choose how much you share with us. More context means deeper coverage in the same time.

No prior knowledge

Black box

We install the client as a normal user would and test it without further information.

Accounts and some context

Grey box

With test accounts and an overview of the architecture, we test the client and server in depth.

Full access

White box

With source code or design documents, we review how security is implemented as well.

Engagement

How we work with you

  1. Scope online

    Describe what you need in Flint, our scoping platform. Answer only the questions that apply.

  2. Proposal, signed online

    Effort, price and the statement of work are built from your answers.

  3. Ready for day one

    Authorisation, test accounts and rules of engagement are agreed before testing starts.

  4. Senior-led testing

    Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.

  5. Report and retest

    Your report is ready in Slate, our client portal, within 48 hours of testing ending.

What you receive

Everything stays in one place, in your own client portal.

  • A report in Slate within 48 hours of testing ending
  • Every finding with evidence, a risk rating and a fix
  • An executive summary for leadership
  • Retests you can request finding by finding
  • Downloads as PDF or Excel
  • Evidence you can hand to your auditors

Standards

Standards we test against

Aligned with the application security frameworks your teams use.

  • OWASP Top 10
  • CREST guidance
  • MITRE ATT&CK
  • CIS Benchmarks

FAQ

Frequently asked questions

Can't find yours? Ask a senior tester and we'll reply directly.

What is a thick client?
An application installed on a computer that does much of its work locally and talks to a server, unlike a web application that runs in the browser.
What do you need from us?
The installer, test accounts for each role, access to a test server and, ideally, a test machine that matches your standard build.
Do you test the server too?
Yes. Many serious findings come from servers that trust the client, so the server side is part of the test unless you exclude it.
Can you test legacy or custom protocols?
Yes. We analyse and test custom and legacy protocols as part of the network traffic review.
How long does it take?
It depends on the size of the application. We confirm the effort and dates in your statement of work before testing begins.
When will we receive the report?
Within 48 hours of testing ending, in Slate, our client portal.

Contact

Tell us what you need to test

A senior tester reads every message and replies directly.