Sushegaad/Claude-Skills-Governance-Risk-and-Compliance / plugins/saudi-arabia-grc/skills/saudi-arabia-grc
saudi-arabia-grc
VerifiedSaudi Arabia Governance, Risk & Compliance advisor - a compliance router that first determines WHICH Saudi regulations apply (NCA ECC-2:2024, NCNICC-1:2025 private-sector controls, Saudi PDPL, NCA Cloud Cybersecurity Controls, SAMA Cyber Security Framework, CST cloud regulations, DCC/OTCC/TCC), then guides framework-specific compliance. Use for any Saudi Arabia / KSA compliance question: NCA Essential Cybersecurity Controls, SDAIA and the Personal Data Protection Law (نظام حماية البيانات الشخصية), PDPL breach notification and data transfers, SAMA compliance for banks/insurers/fintechs, cloud data residency in the Kingdom, CST CSP registration, government/CNI cybersecurity obligations, market-entry compliance ("expanding to Saudi Arabia"), gap assessments, and mapping Saudi requirements to ISO 27001 / NIST CSF / SOC 2. Trigger for any KSA, Riyadh, Vision 2030 compliance, NCA, SDAIA, SAMA, or Saudi data protection question even if no framework is named.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.9 KB |
| references/nca-cloud-ccc.md | markdown | 2.4 KB |
| references/nca-ecc.md | markdown | 2.5 KB |
| references/sama-csf.md | markdown | 1.9 KB |
| references/saudi-pdpl.md | markdown | 2.7 KB |
| references/sector-applicability.md | markdown | 2.7 KB |
references/nca-cloud-ccc.md
View on GitHub# Saudi Cloud Stack - NCA CCC + CST Cloud Regulations
## NCA Cloud Cybersecurity Controls (CCC)
Baseline: **CCC-1:2020**, with an updated **CCC-2:2024** reflected on NCA's site (data-localization responsibility referenced to NDMO). Extension of the ECC for cloud.
- **Role-split control IDs**: CSP-side controls (e.g., 1-3-P-1-1) vs tenant-side controls (e.g., 1-3-T-1-1) - always identify whether the user is the provider or the tenant before citing obligations.
- **Cloud levels tied to data classification** (Top Secret / Secret / Confidential / Public): higher classifications require higher-level cloud environments and stricter controls.
- Applies to CSPs serving ECC-covered entities and to those entities as tenants; tenant remains accountable for its data.
## CST Cloud Computing Services Provisioning Regulations (2023)
- The operative CST instrument is the **Cloud Computing Services Provisioning Regulations**, effective **October 10, 2023**, which replaced the Cloud Computing Regulatory Framework (history: CCRF v2, repealed December 2020, then CCRF v3, then the 2023 Regulations).
- **CSP registration with CST** is required to operate, with provider registration classes under the 2023 Regulations.
- Residency under the current regime distinguishes **Saudi Government Data**, which must remain in-Kingdom (narrow exceptions only), from **Non-Government Data**.
- The CCRF v2 scheme of customer data Levels 1-4 with in-Kingdom residency for Levels 3-4 is **repealed**; do not cite it as current.
- For registration class thresholds and other specifics, direct users to CST's published 2023 Regulations.
## Practical routing
| Situation | Obligations |
|---|---|
| Hyperscaler/CSP entering KSA | CST registration under the 2023 Regulations + CCC CSP-side controls + PDPL (processor posture) for personal data |
| Government entity adopting cloud | ECC + CCC tenant-side controls + in-Kingdom hosting; classification drives cloud level |
| Private SaaS selling to government | Treat as CSP for that workload: CST registration, CCC CSP controls, in-Kingdom residency for government data |
| Private company using foreign cloud for its own data | PDPL transfer rules for personal data; CCC only if ECC-covered |
Cite CCC control IDs only with the role marker and only from confirmed knowledge; otherwise cite by domain and direct to the official CCC document and its methodology/mapping annex.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |