1.1 | Hold a board-approved cloud strategy | 0 |
1.2 | Maintain a risk-based, board-approved policy for the use of cloud services | 0 |
1.3 | Board retains ultimate responsibility and discharges the named oversight duties | 0 |
1.3.2.xi | Receive a comprehensive report before approving any material cloud service | 0 |
1.4 | Branches and subsidiaries of foreign banks adopt group strategy and policy only where they meet the guideline | 0 |
1.5 | Senior management oversees design, implementation and ongoing performance of cloud services | 0 |
10.1.i | Set, agree and test business continuity requirements for material services | 0 |
10.1.v | Keep documented and regularly reviewed exit strategies with the minimum content | 0 |
11.1 | Know, assess and control subcontracting of material services | 0 |
12.1 | Keep an updated register of all cloud services | 0 |
12.2 | Submit the Return on Use of Cloud Services to the Bank | 0 |
12.3 | Report cloud incidents to the Bank promptly | 0 |
13 | Transitional arrangement and the Annex schedules | 0 |
2.1 | Document a risk assessment covering the named elements | 0 |
3.1 | Assess materiality against the minimum factors | 0 |
4.1 | Notify the Bank at least 60 days before deploying a material cloud service, with a CEO attestation | 0 |
4.3 | Include outsourcing and subcontracting details in the notification and notify material subcontracting changes | 0 |
5.1 | Conduct proportionate due diligence on the provider before use | 0 |
5.3 | For material services, cover the named due diligence elements and document and approve the result | 0 |
6.1 | Use a written agreement that secures access to cloud-held information for the institution and the Bank | 0 |
6.2 | Agreements for material and customer-information services protect supervision, data protection and confidentiality | 0 |
6.3.i | Agreements for material services grant audit, access and cooperation rights to the Bank, the institution and their auditors | 0 |
6.3.iii | Agreements for material services cover exit, record keeping, notice of changes, the Bank's step-in, termination, deletion, incidents and governing law | 0 |
7.1 | Determine security controls in line with risk appetite and the characteristics of the service | 0 |
7.2.i | Know the provider's security measures, assess vulnerabilities regularly and keep cloud controls at least as strong as on premise | 0 |
7.2.iv | Obtain assurance over the hypervisor and safeguard against virtualisation risks | 0 |
7.2.vi | Keep an inventory of IT assets on the cloud and apply proportionate identity, access and network controls | 0 |
7.2.viii | Encrypt data at rest and in transit and manage encryption keys under institution control | 0 |
7.2.xi | Segregate, protect and identify the institution's data | 0 |
7.2.xii | Secure containers, microservices and APIs | 0 |
7.2.xv | Operate an incident management process and centralised visibility over core cloud components | 0 |
7.2.xvii | Encrypt point-to-point connectivity, use dual connectivity from Mauritius and keep logs and audit trails | 0 |
7.2.xx | Mitigate concentration risk by provider and by geography | 0 |
7.2.xxi | Apply the enhanced controls required for public cloud | 0 |
8.1 | Set risk-based review, testing and audit frequency, at most 18 months for material services | 0 |
8.3 | Review material and customer-information services end to end | 0 |
8.4 | Rely on third-party reports and pooled audits only with the named safeguards | 0 |
8.6 | Resource the control functions and have them and the external auditors review cloud services periodically | 0 |
8.8 | Assess vulnerabilities before deploying a material service and penetration test immediately after | 0 |
9.1 | Know where data is hosted and satisfy the data location conditions | 0 |
9.2 | Have the data location assessment done by a competent officer or reputable firm | 0 |
9.3 | Agree the list of processing locations and control any processing outside it | 0 |