Penetration Testing

Desktop Application Penetration Test

Once your application is installed, whoever uses it has the whole client in their hands. They can decompile it, read what it saves on disk and intercept the traffic it sends to your servers, then change it to get around the checks it enforces. We test your desktop applications the same way.

REQUEST THIS SERVICE
Why choose us

We are an Italian security company focused on cloud and application security. Our services draw on years of penetration testing, consulting, training and research.

Solid methodology built by experts
International certifications
Fast-growing security company
MORE ABOUT US

FAQ

Desktop application penetration testing: common questions

What clients usually ask us before we test a desktop application.

What do you need from us?

The installer or build of the version you want tested, at least one account for each role and a test back-end we can reach, with our IP addresses allowlisted if needed. If the application only runs in your environment, such as Citrix, a VDI or a kiosk, we work remotely, through access you give us, a virtual machine or an image of the system.

Do you need our source code?

No. We work on the installed application, which is also what an attacker has. If you want to go further, a secure code review of the client and its back-end finds issues that testing the running application alone can miss.

Our application is only used inside the company. Is a test still worth it?

Yes, because anyone who can run it has the client in hand: an employee looking for more access than their role allows, or an attacker who has taken over a single workstation. Internal applications also tend to trust their users more, and some connect straight to a database with the credentials stored in the client.

Our application is built with Electron. Is a web application test enough?

No. An Electron application is a web application with access to the operating system: with the wrong settings, a cross-site scripting flaw that in a browser stays inside the page can run commands on the user's computer. So besides the web part, we check the settings in the Electron security checklist, such as Node.js integration, context isolation and the sandbox.