Mauritius

Bank of Mauritius Guideline on Use of Cloud Services (2022)

42 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

42 controls 0 frameworks share controls with it Mauritius verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1.1Hold a board-approved cloud strategy0
1.2Maintain a risk-based, board-approved policy for the use of cloud services0
1.3Board retains ultimate responsibility and discharges the named oversight duties0
1.3.2.xiReceive a comprehensive report before approving any material cloud service0
1.4Branches and subsidiaries of foreign banks adopt group strategy and policy only where they meet the guideline0
1.5Senior management oversees design, implementation and ongoing performance of cloud services0
10.1.iSet, agree and test business continuity requirements for material services0
10.1.vKeep documented and regularly reviewed exit strategies with the minimum content0
11.1Know, assess and control subcontracting of material services0
12.1Keep an updated register of all cloud services0
12.2Submit the Return on Use of Cloud Services to the Bank0
12.3Report cloud incidents to the Bank promptly0
13Transitional arrangement and the Annex schedules0
2.1Document a risk assessment covering the named elements0
3.1Assess materiality against the minimum factors0
4.1Notify the Bank at least 60 days before deploying a material cloud service, with a CEO attestation0
4.3Include outsourcing and subcontracting details in the notification and notify material subcontracting changes0
5.1Conduct proportionate due diligence on the provider before use0
5.3For material services, cover the named due diligence elements and document and approve the result0
6.1Use a written agreement that secures access to cloud-held information for the institution and the Bank0
6.2Agreements for material and customer-information services protect supervision, data protection and confidentiality0
6.3.iAgreements for material services grant audit, access and cooperation rights to the Bank, the institution and their auditors0
6.3.iiiAgreements for material services cover exit, record keeping, notice of changes, the Bank's step-in, termination, deletion, incidents and governing law0
7.1Determine security controls in line with risk appetite and the characteristics of the service0
7.2.iKnow the provider's security measures, assess vulnerabilities regularly and keep cloud controls at least as strong as on premise0
7.2.ivObtain assurance over the hypervisor and safeguard against virtualisation risks0
7.2.viKeep an inventory of IT assets on the cloud and apply proportionate identity, access and network controls0
7.2.viiiEncrypt data at rest and in transit and manage encryption keys under institution control0
7.2.xiSegregate, protect and identify the institution's data0
7.2.xiiSecure containers, microservices and APIs0
7.2.xvOperate an incident management process and centralised visibility over core cloud components0
7.2.xviiEncrypt point-to-point connectivity, use dual connectivity from Mauritius and keep logs and audit trails0
7.2.xxMitigate concentration risk by provider and by geography0
7.2.xxiApply the enhanced controls required for public cloud0
8.1Set risk-based review, testing and audit frequency, at most 18 months for material services0
8.3Review material and customer-information services end to end0
8.4Rely on third-party reports and pooled audits only with the named safeguards0
8.6Resource the control functions and have them and the external auditors review cloud services periodically0
8.8Assess vulnerabilities before deploying a material service and penetration test immediately after0
9.1Know where data is hosted and satisfy the data location conditions0
9.2Have the data location assessment done by a competent officer or reputable firm0
9.3Agree the list of processing locations and control any processing outside it0

Tell me when Bank of Mauritius Guideline on Use of Cloud Services (2022) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for Bank of Mauritius Guideline on Use of Cloud Services (2022), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition