20 Nov 2026 By CISO Consulting team 1 views 5 min read

Cybersecurity Recruitment Saudi: NCA ECC Technical Assessment

Generic job descriptions attract certification collectors who cannot turn NCA ECC or SAMA CSF controls into working architecture. This article sets out four role-description components and three technical-assessment scenarios that separate practitioners from certificate holders.

Two senior security professionals reviewing a network architecture diagram on a whiteboard in a modern Riyadh office.
In this article
  1. Phase 1: Write the role brief with four components
  2. 1. Regulatory-control ownership
  3. 2. Incident-scenario experience
  4. 3. Architecture-decision authority
  5. 4. Vendor-evaluation criteria
  6. Phase 2: Screen against the brief
  7. Phase 3: Run three technical-assessment scenarios
  8. Scenario 1: Logging-architecture design
  9. Scenario 2: Incident-playbook walkthrough
  10. Scenario 3: Control-evidence gap analysis
  11. Phase 4: Decide, and choose the engagement model
  12. How we support this process
  13. Deliverables checklist
  14. Next step

Hiring for a regulated Saudi organization is different from hiring for an unregulated one. Cybersecurity recruitment in Saudi Arabia under NCA ECC or SAMA CSF needs a technical assessment that tests whether a candidate can build and operate controls, not only name them. A generic job description such as "security specialist with CISSP, CISM and five years of experience" attracts people who hold certifications and can discuss frameworks, but who may never have turned a control into a working architecture.

This article explains how to write the role brief and how to assess candidates against it. It follows the order in which a hiring process normally runs: define the role, screen on the brief, assess technically, and decide. It ends with a list of what you should hold when the process is complete.

Phase 1: Write the role brief with four components

Who takes part on your side: the CISO or head of information security, an HR director, and the compliance lead who knows which regulatory obligations apply.

What happens: before posting, the brief is rewritten around four components. Each filters candidates in a different way.

1. Regulatory-control ownership

State which controls the role will own. Name the framework: NCA ECC domains such as cybersecurity governance, defense, and resilience, or the relevant SAMA CSF domains for a financial institution. Say whether the person is accountable for operating the control, producing its evidence, or both. A candidate who has owned a control will describe the evidence trail; one who has only read it will describe the headline.

2. Incident-scenario experience

Replace "incident response experience" with the scenarios you expect the person to handle: ransomware in a hybrid environment, compromised privileged credentials, a third-party breach, or a reportable data incident. Ask candidates to say which role they played, not which team they were part of. The brief should also state your reporting duties to the regulator, so candidates know the work includes them.

3. Architecture-decision authority

State what the role may decide alone, what needs approval, and what it can only recommend. Examples include choosing a logging platform, setting segmentation rules, or approving an exception. Practitioners want to know their decision rights. Certificate collectors rarely ask.

4. Vendor-evaluation criteria

Say whether the role will evaluate and select tools and service providers, and against what criteria: regulatory fit, data residency, integration with existing controls, and operational burden on your team. Ask for an example of a tool the candidate rejected and why.

What you hold at the end: a role brief with the four components written out, agreed by security, HR and compliance, ready to post.

Phase 2: Screen against the brief

Who takes part on your side: HR for first screening, and a security lead for the technical shortlist.

What happens: screen on the four components rather than on certificate lists. A short written question for each component works well. For example, ask the candidate to describe one control they owned end to end and what evidence it produced. Vague answers at this stage save interview time later.

What you hold at the end: a shortlist ranked by evidence of implementation experience, with notes against each component.

Phase 3: Run three technical-assessment scenarios

Who takes part on your side: the CISO or a senior engineer as assessor, and ideally a compliance representative for the third scenario.

What happens: each shortlisted candidate works through three scenarios. Each lasts about an hour and is discussed, not graded on a trick answer. You are listening for sequence, trade-offs and the questions the candidate asks.

Scenario 1: Logging-architecture design

Give a simplified environment: on-premises servers, a cloud workload, a remote workforce and an identity provider. Ask the candidate to design logging and monitoring that supports NCA ECC expectations on event logging and monitoring.

A practitioner will ask which log sources matter first, how long logs must be kept, where they may be stored, who reviews alerts and how often. They will talk about time synchronization, log integrity and alert tuning. A certificate holder tends to name a product category and stop.

Scenario 2: Incident-playbook walkthrough

Describe a scenario, such as a privileged account used from an unusual location at night. Ask the candidate to walk through the first hours: triage, containment, evidence preservation, escalation and communication.

Listen for who is called and when, how decisions are recorded, and when the regulator or other authorities must be informed. A practitioner will mention what could go wrong with each step. Ask what they would change in the playbook afterwards.

Scenario 3: Control-evidence gap analysis

Provide a mock evidence pack for a few controls with deliberate weaknesses: a policy with no approval date, an access review with no sign-off, and a vulnerability report with no remediation tracking. Ask the candidate to find the gaps and say what an assessor would conclude.

This scenario separates people who have lived through assessments from those who have studied for them. Practitioners spot missing ownership, stale evidence and inconsistent scope quickly, and they propose realistic fixes rather than rewriting the whole control.

What you hold at the end: a scored assessment record per candidate across the three scenarios, with notes that link back to the four components of the brief.

Phase 4: Decide, and choose the engagement model

Who takes part on your side: the CISO, the HR director and the hiring manager.

What happens: compare candidates using the assessment record, not the interview impression. Then decide whether the role should be a permanent hire or filled by a specialist working alongside your team. Some roles are needed for a defined programme, such as a framework implementation, and a permanent post may not fit. Others, such as a security architect or a SOC lead, are long-term.

What you hold at the end: a documented hiring decision, an agreed engagement model and a clear first-90-day expectation tied to the controls the role owns.

How we support this process

Our cybersecurity talent service covers this ground. We find, assess and place cybersecurity people for you, either as permanent hires or as specialists on our payroll working on your team. The service is relevant to organizations working under SAMA CSF, NCA ECC, PDPL, ISO 27001, PCI DSS and SAMA CRFR.

Where a role brief needs a governance view, our GRC advisory work builds frameworks tailored to Saudi regulatory requirements, including SAMA CSF and NCA ECC. Where an organization needs senior leadership before it can hire a full-time head of security, our vCISO service provides strategic cybersecurity leadership on demand, without a full-time hire.

Deliverables checklist

By the end of the process you should hold:

  • A role brief with regulatory-control ownership, incident-scenario experience, architecture-decision authority and vendor-evaluation criteria defined
  • A screened shortlist with notes against each component
  • Three technical-assessment scenarios: logging-architecture design, incident-playbook walkthrough and control-evidence gap analysis
  • A scored assessment record for each assessed candidate
  • A documented hiring decision with the chosen engagement model
  • A first-90-day expectation linked to the controls the role owns

Next step

If you are building or expanding a security team and want the brief and assessments tailored to your regulatory obligations, speak with us about our cybersecurity talent service. We will start from the controls you need operated and work back to the people who can operate them.

Tags: cybersecurity recruitment NCA ECC SAMA CSF technical assessment security hiring job descriptions
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment