Thick Client Penetration Testing

Flow chart of the Thick Client Application engagement, 6 phases in order, each one selectable. Phase 1, Scoping and Rules of Engagement. We agree the application, installers, test accounts and backend services in scope, and set up a controlled test machine. Activities: Confirm the app, installers and backends in scope; Provision test accounts and licences; Set up a controlled test machine; Agree testing windows and contacts. Hands over Signed Rules of Engagement. Phase 2, Reconnaissance and Binary Analysis. We inspect the installed files, configuration and binaries, decompile managed code and look for secrets, weak crypto and unsafe local storage. Activities: Inspect installed files and configuration; Decompile managed .NET and Java code; Hunt for hardcoded secrets and weak crypto; Review local data storage. Hands over Binary Analysis Findings. Phase 3, Traffic and Protocol Analysis. We intercept and decode the client-to-server traffic, including proprietary and non-HTTP protocols, to find weak transport and trust in client input. Activities: Intercept client-to-server traffic; Decode proprietary and non-HTTP protocols; Assess transport security; Probe server trust in client input. Hands over Protocol Analysis Findings. Phase 4, Manual Exploitation. We tamper with the binary, patch runtime behaviour and manipulate memory to bypass client-side controls and licensing checks. Activities: Patch the binary to alter behaviour; Manipulate memory at runtime; Bypass client-side security controls; Defeat licensing and integrity checks. Hands over Proven Client-Side Findings. Phase 5, Backend and Impact. We test the server the client trusts and show how client-side tampering translates into real impact on data and other users. Activities: Test the backend services the client trusts; Turn client tampering into server-side impact; Map exposed data and affected users; Assess combined business impact. Hands over Impact and Risk Assessment. Phase 6, Reporting and Verified Retest. You get a report with proof of concept and clear fixes, and we retest once you remediate to confirm each issue is closed. Activities: Document findings with proof of concept; Produce an executive summary; Walk your team through the results; Retest fixes and confirm closure. Hands over Final Report and Verified Retest. Each phase begins from the artefact the phase before it produced.