Techbanq

NCA · cloud

The provider's half is documented. Yours is the one being assessed

Every major provider publishes where its responsibility ends. Almost every finding on a cloud estate sits on the other side of that line — in identity, logging, network design and the accounts nobody owns.

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

Market
Saudi Arabia
Written for
CTO, CISO
Decision
Bring a cloud estate in line with the Authority's controls

Cybersecurity credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA ECC

    ECC compliance expertise

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The split

Who holds which half, control family by control family

The provider publishes its side and it is genuinely reliable. What follows is the customer side, which is where assessments spend their time.

Identity and access

Every human and machine identity in the account, the permissions attached to them, and the review that removes what is no longer needed.

Evidence the estate should produce: A dated access review with names against it, and a record of privileged sessions.

Logging and monitoring

Which logs are enabled, where they are retained, who reads them, and whether an alert reaches a person.

Evidence the estate should produce: Retention configuration and a sample of alerts with the response recorded.

Network design

Segmentation between environments, what is reachable from the internet, and the justification for each exposure.

Evidence the estate should produce: A current diagram that matches the account, and a review record for public endpoints.

Data protection

Classification, encryption configuration, key custody, and where data is permitted to sit.

Evidence the estate should produce: Key management records and a residency position your legal function has signed.

Change and configuration

How infrastructure changes are proposed, reviewed and applied, and what stops a manual change in the console.

Evidence the estate should produce: Change history from the pipeline, and drift detection output.

Recurring findings

What cloud estates are actually found on

Consistent across the reviews we have run, and none of it exotic. Each is cheaper to close before an assessment than to explain during one.

  1. 01

    The account nobody owns

    A project account opened for a pilot, still running, outside the landing zone and outside the logging configuration. It is found by billing rather than by inventory, which is why it survives so long.

  2. 02

    Logs enabled, retention default

    The control is switched on and the retention window is shorter than the period the assessment covers. The evidence for month one no longer exists when it is asked for in month nine.

  3. 03

    Machine identities with standing permissions

    Pipeline and service credentials created broadly during a migration and never narrowed. They pass a policy review because nobody classifies them as access, and they are the most useful thing an attacker finds.

  4. 04

    A diagram that describes last year

    Network evidence is judged against the account, not the drawing. Where they disagree the assessor works from the account, and the difference becomes a governance finding rather than a technical one.

Residency

A region setting is not a residency position

Selecting a local region is the easy part and it is not the answer to the question. Backups, logs, support access and managed-service control planes each have their own geography, and the ones that surprise organisations are the operational tiers: a support engineer in another region with break-glass access is a data flow whether or not anybody wrote it down.

The determination itself belongs to your legal and compliance function, working from the applicable regulation and your own contracts. What an engineering review can do is give them an accurate map: every location data actually reaches, including the ones the architecture diagram omits, so the position they write is defensible rather than optimistic.

Our role

What we do on the cloud side of the line

  1. 01

    Establishing the position

    We read the published control text against what is actually running and record where you stand, in the words the assessment will use rather than in ours.

  2. 02

    Doing the work

    The remediation is ours — the engineering, the process change and the documentation — rather than a findings list handed to somebody else to implement.

  3. 03

    Leaving evidence behind

    Each control is set up to generate its own record as it runs, so the next assessment costs a fraction of this one.

Residency determinations stay with your legal function and the assessment stays with your assessor; the engineering evidence both of them need is what we produce.

The controls are published in full by the National Cybersecurity Authority. Work from that document rather than from a supplier's summary of it, and take applicability questions to the Authority or to your assessor. Source

Common questions

What buyers ask

Does using a local cloud region make us compliant?+

It settles one question out of several. Residency is about where data rests and is processed, including backups, logs and support access; the control set also asks about identity, logging, segmentation and change management, none of which is affected by the region selector. A local region is frequently necessary and never sufficient.

Our provider is certified. Does that cover us?+

It covers the provider's half, and that half is genuinely covered — the certifications and audit reports are real and worth collecting for your evidence pack. The assessment then looks at your configuration on top of it, which is where the findings are. Provider assurance is a document you file; it is not a control you operate.

How long does a cloud review take?+

Two to four weeks for a single-provider estate with a defined account list, longer where accounts have to be discovered first. The discovery is usually the interesting part: the accounts nobody remembered are also the ones with the findings, and they are found through billing and DNS rather than through the inventory.

Next step

Review the cloud estate against the controls

A cloud estate reviewed against the control set with the responsibility line drawn explicitly, so the remediation list contains only work that is actually yours.

Review the cloud estate against the controls

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.