Techbanq

After an assessment

Most of the findings are not technical

Sort the report before you respond to it. In most failed assessments the majority of findings are controls that exist and were never written down, and buying technology for those closes nothing.

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

Project team in a working session around a meeting table

Cybersecurity credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Triage

Three kinds of finding, and only one needs a purchase

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 first kind is a control that exists and was not evidenced. Access is reviewed quarterly, but nobody records that it happened, so the assessor has nothing to look at and records a gap. This is the largest group in most failed assessments, and the fix is a written procedure and a record of it being followed — no product, no project, a few days of somebody's time.

The second is a control that exists and has no owner. Somebody does it, but if that person leaves, it stops, and there is no policy that would tell the next person to start. Assessors record these because a control that depends on one individual is not a control. The fix is naming an owner and a frequency, and again it is writing rather than buying.

The third is a control that genuinely does not exist — no logging on a critical system, no multi-factor authentication on remote access, no segmentation between environments. This group needs work and sometimes needs spend, and it is usually the smallest of the three. Sorting the report this way before responding is the difference between a remediation plan and a shopping list, and assessors can tell which one they have been handed.

The plan

What a remediation plan has to show

Assessors accept plans, not intentions. Each row below is something the plan has to state per finding, and a plan missing any of them tends to come back with questions rather than acceptance.

Accepted or disputed

A position on each finding, with evidence attached where you are disputing it.

Why the assessor wants it: Silence reads as acceptance, and a genuine misunderstanding closes cheaply if it is raised.

A named owner

A person and a role, not a department. Departments do not close findings.

Why the assessor wants it: It is the single strongest predictor of whether a finding actually closes.

A date that is credible

Staged where the work is large: an interim mitigation date and a full remediation date.

Why the assessor wants it: Twenty findings all dated the same Thursday tells the assessor the plan was written in one sitting.

Interim risk treatment

What reduces the exposure between now and the remediation date, or a stated acceptance of it.

Why the assessor wants it: A twelve-month remediation with nothing in between is an unmanaged risk in writing.

The evidence you will produce

Named artefacts: this policy, this log export, this signed review record.

Why the assessor wants it: It settles at planning time what would otherwise be argued at retest.

What prevents recurrence

The recurring check that would catch this drifting again, and who runs it.

Why the assessor wants it: Without it the same finding returns at the next assessment, and the second time it is worse.

What goes wrong

Four expensive responses to a findings report

  1. 01

    Buying a platform for a documentation gap

    The finding says access reviews are not evidenced. A tool is procured to run access reviews. Six months later the tool runs them and still nobody signs the output, so the finding stands and there is now a licence to renew.

  2. 02

    Treating every finding as equally urgent

    Forty findings, all worked in parallel, none finished by the deadline. Assessors accept a plan that closes the severe ones first and stages the rest; they do not accept forty items at eighty percent.

  3. 03

    Writing policy nobody will follow

    A forty-page document adopted to close a finding, describing a process the organisation does not run. It closes the finding once and fails the next assessment harder, because the gap is now between the policy and practice rather than an absence.

  4. 04

    Not asking the assessor what they will accept

    The cheapest conversation available, and the one people avoid because a failed assessment feels adversarial. Assessors will normally say what evidence closes a finding, and the answer is frequently narrower than the assumption behind the project that got scoped.

Where we sit

We work on your side of the assessment

What we do

  • Triage the findings report and produce the plan, including the position on anything worth disputing.
  • Write the procedures where the control exists and was never documented — which is most of the list.
  • Do the technical remediation and produce the evidence the retest needs.

The assessor decides what closes a finding. Ask them directly what evidence they will accept before scoping any remediation work — it is the cheapest step available and it frequently narrows the project substantially.

Primary source

Common questions

What buyers ask

Can we dispute a finding?+

Yes, and it is worth doing where you have evidence the assessor did not see — a control that was running but was not shown, a system that was out of the agreed scope, a requirement read more broadly than the framework states. Dispute with the evidence attached rather than with an argument. What does not work is disputing on the basis that the finding is inconvenient or that the risk is low; the second of those is a risk acceptance, which is a different response and should be written as one.

How long does remediation usually take?+

The documentation group closes in weeks — it is writing, review and a signature. The ownership group closes in a similar time but needs a decision from someone senior enough to assign it. The genuinely missing controls are where the months are, and how many months depends entirely on whether the work is configuration or architecture. A plan that stages these three groups differently is more credible than one that gives everything the same date, and it is also more likely to be true.

Should the firm that helps us remediate also do the retest?+

No. Whoever assesses should be independent of whoever remediated, and most frameworks say so explicitly. Where the same firm does both, the assessment carries less weight with everyone who reads it afterwards — a customer, an insurer, the next assessor. This is one of the few places in procurement where splitting the work across two suppliers is straightforwardly the right answer rather than a trade-off.

Send us the findings report

A triage session over the findings report that produces a plan an assessor will accept, before anything is bought.

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.