Techbanq

Saudi compliance · the evidence problem

The controls run. The proof is the part that is missing

Access is reviewed, patches land, incidents get handled — and when an assessor asks for proof, the organisation has a week of screenshots and a folder of undated documents. The gap is not diligence; it is that nothing was designed to leave a trail. The remedy is structural: evidence produced by operating, catalogued as it appears.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
CISO, CIO, COO
Languages
EN · AR

Enterprise delivery credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The evidence surface

Your systems of record already hold most of the proof

The platforms an estate already runs timestamp and attribute by default. Routed into one register, their ordinary output becomes the evidence an assessment reads — without anyone producing documents for the occasion.

Four operational sources — ticketing, identity, logging, change records — converge into an evidence register indexed by control, which produces an assessment pack, early gap visibility and proof independent of individual staff.

  • Ticketing and workflow

    Access requests, approvals, incident handling — each closed ticket is a dated, attributed record.

  • Identity platform

    Joiner, mover and leaver events, privilege changes, review campaigns — exportable as system output.

  • Log and monitoring platform

    Coverage, retention, alerts and their responses — the operating record of the monitoring controls.

  • Change and configuration records

    What changed, who approved it, what the baseline is — proof the hardening controls are governed.

What we do

The evidence register

One catalogue, indexed by control reference: what proves each control, where it comes from, how current it is, and who owns the trail.

  • An assessment pack by retrieval

    Assembling for an assessor becomes filtering the register, not a quarter of archaeology.

  • Gaps visible early

    A control whose register entry has gone stale is flagged months before an assessor would find it.

  • Proof that survives staff changes

    The trail lives in systems and the register, not in the memory of whoever ran the control.

Nothing in this picture is produced for the assessment. That is the point.

The scramble

Why proof assembled in the weeks before an assessment keeps failing

The scramble has a recognisable shape: an assessment date lands, a spreadsheet of controls is divided among teams, and everyone spends evenings exporting, screenshotting and writing summaries of what they have been doing all year. The output looks substantial and shares one fatal property — nearly all of it is dated in the weeks before the assessment. An experienced reader sees a photograph of the estate taken for the occasion, and what an assessment wants is a film: records accumulating across the period because the control ran across the period.

This is also why the scramble punishes precisely the organisations that do the work. A team that genuinely reviewed access all year but recorded nothing holds the same evidentiary position as one that never reviewed at all — and must resort to reconstructions and screenshots that read weaker than the practice they describe. The operating habit that replaces the scramble is small: the moment a control produces something, its output lands in a system of record and its register entry updates. No year-end effort, no heroics — just a trail that exists because the work did.

What counts

The properties that separate accepted proof from rejected proof

Assessment practice differs in detail, but the properties below decide most acceptance questions. A piece of evidence missing one of them invites the follow-up question it cannot answer.

A date, native to the record

Evidence has to place the control in time — operating across the period, not performed once before the visit.

What provides it: System-generated timestamps: exports, ticket histories, log entries. A date typed into a document carries no such weight.

A named, accountable owner

A control nobody owns cannot be interviewed about, and interviews are how documents get tested against reality.

What provides it: Attribution captured by the producing system — who approved, who reviewed, who responded — matching a person who can speak to it.

Provenance from a system of record

Proof is stronger the harder it would have been to fabricate, and weakest when a person could have composed it freely.

What provides it: Exports and reports drawn from the operating platform itself. A screenshot shows one screen at one moment; an export shows the system's account of the period.

Continuity across the period

One good record proves one occasion; the claim being assessed is that the control operates as a practice.

What provides it: A register whose entries accumulate on the control's own cadence, with the gaps as visible to you as they would be to an assessor.

Our role

Turning an unprovable estate into one that documents itself

  1. 01

    The evidence inventory

    For every applicable control we establish what would prove it, what your systems already produce, and where the two do not meet — which is usually a shorter list than the scramble suggested.

  2. 02

    Wiring the trail

    Where a control runs without a record, we adjust how it runs — the review lands in a ticket, the export replaces the screenshot, the register entry updates on the control's cadence — so proof becomes an output, not a task.

  3. 03

    The register and its keeper

    The evidence register ships with an owner and a staleness rule, so an entry going quiet is a signal your team acts on long before it becomes a finding.

What any given assessor accepts remains the assessment's own judgement — what we build is a trail with the properties that judgement consistently looks for: dated, owned, system-produced and continuous.

The controls an estate must be able to evidence sit in the sets the National Cybersecurity Authority publishes — design the trail against the published text, and route acceptance questions to your assessor. Source

Common questions

What buyers ask

Are screenshots ever acceptable as control evidence?+

As a supplement, sometimes; as the trail, no. A screenshot shows one screen at one moment, carries whatever date its filename claims, and could show a configuration changed for the photograph. System exports, ticket histories and log extracts carry their own timestamps and attribution, and reconstructing them dishonestly would take real effort — which is exactly why they read as proof. Where a screenshot is genuinely the only artefact a system can give, anchor it: who captured it, when, from where, filed in the register beside the stronger records.

What does each entry in an evidence register need to carry?+

Six things: the control reference it evidences; what the proof is, concretely — an export, a review record, a closed ticket; the system it comes from; the cadence on which fresh instances should appear; the owner of the trail; and the date of the latest instance. The last two are what make the register operational rather than decorative — the owner is who acts when the trail thins, and the date is how thinning becomes visible. A register carrying only the first three is a mapping document; useful, but it will not warn you.

A control has run for years with no records at all. How do we retrofit proof?+

Forward, not backward. The past cannot be evidenced honestly — do not manufacture records for it, because fabricated history discovered by an assessor damages far more than the gap it hides. Instead, start the trail now: route the control's next run through a system of record, open its register entry, and let instances accumulate. By the time an assessment reads it, the control shows a genuine operating period with a documented start. Pair that with a plain account of when recording began, and you present as an organisation that fixed its evidence problem — which is a materially better position than one still hiding it.

Design the evidence trail

An evidence architecture where every applicable control names its proof, the system that produces it, and the register entry an assessor opens first.

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.