Techbanq

NCA · gap assessment

A percentage is not a plan

Most gap assessments end in a maturity score and a heat map. What an organisation needs at that point is a list of controls with an owner, a date and the specific evidence that will close each one.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
CISO, CIO
Decision
Establish the distance between current state and the ECC before committing to a date

Cybersecurity credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA ECC

    ECC compliance expertise

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

What it produces

Three kinds of gap, and they cost very different amounts

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 single most useful thing an assessment can do is separate controls that genuinely do not exist from controls that exist and cannot be evidenced. These read the same on a heat map and they are weeks apart in effort. In most first assessments the undocumented group is the larger one — the organisation reviews access, patches on a cadence and restricts administrative rights, and has no record that any of it happened.

The third group is controls that exist, are documented, and have no owner. Somebody does the work, and the arrangement has no policy behind it and no successor named. These are recorded as gaps because a control that depends on one individual staying is not a control, and the fix is a decision by somebody senior rather than a project.

Sequencing follows from dependency rather than from severity. Asset inventory comes before almost everything, because a control applied to an incomplete list is incomplete by construction. Logging comes before detection. Classification comes before the controls that are scoped by data sensitivity. An assessment that hands over forty findings sorted by risk rating leaves the organisation to discover that ordering by itself, usually two months in.

How it runs

Four weeks, and what happens in each

STAGE 01

1 · Scope and applicability

Which entities, systems and data are in scope, and which controls apply to them. Applicability is a real question rather than a formality, and getting it wrong in either direction is expensive. A scope statement and an applicability position, both written down.

STAGE 02

2 · Evidence collection

Interviews with the people who run each control, and the artefacts that show it running. Where an artefact does not exist we record that rather than accepting a description of it, because the assessor will do the same. An evidence inventory with each item present, absent or partial.

STAGE 03

3 · Technical verification

Configuration read directly for the controls that can be verified that way — logging, access, encryption, network segregation. A stated control that the configuration contradicts is a finding an interview would have missed. Stated state reconciled against actual state.

STAGE 04

4 · Plan and handover

Each gap with a classification, an owner, a date, the evidence that will close it and the dependency it sits behind. Handed over with a working session rather than emailed. A plan the organisation can execute without us.

What goes wrong

Four ways a gap assessment wastes its budget

  1. 01

    Scope set to the whole organisation

    Assessing everything at once produces a document too large to act on and an applicability position nobody has thought through. Scope to the systems and data actually in question, and record why the rest is out.

  2. 02

    A maturity score treated as the deliverable

    A number is useful for a board slide and tells nobody what to do on Monday. Ask for the score if it helps internally, but judge the assessment on whether the plan behind it names owners and dates.

  3. 03

    Interviews accepted without artefacts

    A control described convincingly and never evidenced passes the gap assessment and fails the real one. The assessment is more useful when it is stricter than the assessor, not more generous.

  4. 04

    No dependency order in the plan

    Forty items sorted by severity, worked in parallel, with the asset inventory somewhere in the middle. Everything that depends on it has to be revisited when it lands.

Our role

What we take on in a gap assessment

Techbanq is registered with the National Cybersecurity Authority (NCA) as a cybersecurity service provider. The assessment work below runs on your side of the process.

  1. 01

    Current state against the controls

    We assess what is running against the published control text and produce the remediation plan, sequenced by dependency rather than by control number.

  2. 02

    The remediation itself

    We do the work and produce the evidence artefacts the assessment will look for, rather than leaving a report for another supplier to implement.

  3. 03

    What is already met

    We say plainly where a control is genuinely met, so effort and budget go to the ones that are not.

The assessment that follows is your assessor's, read against the Authority's own scoping rules, and the plan is written so it can be handed straight to them.

The Essential Cybersecurity Controls are published by the National Cybersecurity Authority, and applicability follows from the Authority's own scoping rules rather than from a supplier's reading of them. Work from the published document, and take any applicability question to the Authority or to your assessor. Source

Common questions

What buyers ask

How long does a gap assessment take?+

Three to five weeks for a mid-sized organisation with a defined scope, most of which is availability of the people who run the controls rather than analysis time. The elapsed time is longer when the scope is unclear at the start, which is why the scoping step is separated out rather than folded into week one.

Can we do it ourselves with the published controls?+

The controls are published and readable, so yes in principle, and organisations with a mature internal audit function often should. What an outside reader brings is the absence of the assumptions that produced the gap — a team assessing its own controls tends to accept a description where an assessor would want an artefact. If you do it internally, have someone from outside the operating team run the evidence check.

What if we disagree with the scope our assessor has set?+

Raise it early and in writing, with the reasoning. Applicability disputes are normal and are resolved far more cheaply before the assessment than after a finding has been recorded. What does not work is proceeding on your own reading and discovering the difference at the end — the assessment is measured against their scope, not yours.

Next step

Measure the distance, control by control

A control-by-control assessment that ends in a remediation plan with named owners and dated evidence, not a maturity score.

Measure the distance, control by control

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.