- Market
- Saudi Arabia
- Written for
- CISO, CTO
- Decision
- Commission a breadth-first assessment of the estate
- Languages
- EN · AR
The assessment method
The four stages that turn a scan into a vulnerability assessment
A scanner is the first hour of the work, not the whole of it. The stages that follow are what separate an assessment you can act on from a report that lists everything and prioritises nothing.
1 · Scope and discover the real estate
The asset register is where the assessment starts, not where it stays. Discovery finds the hosts and services the register forgot — the test box that stayed live, the department that stood up its own server — because an assessment measured only against what you already listed misses the very things nobody is watching. The estate as it actually is, not as the register describes it.
2 · Scan authenticated, not only from outside
An unauthenticated scan sees a host the way a stranger does; an authenticated one logs in and reads the patch level, the local configuration and the software actually installed. The difference is large: most of what matters — a missing patch, a weak local setting — is invisible from the network and plain from inside. The state inside each host, not only its network face.
3 · Triage exploitable from theoretical
A raw scan flags every version with a known advisory, whether or not the vulnerable feature is even enabled or the host is reachable. A person reads each high finding against your environment — is the component in use, is the path exposed, is compensating control already in place — and reclassifies it, because a critical nobody can reach outranks nothing. Findings sorted into exploitable, contextual and theoretical.
4 · Build the remediation queue
The output is an ordered list of work, not a severity histogram. Each item carries what it exposes, how reachable it is, and the fix, so the queue reflects the risk you carry rather than the number a scanner printed. A patch on an internet-facing service outranks a higher-scored one buried three networks deep. A queue ordered by risk you can act on this week.
Assessment against test
Why a vulnerability assessment is not a cheaper penetration test
The two are often confused because both produce a list of vulnerabilities, but they answer different questions and neither substitutes for the other. An assessment asks what is present across the whole estate, at breadth, and can cover thousands of hosts. A penetration test asks what an attacker can actually chain together on a few chosen targets, at depth, and proves reachability by reaching it. Buying one when you needed the other is a common and expensive mistake.
The honest use of an assessment is as the wide net that tells you where to point the depth. Run it across the estate, triage the queue, fix the reachable criticals, and then commission a penetration test against the handful of systems the assessment flagged as both exposed and valuable. An assessment on its own does not prove exploitability; a test on its own never sees the estate. Used in that order they are complementary rather than redundant.
What the assessment needs
The access that decides whether a scan is authenticated or blind
Authenticated scanning is where an assessment earns its keep, and it depends on inputs an anonymous scan does not need. These are what we ask for and what each one changes about what the scan can see.
Scanning credentials per platform
A least-privilege account that lets the scanner log in and read patch state, installed software and local settings on each host.
What its absence hides: Blind to missing patches and weak local configuration — the majority of real findings.
An agreed target range and windows
The networks in scope and the hours a scan may run, so nothing fragile is scanned at its busiest moment.
What its absence hides: A scan that either misses segments or disrupts a service that could not take the load.
An asset owner to answer context questions
Someone who can say whether a flagged feature is in use and whether a control already compensates, which is what triage turns on.
What its absence hides: A queue that keeps theoretical findings high because nobody could confirm they were unreachable.
The last assessment, if there was one
Comparing against the previous run shows what was fixed, what recurred, and what has drifted back since remediation.
What its absence hides: No way to tell a new exposure from one that was closed and quietly reopened.
Our role
What the assessment hands back, and what your team decides to fix
- 01
We scan the breadth, authenticated
The assessment covers the whole agreed estate with credentials, so it reads the patch and configuration state inside hosts rather than guessing from a version banner on the network.
- 02
We triage before we report
A person reclassifies the scanner output against your environment, so the report distinguishes what is exploitable from what is merely present. A tool-only report that skips this stage hands you your own noise back.
- 03
Your team owns the queue
We order the remediation by risk and give each item its fix, but which items your maintenance windows and business priorities take first is your call, and we leave the queue in a form you can keep running against.
How fast a given class of risk must close, and which maintenance window takes which fix, are your operational decisions; we establish what is present across the estate, which findings are genuinely exploitable, and the order that reduces risk fastest.
Common questions
What buyers ask
How does a vulnerability assessment differ from a penetration test we already buy?+
By breadth versus depth. An assessment covers the whole estate — potentially thousands of hosts — and tells you what is present everywhere, but it does not prove any single finding is exploitable. A penetration test takes a few chosen targets and proves what an attacker can actually chain on them, in depth, but it never sees the estate. The productive order is to run the assessment first as a wide net, triage the queue, fix the reachable criticals, then point a penetration test at the handful of systems the assessment flagged as both exposed and valuable. They are complements, not two names for the same thing.
Why insist on authenticated scanning rather than an external scan?+
Because most of what matters is invisible from outside. An unauthenticated scan sees a host the way an anonymous visitor does — open ports and a few version banners — and infers the rest. An authenticated scan logs in and reads the actual patch level, the installed software and the local configuration, which is where the majority of real, fixable findings live. Relying on an external scan alone produces a comfortable report that misses the missing patch and the weak local setting precisely because they never showed on the network. We use a least-privilege account so the deeper visibility does not come at the cost of standing access.
The scanner returns thousands of findings — how do you decide the order to fix them?+
Not by the CVSS score, which is the mistake that keeps teams busy on the wrong work. A CVSS number describes a vulnerability in the abstract; it does not know whether the vulnerable feature is enabled in your build, whether the host is reachable, or whether a control already compensates. We triage each finding against your actual environment — is it exploitable here, how exposed is it, what does it protect — and order the queue by that. A critical buried three networks deep and unused outranks nothing; a medium on an internet-facing service that handles customer data goes to the top. The queue reflects the risk you carry, not the histogram the tool printed.
In this cluster
Next step
Scope the estate with us
A scoped assessment across the agreed estate with credentials for authenticated scanning, returning a triaged remediation queue that says what to fix first and what can safely wait.
Scope the estate with us
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

