Techbanq

NCA ECC · gap assessment

Measure the estate against the ECC before anyone prices a programme

A gap assessment is the cheapest work in the whole compliance cycle, and it decides the cost of everything after it. Done control by control against real evidence, it replaces a debate about readiness with a register of work.

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

Method

Four stages of an ECC gap assessment, from scoping to the register

The order matters. Scoping before evidence keeps the review honest about what it covered, and scoring before the register keeps the register about work rather than about grades.

STAGE 01

Scope the estate in writing

Systems, networks, sites and third-party connections are listed with the reasoning for anything excluded. The scope statement is the first artefact the eventual assessment will read, so it is written in that register. A signed scope statement with exclusions reasoned.

STAGE 02

Review evidence control by control

Each control in the published text is read against what actually exists: configuration, records, tickets, logs. A policy that says the right thing scores nothing on its own — the question is whether the control operates and leaves a trace. A finding per control, with the evidence seen or missing named.

STAGE 03

Score maturity without flattery

Each control is placed on a maturity scale using the same reading an assessor would apply. Where a control operates in one business unit and not another, it scores as the weaker case, because that is where the finding will land. A defensible score per control domain, with the reasoning recorded.

STAGE 04

Write the remediation register

Every gap becomes an entry with an owner, a dependency list, the evidence that will prove closure, and a priority set by risk and by what blocks what — not by how easy the fix is. The register: the programme's backlog, priced and sequenced.

Scoring

Why an ECC maturity score is a means, never the deliverable

A maturity score is useful for exactly two things: deciding priority inside the register, and measuring movement between two assessments. It is not useful as a headline, and treating it as one produces the familiar failure — a report presented to a committee, filed, and rediscovered untouched when the assessment date is set.

The score is also where assessments get negotiated, and the negotiation is worthless. A control moved from a two to a three in a workshop is still a two in the estate, and the formal assessment reads the estate. We record the score the evidence supports and put the disagreement, where there is one, in writing next to it.

What survives the engagement is the register. Six months later nobody re-reads the scoring narrative, but the register is opened weekly, entries are closed against named evidence, and the delta between assessments is counted in closed entries rather than in adjectives.

Failure modes

Three ways an ECC assessment produces a report instead of a result

  1. 01

    Interviews instead of evidence

    An assessment built on what teams say about their controls inherits every optimistic assumption in the building. The formal assessment will look at configuration and records, so the gap assessment has to look at the same things or it measures the wrong estate.

  2. 02

    Findings without owners

    A gap that belongs to nobody is re-discovered at the next assessment. Each register entry names the team that closes it and the executive who accepts the risk if it stays open, because an unowned entry is a decision someone is avoiding.

  3. 03

    Priorities set by ease

    Closing forty easy entries feels like progress and can leave the estate no safer. Priority in the register follows exposure and dependency: the control whose absence makes five others unverifiable comes first, however awkward it is.

Our role

What an ECC gap assessment engagement includes, and where it stops

  1. 01

    Reading the estate

    We review evidence against the published control text with the reading a formal assessment would apply, and record what we saw, not what we were told.

  2. 02

    Writing the register

    Every gap becomes an executable entry — owner, dependency, closure evidence, priority — so the next engagement is engineering rather than another study.

  3. 03

    Standing behind the score

    The maturity position is written to be shown to your assessor, with the evidence trail that produced it, rather than adjusted for an internal audience.

The compliance assessment itself belongs to the Authority and to assessors acting within its process — what we hand over is the position and the register that assessment will test.

The Essential Cybersecurity Controls are published in full by the National Cybersecurity Authority. The assessment is measured against that text, so work from it rather than from any summary, including ours. Source

Common questions

What buyers ask

How long does an ECC gap assessment take on a mid-sized estate?+

It is scoped by the size of the evidence review, not by the control count: a single data centre with one platform team is a matter of weeks, while an estate spread across several environments and business units takes longer because each produces its own evidence. The scoping conversation gives you the honest figure before anything is committed.

Should we fix known gaps before the gap assessment starts?+

Only where the fix is already planned and funded. Rushing changes ahead of an internal assessment spends money before the priorities are known, and the assessment exists precisely to set those priorities. Tell the assessing team what you already know is broken — it shortens the review and costs you nothing, because this is a working session, not a judgment.

What does each entry in the remediation register actually contain?+

The control reference, the gap in plain language, the named owner, the dependencies that must close first, the evidence that will demonstrate closure, and a priority derived from exposure and dependency. The test we apply is that an engineer who was not in the assessment can pick up the entry and start work without a meeting.

Next step

Scope an ECC gap assessment

A scoped gap assessment ending in a remediation register your own engineers or ours can execute without reinterpreting it.

Scope an ECC gap assessment

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.