Request a Scope Review
Vendors Scope Regulators Evaluation Pricing Red Flags FAQ Request a Scope Review
Buyer's Guide · UAE 2026

Best Internal Penetration Testing Vendors in UAE

Last updated October 2026

The vendor who wins the proposal is rarely the one who conducts your test. This guide shows UAE buyers how to evaluate who actually runs the engagement, which regulator requires what, and what a compliant report must contain — before signing.

Penetration Testing Vendors in UAE — Named Shortlist

Ten firms deliver genuine internal penetration testing in the UAE in 2026. Our editor's pick is marked ★ — evaluated against the criteria in this guide: individual researcher credentials, AD exploitation depth, and published methodology. Use the shortlist to build your RFQ list, then apply the evaluation framework below to narrow it down.

Firm Internal Pentest Depth Accreditation Best For
Help AG On-site delivery; AD coverage within managed-security engagements DESC Cyber Force certified; e& / Etisalat-owned Large UAE enterprises wanting full MSSP; pentest as one service in a broad portfolio
Big-4 (Deloitte, KPMG, EY, PwC) Deep methodology; enterprise-scale delivery risk (juniors after kickoff) Big-4 internal credentials; variable CREST coverage G-SIB, sovereign entities requiring brand-name sign-off and high spend tolerance
pentest.ae Senior-led; AD exploitation with BloodHound; NESA/DFSA/VARA/CBUAE mapping; published CVEs Senior researchers; full UAE regulator mapping Regulated UAE enterprises and AI-first companies needing senior-led depth with UAE compliance mapping
ValueMentor CREST-accredited; structured internal PT methodology; audit-ready documentation CREST-accredited (verified crest-approved.org); PCI QSA; OSCP/CISSP staff Regulated fintech and healthcare needing CREST-methodology testing with auditor-ready reports
CyberGate Defense Strong UAE government and OT track record; Abu Dhabi presence Emirati-owned; UAE government track record Abu Dhabi government and OT/critical-infrastructure buyers requiring local ownership
DTS Solution / Beyon Cyber Internal network testing within GCC enterprise scope Established GCC enterprise practice UAE enterprise buyers seeking GCC-scale delivery with internal network capability
Wattlecorp Remote-first internal testing; NESA/ISR mapping; accessible pricing NESA/ISR/CREST-aligned SME and mid-market firms with defined budget and UAE compliance mapping requirement
eShield IT Compliance-focused; CBUAE/NESA/PDPL experience OSCP/CISSP/CEH; ISO 27001 LA UAE SMBs where web application compliance is the primary driver
Astra Security / Qualysec Platform-first (Astra); process-driven (Qualysec); remote-only PTaaS platform (Astra); CREST member (Qualysec) Startups and developer-led teams; UAE regulator mapping limited

Note on sourcing: firm profiles are compiled from public company information, published methodologies, and accreditation claims as of mid-2026. Always verify a provider's current accreditation status before signing — accreditation is point-in-time, not permanent.

Internal vs. External — Why the Distinction Matters

UAE regulators treat internal and external penetration testing as distinct obligations with separate scope, methodology, and filing requirements. An internal engagement is not a scanner pointed at internal IPs — it is credentialed Active Directory exploitation with lateral movement to domain admin.

Attribute Internal Pentest External Pentest
Scope Targets Active Directory, domain controllers, internal subnets, workstations, lateral movement paths Internet-facing systems, perimeter firewall, public web apps, DNS, email
Methodology PTES phases 1–7 + NIST SP 800-115; BloodHound AD enumeration, credential harvesting, lateral movement PTES phases 1–7; external recon, perimeter exploitation, web app testing
Regulatory Mandate NESA CII (annual, distinct cycle); DFSA (internal IT systems); VARA (internal infrastructure); CBUAE (Critical Functions) NESA CII (annual, distinct cycle); DFSA (internet-facing systems, at least annually)
UAE Price 2026 AED 55,000–180,000 (enterprise with AD) AED 25,000–100,000 (standard perimeter)
Delivery Model On-site or VPN-segmented with AD-credentialed access required Remote; no physical access needed

What an Internal Network Engagement Actually Involves

Internal network penetration testing follows PTES (Penetration Testing Execution Standard) and NIST SP 800-115 as the two binding methodology anchors. A vendor proposal that references both at phase level signals genuine methodology rather than marketing copy.

The six phases of a credible internal engagement:

  • 1Pre-engagement scoping — scope sheet defines IP ranges, domain controllers, excluded systems, and retest window
  • 2Internal reconnaissance — passive and active enumeration of hosts, services, and domain structure
  • 3Active Directory enumeration — BloodHound graph analysis maps all trust paths, privileged group memberships, and attack routes to domain admin
  • 4Exploitation — Kerberoasting extracts service account ticket hashes; Pass-the-Hash reuses NTLM credentials; DCSync replicates domain controller data
  • 5Lateral movement — researcher pivots from initial foothold toward crown-jewel systems (financial databases, backup servers, domain controllers)
  • 6Reporting — chained attack narrative documents each step from initial access to domain admin, with CVSS v3.1 per finding and regulator control mapping

A vendor that cannot explain BloodHound graph analysis or Pass-the-Hash in a pre-contract technical call is delivering scanner output, not an internal pentest.

UAE Regulator Obligations by Framework

Each UAE regulator imposes distinct internal penetration testing obligations. Collapsing them into a generic "UAE compliance" reference is the single largest gap in competitor content — and the most common reason reports fail audit review.

NESA
National Electronic Security Authority · ISR v2
Entity typeCII operators: banking, telecom, energy, water, transport, healthcare
FrequencyAnnual — both internal and external cycles as distinct obligations
Internal scopeAD, internal networks, critical systems required
IndependenceExplicitly prohibits testers with shared ownership to IT vendors
Report formatISR v2 control mapping per finding; executive summary for board filing
ISR v2 control mapping required
DFSA
Dubai Financial Services Authority · DIFC
Entity typeDIFC-licensed: banks, asset managers, insurance, payments
FrequencyAt least annually; after material infrastructure change
Internal scopeAll internal IT systems, networks, and controls required
IndependenceIndependent third-party required; internal team insufficient
Report formatDFSA control framework references; comprehensive VAPT evidence for desk review
DFSA cyber risk rules effective Jan 2024
VARA
Virtual Asset Regulatory Authority · Dubai
Entity typeVirtual Asset Service Providers (VASPs) licensed in Dubai
FrequencyRegularly and on VARA request; at least annual in practice
Internal scopeInternal network, critical servers, smart contract environments, Kubernetes clusters, admin panels
IndependenceQualified independent third-party auditors mandated
Report formatVARA Technology and Information Rulebook references; results available upon VARA request
Technology & Information Rulebook
CBUAE
Central Bank of the UAE
Entity typeLicensed banks, insurers, payment service providers
FrequencyPeriodic; mandated under Operational Risk Management Regulation C 1/2026 for Critical Functions
Internal scopeCritical Functions infrastructure; internal network for licensed banks
IndependenceIndependent third-party required; results presented to Board
Report formatOperational risk stress-test framing; board-level executive summary
Regulation C 1/2026

The Seven Questions to Ask Before Signing

These questions separate internal-pentest-capable vendors from firms that deliver scanner output in a branded wrapper. Each includes what a strong answer looks like and what constitutes a red flag.

01
Who actually performs the test
Ask for the full name, CV, and published CVEs of the senior researcher leading your engagement. Hands-on certifications (OSCP, OSCE, CREST CRT / CCT) and conference presentations (DEF CON, Black Hat, BSides) are verifiable signals. Tier 1 firms routinely sell partners and deliver juniors — the name on the engagement matters more than the name on the letterhead.
✓ Named individual with published CVEs and OSCP / CREST CRT confirmed ✗ Cannot confirm who conducts the test before signing
02
Manual-to-automated testing ratio
A healthy ratio for credible internal testing is 60–70% manual exploitation with 30–40% automated scanning. Automated tools handle initial discovery and known-CVE coverage; manual work covers Active Directory attack chains, business logic, and chained exploits no scanner can replicate. Ask directly and record the answer.
Manual exploitation Automated scanning
✓ Specific ratio with explanation of what each phase covers ✗ Evasion, "100% manual" claim, or inability to explain the split
03
CREST accreditation — what it validates and what it doesn't
CREST organizational accreditation validates that the firm's methodology meets CREST standards and that named staff have passed hands-on examinations (CRT or CCT). It does not guarantee that accredited staff are assigned to your specific engagement. Verify current accreditation status independently at crest-approved.org before signing — accreditation is point-in-time, not permanent.
✓ Current CREST listing confirmed at crest-approved.org with CRT/CCT-certified engagement lead named ✗ CREST listed in proposal but no accredited individual named for your engagement
04
Report quality — the five elements a UAE auditor requires
Request a redacted sample report from a comparable engagement. Apply this checklist before signing:
  • Executive summary in business language — connects findings to business risk, not just CVSS scores
  • Regulator control mapping section — NESA ISR v2, DFSA, VARA, or CBUAE framework references per finding
  • CVSS v3.1 per finding with justification — Attack Vector, Complexity, Privileges Required all explained; uniform scores across findings = red flag
  • Chained attack narrative for all Critical and High findings, documenting full exploitation path
  • Retest attestation letter as a separate document, suitable for filing alongside the original report
05
Regulator mapping capability
Your report must map findings to your specific regulator — NESA ISR v2, DFSA, VARA, or CBUAE — not generic "UAE compliance" references. Ask the vendor to show you the table of contents of a comparable report. If the control mapping section is absent, your auditor cannot file the report without revision.
06
Retest discipline
Any firm can find vulnerabilities. A capable firm validates remediation. Your contract must specify: number of retests included, retest window from original report delivery, and that a retest attestation letter is produced as a separate document for audit filing. NESA increasingly treats this letter as independent audit evidence that remediation occurred.
✓ Retest cycle and attestation letter specified in contract terms ✗ "Retest available on request" with no defined window or attestation output
07
Testing independence
The testing firm must be demonstrably independent of your IT vendors, cloud reseller, managed security provider, and audit firm. NESA explicitly requires this independence — making it a regulatory obligation, not merely good practice. Confirm no shared ownership, shared staff, or commercial relationship before signing.
✗ Shared ownership with your IT vendor or MSP violates NESA independence requirement by regulatory definition

What Internal Network Penetration Testing Costs in UAE

Internal scope pricing responds primarily to four variables: number of domain controllers, breadth of IP ranges, number of network segments, and inclusion of wireless or OT scope. A quote below AED 25,000 for an internal engagement with AD coverage is a signal that the deliverable is automated scanning output.

Fixed-price contracts suit well-defined single-segment scope. Time-and-materials is standard for enterprise internal engagements where scope complexity is not fully known at contract signature. A quote significantly below AED 25,000 for full AD lateral-movement coverage is a commercial signal worth investigating before signing.

Red Flags to Walk Away From

Eight signals indicate a vendor is delivering commodity output dressed as penetration testing. The last two are not just bad practice — they violate NESA's explicit independence requirement.

Cannot name the tester before signing
If the firm cannot confirm who runs your engagement at contract stage, the named senior researcher in the proposal will not conduct your test.
Quotes volume as value
"Up to 100 CVEs" or "5,000+ vulnerabilities found" signals scanner-output delivery. A credible internal engagement produces 20–40 high-quality findings, not volume.
Uniform CVSS scores across all findings
Identical CVSS scores indicate template-filling, not per-finding risk analysis. CVSS v3.1 components must vary by finding — Attack Vector, Complexity, and Privileges Required differ for every real vulnerability.
No regulator mapping in sample report
A sample report without NESA, DFSA, VARA, or CBUAE control references cannot be filed with a UAE auditor without revision — making the engagement cost twice to produce a compliant document.
Deliverable is a scanner export with a branded cover
A Qualys or Nessus output with a firm's logo is not a penetration test report. Automated scanner findings are a starting point for manual exploitation — not the final deliverable.
Flat-rate quote regardless of scope
Fixed pricing that does not respond to DC count, IP range size, or network segment breadth indicates sandbagged scope or commodity-scan delivery. A genuine internal engagement's price varies with complexity.
Remediation upsell without an independence wall
A firm that offers to fix what it finds, without formal conflict-of-interest separation between the testing team and the remediation team, compromises finding integrity and creates regulatory exposure.
Shared ownership with IT vendor or MSP
NESA explicitly requires independence from IT vendors. A testing firm with common ownership to your managed service provider violates this requirement by regulatory definition — not just good practice.

Running the Engagement from Scoping to Contract

Six steps cover the full procurement sequence. Step 6 — retest attestation in the contract — is the step all competitors omit, and the one UAE regulators increasingly require as independent audit evidence.

  • 1Write a one-page scope sheet — define IP ranges, domain controllers, explicitly excluded systems, regulatory mapping requirement (NESA/DFSA/VARA/CBUAE), and timing constraints before approaching vendors
  • 2Invite 3–5 firms across tiers — mix Tier 1 for benchmark pricing and Tier 2 for technical value comparison; Tier 3 for SMB scope only
  • 3Require CVs and a redacted sample report as part of the quote — vendors that cannot produce both within standard procurement timelines cannot provide senior-led delivery
  • 4Run a 30-minute technical call with the proposed engagement lead — not the sales team; ask the manual-to-automated ratio question and the AD methodology question directly
  • 5Verify independence — confirm no shared ownership, shared staff, or commercial relationship between the testing firm and your IT vendors, cloud reseller, managed security provider, or audit firm
  • 6Contract must include retest cycle and retest attestation language — specify the number of retests, the retest window from report delivery, and that a retest attestation letter is produced as a separate filing document

Frequently Asked Questions

CREST organizational accreditation validates that the firm's methodology meets CREST standards and that named staff have passed hands-on examinations (CRT or CCT). CREST accreditation does not guarantee that those accredited staff are assigned to your engagement. Always ask specifically who performs your test and verify current accreditation status at crest-approved.org before signing.
Internal penetration testing targets inside-the-perimeter assets: Active Directory, domain controllers, internal subnets, and lateral movement paths. External penetration testing targets internet-facing assets: perimeter firewall, public web applications, and DNS infrastructure. UAE regulators — including NESA and DFSA — treat them as distinct obligations with distinct scope, methodology, and reporting requirements.
Yes. NESA mandates both internal and external penetration testing cycles annually for Critical Information Infrastructure entities under the UAE Information Assurance Standards. The two cycles are distinct obligations with distinct scope definitions. A single combined engagement does not satisfy both NESA requirements.
Internal network penetration testing in the UAE runs AED 55,000–180,000 for enterprise scope with Active Directory coverage. Focused single-segment internal engagements start at AED 25,000–55,000. A quote below AED 25,000 for a full internal engagement with AD lateral movement is a commercial signal that the deliverable is automated scanning, not manual exploitation.
A UAE-regulator-ready report must contain five elements: an executive summary in business language; a regulator control mapping section (NESA ISR v2, DFSA, VARA, or CBUAE references per finding); CVSS v3.1 score with component justification per finding; a chained attack narrative for all Critical and High findings; and a retest attestation letter as a separate filing document confirming remediation of critical findings.

Not sure which scope applies to your regulator?

Send us your regulator (NESA, DFSA, VARA, CBUAE) and we'll map the exact internal pentest obligations that apply to your entity type — at no cost.

Request a Scope Review