A VAPT report can run to a hundred pages and still leave you exposed. The difference between a useful test and an expensive PDF comes down to a few choices you make before the work starts: what gets tested, how, by whom, and what happens after the report lands.
The short answer
Pick a provider that agrees the scope in writing, tests by hand as well as with scanners, maps findings to the UAE rules you answer to, ranks what to fix first and re-tests once you have fixed it. Ask for a redacted sample report before you sign.
Start with the scope
Most weak VAPT engagements fail here. Decide what matters before anyone runs a tool.
- Applications Customer portals, internal web apps and mobile apps, especially anything that handles personal or payment data.
- APIs The endpoints behind your apps and integrations, where broken authorisation often hides.
- Networks Internet-facing systems first, then what an attacker could reach once inside.
- Cloud Identities, storage and configuration in AWS, Azure or Google Cloud.
- People Phishing simulations, if staff awareness is part of the risk you want to measure.
Eight questions to ask a VAPT provider
| Question | A good answer | A red flag |
|---|---|---|
| Who does the testing? | Named testers who test by hand | Automated tools only |
| Which method do you follow? | OWASP for web, mobile and APIs. PTES or NIST SP 800-115 for networks. | No method named |
| How do you rate severity? | CVSS, adjusted for business impact | The scanner's rating, unchanged |
| Can we see a sample report? | Yes, redacted | "Our reports are confidential" |
| Do you map findings to UAE rules? | Yes, to UAE IA, Dubai ISR, PCI DSS or ISO 27001 where they apply | A generic report only |
| How do you protect live systems? | Agreed test windows, rules of engagement and an emergency contact | No plan |
| Is re-testing part of the engagement? | Yes, once fixes are in | Not offered |
| How do you handle our data? | An NDA, secure handling and deletion of test data | No clear answer |
When a vulnerability assessment is enough
- Regular checks between full tests.
- Large estates where you need breadth first.
- Tracking whether known issues are getting fixed.
When you need a full penetration test
- Before an audit or a certification.
- Before a new application or platform goes live.
- For systems that hold personal, payment or sensitive data.
- After a major change to your network or cloud.
A sensible order of work
- Scope. Agree targets, test windows, rules of engagement and contacts in writing.
- Test. Scanning first, then manual testing that proves real impact.
- Report. A summary for leadership, a fix-first list for engineers.
- Fix. Your team closes the findings, starting with the highest business impact.
- Re-test. The provider confirms which findings are closed, so your evidence is complete.
Not sure which rules apply to you? Our UAE cybersecurity compliance checklist covers UAE IA, Dubai ISR, PDPL and ISO 27001.
Second pair of eyes
Want a VAPT that ends in fixes, not just findings?
We test web, mobile, APIs, networks and cloud, map every finding to the UAE rules you answer to, and re-test once your team has fixed them.
See our VAPT serviceExplore cybersecurity · talk to our security team



