18 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
| Code | Control | Also in |
1 | Who the guidelines bind and how they sit with other law | 0 |
10.1 | Board keeps its responsibilities and discharges the named duties | 0 |
10.2 | Senior management provides effective oversight of cloud deployment and reports incidents | 0 |
11.1 | Be able to retrieve any information held by the provider at any time and keep meeting legal duties | 0 |
2.1 | Implement a risk-based cloud strategy and policy covering the named aspects | 0 |
2.2 | Board approves the strategy and policy and reviews them at least yearly | 0 |
3.1 | Maintain a documented cloud risk management framework with the named content | 0 |
4.1 | Assess materiality against the five factors | 0 |
4.2 | Notify the FSC in writing at least 15 business days before deploying a material cloud service | 0 |
5.1 | Use a written contract with the required cloud clauses | 0 |
5.2 | Control the provider's subcontracting and keep the provider fully liable | 0 |
6.1 | Conduct documented due diligence before engaging a provider | 0 |
7.1 | Maintain a cloud security management framework built on the named elements | 0 |
7.3 | Align security controls with materiality, sensitivity, classification and data location | 0 |
8.1 | Make sure the provider has a contingency plan with continuity and resilience elements | 0 |
8.3 | Hold a well-designed exit strategy and review it with the contingency plans at least yearly | 0 |
9.1 | Apply risk-based, consistently organised ongoing controls and monitoring of providers | 0 |
9.3 | Review all material cloud services at least yearly with skilled auditors and audited providers | 0 |
Tell me when FSC Mauritius Guidelines on Cloud Computing Services (2023) 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 FSC Mauritius Guidelines on Cloud Computing Services (2023), 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