12 | Keep a defined, up-to-date cloud outsourcing strategy | 0 |
13 | Assign responsibilities, resource compliance and set up oversight of cloud outsourcing | 0 |
14 | Monitor cloud service provider performance, security and service levels on a risk basis | 0 |
15 | Reassess whether each arrangement is critical or important | 0 |
16 | Maintain a register of all cloud outsourcing arrangements | 0 |
17 | Record the required details for every critical or important arrangement | 0 |
18 | Define what the register holds for non-critical arrangements | 0 |
19 | Before outsourcing: assess criticality, risks, due diligence and conflicts of interest | 0 |
20 | Make the pre-outsourcing analysis proportionate and cover operational, legal, compliance and reputational impact | 0 |
21 | For critical or important functions: assess the full risk picture and weigh costs and benefits | 0 |
22 | Evaluate the suitability of the cloud service provider for critical or important functions | 0 |
23 | Use certifications and audit reports to support due diligence where appropriate | 0 |
24 | Review or redo due diligence when significant deficiencies or changes come to light | 0 |
25 | Decide on a risk basis whether new due diligence is needed for a new or renewed arrangement with an assessed CSP | 0 |
26 | Set out the rights and obligations of firm and provider in a written agreement that the firm can terminate | 0 |
28 | Include the minimum contractual elements for critical or important functions | 0 |
29 | Set information security requirements in policy and contract and monitor compliance | 0 |
30 | For critical or important functions: apply the minimum information security measures | 0 |
31 | Be able to exit critical or important cloud arrangements without undue disruption | 0 |
32 | Build the exit strategy around objectives, triggers, impact analysis, roles, testing and success criteria | 0 |
33 | Monitor for exit trigger indicators as part of ongoing oversight | 0 |
34 | Keep the contract from limiting the firm's and the competent authority's access and audit rights | 0 |
35 | Scale the exercise of access and audit rights to criticality and risk | 0 |
36 | Agree alternative assurance where an audit would put the provider's environment at risk | 0 |
37 | Use third-party certifications, audit reports and pooled audits to use audit resources efficiently | 0 |
38 | Assess the adequacy of certifications and reports for critical or important functions and avoid sole reliance | 0 |
39 | Rely on certifications and reports only when the scope, currency, auditor, standards and rights are satisfactory | 0 |
40 | Give the provider reasonable prior notice of on-site visits, except in emergencies | 0 |
41 | Staff audits and report reviews with people who have the skills for cloud services | 0 |
42 | Where sub-outsourcing of critical or important functions is permitted, set the contractual conditions | 0 |
43 | Make sure the provider oversees its sub-outsourcers | 0 |
44 | Notify the competent authority in writing of planned critical or important cloud outsourcing | 0 |
45 | Include the required content in the notification | 0 |
46 | Guideline 9: supervision by competent authorities | 0 |