Mendix Pentesting
A standard pentest can miss what makes Mendix different. We target vulnerabilities specific to the platform, test against the weaknesses we encounter most often in Mendix applications and uncover what an attacker can actually exploit.
Low-code doesn't solve everything
Mendix makes it easier to build and move fast, but low-code doesn’t remove the security risks developers and security teams need to manage.
Developers build production apps without a security background
Mendix lowers the barrier to building software, but not every developer is trained to think like an attacker. Security mistakes can easily become part of an application without anyone noticing.
Your dependencies keep changing
Marketplace modules depend on other components and libraries, allowing new vulnerabilities to enter your Mendix application. Updates to functionality, libraries, APIs and SSO integrations can introduce new security risks and configuration errors.
Your Mendix app is going live. But has it been tested?
A late-stage pentest may uncover findings that affect planning, risk acceptance or the release.
AI adds a new attack surface
AI agents are becoming part of Mendix applications, bringing new behaviour, data flows and attack paths with them. The question is whether your security approach is keeping up.
How we put your security to the test
Our approach goes beyond a standard pentest. Drawing on more then a decade of experience with Mendix, we developed a Top 10 of Mendix-specific vulnerabilities that we test every application against, examining how an attacker could exploit roles, entities, microflows, integrations and custom functionality.
Define what you want to test
The Mendix expert defines the scope, objectives, goals and planning together with your team. We document these in a scope document, so your organisation knows what we will attack, how we will test it and what is off limits.
Prepare for the pentest
Before the pentest begins, we make sure everything is ready for testing. We verify access, test accounts, environments, potential escalation paths, and technical requirements with your team, preventing unnecessary delays and keeping the available test time focused on what matters: finding vulnerabilities.
Identify vulnerabilities
Our pentesters search within the agreed scope for vulnerabilities, Mendix-specific risks and weaknesses in the application’s business logic. They validate their findings and investigate what an attacker could achieve by exploiting them, while the Lead Pentester remains your dedicated point of contact and keeps you updated throughout the test.
Turn findings into insight
Our pentesters compiles the findings, their impact and recommendations into a clear pentest report. An independent pentester reviews the report for quality and accuracy, giving you a reliable basis for remediation and security decisions.
Debrief and define next steps
After the pentest, we walk through the report together and discuss the findings in detail. We provide strategic advice on remediation, giving your team a clear understanding of the findings and how to address them.
What you get from us
After every pentest, you receive one comprehensive report that translates our technical findings into concrete risks and actions for both technical teams and management.
Technical report
Management summary
Risk prioritization
Mitigation advice
Your primary point of contact
“Finding vulnerabilities is only part of the picture. Understanding what can actually be exploited shows where the real risk lies.”
Dirk van Veen
Founder and Lead Pentester
Getest in de echte wereld
Zie wat er gebeurt wanneer onze hackers echte omgevingen op de proef stellen en na de eerste finding verder blijven graven.
PDF-generatie als aanvalspad naar server secrets | What The Hack
Een PDF-generator in een applicatie met gevoelige persoonsgegevens vormde een onverwacht aanvalspad.
Databasetoegang via Time-Based SQL Injection | What The Hack
Een geautomatiseerde scan signaleerde een mogelijke SQL-injectie in een applicatie met gevoelige persoonsgegevens, maar de finding moest nog handmatig worden gevalideerd.