This page provides AWS financial institution customers with information about the legal and regulatory requirements in Mauritius that may apply to their use of AWS services.
Regulations
-
Can financial institutions use AWS?
Yes. Financial institutions in Mauritius are permitted to use cloud services, provided that they comply with applicable legal and regulatory requirements, such as those described below.
-
Who are the financial regulators?
The Bank of Mauritius has an explicit mandate to formulate and implement monetary policy directed to achieving and maintaining price stability and supervises banking institutions to safeguard the stability and strength of the financial system. The Financial Services Commission (FSC) is responsible for supervising, licensing, and monitoring the activities of non-banking financial services companies.
-
What regulations apply to financial institutions using AWS?
Financial Institutions in Mauritius may be subject to a number of different legal and regulatory requirements when they use cloud services.
Legislation and relevant guidelines issued by the Bank of Mauritius provide a framework for financial institutions in Mauritius when they are planning to use cloud services or offshore data. Key legislation and guidelines include the following:
The above framework covers a variety of contractual and operational areas, including due diligence, risk management, business continuity, and monitoring and oversight.
Customers that have questions about the applicable regulations, and how these may apply to their use of AWS services, can reach out to their account representative.
Regulations are changing rapidly in this space, and AWS is working to help customers proactively respond to new rules and guidelines. AWS encourages its financial institutions customers to obtain appropriate advice on their compliance with all regulatory and legal requirements that are relevant to their business, including other local regulations, guidelines and laws.
-
Key considerations for financial institutions using AWS
AWS is committed to offering customers a strong compliance framework and advanced tools and security measures that customers can use to evaluate meet, and demonstrate compliance with applicable legal and regulatory requirements.
Financial institutions who are using or planning to use AWS services can take the following steps to better understand their compliance needs:
1. Consider the purpose of the workload(s) under consideration and the relevant categories of data in order to anticipate which legal and regulatory requirements may apply.
2. Assess the materiality or criticality of the relevant workload(s) in light of local requirements. For example, under the Guidelines on Outsourcing by Financial Institutions financial institutions should consider the different provisions with regards to “core” and “non-core” activities.
3. Review the AWS Shared Responsibility Model and map AWS responsibilities and customer responsibilities according to each AWS service that will be used. Customers can also use AWS Artifact to access AWS’s audit reports and conduct their assessment of the control responsibilities.
4. Customers who have further questions about how AWS services can enable their security and compliance needs, or who would like more information, can contact their account representative.
-
Key data privacy and protection considerations for financial institutions using AWS
Financial institutions in Mauritius using AWS should also consider applicable privacy requirements, including local privacy requirements in Mauritius. The AWS whitepaper Using AWS in the Context of Common Privacy and Data Protection Considerations provides useful information to customers using AWS cloud services to store or process personal data.
If customers process or are planning to process the personal data of data subjects in the European Union (EU), they should visit AWS’s General Data Protection Regulation (GDPR) Center. More information on these requirements is included in Navigating GDPR Compliance on AWS.
Resources
-
General
-
Compliance Programs
-
General
-
Payment Card Industry Data Security Standard (PCI DSS) on AWS
This guide provides customers with information to be able to plan for and document the Payment Card Industry Data Security Standard (PCI DSS) compliance of their AWS workloads. This includes the selection of controls that meet specific PCI DSS requirements, planning of evidence gathering to meet assessment testing procedures, and explaining their control implementation to their PCI Qualified Security Assessor (QSA).
AWS has many compliance-enabling features that you can use for your regulated workloads in the AWS cloud. These features allow you to achieve a higher level of security at scale. Cloud-based compliance offers a lower cost of entry, easier operations, and improved agility by providing more oversight, security control, and central automation.
The purpose of this paper is to describe how AWS and our customers in the financial services industry achieve operational resilience using AWS services.
This paper provides insight into classification schemes for public and private organizations to leverage when moving data to the cloud. It identifies practices and models currently implemented by global first movers and early adopters, examines how implementation of these schemes can simplify cloud adoption, and recommends practices to harmonize national requirements to internationally recognized standards and frameworks.
This paper addresses: The real and perceived security risks expressed by governments when they demand in-country data residency. Commercial, public sector, and economic impact of in-country data residency policies with a focus on government data. Considerations for governments to evaluate before enforcing requirements that can unintentionally limit public sector digital transformation goals leading to increased cybersecurity risk.
This document is intended to provide information to assist AWS customers with integrating AWS into their existing control framework supporting their IT environment. This document includes a basic approach to evaluating AWS controls and provides information to assist customers with integrating control environments. This document also addresses AWS-specific information around general cloud computing compliance questions.
Guidelines for systematically reviewing and monitoring your AWS resources for security best practices.
Describes general design principles, as well as specific best practices and guidance for the five pillars of the Well-Architected Framework.
The paper discusses using a multi-pronged approach—for example, leveraging virtualization, encryption, and programmatic policies—to build logical security mechanisms that meet and often exceed the security results of physical separation and other on-premises security approaches. Public sector and commercial organizations worldwide can leverage these mechanisms to more confidently migrate sensitive workloads to the cloud without the need for physically dedicated infrastructure.
-
Compliance Programs

We are continually adapting to evolving regulations. Check often for updates.