Many organizations in the Kingdom pass a first NCA CCC review, close the findings, and then see the same ones again at the next check. Cloud misconfiguration recurring findings against NCA CCC are rarely a sign that teams are careless. They are usually a sign that the fix was applied in the wrong place.
This article describes a pattern that is common in cloud reviews across regulated sectors, and sets out how to trace a recurring finding to its source, decide what belongs in templates and guardrails, and set drift alerts that connect to specific control areas.
The pattern in brief
A review identifies a finding: a storage container readable from the internet, a management port open to any address, or a role with far wider permissions than its function needs. The operations team corrects it in the cloud console. The finding is marked closed and the evidence is filed.
Weeks later the same finding appears again. Nothing was reversed by hand. The infrastructure code or deployment template that created the resource still contains the original setting, and the next pipeline run, scheduled redeployment or environment rebuild puts the flaw back.
The console fix changed the running state. It did not change the source of truth. Until both match, the finding is only paused.
How this shows up by sector
The mechanics are the same everywhere, but the visible form differs.
- Banking and financial services: Platform teams often maintain shared templates for application landing zones. A permissive role or an open administrative port defined once in a shared module is copied into every new environment, so each project reintroduces it.
- Healthcare: Storage used for imaging, exports or analytics is frequently created by project teams from older templates. Public access settings and missing encryption options reappear whenever a project is redeployed.
- Government and public entities: Responsibility is often split between a central cloud team and supplier-managed workloads. A fix made by one party is overwritten by the other's pipeline.
- Retail and telecom: Fast release cycles and many short-lived environments mean test configurations, including open ports used for debugging, are promoted to production by template reuse.
These are typical patterns rather than a description of any single organization.
Step 1: Trace a recurring finding to its source
Treat every repeated finding as a question of origin. For each one, work through the following in order.
- Identify the resource and how it was created. Resource tags, deployment history and audit logs show whether it came from a template, a pipeline, a script or a manual action.
- Locate the definition. Find the code or template that declares the resource, and the shared module it inherits from, if any.
- Compare declared and running state. If the template says one thing and the console shows another, you have found the gap.
- Find every other consumer. A flawed shared module affects every environment built from it, not only the one in the report.
- Record the owner. Someone must own the template, not only the resource.
Most recurring findings resolve at step 2 or 3. The remainder usually come from identity: roles granted manually, then granted again by automation.
Step 2: Decide what belongs in templates and guardrails
Not every fix should live in the same place. A useful way to decide is to ask how often the flaw could be reintroduced and how serious it is.
Fix in the template
Anything that a deployment creates should be corrected where it is defined. This includes default storage access settings, encryption options, network rules for management ports, and role definitions. Once the template is corrected, redeployment reinforces the fix instead of undoing it.
Enforce with a guardrail
For settings that must never be permitted, such as public storage access or administrative ports open to any source, a preventive policy at the account or subscription level stops the configuration from being created, whatever the template says. Guardrails protect you from templates you have not reviewed yet and from manual changes.
Keep as a monitored exception
Some configurations are legitimate for a defined period. These should have a named owner, a documented reason and an expiry date, and should be monitored rather than silently tolerated.
The aim is layered: correct templates, preventive guardrails, and detection for whatever gets through.
Step 3: Tie drift alerts to NCA CCC
The Cloud Cybersecurity Controls (CCC) published by the National Cybersecurity Authority (NCA) cover areas such as identity and access management, network security, data protection and cryptography, and logging and monitoring for cloud environments. Drift alerts are most useful when each one points to the control area it affects, because the alert then doubles as evidence for the next review.
A simple structure works well:
- Storage exposure alerts map to the data protection and access control requirements.
- Open management port alerts map to the network security and remote access requirements.
- Excessive role alerts map to the identity and privilege management requirements.
- Logging disabled or altered alerts map to the logging and monitoring requirements.
Each alert should carry the resource, the owner, the template it came from if known, and the fix guidance. We recommend confirming exact control references against the current published NCA CCC text rather than relying on informal mappings.
Step 4: Close the loop with owners
Detection that does not reach a named owner produces a growing list rather than a falling one. For each alert, agree who corrects the resource, who corrects the template, and how closure is verified. Closure should mean that the template and the running state both match the policy, and that a redeployment in a test environment does not bring the finding back.
Reviewing closed findings for recurrence is a worthwhile habit in itself. A finding that returns twice indicates a missing guardrail, not a missing reminder.
A short checklist for the next review
- Can every production resource be traced to a template or a documented manual change?
- Are shared modules reviewed against policy before they are reused?
- Are the settings that must never occur blocked by preventive policy?
- Does each drift alert state the NCA CCC control area it relates to?
- Are exceptions owned, justified and time-limited?
How this becomes routine
Managing posture continuously is mostly a matter of keeping this loop running month after month. Our Managed Cloud Security Posture service is built around that loop. The process runs through four stages: connect, baseline, monitor and improve.
Monitoring uses read-only access to accounts and subscriptions, so your teams keep control of changes. The service provides continuous configuration monitoring, mapping to NCA CCC and your baseline, and drift alerts with fix guidance. We also review identity and privilege, which is where many recurring findings originate. The deliverables are a cloud posture baseline, a monthly posture report, a findings tracker and control mapping evidence.
If your cloud accounts have passed one review but keep producing the same findings, the first useful step is to trace them to their source. A conversation about your current templates and findings is a practical place to begin.