- Market
- Saudi Arabia
- Written for
- CISO, CIO
- Decision
- Plan an ECC programme in an order that does not create rework
Cybersecurity credentials
NCA ECC
ECC compliance expertise
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
Sequence
Four stages, ordered by what gates what
The stages are not equal in effort and are not meant to be. The first is small and gates most of the rest; the third is where the months go.
1 · Scope, inventory, classification
What is in scope, what assets exist, and how the data is classified. Small in effort, and it scopes the access, cryptography, protection and third-party work that follows. Doing it late is the single most common source of rework in this programme. A scope statement, an inventory with owners, and a classification scheme in use.
2 · Governance and evidence design
Policies approved, roles named, risk process running — and, in the same stage, the decision about what each control will produce as its record. Designing evidence now is what makes the assessment an assembly job rather than a reconstruction. An approved policy set and an evidence register naming the artefact per control.
3 · Technical remediation
Segmentation, access, hardening, logging, vulnerability management. The bulk of the elapsed time, and the part whose length depends almost entirely on whether the estate is already segmented. Controls operating, each producing the record designed in stage two.
4 · Operate, sample, assess
A period of the controls simply running and producing evidence, sampled quarterly to catch the one that quietly stopped. The assessment measures that period, which is why it cannot be compressed by starting the programme later. A period of operation an assessment can measure.
How long
The variable is segmentation, not scale
Two organisations of the same size can be six months apart on this programme, and the difference is almost never headcount or budget. It is whether the estate is already separated into zones that can be described. Where it is, technical remediation is configuration work against a known map. Where it is not, the map has to be drawn and the estate separated while it keeps running, and that is slow for reasons that have nothing to do with the difficulty of the work.
The second variable is how much of the evidence period has already been served. A control that has been operating and recording for a year needs nothing; the same control switched on this month needs the year. This is why the evidence decision belongs in stage two rather than at the end — every month it is deferred is a month the assessment cannot measure.
Sequencing errors
Four orders that cost months
- 01
Inventory last
Access reviews, hardening baselines, vulnerability coverage and third-party scope are all measured against the asset list. Completing them against a partial list means revisiting them, and the revisit is rarely budgeted.
- 02
Policies written before the practice exists
Approving a policy set that describes controls nobody runs converts an absence into a contradiction. Write the policy against what will actually be done in stage three, or write it after.
- 03
Evidence decided at the end
The most expensive error available, because it cannot be corrected retrospectively. Evidence for a period that has passed cannot be created; the only honest options at that point are disclosure or waiting.
- 04
The assessment booked before the operating period
The assessment measures a period of operation. Booking it for the month remediation finishes measures a month of operation, which is not what the controls are asking to demonstrate.
Our role
What we take on once the roadmap is agreed
Techbanq is registered with the National Cybersecurity Authority (NCA) as a cybersecurity service provider. Our work runs on your side of the assessment — reading the controls, closing what is open, and preparing what the assessor will ask to see.
- 01
Reading the controls with you
We work through the published control text and say where you stand against it, control by control, in the words the assessment will use.
- 02
Closing the gaps
We do the remediation work itself — the engineering, the process changes and the documentation — rather than handing over a list of findings for someone else to act on.
- 03
Preparing the evidence
We produce the artefacts the assessment looks for, generated by the control that runs rather than assembled the week before, and review them against the published text before anyone else reads them.
- 04
Saying where you are already covered
Where a control is already met we say so, so the budget goes to the ones that are not. It is the cheapest finding in the engagement and the one a supplier has least incentive to report.
The assessment itself is conducted by your assessor against the Authority's scoping rules, and we stay available through it — the evidence pack is written to be read by them.
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
Can a programme be done in six months?+
The remediation can, for an organisation whose estate is already segmented and whose governance exists. What cannot be compressed is the operating period the assessment measures — a control switched on in month five has five months of record by month ten, and no amount of resourcing changes that. So the honest six-month answer is: remediation complete, assessment later, and the gap stated rather than hidden.
Should we run domains in parallel at all?+
Yes, once stage one has landed — after that the constraint is people rather than dependencies, and governance, technical and third-party work go on concurrently with different owners. What should not run in parallel with anything is inventory and classification, because they are what the others are measured against and they are quick.
What does the programme cost?+
It splits into three unequal parts and only one of them is a supplier invoice. Internal time is usually the largest and is rarely counted: the people who run the controls have to be available for interviews, decisions and the work itself. Technology is the second and is smaller than expected once the requirements are read as outcomes. Advisory is the third. Anyone quoting a total before seeing whether the estate is segmented is quoting a template.
In this cluster
Next step
Sequence the work by dependency
A sequenced plan with the dependency order made explicit, so the work that gates other work lands first.
Sequence the work by dependency
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
