Cybersecurity credentials
NCA ECC
ECC compliance expertise
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
Why first
Why ECC readiness starts before the first vendor meeting
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 Essential Cybersecurity Controls, issued by the National Cybersecurity Authority, are organised into domains that any experienced security leader will recognise: governance, defence, resilience, third-party and cloud considerations, and the security of industrial systems where they apply. The detail belongs to the framework document itself; what matters here is that a large share of what the framework asks about is fact-finding an organisation can do internally, without interpretation and without a consultant.
Who is accountable for cybersecurity, and does the board know it? What systems exist, and who owns each? What gets logged, and would anyone notice if logging stopped? Which suppliers hold access into your environment? No framework expertise is needed to answer these — only the discipline to ask them and write the answers down. An organisation that arrives at its first vendor conversation with these answers documented buys engineering and judgement; one that arrives without them buys weeks of interviews.
The readiness pass also changes the power balance of the procurement. When you can state your asset count, your logging coverage and your third-party list, a vendor cannot price uncertainty into the proposal, and a proposal that still leads with a long discovery phase tells you something about the bidder.
The walkthrough
The ECC readiness walkthrough you can run without a consultant
Work through these in order, writing the answers down as you go. The output is not a compliance report; it is the factual baseline every later step builds on.
Governance — name the owner
Identify who is accountable for cybersecurity, whether that role is documented and given real authority, and which policies actually exist as approved documents rather than as intentions. If nobody owns security, that is the first gap, and it precedes every technical one. A named, documented security owner and an honest policy inventory.
Assets — list what you would have to defend
Build an inventory of systems, applications, data stores and the infrastructure they run on, with a named owner for each. It will be incomplete on the first pass — the point is to discover how incomplete, because every control that follows applies "to your assets", and an unlisted asset is an unprotected one. A first-pass asset register with owners and known blind spots.
Logging — check what would be visible after an incident
For your most important systems, establish whether authentication events, administrative actions and network boundaries are logged, where those logs go, how long they are kept, and whether anyone reviews them. The test is simple: if a credential were misused last month, could you reconstruct what happened? A logging coverage map and the incident question answered honestly.
Identity — count the ways in
Establish how many privileged accounts exist, whether multi-factor authentication protects remote and administrative access, and how leavers actually lose access. This domain produces the findings organisations most often fix themselves within days of looking. A privileged-access picture and the quick wins it exposes.
Third parties — know who reaches into your environment
List the suppliers, cloud services and support arrangements that hold credentials, network paths or data of yours, and what each contract says about security. Third-party and cloud posture is a domain the framework treats seriously, and most organisations discover their list is longer than anyone believed. A third-party access register your contracts can be checked against.
In practice
A readiness pass in practice, before formal ECC work begins
Illustrative — a typical shape, not a named client
A mid-sized organisation learns it falls within ECC scope and its instinct is to issue an RFP immediately. Instead, the IT director takes three weeks to run the walkthrough above with the infrastructure lead and one person from procurement.
- 01The governance question exposes that security is owned by "IT generally", so the organisation names an owner and drafts the accountability line before any vendor is contacted — a fix that costs a management decision, not a contract.
- 02The asset and identity passes surface a handful of forgotten systems and dormant privileged accounts, which internal staff close within the month, shrinking the scope any future engagement has to cover.
- 03The logging and third-party findings are written up as a gap list with owners, and that document — not a blank page — becomes the basis of the RFP the organisation eventually issues.
The engagement that follows starts at remediation rather than discovery, the proposals received are comparable because every bidder priced the same documented baseline, and the organisation can tell which findings it could have fixed alone.
Our role
What we add once your ECC readiness answers exist
- 01
Interpretation against the framework
Your walkthrough establishes the facts; we map them to what the framework actually expects, domain by domain, and separate the gaps that need engineering from the ones that need a policy and a signature.
- 02
Remediation, prioritised by exposure
We design and implement the missing controls in an order set by risk rather than by the framework's table of contents, so the work reduces real exposure from the first month.
- 03
Evidence that survives scrutiny
We help assemble the documentation and technical evidence that shows each control operating, so what you built can be demonstrated rather than asserted.
The framework is issued and overseen by the National Cybersecurity Authority, and compliance is determined through the processes the Authority defines; our work is the readiness, remediation and evidence that precede that determination.
The Essential Cybersecurity Controls are issued by the National Cybersecurity Authority, which alone defines their scope and how compliance is assessed. Source
Common questions
What buyers ask
Do we need a consultant to run an ECC readiness self-assessment?+
Not for the walkthrough on this page, which is deliberately limited to fact-finding: naming owners, listing assets, checking logging and counting third parties. Those are questions about your own organisation that your own people answer best. Where outside help earns its fee is the step after — interpreting your facts against the framework's expectations, judging which gaps carry real exposure, and designing remediation. Buying interpretation before you have established the facts means paying consulting rates for stocktaking, which is the exact inefficiency a readiness pass exists to remove.
What if the ECC readiness walkthrough shows we have almost nothing in place?+
Then the walkthrough has done its job, because that is far better learned from an internal exercise than from a formal engagement or an incident. A largely empty baseline changes the sequencing, not the destination: the first moves are organisational — an accountable owner, a minimal policy set, an asset list — and several of the highest-value technical steps, such as multi-factor authentication on administrative access, are within reach of most internal teams. It also changes what you should buy: a long assessment of an environment you already know is bare adds little, while a remediation-led engagement starts adding protection immediately.
Does an ECC readiness pass overlap with preparing for ISO 27001?+
Substantially, at the level this page works at. An accountable owner, an asset inventory, logging visibility, access discipline and a third-party register are foundations both frameworks assume, so the walkthrough's output serves either path and you should not pay to produce it twice. The frameworks then diverge in structure and purpose — one is a national regulatory baseline, the other an international certifiable management system — and which to pursue, or in what order, depends on who requires what of you. Establish the shared baseline first; it makes that later decision cheaper and better informed.
In this cluster
Discuss your readiness picture
A conversation about what your walkthrough surfaced — which gaps need engineering, which need governance, and what a proportionate next step looks like.
Start the conversation