08 Nov 2026 By CISO Consulting team 38 views 5 min read

CST CRF Penetration Testing Scope for Cloud: A Quarterly Plan

A single annual test leaves most cloud assets untested for months. This article shows how to rank assets by exposure and change rate, rotate testing across quarters and keep one tracker as CST CRF evidence.

A security manager and an engineer reviewing a quarterly calendar on a wall screen in a modern office in Riyadh.
In this article
  1. Why one annual test is not enough
  2. Phase 1: Plan
  3. Phase 2: Test
  4. Phase 3: Fix
  5. Phase 4: Retest
  6. Keeping the evidence together
  7. Full list of deliverables
  8. Next step

Defining the CST CRF penetration testing scope for cloud environments is mostly a question of sequencing. The Communications, Space and Technology Commission (CST) sets the Cloud Computing Regulatory Framework (CRF) for providers and for organizations that host workloads with them. A single annual test, however carefully run, examines a moment in time. Most cloud assets then go untested for months while releases, configuration changes and new services continue to arrive.

The approach below ranks assets by exposure and change rate, spreads testing across the quarters, and keeps one tracker that follows every finding to closure. It follows the four phases of our Penetration Testing as a Service: Plan, Test, Fix and Retest. For each phase we describe what happens, who takes part on your side, and what you hold at the end.

Why one annual test is not enough

An annual test covers whatever was in scope on the test dates. A service launched in the second month, or an API changed in the fifth, may never be examined before the next cycle. Auditors reviewing your CST CRF alignment will ask what was tested, when, what was found and how it was closed. A single report answers only the first of those questions well.

A recurring program gives a better answer. Testing runs on a rhythm, each asset has a known place in the calendar, and the evidence builds up through the year.

Phase 1: Plan

What happens. We agree the scope, the rules of engagement and the calendar. This is where the ranking happens. Start with an inventory of cloud assets: internet-facing applications, APIs, mobile back ends, management consoles, network entry points and the cloud accounts or subscriptions that hold them. Then score each asset on two questions:

  • Exposure: is it reachable from the internet, from partners, or only from internal networks?
  • Change rate: how often do releases, configuration changes or infrastructure updates alter it?

Assets that are highly exposed and change often go into the first slot of each quarter, or are tested every quarter. Assets that are exposed but stable, or internal and changing, are tested at least twice a year. Stable, internal assets are tested once in the annual cycle. The result is a rotating calendar in which nothing is left without a scheduled date.

We schedule recurring tests with your releases, so a major release is followed by a test in the next window instead of waiting for a fixed date. The service covers web, mobile, API, network and cloud scope, so the calendar can mix them.

The rules of engagement settle the practical questions: test windows, contacts, escalation if something serious is found, and what is out of bounds. On production, we test only with your written approval and agreed safeguards, within the rules of engagement. The proposal also states who performs the tests: testers may be from our team or a vetted partner under our quality oversight.

At this stage, agree the retest rules in writing:

  1. Every fixed finding is retested, and retesting is included in the service.
  2. The owner marks a finding as fixed in the tracker before a retest is requested.
  3. A finding closes only when the retest confirms it.
  4. Findings that fail retest return to the owner with the reason.

Client participants. The CISO or security manager, the owners of cloud platforms and applications, the release or change manager, and a compliance representative who maps the program to CST CRF.

What you hold at the end. The annual testing calendar, with the agreed scope, rules of engagement and retest rules behind it.

Phase 2: Test

What happens. We run each test in the agreed window. A quarterly slot might cover your most exposed applications and APIs in one quarter, then the network perimeter and cloud configuration in the next, with highly changing assets returning in each. Because the calendar is fixed in advance, your teams know when testing happens and can staff for it.

Client participants. A technical contact available during the window, the platform owners whose assets are in the slot, and the operations team that needs to know when testing traffic is expected.

What you hold at the end. A test report with remediation guidance for that window. Each finding carries enough detail for the owner to reproduce it and fix it.

Phase 3: Fix

What happens. Findings are tracked with your owners in a single tracker shared with your teams. Each entry has an owner, a status and a history. This tracker is what turns separate quarterly reports into continuous CST CRF evidence: one place shows each finding from discovery, through assignment and fix, to confirmed closure.

Keep the tracker disciplined. Use the same statuses for every test, record the date of each change, and avoid parallel spreadsheets. If a finding is accepted rather than fixed, record who accepted it and why, so the decision can be reviewed later.

Client participants. Application and infrastructure owners who carry out the fixes, the security manager who monitors progress, and the risk owner who decides on any accepted risk.

What you hold at the end. A live tracker showing the state of every finding, with named owners.

Phase 4: Retest

What happens. We confirm closure and report. Retesting of fixed findings is included, so owners do not need to wait for the next quarterly slot to prove a fix. Each retest produces a confirmation that the finding is closed, or a note that it remains open.

Each quarter also ends with a findings and trend review. It shows what was found, what has closed, what remains and how the picture changes from one quarter to the next. For a board or an auditor, this is the clearest summary of whether the program is working.

Client participants. Finding owners who request retests, the CISO who attends the quarterly review, and compliance staff who file the outputs as evidence.

What you hold at the end. Retest confirmations, an updated tracker and the quarterly findings and trend review. Our reports are accepted by regulators and auditors.

Keeping the evidence together

For CST CRF, the useful evidence is a connected set: the calendar that shows planned coverage, the reports that show what was tested, the tracker that shows how each finding moved, and the confirmations that show it closed. Store them together and refer to the same asset names in each. When an assessor asks about one cloud service, you can show its place in the calendar, its test results and the closure of each issue.

The same program also supports other frameworks. The service is aligned to SAMA CSF, NCA ECC, PCI DSS and CST CRF, which helps organizations that answer to more than one regulator.

Full list of deliverables

  • Annual testing calendar
  • Test reports with remediation guidance
  • Retest confirmations
  • Quarterly findings and trend review

The service is an annual program, tested quarterly, and managed on your behalf.

Next step

If your cloud assets are tested once a year, or you cannot yet show each finding through to closure, the first step is the Plan phase: an asset ranking and a draft calendar. Penetration Testing as a Service is built around that rhythm. Speak to CISO Consulting about scoping your first annual program.

Tags: CST CRF penetration testing cloud security scoping retesting GRC
C

CISO Consulting team

Cybersecurity Expert

Need help?

Our experts are ready to assist.

Contact Us
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