2.10 | Secure business continuity for the assigned services | 0 |
2.11 | Agree change management arrangements with the provider | 0 |
2.12 | Assess the provider's country before placing data there and bind the provider to disclose compelled access | 0 |
2.13 | Maintain a documented, tested termination plan with data retrieval and deletion | 0 |
2.2.1 | Board approves the cloud computing policy and follows its implementation | 0 |
2.2.2 | Senior executive management discharges the named cloud governance duties | 0 |
2.3.1 | Policy defines the services and data to be assigned, their classification and the chosen models | 0 |
2.3.2 | Policy sets data handling, security controls, provider assessment standards and expected outcomes | 0 |
2.3.3 | Policy addresses integration, multi-provider interoperability, customer data protection and oversight mechanisms | 0 |
2.4.1 | Integrate cloud risks into the company's risk assessment framework with the minimum content | 0 |
2.4.2 | Set key risk indicators and monitor failure, customer impact, security and concentration risks | 0 |
2.5.1 | Contracts carry the minimum commercial, control and governance terms | 0 |
2.5.2 | Contracts protect data ownership, require consent to material changes and fix data locations | 0 |
2.5.3 | Contracts require cooperation with third parties, consent to subcontracting, incident notification and the Central Bank's supervisory access | 0 |
2.5.4 | Contracts state termination rights clearly and contain no impediment to immediate termination | 0 |
2.5.5 | Cloud service level agreement sets the minimum performance and security terms | 0 |
2.6.1 | Keep full responsibility, notify the Central Bank on contracting, resource supervision and secure on-site visit rights | 0 |
2.6.2 | Put in place the procedures that let the Central Bank supervise | 0 |
2.7.1 | Protect data through physical security, classification, segregation, backup ownership and loss mitigation | 0 |
2.7.2 | Encrypt data at rest, in transit and in backups under controlled key management | 0 |
2.7.3 | Assess tokenisation solutions and keep tokenised data out of the provider's reach | 0 |
2.7.4 | Define incident handling and run periodic penetration tests and vulnerability scans with the provider | 0 |
2.8.1 | Control the provider's access to company systems and separate duties | 0 |
2.8.2 | Guarantee effective, unrestricted access to the company's own data | 0 |
2.9 | Monitor security events and retain unrestricted access to the provider's log files | 0 |
3 | Chapter 3 reference standards and the appendix of Central Bank instructions | 0 |