1 | Title, commencement, definitions, purpose and scope | 0 |
10 | Plan the transition and check legal, consent, policy, data governance and architecture constraints first | 0 |
11.1 | Perform proportionate due diligence on every CSP, direct or via intermediary, with a documented business case | 0 |
11.13 | Conduct an initial security and risk assessment, a TVRA, continuity, financial and standards checks before implementation | 0 |
11.8 | Examine the CSP's track record, recovery capability, every location, security controls and regulatory adherence | 0 |
12 | Govern sub-contracting of material functions by contract and review sub-contractors' compliance | 0 |
13.1 | Use a written agreement with termination rights and the prescribed terms for material arrangements | 0 |
13.4 | Obtain QCB approval before signing or materially modifying any material arrangement | 0 |
14 | Plan a post-implementation review before signing and run it with the CSP | 0 |
15 | Assess every cloud arrangement fully each year and use compliance as a renewal criterion | 0 |
16 | Secure access, audit and information rights equivalent to direct management, for the entity and for QCB | 0 |
17 | Integrate cloud into business continuity, assess substitutability and test with the CSP | 0 |
18 | Provide for termination: data return and removal, termination triggers, minimum execution period and CSP exit assistance | 0 |
19 | Keep a documented exit plan covering stressed and managed exit | 0 |
20 | Remain accountable for key management with documented access procedures, least privilege and full log access | 0 |
21 | Protect data on a need-to-know basis, segregate tenants, protect data at rest, in motion and in memory, keep PII and financial data in Qatar and obtain QCB approval | 0 |
22 | Perform regular cloud security testing by service model, using third parties or CSP-provided reports where direct testing is not allowed | 0 |
23 | Seek any exemption from QCB with a linked requirement, business case, approvals, a register entry and an expiry date | 0 |
6 | Keep a defined, periodically reviewed cloud computing strategy with resources, policies and an implementation roadmap | 0 |
7 | Board and senior management govern technology and cloud risk with defined appetite and an oversight function | 0 |
8 | Maintain an approved cloud governance policy with the required content and apply it to every arrangement | 0 |
9 | Keep a complete register of cloud arrangements with the prescribed fields, disclose it to QCB annually and cover intermediaries and primary sub-contractors | 0 |