- Market
- Saudi Arabia
- Written for
- CISO, CIO
- Decision
- Assemble the evidence an ECC assessment will ask for
- Languages
- EN · AR
Cybersecurity credentials
NCA ECC
ECC compliance expertise
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
What counts
Evidence has to have a date and a signature on it
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.
An assessor is answering one question per control: did this operate, over the period, as described. Three things establish that. The artefact is dated, and the dates fall across the period rather than clustering in one week. Somebody is identifiable as having produced or approved it. And the artefact is the natural output of the control rather than something created to demonstrate it.
That third point is where most preparation goes wrong. A screenshot of a configuration page shows the state at the moment it was taken; it does not show that the state held for a year, and it does not show who was responsible for it holding. A log export covering the assessment period, an approval record with a name against it, a ticket queue showing the work being done — these are the same information with the dimension the screenshot lacks.
The practical consequence is that evidence has to be designed before the period it covers, not collected after it. An organisation that decides in January what each control will produce, and where it will be filed, arrives at the assessment with a folder. An organisation that starts in the fortnight before arrives with screenshots and a story, and the story is usually true — which makes failing on it particularly frustrating.
By control family
What each family has to produce
Governance and policy
Approved documents with a version history, an approval date and an owner, plus the record of the review that kept them current.
What gets rejected: A policy adopted last month covering a twelve-month assessment period.
Asset management
The inventory itself, plus the record of it being reconciled — dated, with what changed each time.
What gets rejected: A spreadsheet with no modification history, which cannot show it was maintained.
Identity and access
The dated access review record with a reviewer named, and the tickets showing what was revoked as a result.
What gets rejected: A current user list. It shows today's state and nothing about review.
Vulnerability management
Scan history across the period with remediation timelines against the policy's own targets.
What gets rejected: One recent scan report showing few findings.
Logging and monitoring
Retention configuration, a sample export from across the period, and the record of alerts being actioned.
What gets rejected: A screenshot of the logging dashboard, which shows collection but not action.
Incident management
The incident register including minor incidents, plus at least one exercise record with the lessons recorded.
What gets rejected: An empty register. It reads as no detection rather than no incidents.
Third-party management
The supplier register with the security terms in each contract, and the assessment record for the material ones.
What gets rejected: A contract list with no security clauses identified and no assessment behind it.
Designing it
Making the record a by-product
The organisations that find assessments cheap are not the ones with more controls. They are the ones whose controls produce their own evidence without anybody being asked to write something down afterwards.
1 · Name the artefact per control
One line per control: what will be produced, by whom, how often, and where it will be filed. Written once, and it is the document that makes the next three steps possible. An evidence register, which is itself an artefact assessors like.
2 · Move it into the workflow
Access reviews raised as tickets that require a sign-off to close. Patch cycles recorded by the deployment system. Policy reviews scheduled as calendar items with an approver. The evidence is generated by doing the work. Records with dates and names, produced without extra effort.
3 · Sample it quarterly
Pull five controls at random each quarter and check the evidence would satisfy an assessor. Quarterly sampling finds the control that quietly stopped producing its record months before the assessment does. Drift caught while it is cheap to correct.
4 · Assemble, do not reconstruct
The month before the assessment is collation and a read-through against the published control text, not evidence creation. If it is creation, the assessment will show that. An assessment that measures the controls rather than the preparation.
Our role
How the evidence gets built
Evidence holds when it is produced by the control that runs, in the period it ran. That is a design problem before it is a documentation one, and it is the part we take on.
- 01
Designing what each control produces
We design the artefact each control should generate and put its production inside the workflow that runs it, so evidence accumulates instead of being assembled.
- 02
Reviewing it against the control text
We read the assembled evidence against the published wording before the assessment and say where it will not hold, while there is still time to fix the underlying control.
- 03
Saying when a period is not covered
Where a control did not operate over the period, we say so, so it is disclosed on your terms rather than discovered on someone else's.
The assessor then reads the pack as its own record, which is the standard it is written to meet.
The Essential Cybersecurity Controls are published by the National Cybersecurity Authority. Work from the published document, and take any applicability question to the Authority or to your assessor. Source
Common questions
What buyers ask
Our assessment is in six weeks. Is it too late?+
Not to improve the outcome, but the honest framing matters. Evidence for a period that has already passed cannot be created — what can be done in six weeks is assembling what genuinely exists, finding the controls where the record is missing, and deciding for each whether to disclose the gap or start the record now and state its start date. Disclosing is nearly always better received than an artefact whose dates do not survive a question.
How much evidence is enough per control?+
Enough to show the control operated across the period, which for most controls is a sample rather than everything. A quarterly access review needs the four records, not every ticket they generated. Volume is not a substitute for coverage: a thousand pages that all date from the same fortnight demonstrate less than four dated records spread across the year.
Can evidence be produced in Arabic or English?+
Confirm with your assessor, and confirm before the period rather than during it. System-generated records are frequently English because the tooling is, while policies and approval records are commonly Arabic — a mixed pack is normal and is not usually an issue, but where a specific document is expected in a specific language, that is much cheaper to know in advance than to translate under time pressure.
In this cluster
Next step
Review your evidence before the assessment
An evidence design that makes the record a by-product of running the control, so the next assessment needs assembly rather than reconstruction.
Review your evidence before the assessment
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
