Cybersecurity credentials
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
Scoping
Most disappointing tests were scoped badly, not run badly
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
The two decisions that determine whether a test is worth its cost are made before anyone starts testing: which test type you are buying, and what the report has to contain. Get those right and even a modest engagement produces work the engineering team can act on. Get them wrong and a large budget produces a document that gets filed.
The most common scoping error in this market is testing without credentials. An unauthenticated test of a business application tells you what an anonymous visitor can reach, which is usually the least interesting question. The valuable findings — a user reading another tenant's records, a role escalating itself, an API trusting a client-supplied identifier — only appear when the tester is logged in at each privilege level you actually operate.
The second is asking for a fixed price before the scope exists. Testing effort scales with the number of applications, network ranges, roles and cloud accounts in scope. A firm price quoted against a vague brief means either the supplier has guessed, or they have priced the smallest defensible interpretation and will raise a change request later.
Coverage
What each test type covers — and what it will not find
The second column is the one worth reading. Every test type has a blind spot, and knowing it is how you decide whether one engagement is enough.
Web application (authenticated)
Authorisation logic between roles and tenants, session handling, injection, business-logic abuse, file handling, and the workflows a user can drive out of order.
What it will not find: Weaknesses in the infrastructure the application runs on, or in a second application that shares its database
API (REST or GraphQL)
Object-level and function-level authorisation, mass assignment, rate limiting, token handling, and endpoints that exist but are not in the documentation.
What it will not find: Issues only reachable through the user interface that calls the API
Mobile application
Local data storage, certificate handling, hardcoded secrets, platform permission misuse, and whether server-side controls hold when the client is modified.
What it will not find: Server-side problems in systems the app does not call
Network (internal or external)
Exposed services, patch levels, segmentation between zones, credential reuse, and lateral movement paths from a compromised workstation.
What it will not find: Application-layer logic flaws inside an otherwise well-patched service
Cloud configuration and identity
Over-permissive roles, public storage, network exposure, key management, logging gaps, and the trust relationships between accounts.
What it will not find: Vulnerabilities inside the application code deployed on that infrastructure
The report
What the deliverable has to contain to be useful
Ask for a redacted sample before engaging anyone, including us. The sample tells you more about what you are buying than the proposal does.
Reproduction steps a developer can follow
The exact request, the account used, the state the system was in. A finding a developer cannot reproduce becomes an argument about whether it is real, and those arguments are how findings stay open for a year.
Impact stated in business terms
Not "high severity" but what an attacker gets: which records, whose data, what action they could take. Severity labels without that context produce the wrong remediation order, because the label does not know your business.
Root cause, not just the instance
If the same authorisation check is missing on eleven endpoints, that is one design problem, not eleven findings. Reporting it as eleven produces eleven patches and a twelfth endpoint next quarter.
Retest of what was fixed
Included in the engagement, not sold separately. Closure that is asserted rather than verified is exactly the gap an assessor looks for, and the retest is usually a fraction of the original effort.
Cost
What moves the price of a test
We do not publish a price list, because a figure quoted before the scope is known is a guess. These are the variables that actually set it — and the questions to put to anyone who quotes you.
| Variable | Effect on price | Why |
|---|---|---|
| Number of applications and roles | Largest single driver | Each additional application adds testing time, and each additional privilege level roughly multiplies the authorisation testing within it. |
| Authenticated or unauthenticated | Significant | Authenticated testing costs more and finds the issues that matter. Unauthenticated-only testing is cheaper and rarely worth buying for a business application. |
| Control framework mapping | Adds documentation effort | Reporting findings against a published control set with a required evidence format is additional work beyond the testing itself. |
| Environment type | Extends the timeline | Industrial and operating technology environments take longer because active steps must be planned around production and approved as changes. |
| Retest and remediation support | Small relative to the test | Usually a fraction of the original effort, and the part most often left out of a cheap quote. |
Ask any supplier quoting this
- How many tester-days sit behind this figure, and at what seniority?
- Is retest included, or quoted separately?
- Will you test with credentials at every privilege level we operate?
- Can we see a redacted report from an engagement like ours?
Common questions
What buyers ask
What is the difference between VAPT and a penetration test?+
In common usage VAPT bundles a vulnerability assessment — broad, largely automated coverage that finds known weaknesses — with penetration testing, which is manual work chaining those weaknesses into a demonstrated attack path. The assessment tells you what is out of date; the test tells you what an attacker could actually do with it. Buying only the first and calling it a penetration test is the most common mis-sale in this market.
How often should we test?+
Tie it to change rather than the calendar. An application under active development benefits from testing at each significant release and a fuller engagement annually. A stable internal system may need testing only annually. Testing a system that has not changed since the last test mostly re-buys the previous report.
Do you provide a certificate or attestation letter?+
We provide a letter of attestation stating the scope tested, the dates, the methodology and the status of findings at retest. That is a factual record of work performed, which is what a customer or auditor asking for one actually needs. It is not a certification, and any supplier offering a "penetration test certificate" that implies more than this is overstating what such a document can mean.
Can you test systems hosted outside Saudi Arabia?+
Yes, subject to your own data residency rules and the hosting provider's testing policy. Most major cloud providers permit customer-authorised testing of your own resources without prior notice, but the boundary of what you are allowed to test differs by provider and service. We confirm that in scoping rather than after.
In this cluster
Scope a test
A scoping conversation that produces a written scope, a rules-of-engagement draft, the tester-days behind the estimate and a testing window. One hour, no cost, no commitment.
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly
