Techbanq

NCA · applicability

Three ways this lands on your desk

Very few organisations are named in a document. Most acquire the obligation through a regulator or a customer contract, and which route you came by decides what you have to defend and to whom.

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

The routes

How the obligation reaches you, and what changes

The control text is the same in all three cases. What differs is who decides your scope, who reads your evidence, and how much room there is to argue about either.

OptionWho sets the scopeWho reads the evidenceWhere the deadline comes fromRoom to negotiateBest for
Named directlyThe Authority's own scoping rules, read against your systems.The Authority or an assessor acting within its process.The Authority's published cycle.Applicability questions are raised with the Authority, in writing, early.Entities the Authority supervises directly.
Through a sector regulatorYour regulator, whose framework often maps onto the ECC rather than repeating it.The regulator's supervision function, on its own cycle.The regulator's reporting calendar, which rarely matches anyone else's.The mapping is arguable; the underlying control is not.Banks, insurers, telecoms and other supervised sectors.
Inherited from a contractYour customer, through a clause that usually names a standard rather than a scope.Your customer's security function, or an auditor they nominate.The contract date, which is the one nobody can move.Scope is genuinely negotiable here, and it is where the cost is decided.Suppliers to a regulated customer — most private companies.

The common mistake

Assuming the whole organisation is in scope

The instinct on receiving a clause is to treat every system as covered, because that feels like the safe reading. It is the expensive one. A scope defined as "everything" cannot be defended in an assessment either — an assessor asked to review an undefined estate will define it themselves, usually more widely than you would have.

The opposite mistake costs more. A scope drawn narrowly around one platform, with a connection into it that nobody declared, fails at the first question about that connection. The boundary is not a list of systems; it is a list of systems plus the reasoning for what was left out, and the second half is what an assessor reads.

Where a private organisation is not directly in scope, that finding is worth having in writing before a programme is funded. It happens more often than the market suggests, and it changes the conversation from a compliance programme to a security programme with a customer-facing summary — which is cheaper and usually more useful.

Scope questions

Four questions that settle most of it

Answerable in a week from documents you already hold, and each one narrows the estate before anybody prices remediation.

  1. 01

    What exactly does the clause name?

    A standard, a control set, a certificate, or "appropriate measures"? Each demands something different, and the last one is a negotiation rather than a requirement. Ask for the clause and the referenced document in writing before designing anything against a second-hand description of them.

  2. 02

    Which systems touch the customer's data or network?

    That set is in scope in every reading. Everything else needs an argument, and the argument is usually about a connection: a jump host, a shared identity provider, a monitoring agent that reaches into both estates.

  3. 03

    Does a sector framework already cover this?

    Regulated organisations frequently hold most of the evidence already, produced for a different supervisor in a different format. Mapping what exists costs days; producing it again costs months.

  4. 04

    Who signs the scope?

    A scope nobody owns is revisited every time a new stakeholder reads it. Name the executive who approves the boundary and the date they approved it, because that record is itself evidence.

Our role

What we do once the scope is settled

  1. 01

    Establishing the position

    We read the published control text against what is actually running and record where you stand, in the words the assessment will use rather than in ours.

  2. 02

    Doing the work

    The remediation is ours — the engineering, the process change and the documentation — rather than a findings list handed to somebody else to implement.

  3. 03

    Leaving evidence behind

    Each control is set up to generate its own record as it runs, so the next assessment costs a fraction of this one.

Applicability itself is determined by the Authority's scoping rules and, where a contract is involved, by your customer — we prepare the position and the reasoning that conversation needs.

The controls are published in full by the National Cybersecurity Authority. Work from that document rather than from a supplier's summary of it, and take applicability questions to the Authority or to your assessor. Source

Common questions

What buyers ask

We are a private company. Which route are we most likely on?+

Directly, it applies to government entities and to organisations that own, operate or host critical national infrastructure. A great many private companies are not in that population and still carry equivalent obligations, inherited through a customer contract or a sector regulator. The distinction matters because the second route lets you define the scope, and the first largely does not.

Our customer asked for "ECC compliance" with no further detail. What do we ask for?+

Ask for three things in writing: the clause, the control set they are referring to, and what evidence they expect to receive. Most requests of this kind resolve into a supplier assurance questionnaire rather than a full assessment, and the gap between those two is several months of work.

Can we scope out a system by disconnecting it?+

Sometimes, and it is a legitimate design decision when the disconnection is real and permanent. It is not legitimate when the connection is disabled for the assessment window and restored afterwards; that is a finding waiting to be made, and it is the kind that damages the relationship with the assessor rather than just the result.

Establish which controls apply to you

A written scope position stating which route applies to you, which systems fall inside it, and the reasoning for what sits outside.

Start the conversation