Microsoft Azure Compliance Offerings
Microsoft Azure Compliance Offerings
Compliance Offerings
Microsoft Azure Compliance Offerings
Abstract
This document provides an overview of Microsoft Azure compliance offerings intended to help
customers meet their own compliance obligations across regulated industries and markets worldwide.
Azure maintains the largest compliance portfolio in the industry both in terms of breadth (total number
of offerings), as well as depth (number of customer-facing services in assessment scope). Azure
compliance offerings are grouped into four segments: globally applicable, US government, industry
specific, and region/country specific. Each offering description provides an up to-date-scope statement
and links to useful downloadable resources.
November 2021
https://aka.ms/AzureCompliance
Acknowledgments
Author: Colin Yuen and Stevan Vidich
Reviewers: Derek Harris, Garima Jain, Shont Miller
(c) 2020 Microsoft Corporation. All rights reserved. This document is provided “as-is”. Information and views expressed in this
document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy
and use this document for your internal, reference purposes.
2
Microsoft Azure Compliance Offerings
Contents
Overview ....................................................................................................................................................... 7
Globally Applicable ....................................................................................................................................... 8
1 CIS Benchmark .................................................................................................................................. 8
2 CSA STAR Self-Assessment ................................................................................................................ 8
3 CSA STAR Certification ...................................................................................................................... 9
4 CSA STAR Attestation ........................................................................................................................ 9
5 ISO 20000-1:2011............................................................................................................................ 10
6 ISO 22301:2012 ............................................................................................................................... 10
7 ISO 27001:2013 ............................................................................................................................... 10
8 ISO 27017:2015 ............................................................................................................................... 11
9 ISO 27018:2014 ............................................................................................................................... 11
10 ISO 27701 ........................................................................................................................................ 12
11 ISO 9001:2015 ................................................................................................................................. 12
12 SOC 1 Type 2 ................................................................................................................................... 13
13 SOC 2 Type 2 ................................................................................................................................... 14
14 SOC 3 ............................................................................................................................................... 14
15 WCAG 2.0 (ISO 40500:2012) ........................................................................................................... 15
US Government........................................................................................................................................... 15
16 CJIS .................................................................................................................................................. 15
17 CNSSI 1253 ...................................................................................................................................... 16
18 DFARS .............................................................................................................................................. 17
19 DoD DISA SRG Level 2 ..................................................................................................................... 17
20 DoD DISA SRG Level 4 ..................................................................................................................... 18
21 DoD DISA SRG Level 5 ..................................................................................................................... 18
22 DoE 10 CFR Part 810 ....................................................................................................................... 18
23 EAR .................................................................................................................................................. 19
24 FedRAMP High (NIST SP 800-53) ..................................................................................................... 19
25 FIPS 140-2........................................................................................................................................ 20
26 IRS 1075 .......................................................................................................................................... 21
27 ITAR ................................................................................................................................................. 21
28 NIST Cybersecurity Framework (CSF).............................................................................................. 22
29 NIST SP 800-171 .............................................................................................................................. 23
3
Microsoft Azure Compliance Offerings
4
Microsoft Azure Compliance Offerings
5
Microsoft Azure Compliance Offerings
6
Microsoft Azure Compliance Offerings
Overview
Azure is a multi-tenant hyperscale cloud platform that is available or announced to customers in
60+regions worldwide. Most Azure services enable customers to specify the Region where their
Customer Data will be located. Microsoft may replicate Customer Data to other Regions within the
same Geo for data resiliency but Microsoft will not replicate Customer Data outside the chosen Geo
(e.g., United States). Microsoft makes 5 distinct Azure cloud environments available to customers:
To help customers meet their own compliance obligations across regulated industries and markets
worldwide, Azure maintains the largest compliance portfolio in the industry both in terms of breadth
(total number of offerings), as well as depth (number of customer-facing services in assessment scope).
To find out which Azure services are available in which regions, customers should explore the Azure
global infrastructure product availability dashboard.
Azure compliance offerings are grouped into four segments: globally applicable, US government,
industry specific, and region/country specific. Compliance offerings are based on various types of
assurances, including formal certifications, attestations, validations, authorizations, and assessments
produced by independent third-party auditing firms, as well as contractual amendments, self-
assessments, and customer guidance documents produced by Microsoft. Each offering description in
this document provides an up to date scope statement indicating which Azure customer-facing services
are in scope for the assessment, as well as links to downloadable resources to assist customers with
their own compliance obligations. For select third-party assessments, Appendices A and B list services
in audit scope for Azure and Azure Government, respectively.
More detailed information about Azure compliance offerings is available from the Trust Center.
Moreover, all downloadable documentation is available to Azure customers under a non-disclosure
agreement from the Service Trust Portal in sections labeled:
• Audit Reports, which is further divided into FedRAMP, GRC Assessment, ISO, PCI DSS, and SOC
reports sections;
• Data Protection Resources, which is further divided into Compliance Guides, FAQ and White
Papers, and Pen Test and Security Assessments sections.
Customers are wholly responsible for ensuring their own compliance with all applicable laws and
regulations. Information provided in this document does not constitute legal advice, and customers
should consult their legal advisors for any questions regarding regulatory compliance.
7
Microsoft Azure Compliance Offerings
Globally Applicable
Compliance offerings covered in this section have global applicability across regulated industries and
markets. They can often be relied upon by customers when addressing specific industry and regional
compliance obligations. For example, ISO 27001 certification provides a baseline set of requirements for
many other international standards and regulations.
1 CIS Benchmark
The Center for Internet Security (CIS) has published the CIS Microsoft Azure Foundations Benchmark
intended for customers who plan to develop, deploy, assess, or secure solutions that incorporate Azure.
The document provides prescriptive guidance for establishing a secure baseline configuration for Azure.
The benchmark was created using a consensus review process based on input from subject matter
experts with diverse backgrounds spanning consulting, software development, audit and compliance,
security research, operations, government, and legal. The resulting best practices guidance can be
leveraged by customers to assess and improve the security posture of their applications deployed in
Azure.
Each of the guidance recommendations in the CIS Azure Benchmark references one or more CIS Controls
that were developed as a set of actions to help organizations improve their cyber defense capabilities.
CIS Controls map to many established standards and regulatory frameworks, including the NIST
Cybersecurity Framework (CSF), NIST SP 800-53, ISO 27000 series of standards, PCI DSS, HIPAA, NERC
CIP, and others.
• Cloud Controls Matrix (CCM): a controls framework covering fundamental security principles
across 17 domains to help cloud customers assess the overall security risk of a CSP.
• Consensus Assessments Initiative Questionnaire (CAIQ): a set of nearly 300 questions based on
the CCM that a customer or cloud auditor may want to ask of CSPs to assess their compliance
with CSA best practices.
STAR provides three levels of assurance. CSA STAR Self-Assessment is the introductory offering at Level
1, which is free and open to all CSPs. Going further up the assurance stack, Level 2 of the STAR program
involves third-party assessment-based certifications.
8
Microsoft Azure Compliance Offerings
As part of the STAR Self-Assessment, CSPs can submit the CAIQ to document compliance with the CCM.
For the CSA STAR Self-Assessment, Microsoft Azure publishes the CAIQ.
During the assessment, an accredited CSA certification auditor assigns a Maturity Capability score to
each of the 16 CCM control areas. The average score is then used to assign the overall level of maturity
and the corresponding Bronze, Silver, or Gold award. Azure was awarded the CSA STAR Certification at
the Gold level. Aside from Azure services listed in Appendices A and Azure Government services in
Appendix B Microsoft Intune, Microsoft Power BI, and Microsoft Defender Advanced Threat
Protection online services have also obtained STAR Certification.
A SOC 2 Type 2 audit is based on the American Institute of Certified Public Accountants (AICPA) Trust
Services Principles and Criteria, including security, availability, confidentiality, privacy, and processing
integrity, and the criteria in the CCM. STAR Attestation provides an auditor’s findings on the design
suitability and operating effectiveness of Azure SOC 2 controls. The objective is to meet both the AICPA
criteria mentioned above and requirements set forth in the CCM.
Based on this audit, Microsoft Azure has been awarded the CSA STAR Attestation.
5 ISO 20000-1
ISO 20000-1 is an international standard for IT service management that defines requirements for the
development, implementation, monitoring, maintenance, and improvement of an IT service
management system. A related standard ISO/IEC 20000-2 provides guidance on the application of
service management systems. Moreover, ISO/IEC 27013 guidance on the integrated implementation of
ISO/IEC 27001 and ISO/IEC 20000-1 was released for organizations planning to implement ISO/IEC
20000-1 when ISO/IEC 27001 is already implemented or planning to implement these two standards
together. ISO/IEC 20000-1:2018 is the only standard in the ISO/IEC 20000 family that results in a formal
certification.
The ISO 20000-1 certificate demonstrates that a cloud service provider has implemented the right IT
service management procedures to deliver efficient and reliable IT services that are subject to regular
monitoring, review, and improvement. Aside from Azure services listed in Appendices A and Azure
Government services in Appendix B Microsoft Intune, Microsoft Power BI, and Microsoft Defender
Advanced Threat Protection online services are also included in the ISO 20000-1 certificate.
6 ISO 22301
ISO 22301 is the premium international standard for business continuity management that provides for
a formal certification. Azure has established a Business Continuity Management System (BCMS) in
accordance with the ISO 22301 standard and has received the corresponding certificate. ISO 22301
specifies the requirements for a BCMS to help organizations protect against, prepare for, and recover
from disruptive incidents. It is a comprehensive standard that organizations can use to demonstrate the
highest level of commitment to business continuity and disaster preparedness. Aside from Azure
services listed in Appendices A and Azure Government services in Appendix B Microsoft Intune,
Microsoft Power BI, and Microsoft Defender Advanced Threat Protection online services are also
included in the ISO 22301:2012 certificate.
7 ISO 27001
Azure maintains its ISO 27001 certification and makes the corresponding audit report and certificate
available to customers from the Service Trust Portal. ISO 27000 family of standards provide a
framework for policies and procedures that include all legal, physical, and technical controls involved in
10
Microsoft Azure Compliance Offerings
an organization’s information risk management processes. ISO 27001 specifies the requirements for
implementing, maintaining, monitoring, and continually improving an information security management
standard (ISMS). ISO 27002 provides guidelines and best practices for information security
management; however, an organization cannot get certified against ISO 27002 because it is not a
management standard. The audit vehicle is ISO 27001, which relies on detailed guidelines in ISO 27002
for control implementation. Aside from Azure services listed in Appendices A and Azure Government
services in Appendix B Intune, Microsoft Cloud App Security, Microsoft Graph, Microsoft Managed
Desktop, Microsoft Stream, Microsoft Threat Experts, Microsoft Threat Protection, Power Apps,
Power Automate, Power BI, Power Virtual Agents, Nomination Portal, Microsoft Forms Pro, Microsoft
365 Defender, Microsoft Defender for Endpoint and Microsoft Defender for Identity, Universal Print.
online services are also included in the ISO 27001 certificate.
8 ISO 27017
The ISO 27017 code of practice is designed for organizations to use as a reference for selecting cloud
services information security controls when implementing a cloud computing information security
management system based on ISO 27002. It can also be used by cloud service providers as a guidance
document for implementing commonly accepted protection controls. This international standard
provides additional cloud-specific implementation guidance based on ISO/IEC 27002, and provides
additional controls to address cloud-specific information security threats and risks. The Azure ISO 27017
certificate is available for download. ISO 27017 is unique in providing guidance for both cloud service
providers and cloud service customers. It also provides cloud service customers with practical
information on what they should expect from cloud service providers. Customers can benefit directly
from ISO 27017 by ensuring they understand the concept of shared responsibilities in the cloud. Aside
from Azure services listed in Appendices A and Azure Government services in Appendix B Intune,
Microsoft Cloud App Security, Microsoft Graph, Microsoft Managed Desktop, Microsoft Stream,
Microsoft Threat Experts, Microsoft Threat Protection, Power Apps, Power Automate, Power BI,
Power Virtual Agents, Nomination Portal, Microsoft Forms Pro, Microsoft 365 Defender, Microsoft
Defender for Endpoint and Microsoft Defender for Identity, Universal Print online services are also
included in the ISO 27017 certificate.
9 ISO 27018
ISO 27018 is the first international code of practice for cloud privacy that provides guidelines based on
ISO 27002 guidelines and best practices for information security management. Based on EU data-
11
Microsoft Azure Compliance Offerings
protection laws, it gives specific guidance to cloud service providers acting as processors of personally
identifiable information (PII) on assessing risks and implementing state-of-the-art controls for protecting
PII. ISO 27018 establishes cloud-specific control objectives and guidelines for PII in accordance with the
privacy principles in ISO 29100. Aside from Azure services listed in Appendices A and Azure Government
services in Appendix B Intune, Microsoft Cloud App Security, Microsoft Graph, Microsoft Managed
Desktop, Microsoft Stream, Microsoft Threat Experts, Microsoft Threat Protection, Power Apps,
Power Automate, Power BI, Power Virtual Agents, Nomination Portal, Microsoft Forms Pro, Microsoft
365 Defender, Microsoft Defender for Endpoint and Microsoft Defender for Identity, Universal Print
online services are also included in the ISO 27018:2014 certificate. The Azure ISO 27018 certificate and
audit report are available for download from the Service Trust Portal.
10 ISO 27701
ISO 27701 is built as an extension of the widely-used ISO/IEC 27001 standard for information security
management, making the implementation of PIMS’s privacy information management system a helpful
compliance extension for the many organizations that rely on ISO/IEC 27001, as well as creating a strong
integration point for aligning security and privacy controls. PIMS accomplishes this through a framework
for managing personal data that can be used by both data controllers and data processors, a key
distinction for GDPR compliance. In addition, any PIMS audit requires the organization to declare
applicable laws/regulations in its criteria for the audit meaning that the standard can be mapped to
many of the requirements under GDPR, CCPA (California Consumer Privacy Act), or other laws. This
universal framework allows organizations to efficiently operationalize compliance with new regulatory
requirements. Aside from Azure services listed in Appendices A and Azure Government services in
Appendix B Intune, Microsoft Cloud App Security, Microsoft Graph, Microsoft Managed Desktop,
Microsoft Stream, Microsoft Threat Experts, Microsoft Threat Protection, Power Apps, Power
Automate, Power BI, Power Virtual Agents, Nomination Portal, Microsoft Forms Pro, Microsoft 365
Defender, Microsoft Defender for Endpoint and Microsoft Defender for Identity, Universal Print
online services are also included in the ISO 27701:2019 certificate. The Azure ISO 27701 certificate and
audit report are available from the Service Trust Portal.
11 ISO 9001
ISO 9001 is an international standard that establishes the criteria for a quality management system. It is
the only standard in the ISO 9000 family that results in a formal certification. The standard is based on
several quality management principles, including clear focus on meeting customer requirements, strong
12
Microsoft Azure Compliance Offerings
12 SOC 1 Type 2
The American Institute of Certified Public Accountants (AICPA) has established three Service
Organization Controls (SOC) reporting options (SOC 1, SOC 2, and SOC 3) to assist CPAs with examining
and reporting on a service organization’s controls. The SOC 1 Type 2 attestation is based on the AICPA
Statement on Standards for Attestation Engagements 18 (SSAE 18) standard (see AT-C Section 105) and
the International Standard on Assurance Engagements No. 3402 (ISAE 3402). For Azure Germany, the
attestation is done in accordance with the IDW PS 951 standard. The SOC 1 attestation has replaced SAS
70, and it is appropriate for reporting on controls at a service organization relevant to user entities
internal controls over financial reporting. A Type 2 report includes auditor’s opinion on the control
effectiveness to achieve the related control objectives during the specified monitoring period.
Customers can leverage the Azure SOC 1 Type 2 attestation when pursuing their own financial industry
specific compliance requirements such as Sarbanes-Oxley (SOX), Federal Financial Institutions
Examination Council (FFIEC), Gramm-Leach-Bliley Act (GLBA), etc. Azure maintains a SOC 1 Type 2
attestation that is based on a rolling 12-month run window (audit period) with new reports issued semi-
annually. Customers can download the latest attestation report form the Azure Security Center Audit
Reports Portal (see SOC section). Aside from Azure services listed in Appendices A and Azure
Government services in Appendix B, the following online services are also included in the SOC 1
attestation report: Intune, Microsoft Cloud App Security, Microsoft Graph, Microsoft Managed
Desktop, Microsoft Stream, Microsoft Threat Experts, Microsoft Threat Protection, Power Apps,
Power Automate, Power BI, Power Virtual Agents, Microsoft Forms Pro, Microsoft 365 Defender,
Microsoft Defender for Endpoint and Microsoft Defender for Identity.
13
Microsoft Azure Compliance Offerings
13 SOC 2 Type 2
SOC 2 Type 2 is a restricted use report intended to report on controls relevant to Security, Availability,
Confidentiality, Processing Integrity, and Privacy system attributes. SOC 2 engagements are conducted
in accordance with the Trust Services Principles and Criteria, as well as the requirements stated in the
AICPA AT Section 101 standard. In addition, Azure SOC 2 Type 2 report addresses the requirements set
forth in the Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM). Azure SOC 1 and SOC 2
attestations are based on rigorous independent third-party audits conducted by a reputable CPA firm.
At the conclusion of a SOC 1 or SOC 2 audit, the auditor renders an opinion in a SOC 1 Type 2 or SOC 2
Type 2 report, which describes the cloud service provider’s (CSP’s) system and assesses the fairness of
the CSP’s description of its controls. It also evaluates whether the CSP’s controls are designed
appropriately, were in operation on a specified date, and were operating effectively over a specified
time period. Azure SOC 2 Type 2 report is relevant to the Security, Availability, Confidentiality, and
Processing Integrity trust principles. Azure maintains a SOC 2 Type 2 attestation that is based on a
rolling 12-month run window (audit period) with new reports issued semi-annually. Customers can
download the latest attestation report form the Service Trust Portal (see SOC Reports section). Aside
from Azure services listed in Appendices A and Azure Government services in Appendix B, the following
online services are also included in the SOC 2 Type 2 attestation report: Intune, Microsoft Cloud App
Security, Microsoft Graph, Microsoft Managed Desktop, Microsoft Stream, Microsoft Threat Experts,
Microsoft Threat Protection, Power Apps, Power Automate, Power BI, Power Virtual Agents,
Microsoft Forms Pro, Microsoft 365 Defender, Microsoft Defender for Endpoint and Microsoft
Defender for Identity.
14 SOC 3
A SOC 3 report is a short, publicly facing version of the SOC 2 Type 2 attestation report, for users who
want assurances about the cloud service provider’s controls but do not need a full SOC 2 report. Azure
SOC 3 report can be downloaded from the Service Trust Portal. Aside from Azure services listed in
Appendices A and Azure Government services in Appendix B, the following online services are also
included in the SOC 3 report: Intune, Microsoft Cloud App Security, Microsoft Graph, Microsoft
Managed Desktop, Microsoft Stream, Microsoft Threat Experts, Microsoft Threat Protection, Power
Apps, Power Automate, Power BI, Power Virtual Agents, Nomination Portal, Microsoft Forms Pro,
Microsoft 365 Defender, Microsoft Defender for Endpoint and Microsoft Defender for Identity.
14
Microsoft Azure Compliance Offerings
Microsoft is a major software and cloud-services provider to consumers, businesses, and governments
around the world. To assist customers in making purchasing decisions, Microsoft publishes Accessibility
Conformance Reports describing the extent to which our products and services support the WCAG
criteria. This information can help Microsoft customers determine whether a particular product or
service will meet their specific needs.
US Government
The following compliance offerings are focused primarily on addressing the needs of US Government.
Azure, Azure Government, and Azure Government for DoD have the same comprehensive security
controls in place, as well as the same Microsoft commitment on the safeguarding of Customer Data.
Azure Government provides additional controls regarding US Government specific background screening
requirements, including maintaining US persons for Azure Government operations. Azure Government
for DoD is reserved for exclusive use by the Department of Defense.
16 CJIS
The Criminal Justice Information Services (CJIS) Division of the US Federal Bureau of Investigation (FBI)
gives state, local, and federal law enforcement and criminal justice agencies access to criminal justice
information (CJI)—for example, fingerprint records and criminal histories. Law enforcement and other
government agencies in the United States must ensure that their use of cloud services for the
transmission, storage, or processing of CJI complies with the CJIS Security Policy, which establishes
minimum security requirements and controls to safeguard CJI. All private contractors who process CJI
must sign the CJIS Security Addendum, a uniform agreement approved by the US Attorney General that
helps ensure the security and confidentiality of CJI required by the Security Policy. It also commits the
contractor to maintaining a security program consistent with federal and state laws, regulations, and
standards, and limits the use of CJI to the purposes for which a government agency provided it.
Microsoft has agreements signed with nearly all 50 states and the District of Columbia except for the
following states: Delaware, Louisiana, Maryland, New Mexico, Ohio, and South Dakota. Microsoft
continues to work with state governments to enter into CJIS Information Agreements.
15
Microsoft Azure Compliance Offerings
Customers subject to CJIS requirements should review the CJIS Implementation Guidelines for Azure
Government. Also available is the Microsoft Cloud – CJIS Cloud Computing Requirements Mapping,
which details CJIS specific requirements and Microsoft cloud provider’s responses.
17 CNSSI 1253
The Committee on National Security Systems (CNSS) Instruction No. 1253, “Security Categorization and
Control Selection for National Security Systems” provides all federal government departments, agencies,
bureaus, and offices with a guidance for security categorization of National Security Systems (NSS) that
collect, generate, process, store, display, transmit, or receive National Security Information. The CNSSI
1253 builds on the NIST SP 800-53, which provides the control baseline for Azure Government FedRAMP
High authorization. There are some key differences between the CNSSI 1253 and NIST publications,
including the approach adopted by the CNSSI 1253 to define explicitly the associations of Confidentiality,
Integrity, and Availability to security controls, as well as to refine the use of security control overlays for
the national security community.
NSS are categorized using separate Low, Medium, and High categorization for each of the security
objectives, Confidentiality, Integrity, and Availability, resulting in categorizations such as “Moderate-
Moderate-Low”, “Moderate-Moderate-High”, etc., CNSSI 1253 then provides the appropriate security
baselines for each of the possible system categorizations using controls from NIST SP 800-53. To assist
customers who require support for the CNSSI 1253 High-High-High baseline, Azure Government has
been validated by an independent third-party assessment organization (3PAO). The resulting Security
Assessment Plan documents the testing conducted to validate Azure Government against a selection of
CNSSI 1253 security controls for systems requiring High Confidentiality, High Integrity, and High
Availability.
Azure Government currently possesses a FedRAMP High Provisional Authorization to Operate issued by
the Joint Authorization Board (JAB), as well as the Department of Defense Provisional Authorization at
the Security Requirements Guide (SRG) Impact Level 5. Leveraging these authorizations, the 3PAO
performed an analysis on the security controls that have already been tested to determine which
additional CNSSI 1253 security controls needed to be assessed to ensure compliance with a High-High-
High baseline. The results of this testing are provided in the accompanying Security Assessment Report
(SAR).
The SAR from the Azure Government assessment testing provides a complete assessment of the
applicable security controls as stipulated in the SAP. Evidence and interviews were conducted to
validate the successful implementation of the various security controls. The attestation of compliance
with the CNSSI 1253 High-High-High baseline can be downloaded from the Service Trust Portal GRC
Assessment Reports section.
16
Microsoft Azure Compliance Offerings
18 DFARS
Defense contractors whose information systems process, store, or transmit covered defense
information (CDI) must comply with the Department of Defense (DoD) Defense Federal Acquisition
Regulation Supplement (DFARS) Clause 252.204-7012, which specifies requirements for the protection
of controlled unclassified information (CUI) in accordance with NIST SP 800-171, cyber incident reporting
obligations, and other considerations for cloud service providers. All DoD contractors are required to
comply with DFARS requirements for adequate security “as soon as practical, but not later than 31
December 2017.
Azure Government has attained a FedRAMP High Provisional Authorization to Operate (P-ATO) as well
as a DoD DISA SRG Level 4 Provisional Authorization (PA) whereas Azure Government for DoD has
attained a DoD DISA SRG Level 5 PA. These authorizations allow DoD mission partners to host CDI within
the Azure Government and Azure Government for DoD clouds. Microsoft provides a contract
amendment to help defense contractors meet the requirements in the DFARS Clause 252.204-7012 that
apply to cloud service providers. When defense contractors are required to include the DFARS Clause
252.204-7012 flow-downs in subcontracts, Microsoft can accept the flow-down terms applicable to
cloud service providers for Azure Government and Azure Government for DoD.
An accredited third-party assessment organization (3PAO) has attested that Azure Government meets
the applicable requirements of DFARS Clause 252.204-7012. The attestation of compliance with DFARS
can be downloaded from the Service Trust Portal GRC Assessment Reports section. Aside from Azure
services listed in Appendices A and Azure Government services in Appendix B Microsoft Intune online
service also meet the applicable requirements of DFARS Clause 252.204-7012.
Azure maintains a DoD PA at SRG Impact Level 2, which covers non-controlled unclassified information
including all data cleared for public release, for the in-scope services.
17
Microsoft Azure Compliance Offerings
Azure Government can accommodate customers subject to DoE 10 CFR Part 810 export control
requirements because it is designed to meet specific controls that restrict access to information and
systems to US persons among Azure operations personnel. Customers deploying data to Azure
Government are responsible for their own security classification process. For data subject to DoE export
controls, the classification system is augmented by the Unclassified Controlled Nuclear Information
(UCNI) controls established by section 148 of the AEA.
The Nuclear Regulatory Commission (NRC) regulates the export and import of nuclear facilities and
related equipment and materials under 10 CFR Part 110. The NRC does not regulate nuclear technology
and assistance related to these items which are under the DoE jurisdiction. Consequently, NRC 10 CFR
Part 110 regulations would not be applicable to Azure.
23 EAR
The US Department of Commerce is responsible for enforcing the Export Administration Regulations
(EAR) through the Bureau of Industry and Security (BIS). According to BIS definitions, Export is the
transfer of protected technology or information to a foreign destination or release of protected
technology or information to a foreign person in the United States (aka Deemed Export). Items subject
to EAR can be found on the Commerce Control List (CCL), and each item has a unique Export Control
Classification Number (ECCN) assigned. Items not listed on the CCL are designated as EAR99.
The EAR is applicable to dual-use items that have both commercial and military applications, as well as
to items with purely commercial application. The BIS has provided guidance holding that cloud service
providers (CSP) are not exporters of customers’ data due to the customers’ use of cloud services.
Moreover, in the final rule published on 3 June 2016, BIS clarified that EAR licensing requirements would
not apply if the transmission and storage of unclassified technical data and software were encrypted
end-to-end using FIPS 140-2 validated cryptographic modules and not intentionally stored in a military-
embargoed country (i.e., Country Group D:5 as described in Supplement No. 1 to Part 740 of the EAR) or
in the Russian Federation.
Both Azure and Azure Government can help customers subject to the EAR meet their compliance
requirements. Except for the Hong Kong region, Azure and Azure Government datacenters are not
located in proscribed countries or in the Russian Federation. Azure and Azure Government rely on FIPS
140-2 validated cryptographic modules in the underlying operating system, and provide customers with
a wide range of options for encrypting data in transit and at rest, including encryption key management
using Azure Key Vault, which can store encryption keys in FIPS 140-2 validated Hardware Security
Modules (HSM) under customer control (Customer Managed Keys, CMK). Keys generated inside the
Azure Key Vault HSMs are not exportable – there can be no clear version of the key outside the HSMs.
This binding is enforced by the underlying HSM. Moreover, Azure Key Vault is designed, deployed, and
operated such that Microsoft and its agents do not see or extract customer keys.
Customers are responsible for choosing Azure or Azure Government regions for deploying their
applications and data. Moreover, customers are responsible for designing their applications to leverage
end-to-end data encryption that meets EAR requirements. Microsoft does not inspect or approve
customer applications deployed in Azure or Azure Government.
providers (CSPs). CSPs desiring to sell services to a federal agency requiring FedRAMP can take three
paths to demonstrate FedRAMP compliance: 1) earn a Provisional Authorization to Operate (P-ATO)
from the Joint Authorization Board (JAB); 2) receive an Authorization to Operate (ATO) from a federal
agency; or 3) work independently to develop a CSP Supplied Package that meets program requirements.
Each of these paths requires a stringent technical review by the FedRAMP Program Management Office
(PMO) and an assessment by an independent third-party assessment organization (3PAO) that is
accredited by the program.
FedRAMP is based on the National Institute of Standards and Technology (NIST) SP 800-53 Rev 4
standard, augmented by FedRAMP controls and enhancements. FedRAMP authorizations are granted at
three impact levels based on the NIST FIPS 199 guidelines—Low, Moderate, and High. These levels rank
the impact that the loss of confidentiality, integrity, or availability could have on an organization—Low
(limited effect), Moderate (serious adverse effect), and High (severe or catastrophic effect). The number
of controls in the corresponding baseline increases as the impact level increases, e.g., FedRAMP
Moderate baseline has 325 controls whereas FedRAMP High baseline has 421 controls.
The FedRAMP High authorization represents the highest bar for FedRAMP compliance. The FedRAMP
Joint Authorization Board (JAB) is the primary governance and decision-making body for FedRAMP.
Representatives from the Department of Defense (DoD), Department of Homeland Security (DHS), and
General Services Administration (GSA) serve on the board. The board grants a P-ATO to cloud service
providers that have demonstrated FedRAMP compliance. It’s important to note that FedRAMP is not a
point-in-time certification but an assessment and authorization program that also comes with provisions
for continuous monitoring mandated by the DHS.
Azure and Azure Government maintain FedRAMP High P-ATOs issued by the JAB in addition to more
than 90 Moderate and High ATOs issued by individual federal agencies for the in-scope services. Aside
from Azure services listed in the Azure Services in FedRAMP and DoD SRG Audit Scope, Microsoft Cloud
App Security, Microsoft Intune, Microsoft Flow, Microsoft PowerApps, Microsoft Graph (Azure
Government only), Microsoft Stream, Power BI, and Power Virtual Agents online services are also
included in the P-ATO packages. Customers can leverage the FedRAMP High Blueprint for assistance
with implementing FedRAMP-compliant workloads in Azure.
25 FIPS 140-2
The Federal Information Processing Standard (FIPS) Publication 140-2 is a US government standard that
defines minimum security requirements for cryptographic modules in products and systems. Validation
against the FIPS 140-2 standard is required for all US federal government agencies that use
cryptography-based security systems to protect sensitive but unclassified information stored digitally.
NIST publishes a list of vendors and their cryptographic modules validated for FIPS 140-2. Microsoft
certifies the cryptographic modules used in Microsoft products with each new release of the Windows
operating system, and Azure relies on FIPS 140-2 validated modules in the underlying operating system.
Moreover, Azure customers can store their own cryptographic keys and other secrets in FIPS 140-2
validated hardware security modules (HSM).
20
Microsoft Azure Compliance Offerings
26 IRS 1075
Internal Revenue Service Publication 1075 (IRS 1075) provides safeguards for protecting Federal Tax
Information (FTI) at all points where it is received, processed, stored, and maintained. It applies to
federal, state, and local agencies with whom IRS shares FTI, and it defines a broad set of management,
operations, and technology specific security controls that must be in place to protect FTI. The core
control scope is based on NIST SP 800-53 R4 that Azure Government covers as part of the existing
FedRAMP High authorization. Additional requirements cover protection of FTI in a cloud computing
environment (aka Exhibit 16), and place much emphasis on FIPS 140-2 validated data encryption in
transit and at rest.
Microsoft can provide customers with contractual commitment to demonstrate that Azure Government
has appropriate security controls and capabilities in place necessary for customers to meet the
substantive IRS 1075 requirements. Customers can download the Azure IRS 1075 Safeguard Security
Report from the Service Trust Portal GRC Assessment Reports section to understand how Azure
Government implements the applicable IRS controls. Moreover, Microsoft provides another document,
Azure Government Compliance Considerations, directly to the IRS to outline how an agency can use
Azure Government services in a way that complies with IRS 1075 requirements. Government customers
under NDA can request this document.
27 ITAR
The US Department of State has export control authority over defense articles, services, and related
technologies under the International Traffic in Arms Regulations (ITAR) managed by the Directorate of
Defense Trade Controls (DDTC). Items under ITAR protection are documented on the United States
Munitions List (USML). Customers who are manufacturers, exporters, and brokers of defense articles,
services, and related technologies as defined on the USML must be registered with DDTC, must
understand and abide by ITAR, and must self-certify that they operate in accordance with ITAR.
DDTC revised the ITAR rules effective 25 March 2020 to align them more closely with the EAR. These
ITAR revisions introduced an end-to-end data encryption carve-out that incorporated many of the same
terms that the Commerce Department adopted in 2016 for the EAR. Specifically, the revised ITAR rules
state that activities that do not constitute exports, re-exports, re-transfers, or temporary imports
include (among other activities) the sending, taking, or storing of technical data that is 1) unclassified, 2)
secured using end-to-end encryption, 3) secured using FIPS 140-2 compliant cryptographic modules as
prescribed in the regulations, 4) not intentionally sent to a person in or stored in a country proscribed in
§ 126.1 or the Russian Federation, and 5) not sent from a country proscribed in § 126.1 or the Russian
Federation. Moreover, DDTC clarified that data in-transit via the Internet is not deemed to be stored.
21
Microsoft Azure Compliance Offerings
End-to-end encryption implies the data is kept encrypted at all times between the originator and
intended recipient, and the means of decryption are not provided to any third party.
There is no ITAR compliance certification; however, both Azure and Azure Government can help
customers subject to ITAR meet their compliance obligations. Except for the Hong Kong region, Azure
and Azure Government datacenters are not located in proscribed countries or in the Russian Federation.
Azure and Azure Government rely on FIPS 140-2 validated cryptographic modules in the underlying
operating system, and provide customers with a wide range of options for encrypting data in transit and
at rest, including encryption key management using Azure Key Vault, which can store encryption keys in
FIPS 140-2 validated Hardware Security Modules (HSM) under customer control (Customer Managed
Keys, CMK). Keys generated inside the Azure Key Vault HSMs are not exportable – there can be no clear
version of the key outside the HSMs. This binding is enforced by the underlying HSM. Moreover, Azure
Key Vault is designed, deployed, and operated such that Microsoft and its agents do not see or extract
customer keys.
Customers are responsible for choosing Azure or Azure Government regions for deploying their
applications and data. Moreover, customers are responsible for designing their applications to leverage
end-to-end data encryption that meets ITAR requirements. Microsoft does not inspect or approve
customer applications deployed in Azure or Azure Government.
Microsoft has developed a Customer Responsibility Matrix (CRM) for NIST CSF that lists all control
requirements that require customer implementation, shared responsibility controls, and control
implementation details for controls owned by Microsoft. For questions about the NIST CSF template or
access to the CRM, customers should visit
https://servicetrust.microsoft.com/ViewPage/BlueprintLegacy. Moreover, an accredited third-party
22
Microsoft Azure Compliance Offerings
assessment organization (3PAO) has attested that Microsoft Azure system conforms to the NIST CSF risk
management practices, as defined in the Framework for Improving Critical Infrastructure Cybersecurity,
Version 1.0, dated February 12, 2014. The Azure NIST CSF control mapping demonstrates alignment of
the Azure FedRAMP authorized services against the CSF Core. In the course of this assessment,
Microsoft also leveraged the NIST CSF Draft Version 1.1, which includes guidance for a new Supply Chain
Risk Management category and three additional subcategories. Customers can download the 3PAO
attestation letter from the Service Trust Portal (see GRC Assessment Reports section). Also available for
download from the Service Trust Portal (see GRC Assessment Reports section) are several NIST CSF
specific guides, including the NIST CSF Risk Assessment Checklist, NIST CSF Enablement Detect Function,
NIST CSF Enablement Protect Function, and NIST CSF Enablement Identity Function.
29 NIST SP 800-171
The NIST SP 800-171 provides guidelines for the protection of controlled unclassified information (CUI)
in nonfederal information systems and organizations. Mapping tables in Appendix D (D1 through D14)
provide control mapping between CUI security requirements and relevant security controls in NIST SP
800-53, indicating that NIST SP 800-171 represents a subset of the NIST SP 800-53 controls for which
Azure has already been assessed and authorized under the FedRAMP program. Consequently,
customers can be assured that FedRAMP High baseline addresses fully and exceeds the requirements of
NIST SP 800-171. All Azure Government services that have received FedRAMP authorizations conform
to the NIST SP 800-171 requirements and can accommodate customers looking to deploy CUI workloads.
An accredited third-party assessment organization (3PAO) has attested that Azure Government meets
the criteria in the NIST SP 800-171 if the system processes CUI. Customers can download the 3PAO
attestation letter from the Service Trust Portal (see GRC Assessment Reports section).
Moreover, the Azure Security and Compliance Blueprint for NIST SP 800-171 is available to help
customers deploy a secure and compliant Data analytics, Data warehouse, IaaS web application, and
PaaS web application environment that implements a subset of NIST SP 800-171 controls. The NIST SP
800-171 Blueprint consists of four reference architectures with supporting deployment guidance,
security control mapping, threat model, and customer responsibility matrix. More information is
available from the NIST SP 800-171 Blueprint landing page on Service Trust Portal.
A Voluntary Product Accessibility Template (VPAT) is a standardized form developed by the Information
Technology Industry Council to document whether a product meets key Section 508 requirements.
Federal procurement officers and other buyers can use completed templates to help evaluate products
they are considering. Microsoft offers detailed VPATs for many Azure services, describing the
accessibility features of those services.
Applicability VPATs
Azure See Section 508 VPATs for Microsoft products.
Azure Government
Azure Government for DoD
Industry Specific
The following compliance offerings are intended to address the needs of customers subject to various
industry regulations such as those in financial services, healthcare and life sciences, media and
entertainment, education, etc. Azure is not subject directly to oversight by these regulators; however,
Azure can help customers meet their own compliance requirements by furnishing a variety of
documents ranging from formal independent third-party assessments to guidance documentation and
contractual commitments produced by Microsoft.
31 23 NYCRR 500
The State of New York recently adopted a rule that imposes a new set of cybersecurity requirements (23
NYCRR 500) on financial institutions that are licensed or authorized to do business by the New York
State Department of Financial Services (DFS). This regulation is designed to protect customer data and
the information technology systems of regulated institutions. It requires each financial institution to
assess its specific risk profile and design a program that addresses the risks. Microsoft has prepared a
document (“Microsoft Cloud – NYDFS”) to explain how Azure can help financial institutions comply with
23 NYCRR 500 requirements. Customers can download this document from the Service Trust Portal (see
Compliance Guides section).
• Financial Supervision Act (Wet op het financieel toezicht, FSA), issued by the Dutch legislature in
February 2018.
24
Microsoft Azure Compliance Offerings
• Decree on Prudential Rules Pursuant to the FSA (Besluit prudentiële regels Wft, “Bpr”), issued by
the Dutch government executive branch in January 2018.
• Circulaire Cloud Computing, issued by the DNB in January 2012.
• Commission Delegated Regulation EU 2017/565 of 25 April 2016 supplementing Directive
2014/65 of the European Parliament and of the Council (MODR)
• And others.
DNB’s point of view is that cloud computing involving third-party services qualifies as a form of
outsourcing. For example, the Circulaire states that DNB expects to be informed of prospective
outsourcing arrangements before a supervised Dutch institution engages in cloud computing.
Supervised institutions must ensure that operational processes and risks are under control.
To assist financial institutions in the Netherlands with cloud adoption, Microsoft published a guidance
document titled “Microsoft Cloud – Checklist for Financial Institutions in the Netherlands” that can be
downloaded from the Service Trust Portal (see Compliance Guides section). This document contains:
Compliance Checklist can be used as a tool to measure compliance against a regulatory framework and
to help customers conduct their own risk assessment.
The AMF and/or ACPR need to be notified regarding outsourcing arrangements in certain cases involving
material outsourcing and particularly if the outsourcing involves “critical or important provision of
25
Microsoft Azure Compliance Offerings
services or operational tasks and functions”. There are also mandatory terms that must be included in
contracts with cloud service providers per the Order dated 3-Nov-2014 and the AMF General Regulation.
To assist financial institutions in France with cloud adoption, Microsoft published a guidance document
titled “Microsoft Cloud Checklist France” that can be downloaded from the Service Trust Portal (see
Compliance Guides section). This document contains:
Compliance Checklist can be used as a tool to measure compliance against a regulatory framework and
to help customers conduct their own risk assessment.
34 APRA (Australia)
The Australian Prudential Regulation Authority (APRA) oversees banks, credit unions, insurance
companies, and other financial services institutions (FSIs) in Australia. Recognizing the momentum
towards cloud computing, APRA has called on regulated entities to implement a thoughtful cloud
adoption strategy with effective governance, thorough risk assessment, and regular assurance
processes. APRA’s information paper, “Outsourcing involving shared computing services (including
cloud)”, outlines important guidance for regulated entities in their assessment of cloud providers and
cloud services.
Customers should review the Microsoft Response to the APRA Information Paper on Cloud, which
follows the structure and topics of the APRA’s information paper on outsourcing. The paper provides a
detailed response to each issue raised by APRA to demonstrate how FSIs can move data and workloads
to Azure and comply with the APRA guidance. Moreover, for the next level of detail, the “Microsoft
Cloud – Checklist for Financial Institutions in Australia” can be downloaded from the Service Trust Portal
(see Compliance Guides section). The checklist covers regulatory issues that need to be addressed
under regulations such as APRA CPS 231, APRA PPG 231, and others. More information is available from
the Australian FSI Trusted Cloud webpage.
35 CDSA
The Content Delivery & Security Association (CDSA) Content Protection & Security (CPS) Standard
provides guidance and requirements for securing media assets within a Content Security Management
System (CSMS). The standard specifies a set of controls designed to ensure the integrity of intellectual
property and the confidentiality and security of media assets at every stage of the digital media supply
chain.
26
Microsoft Azure Compliance Offerings
The CPS certification audit is administered directly by the CDSA and consists of over 300 distinct controls
that help secure and manage physical datacenters, harden services, and protect storage facilities. All
controls are optimized to handle sensitive and valuable media assets. Once a system is validated by the
CDSA assessor, the CDSA issues a certificate of compliance. To maintain compliance, the certified entity
must submit the results of annual audits to the CDSA. Customers can download the Azure Media
Services Certificate of Compliance as well as the Azure CDSA CPS Audit Report from the Service Trust
Portal (see GRC Assessment Reports section). Also available for download from the Service Trust Portal
(see Compliance Guides section) is the CDSA CPS Implementation Guide, which describes how Azure
Media Services can help customers create CDSA CPS compliant solutions securely, as well as how
customers can create, protect, and operate digital media services on Azure.
Azure Immutable Blob Storage can help customers address their records retention requirements.
Microsoft retained an independent third-party assessment firm that specializes in records management
and information governance to evaluate Azure Immutable Blob Storage compliance with CFTC Rule
1.31(c)-(d) requirements. The resulting report “Cohasset Assessment – Microsoft Azure WORM Storage”
can be downloaded from the Service Trust Portal GRC Assessment Reports section. It is the assessor’s
opinion that Azure Immutable Blob Storage with Policy Lock option when utilized to retain time-based
Blobs in a non-erasable and non-rewritable format, meets the relevant storage requirements of CFTC
Rule 1.31(c)-(d).
37 DPP (UK)
The Digital Production Partnership (DPP) partnered with the North American Broadcasters Association
(NABA) to develop the NABA DPP Broadcasters Cyber Security Requirements, which are endorsed by
chief information security officers from the UK broadcasters as being the minimum set of requirements
for cyber security. The DPP worked with broadcasters and supplier security experts to create a self-
assessment format designed to enable suppliers to demonstrate commitment to achieving security best
practices. This work has led to the establishment of a formal Committed to Security Program that DPP
launched in October 2017 with two different logos: Broadcast Checklist and Production Checklist.
27
Microsoft Azure Compliance Offerings
Microsoft Azure has been awarded the DPP Committed to Security Mark (Broadcast Checklist) as
mentioned on the DPP web site. Moreover, customers can download the Azure NABA DPP Broadcaster
Cyber Security Requirements Checklist from the Service Trust Portal (see Compliance Guides section).
To assist financial institutions in the EU with cloud adoption, Microsoft published a guidance document
addressing key points in EBA’s cloud computing recommendations. This document is titled “Microsoft
Cloud – European Banking Authority Guidance”, and it can be downloaded from the Service Trust Portal
(see Compliance Guides section). The purpose of the document is to explain how Microsoft meets the
requirements applicable to it as a Cloud Service Provider and to help customers meet their obligations
under the EBA framework. Specifically, the document covers:
Microsoft welcomes the Recommendations on Outsourcing to Cloud Service Providers as they provide
clarity on cloud usage permissibility, apply a principles-based approach towards measuring risk from a
technology-neutral perspective, and strive towards greater harmonization within Europe and beyond.
39 FACT (UK)
Copyrighted content comes in many forms—pictures, videos, music, contracts, scripts, workflows, art,
architecture, and more—and represents the core assets of many businesses. To underscore Microsoft’s
commitment to protect customers when they entrust such assets to the public cloud, Microsoft Azure
has been certified by the Federation Against Copyright Theft (FACT) in the United Kingdom. FACT
certification is based on ISO 27001, focusing on physical and digital security, staff screening and training,
and access control. The FACT content protection and security program draws on expertise across law
28
Microsoft Azure Compliance Offerings
enforcement, technology partners, and industry associations to fight copyright infringement and
content theft, such as peer-to-peer sharing, illegal disc duplication, and signal theft. Customers can
download the Azure FACT certificate.
In July 2016, the FCA published the “FG 16/5 – Guidance for firms outsourcing to the cloud and other
third-party IT services” intended to help firms authorized under the Financial Services and Markets Act
(FSMA) oversee all aspects of their outsourcing arrangements. To help firms that are authorized and
regulated by the FCA and the PRA comply with their regulatory obligations, Microsoft published a
document detailing how Azure helps customers meet the standards set out in the FCA Guidance. The
document is titled “Microsoft Cloud – Microsoft Approach to Enabling Compliance with FCA Finalized
Guidance”, and it can be downloaded from the Service Trust Portal (see Compliance Guides section). The
sections in the document track the “Area of interest” titles found in the FCA Guidance for ease of
reference and navigation.
Aside from the FCA FG 16/5 Guidance, there are additional requirements and guidelines that financial
institutions in the United Kingdom should be aware of when moving to the cloud, including the Financial
Services and Markets Act 2000, the Senior Management Arrangements, Systems, and Controls
Sourcebook (SYSC) in the FCA Handbook, the European Banking Authority (EBA) Final Report on
Recommendations on Outsourcing to Cloud Service Providers EBA/REC/2017/03, and others. To assist
UK financial services firms regulated by the FCA and PRA with cloud adoption, Microsoft published a
guidance document titled “Microsoft Cloud – Checklist for Financial Institutions in the UK” that can be
downloaded from the Service Trust Portal (see Compliance Guides section). This document contains a
Compliance Checklist as a tool to measure compliance against a regulatory framework and to help
customers conduct their own risk assessment.
29
Microsoft Azure Compliance Offerings
41 FERPA (US)
The Family Educational Rights and Privacy Act (FERPA) is a US federal law that protects the privacy of
students’ education records, including personally identifiable and directory information. FERPA was
enacted to ensure that parents and students age 18 and older can access those records, request
changes to them, and control the disclosure of information, except in specific and limited cases where
FERPA allows for disclosure without consent. The law applies to schools, school districts, and any other
institution that receives funding from the US Department of Education—that is, virtually all public K–12
schools and school districts, as well as most post-secondary institutions, both public and private.
FERPA does not require or recognize audits or other certifications, so any academic institution that is
subject to FERPA must assess for itself whether and how its use of a cloud service affects its ability to
comply with FERPA requirements. In the Online Services Terms Data Protection Addendum (DPA),
Microsoft agrees to be designated as a “school official” with “legitimate educational interests” in
customer data as defined under FERPA. Customer data would include any student records provided
through a school’s use of Azure. When handling student education records, Microsoft agrees to abide by
the limitations and requirements imposed by 34 CFR 99.33(a) just as school officials do. Microsoft has
published guidance documentation to assist Azure customers with satisfying their FERPA compliance
requirements. Customers subject to FERPA can download the Azure FERPA Compliance Framework
Mapping from the Service Trust Portal (see Compliance Guides section) for assistance with satisfying
FERPA compliance requirements.
COPPA and CIPA are additional laws intended to protect the privacy of children; however, they are not
directly applicable to Azure. The Children’s Online Privacy Protection Act (COPPA) is a US federal law
enacted to protect the privacy of children under 13. It is managed by the Federal Trade
Commission (FTC). COPPA applies to websites and online services directed to children and stipulates
that these sites and services must require parental consent for the collection and use of any personal
information belonging to children. The Children’s Internet Protection Act (CIPA) was enacted to address
concerns about children’s access to harmful content over the Internet. The Federal Communications
Commission (FCC) issued rules implementing CIPA and defined requirements for schools and libraries
subject to CIPA. Customers enquiring about COPPA and CIPA in the context of Azure adoption should
review the section titled Educational Institutions in the Online Services Terms DPA where we explain
that customers are responsible for obtaining any parental consent for any end user’s use of Microsoft
online services.
42 FFIEC (US)
The Federal Financial Institutions Examination Council (FFIEC) is a formal interagency body comprised of
five banking regulators that is responsible for the federal examination of financial institutions in the
United States. The FFIEC Examiner Education Office publishes IT Examination Handbooks intended for
field examiners from the FFIEC member agencies. The FFIEC Audit IT Examination Handbook contains
guidance on third-party reviews of technology service providers that enables financial institutions to
review sufficiently detailed independent audit reports of technology service providers (TSPs) as part of
30
Microsoft Azure Compliance Offerings
their overall responsibility to manage their relationships with TSPs. Specifically, AICPA’s SOC 1, SOC 2,
and SOC 3 attestation reports are mentioned in the Audit Handbook as examples of independent audit
reports pertinent to TSPs. However, FFIEC also mentions that financial institutions should not rely solely
on the information contained in these reports and should instead use additional verification and
monitoring procedures discussed in more detail in the FFIEC Outsourcing Technology Services IT
Examination Handbook.
Azure provides financial institutions with SOC 1 Type 2, SOC 2 Type 2, and SOC 3 attestation reports
produced by an independent CPA firm to help customers meet their own FFIEC compliance obligations.
For example, the SOC 1 Type 2 attestation is based on the AICPA SSAE 18 standard (see AT-C Section
105) that replaced SAS 70, and it is appropriate for reporting on controls at a service organization
relevant to user entities internal controls over financial reporting. This is the formal audit that financial
institutions can leverage for third-party reviews of technology service providers when pursuing their
own FFIEC specific compliance obligations for assets deployed to Azure. It includes auditor’s opinion on
control effectiveness to achieve the related control objectives during the specified monitoring period.
Moreover, Azure has developed an Excel-based Cloud Security Diagnostic Tool that customers can
download from the Service Trust Portal (see Compliance Guides section). This tool is meant to expedite
a risk assessment that a financial institution may want to conduct relative to Azure services. The tool is
based on a spreadsheet featuring 19 tabs (each for a separate information security domain) that track
requirements set forth by relevant standards and financial services regulations, including FFIEC IT
Examination Handbooks. The tool is prepopulated with explanations how Azure complies with
requirements applicable to cloud service providers and can assist customers in meeting their own FFIEC
compliance requirements. Also available for download in the Compliance Guides section of the Service
Trust Portal is the Azure FFIEC Cloud Security Diagnostic workbook companion that offers guidance on
the use of Azure cloud services and considerations for customer compliance with FFIEC requirements.
Finally, the Azure Security and Compliance FFIEC Financial Services Blueprint is available to help
customers deploy a secure and compliant Data analytics, Data warehouse, IaaS web application, and
PaaS web application environment suitable for the collection, storage, and retrieval of financial data
regulated by the FFIEC. The FFIEC Blueprint consists of four reference architectures with supporting
deployment guidance, security control mapping, threat model, and customer responsibility matrix.
More information is available from the FFIEC Blueprint landing page on Service Trust Portal.
43 FINMA (Switzerland)
The Swiss Financial Market Supervisory Authority (FINMA) is Switzerland’s independent financial
markets regulator with prudential supervision over banks, insurance companies, exchanges, securities
dealers, and other financial industry participants. FINMA Circular 2018/3 Outsourcing – Banks and
Insurers defines the risk-based supervisory requirements applicable to outsourcing solutions at banks,
securities dealers, and insurance companies. Moreover, when moving to the cloud, Swiss financial
institutions should be aware of additional requirements and guidelines, including the Swiss Bank Act,
Swiss Bank Ordinance, Swiss Insurance Supervision Act, and others.
31
Microsoft Azure Compliance Offerings
To assist financial institutions in Switzerland with cloud adoption, Microsoft published a guidance
document titled “Microsoft Cloud – Checklist for Financial Institutions in Switzerland” that can be
downloaded from the Service Trust Portal (see Compliance Guides section). This document contains:
Compliance Checklist can be used as a tool to measure compliance against a regulatory framework and
to help customers conduct their own risk assessment.
Azure Immutable Blob Storage can help customers address their records retention requirements.
Microsoft retained an independent third-party assessment firm that specializes in records management
and information governance to evaluate Azure Immutable Blob Storage compliance with FINRA Rule
4511(c) requirements. The resulting report “Cohasset Assessment – Microsoft Azure WORM Storage”
can be downloaded from the Service Trust Portal GRC Assessment Reports section. It is the assessor’s
opinion that Azure Immutable Blob Storage with Policy Lock option when utilized to retain time-based
Blobs in a non-erasable and non-rewritable format, meets the relevant storage requirements of FINRA
Rule 4511(c).
45 FISC (Japan)
Supporting members, including major financial institutions, insurance and credit companies, securities
firms, computer manufacturers, and telecommunications enterprises.
In collaboration with its member institutions, the Bank of Japan, and the Financial Services Agency, the
FISC created guidelines for the security of banking information systems. These guidelines include basic
auditing standards for computer system controls, contingency planning in the event of a disaster, and
development of security policies and standards encompassed in more than 300 controls.
32
Microsoft Azure Compliance Offerings
Although the application of these guidelines in a cloud computing environment is not required by
regulation, most financial institutions in Japan that implement cloud services have built information
systems that satisfy these security standards. Microsoft engaged outside assessors to validate that
Microsoft Azure meet the requirements of the FISC Security Guidelines on Computer Systems for
Financial Institutions 9th Edition Revised. Financial institutions can rely on this evaluation of compliance
for the in-scope infrastructure and platform services of these services. Aside from Azure services listed
in table below Microsoft Cloud App Security online service is also included in the Scope.
46 FSA (Denmark)
The Danish Financial Supervisory Authority (FSA, in Danish: Finanstilsynet) is a government agency
residing under the Ministry of Industry, Business and Financial Affairs but with a separate board of
directors. The principal role of the FSA is to prepare regulatory guidelines for financial institutions in
Denmark, cooperate with other authorities and regulators on a regional and international level, and
monitor financial institutions’ regulatory compliance.
There are several requirements and guidelines that financial institutions in Denmark should be aware of
when moving to the cloud, including:
• Danish Act on Financial Institutions (in Danish: Bekendtgørelse af lov om Finansiel Virksomhed),
Ministry of Industry, Business and Financial Affairs, released in September 2017.
• Executive Order on Outsourcing of Significant Areas of Activity (In Danish: Bekendtgørelse om
outsourcing af væsentlige aktivitetsområder), Ministry of Industry, Business and Financial
Affairs, released in January 2010 and amended in December 2017).
• Guideline for Executive Order on Outsourcing of Significant Areas of Activity” (in Danish:
Vejledning til bekendtgørelse om outsourcing af væsentlige aktivitetsområder), Ministry of
Industry, Business and Financial Affairs, released in May 2010.
• Guidance on Use of Cloud Services as Part of IT-Outsourcing (in Danish: Anvendelse af cloud-
tjenester som led I IT-outsourcing), FSA.
To assist financial institutions in Denmark with cloud adoption, Microsoft published a guidance
document titled “Microsoft Cloud – Checklist for Financial Institutions in Denmark” that can be
downloaded from the Service Trust Portal (see Compliance Guides section). This document contains:
33
Microsoft Azure Compliance Offerings
Compliance Checklist can be used as a tool to measure compliance against a regulatory framework and
to help customers conduct their own risk assessment.
47 GLBA (US)
The Gramm-Leach-Bliley Act (GLBA) is a US public law that reformed the financial services industry and
addressed concerns about consumer privacy protection. It required the Federal Trade Commission (FTC)
and other financial services regulators to implement regulation addressing GLBA privacy provisions such
as the Financial Privacy Rule and Safeguards Rule. GLBA requirements to safeguard sensitive consumer
data apply to financial institutions that offer financial products and services to consumers (e.g., loans,
investment advice, etc.). Azure can help customers comply with the security requirements of the GLBA
by providing technical and organizational safeguards to help customers maintain security and prevent
unauthorized usage.
Azure has developed an Excel-based Cloud Security Diagnostic Tool that customers can download from
the Service Trust Portal (see Compliance Guides section). This tool is meant to expedite a risk
assessment that a financial institution may want to conduct relative to Azure services. The tool is based
on a spreadsheet featuring 19 tabs (each for a separate information security domain) that track
requirements set forth by relevant standards and financial services regulations, including GLBA (see
Column R in the spreadsheet). The tool is prepopulated with explanations how Azure complies with
requirements applicable to cloud service providers and can assist customers in meeting their own
compliance requirements, including the security requirements of GLBA.
Azure has obtained the GSMA SAS-SM accreditation for data center operations and management only
across the two French regions at this time which includes France Central region based in Paris and
France South region in Marseille. France Central region offers three availability zones for increased
availability, resiliency, and business continuity. With more than 100 available Azure services being SAS-
SM accredited we enable any telecom operator to use Azure to support a massive global increase in the
volume of embedded mobile subscriptions with the right level of security assurance. This capability will
34
Microsoft Azure Compliance Offerings
be critical to the implementation of 5G networks and the cellular network connectivity of billions of IoT
devices worldwide.
Customers should review a white paper “Strategies for Life Sciences Companies using Microsoft Azure
with GxP Systems” produced by Accenture to learn how to analyze controls required to leverage Azure,
define how Azure can meet those controls, and define the levels of ownership from Life Sciences
companies when validating and maintaining GxP systems hosted on Azure. Among other things, the
white paper shows how certain FDA regulations (21 CFR Part 820 and 21 CFR Part 11) apply to Azure.
50 HDS (France)
Microsoft Azure has been granted the Health Data Hosting (Hébergeurs de Données de Santé, HDS)
certification, which is required for all entities hosting personal health data governed by French law. This
made Microsoft the first major cloud service provider to meet the strict French standards for storing and
processing health data. This certification, required by the revision to the 2018 French Public Health
35
Microsoft Azure Compliance Offerings
Code, imposes advanced security and privacy requirements on hosting services and cloud providers to
ensure that the confidentiality and integrity of sensitive data is adequately protected.
Microsoft Azure compliance with the HDS requirements has been audited and certified by the BSI
Group, an independent certifying body accredited by French authorities to conduct HDS audits.
The HDS certification enables healthcare providers in France to use Microsoft cloud services to save
costs by improving clinical and operational efficiency, and it opens the door to the development of
innovative, cutting-edge healthcare solutions. Providers will be able to develop smart applications or use
third-party applications hosted on Azure to implement predictive analytics to personalize healthcare,
evaluate and treat patients at a distance (telemedicine), and sharpen therapeutic drug monitoring.
HIPAA regulations require that covered entities and their business associates enter into a contract called
a Business Associate Agreement (BAA) to ensure the business associates will protect PHI adequately.
Azure has enabled the physical, technical, and administrative safeguards required by HIPAA and the
HITECH Act inside the in-scope Azure services, and offers a HIPAA BAA as part of the Microsoft Online
Services Terms to all customers who are covered entities or business associates under HIPAA for use of
such in-scope Azure services. In the BAA, Microsoft makes contractual assurances about data
safeguarding, reporting (including breach notifications), data access in accordance with HIPAA and the
HITECH Act, and many other important provisions. Aside from Azure services listed in Appendices A and
Azure Government services in Appendix B Microsoft Intune, Microsoft Power BI and Power Virtual
Agents online services are also included.
Customers subject to HIPAA/HITECH Act compliance obligations should review Microsoft Azure
HIPAA/HITECH Act Implementation Guidance to learn about concrete steps needed to maintain
compliance on Azure and to better understand what it takes to adopt a cloud platform in a secure
manner. Also available to customers is the Azure Security and Compliance HIPAA/HITRUST Blueprint,
which offers a turnkey deployment of an Azure PaaS solution to demonstrate how to securely ingest,
store, analyze, and interact with health data while addressing industry compliance requirements.
52 HITRUST
The Health Information Trust Alliance (HITRUST) is an organization governed by representatives from
the healthcare industry. HITRUST created and maintains the Common Security Framework (CSF), a
certifiable framework to help healthcare organizations and their providers demonstrate their security
and compliance in a consistent and streamlined manner. The CSF builds on HIPAA and the HITECH Act,
and incorporates healthcare-specific security, privacy, and other regulatory requirements from existing
frameworks such as the PCI DSS, ISO 27001, and MARS-E.
Also available to customers is the Azure Security and Compliance HIPAA/HITRUST Blueprint, which offers
a turnkey deployment of an Azure PaaS solution to demonstrate how to securely ingest, store, analyze,
and interact with health data while addressing industry compliance requirements.
37
Microsoft Azure Compliance Offerings
53 K-ISMS
Based on a rigorous evaluation by the Korea Internet & Security Agency (KISA), Microsoft Azure achieved
the Korea Information Security Management System (K-ISMS) certification to host data. The certification
covers Azure services that encompass compute, storage, networking, databases, and security, and the
datacenter infrastructure of the Microsoft Korea Central and Korea South regions. The specifications for
K-ISMS certification are based on ISO/IEC 27001, ISO/IEC 27018, and other international standards that
govern the hosting of data.
Achieving this certification means Azure customers in Korea can more easily demonstrate adherence to
local legal requirements to protect key digital information assets and meet KISA compliance standards
more easily. In addition, Korean organizations that have a legislated mandate to obtain their own K-ISMS
certification—certain internet and information network service providers, large hospitals and schools,
and so on—can more efficiently meet their own KISMS compliance requirements by building on the
Azure certification.
The Azure K-ISMS certification can be reviewed for details. The audit covered the measures Microsoft
takes to secure data and protect its confidentiality including the:
• Certification of Microsoft business cloud services (with annual audits for compliance) to ISO/IEC
27001:2013 Information Security Management Standards.
• High level of privacy protection based on Microsoft compliance with the ISO/IEC 27018 Code of
Practice for Protecting Personal Data in the Cloud.
• Layered approach in how Microsoft datacenters are designed, built, and operated to strictly
control physical access to the areas where customer data is stored.
Aside from Azure services listed in Appendices A, Microsoft Intune, Microsoft Power BI and online
services are also included in the Azure K-ISMS certification.
54 KNF (Poland)
The Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) is the financial
regulatory authority in Poland, responsible for supervising the financial markets, including the oversight
over banking, capital markets, insurance, pension schemes, and other market sectors. There are several
requirements and guidelines that financial institutions in Poland should be aware of when moving to the
cloud, including:
38
Microsoft Azure Compliance Offerings
The Banking Act does not regulate cloud services directly but instead sets out legal requirements for the
outsourcing of banking operations. Cloud services could be subject to the Banking Act provisions if the
outsourced services are of key significance for the bank, or if outsourcing involves giving the service
provider access to sensitive data subject to banking secrecy.
To assist financial institutions in Poland with cloud adoption, Microsoft published a guidance document
titled “Microsoft Cloud Checklist Poland” that can be downloaded from the Service Trust Portal (see
Compliance Guides section). This document contains:
Compliance Checklist can be used as a tool to measure compliance against a regulatory framework and
to help customers conduct their own risk assessment.
55 MARS-E (US)
In 2012, the Center for Medicare and Medicaid Services (CMS) published the Minimum Acceptable Risk
Standards for Exchanges (MARS-E) in accordance with CMS information security and privacy programs.
The suite of documents, including guidance, requirements, and templates, was designed to address
mandates of the Patient Protection and Affordable Care Act (ACA) and regulations of the Department of
Health and Human Services that apply to the ACA. The National Institute of Standards and Technology
(NIST) Special Publication 800-53 serves as the parent framework that establishes the security and
compliance requirements for all systems, interfaces, and connections between ACA-mandated health
exchanges and marketplaces.
Following the updated NIST SP 800-53 R4, CMS revised the MARS-E framework to align with the updated
controls and parameters in NIST SP 800-53 R4, publishing MARS-E 2.0 in 2015. These updates address
the confidentiality, integrity, and availability in health exchanges of protected data, which includes
personally identifiable information, protected health information, and federal tax information. The
MARS-E 2.0 framework aims to secure this protected data and applies to all ACA administering entities,
including exchanges or marketplaces—federal, state, state Medicaid, or Children’s Health Insurance
Program (CHIP) agencies—and supporting contractors.
There is no formal certification process for MARS-E. However, Microsoft maintains a FedRAMP High
authorization for Azure and for Azure Government issued by the FedRAMP Joint Authorization Board
(JAB). Although FedRAMP does not specifically focus on MARS-E, the MARS-E control requirements and
objectives are very closely aligned with FedRAMP and serve to protect the confidentiality, integrity, and
availability of data on Azure.
Shortly after the release of the MAS Guidelines on Outsourcing, the Association of Banks in Singapore
(ABS) introduced the ABS Cloud Implementation Guide, a non-binding practical guide designed to assist
banks in Singapore as they implement cloud services. The ABS Cloud Implementation Guide applies only
to banks and not to other categories of financial institutions.
In response to the release of the MAS Guidelines on Outsourcing and the ABS Cloud Implementation
Guide, Microsoft produced a document to:
• Help financial institutions understand the key issues raised by the MAS Guidelines and the ABS
Guide as they apply to cloud services
• Set out Microsoft’s interpretations of and responses to each of the key issues
• Provide financial institutions with information about how Microsoft helps facilitate compliance
with the new guidelines
The document is titled “Microsoft Cloud – Singapore MAS and ABS requirements implementation
guide,” and it can be downloaded from the Service Trust Portal (see Compliance Guides section).
Moreover, to assist financial institutions in Singapore with cloud adoption, Microsoft published a
guidance document titled “Microsoft Cloud – Checklist for Financial Institutions in Singapore” that can
be downloaded from the Service Trust Portal (see Compliance Guides section). This document contains
a Compliance Checklist as a tool to measure compliance against a regulatory framework and to help
customers conduct their own risk assessment.
57 MPAA (US)
The Motion Picture Association of America (MPAA) provides best-practices guidance and control
frameworks to help major studio partners and vendors design infrastructure and solutions to ensure the
security of digital film assets. The MPAA also performs content security assessments on behalf of its
member companies. In February 2016, Microsoft Azure became the first hyperscale, multitenant cloud
service provider to successfully complete a formal assessment by independent MPAA auditors and
comply with all three of the MPAA content security best practices frameworks: Common, Application,
and Cloud Security Guidelines.
The MPAA assessment covers 48 security topics in the Common Guidelines and an additional six in the
Application and Cloud Security Guidelines. These topics are built on industry-accepted security
40
Microsoft Azure Compliance Offerings
standards such as ISO 27001 and NIST SP 800-53, and are aligned to industry best practices, such as the
Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM).
The formal assessment of Azure compliance means that companies who do business with major studios
can use Azure to help reduce the IT costs that are normally associated with the securUK management,
storage, and distribution of content while complying with MPAA requirements. Azure services in scope
for the MPAA assessment provide a content workflow engine in the cloud that customers can use to
build secure and scalable production processes while protecting media assets downstream.
Customers can download Azure responses to the Common Guidelines and the Application and Cloud
Security Guidelines from the Service Trust Portal (see Compliance Guides section).
There are several requirements and guidelines that financial institutions in Belgium should be aware of
when moving to the cloud, including:
• Circular NBB PPB 2004/5 on sound management practices in outsourcing by credit institutions
and investment firms and the broadly equivalent provisions of the Circular FSMA dated 5 June
2007 on the organizational requirements for firms providing investment services.
• Circular NBB_2009_17 on financial services via the Internet: Prudential requirements.
• Circular NBB_2015_32 on additional prudential expectations regarding operational business
continuity and security of systemically important financial institutions.
To assist financial institutions in Belgium with cloud adoption, Microsoft published a guidance document
titled “Microsoft Cloud – Checklist for Financial Institutions in Belgium” that can be downloaded from
the Service Trust Portal (see Compliance Guides section). This document contains:
Compliance Checklist can be used as a tool to measure compliance against a regulatory framework and
to help customers conduct their own risk assessment.
41
Microsoft Azure Compliance Offerings
Microsoft retained an independent, third-party auditing firm to analyze the extent to which current
Azure certifications and attestations (such as ISO 27001 and SOC 2 Type 2) cover the part of NEN 7510
that Microsoft is responsible for. The resulting NEN 7510 Coverage Report provides a mapping of these
existing certifications and attestations to the controls listed in the NEN 7510 standard. Customers in the
Dutch healthcare industry can use the report as a tool to help adopt Azure in a NEN 7510 compliant way.
The report clearly demonstrates which NEN 7510 controls are covered by Microsoft and which controls
remain to be covered by the customers. The “Microsoft Cloud – Azure and Office 365 NEN 7510-2011
Standard Coverage” report can be downloaded from the Service Trust Portal GRC Assessment Reports
section. Also available for download is the “Microsoft Cloud – Azure and Office 365 NEN 7510-2011
Standard Coverage User Guide” (see the Service Trust Portal Compliance Guides section).
60 NERC
The North American Electric Reliability Corporation (NERC) is a nonprofit regulatory authority whose
mission is to ensure the reliability of the North American bulk power system. NERC is subject to
oversight by the U.S. Federal Energy Regulatory Commission (FERC) and governmental authorities in
Canada. In 2006, FERC granted the Electric Reliability Organization (ERO) designation to NERC in
accordance with the Energy Policy Act of 2005 (U.S. Public Law 109-58). NERC develops and enforces
reliability standards known as NERC Critical Infrastructure Protection (CIP) standards.
All bulk power system owners, operators, and users must comply with NERC CIP standards. These
entities are required to register with NERC. Cloud Service Providers and third-party vendors are not
subject to NERC CIP standards; however, the CIP standards include goals that should be considered
when Registered Entities use vendors in the operation of the Bulk Electric System (BES). Microsoft
customers operating Bulk Electric Systems are wholly responsible for ensuring their own compliance
with NERC CIP standards. Neither Azure nor Azure Government constitutes a BES or BES Cyber Asset.
As stated by NERC in the current set of CIP standards and NERC’s Glossary of Terms, BES Cyber Assets
perform real-time functions of monitoring or controlling the BES, and would affect the reliable operation
of the BES within 15 minutes of being impaired. To properly accommodate BES Cyber Assets and
Protected Cyber Assets in cloud computing, existing definitions in NERC CIP standards would need to be
revised. However, there are many workloads that deal with CIP sensitive data and do not fall under the
15-minute rule, including the broad category of BES Cyber System Information (BCSI).
42
Microsoft Azure Compliance Offerings
Both Azure and Azure Government are suitable for Registered Entities deploying certain workloads
subject to NERC CIP standards, including BCSI workloads. Microsoft makes the following documents
available to Registered Entities interested in deploying data and workloads subject to NERC CIP
compliance obligations in Azure or Azure Government:
• NERC CIP Standards and Cloud Computing is a white paper that discusses compliance
considerations for NERC CIP requirements based on established third-party audits that are
applicable to cloud service providers such as FedRAMP. It covers background screening for
cloud operations personnel and answers common question about logical isolation and multi-
tenancy that are of interest to Registered Entities. It also addresses security considerations for
on-premises vs. cloud deployment.
• Cloud Implementation Guide for NERC Audits is a guidance document that provides control
mapping between the current set of NERC CIP standards requirements and NIST SP 800-53 Rev 4
control set that forms the basis for FedRAMP. It is designed as a technical how-to guidance to
help Registered Entities address NERC CIP compliance requirements for assets deployed in the
cloud. The document contains pre-filled Reliability Standard Audit Worksheets (RSAWs)
narratives that help explain how Azure controls address NERC CIP requirements, as well as
guidance for Registered Entities on how to use Azure services to implement controls that they
own.
The NERC ERO Enterprise released a Compliance Monitoring and Enforcement Program (CMEP) practice
guide to provide guidance to ERO Enterprise CMEP staff when assessing a Registered Entity’s process to
authorize access to designated BCSI storage locations and any access controls the Registered Entity
implemented. Moreover, NERC reviewed Azure control implementation details and FedRAMP audit
evidence related to NERC CIP-004-6 and CIP-011-2 standards that are applicable to BCSI. Based on the
ERO issued practice guide and reviewed FedRAMP controls to ensure Registered Entities encrypt their
data, no additional guidance or clarification is needed for Registered Entities to deploy BCSI and
associated workloads in the cloud; however, Registered Entities are ultimately responsible for
compliance with NERC CIP standards according to their own facts and circumstances. Registered Entities
should review the Cloud Implementation Guide for NERC Audits for help with documenting their
processes and evidence used to authorize electronic access to BCSI storage locations, including
encryption key management used for BCSI encryption in Azure and Azure Government.
61 OSFI (Canada)
The Office of the Superintendent of Financial Institutions (OSFI) is an independent agency of the
Government of Canada responsible for the prudential regulation and supervision of federally regulated
financial institutions. OSFI published the OSFI B-10 Guidelines on the Outsourcing of Business Activities,
Functions, and Processes to set out expectations for federally regulated entities that outsource their
business activities to a service provider. A memorandum published subsequently by OSFI reminded
federally regulated financial institutions that B-10 Guidelines remain current and continue to apply to
technology-based outsourcing services.
43
Microsoft Azure Compliance Offerings
The financial institution’s use of cloud services must also comply with the Personal Information
Protection and Electronic Documents Act (PIPEDA), and in some instances one or more of the provincial
data privacy laws.
To assist financial institutions in Canada with cloud adoption, Microsoft published a guidance document
titled “Microsoft Cloud – Checklist for Financial Institutions in Canada” that can be downloaded from the
Service Trust Portal (see Compliance Guides section). This document contains:
Compliance Checklist can be used as a tool to measure compliance against a regulatory framework and
to help customers conduct their own risk assessment.
44
Microsoft Azure Compliance Offerings
62 PCI 3DS
Europay, Mastercard, and Visa (EMV) three-domain secure (3-D Secure or 3DS) is an EMVCo messaging
protocol that enables cardholders to authenticate with their card issuers when making card-not-present
(CNP) online transactions. The specification aims at securing authentication and identity verification in
mobile and browser-based applications. The additional security layer helps prevent unauthorized CNP
transactions and protects the merchant from exposure to CNP fraud.
Microsoft retained a qualified 3DS Assessor company to conduct an assessment of the PCI 3-D Secure
Environment (3DE) hosted on Azure against the PCI 3DS Core Security Standard. The 3DS Assessor
determined that Azure PCI 3DS service provider environment meets applicable PCI 3DS controls and
issued an Attestation of Compliance (AoC) for the Azure PCI 3DS environment.
Customers can download the following documents from the Service Trust Portal Audit Reports - PCI DSS
section as part of the Azure PCI 3DS package:
• Azure PCI 3DS Attestation of Compliance (AoC) provides evidence that Azure complies with the
PCI 3DS Core Security Standard based on a PCI 3DS assessment conducted by a qualified 3DS
Assessor.
• Azure PCI 3DS Shared Responsibility Matrix supports Azure customers implementing and
documenting security controls for a system built on Azure.
o Understanding the shared responsibility for implementing security controls in a cloud
environment is essential for customers building systems and utilizing services in Azure.
Implementing a specific security control may be the responsibility of Azure, the
responsibility of Azure's customers, or a shared responsibility between Azure and its
customers. Different cloud service models affect the way that responsibilities are shared
between Azure and its customers.
o Azure does not directly perform the functions of a 3DS Server (3DSS), 3DS Directory
Server (DS), or 3DS Access Control Server (ACS). Azure customers have the ability to host
their own 3DS environment on Azure using services offered. The Azure PCI 3DS shared
responsibility matrix describes the Azure 3DS assessment scope and illustrates the PCI
3DS compliance responsibilities for Azure and its customers. It is intended to be used by
Azure customers and their compliance advisors to understand the scope of the Azure
PCI 3DS assessment and expectations for responsibilities when using Azure services as
part of the customer’s 3DS environments (3DE). It is the customer’s responsibility to
assess and understand their full scope of responsibility for implementing security
controls and ensuring security controls are implemented in accordance with their
compliance obligations.
o Azure best practices and recommendations should be taken into consideration.
• Azure PCI 3DS whitepaper provides customer guidance on the PCI 3DS Core Security Standard
and how the Azure 3DE can be utilized to implement a customer 3DE on Azure. The whitepaper
addresses the following key areas:
o Provides an overview of the 3DS domains
o Examines the relationship between the PCI Data Security Standard (DSS) and 3DS Core
Security Standard
45
Microsoft Azure Compliance Offerings
o Defines the responsibilities shared by Azure and its customers to meet the 3DS Core
Security Standard requirements
A 3DS entity can choose to outsource the hosting and management of its hardware security module
(HSM) infrastructure to a third-party service provider if the applicable requirements are met. Entities
performing 3DS functions who use the Azure environment for hosting their 3DE are still subject to the
PCI 3DS Core Security Standard and must have their environment assessed for all applicable
requirements.
It is, however, important to understand that Azure PCI DSS compliance status does not automatically
translate to PCI DSS validation for the services that customers build or host on the Azure platform.
Customers are responsible for ensuring that they achieve compliance with PCI DSS requirements. The
Azure PCI DSS Responsibility Matrix specifies areas of responsibility for each PCI DSS requirement, and
whether it is assigned to Azure or the customer, or if the responsibility is shared. Moreover, customers
should review the Azure Security and Compliance PCI DSS Blueprint, which provides guidance for the
deployment of a PCI DSS-compliant Platform as a Service (PaaS) environment suitable for handling
sensitive payment card data.
• Guidelines on Managing Risk and Code of Conduct in Outsourcing of Financial Services by Banks,
published by the RBI in November 2006
• Guidelines on Information Security, Electronic Banking, Technology Risk Management and Cyber
Frauds, published by the RBI in April 2011
• Outsourcing of Activities by Indian Insurers Regulation, published by the IRDAI in 2017
• And others as documented in the “Microsoft Cloud – Checklist for Financial Institutions in India”
available to customers from the Service Trust Portal.
Moreover, the financial institution’s use of cloud services must also comply with privacy rules, including
the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data
or Information) Rules, 2011.
Financial institutions must report outsourcing arrangements where the scale and nature of the activities
outsourced by the financial institution are significant or require extensive data sharing with service
providers. Insurance organizations are required to report outsourcing of certain support functions of
core activities within 45 days of entering into an outsourcing agreement.
To assist financial institutions in India with cloud adoption, Microsoft published a guidance document
titled “Microsoft Cloud – Checklist for Financial Institutions in India” that can be downloaded from the
Service Trust Portal (see Compliance Guides section). This document contains:
Compliance Checklist can be used as a tool to measure compliance against a regulatory framework and
to help customers conduct their own risk assessment.
The SCI rules apply to SCI entities, which include such self-regulatory organizations (SROs) as stock and
options exchanges, registered clearing agencies, and alternative trading systems (ATSs). The rules
primarily regulate the systems that directly support key securities market functions: trading, clearance
and settlement, order routing, market data, market regulation, and market surveillance.
The US Securities and Exchange Commission (SEC) adopted Regulation SCI to strengthen the technology
infrastructure of the financial organizations that operate and support the US securities markets. Under
SEC oversight, its requirements are designed to ensure that these systems have high availability, strong
resiliency, and low latency (high volume of messages with little delay).
To help guide US financial services customers who must comply with this regulation, Microsoft has
published the Microsoft Azure SEC Regulation Systems Compliance and Integrity Cloud Implementation
Guide. The guidance within this document:
• Provides an overview of overall Azure capabilities that support strong resiliency, high
availability, and low latency.
• Makes clear which control areas and regulatory aspects Azure addresses. This point-by-point
mapping of Azure features and services to SCI requirements measures Azure compliance against
the regulatory framework. It also helps customers understand where they can shift security
responsibilities to Azure that they had fully owned when they operated on premises. These
capabilities are backed by the promises Microsoft makes in Azure SLAs.
• Specifies each Regulation SCI requirement that is the customer’s responsibility to address, and
offers Azure documentation and services to help them address these responsibilities.
This document provides a thorough checklist of critical Regulation SCI focus areas. This will help financial
organizations understand how they can adopt Azure to help assure their regulators, customers, and
leadership that they can comply with the applicable regulatory requirements.
from 3 to 6 years based on record types, with immediate accessibility mandated for the first 2 years.
Moreover, one of the interpretative releases requires the storage system to be capable of retaining
records beyond the SEC-established retention period to comply with subpoenas, legal hold, or other
similar requirements.
Records retention requirements established by the SEC Rule 17a-4(f) are relied upon by other regulators
such as the Financial Industry Regulatory Authority (FINRA) and Commodity Futures Trading Commission
(CFTC) as described elsewhere in this document. Azure Immutable Blob Storage can help customers
address their records retention requirements. Microsoft retained an independent third-party
assessment firm that specializes in records management and information governance to evaluate Azure
Immutable Blob Storage compliance with SEC 17a-4(f) requirements. The resulting report “Cohasset
Assessment – Microsoft Azure WORM Storage” can be downloaded from the Service Trust Portal GRC
Assessment Reports section. It is the assessor’s opinion that Azure Immutable Blob Storage with Policy
Lock option when utilized to retain time-based Blobs in a non-erasable and non-rewritable format,
meets the relevant storage requirements of SEC Rule 17a-4(f).
67 Shared Assessments
The Shared Assessment Program (formerly known as BITS Shared Assessments) is used by many
commercial, retail, and investment banks around the world as a proxy for managing their third-party
vendor risk assessment process. Microsoft Azure aligns to the Program’s Standard Information
Gathering (SIG) questionnaire and the Agreed Upon Procedures (AUP) by way of Azure’s self-assessment
to the Cloud Security Alliance (CSA) STAR program. Azure maintains STAR registry submissions based on
both the Cloud Controls Matrix (CCM) and Consensus Assessments Initiative Questionnaire (CAIQ). The
CCM maps to the Shared Assessments SIG v6.0 and AUP v5.0. Azure also maintains formal CSA STAR
Certification and CSA STAR Attestation as documented in the STAR registry. Customers can download
the “Azure Standard Response to Request for Information – Security, Privacy, and Compliance” from the
Service Trust Portal (see FAQ and White Papers section).
68 SOX (US)
The Sarbanes-Oxley Act of 2002 (SOX) is a US federal law administered by the Securities and Exchange
Commission (SEC). There is no SOX certification or validation for cloud service providers; however,
Azure can help customers meet their obligations under SOX, which is heavily influenced by customer’s
internal processes especially when it comes to controls for financial reporting. Customers enquiring
about Azure SOX compliance should review the Azure SOC 1 Type 2 attestation that is based on the
American Institute of Certified Public Accountants (AICPA) Statement on Standards for Attestation
Engagements 18 (SSAE 18) standard (see AT-C Section 105) and the International Standard on Assurance
Engagements No. 3402 (ISAE 3402). This attestation has replaced SAS 70, and it is appropriate for
reporting on controls at a service organization relevant to user entities internal controls over financial
49
Microsoft Azure Compliance Offerings
reporting. Customers can download this attestation report from the Service Trust Portal. Moreover,
Azure has produced customer guidance for SOX that is available for download from the Service Trust
Portal (see Compliance Guides section). It covers case studies and lessons learned from migrating
internal Microsoft SOX relevant applications to Azure.
69 TISAX (Germany)
The protection of business processes and information is a core management task in any industry. In the
automotive industry, connected and autonomous vehicles, cloud-based services, and digital
communication between OEM and supplier have increased the pressure for information security, data
protection, and trustworthy solutions. The Trusted Information Security Assessment Exchange (TISAX)
developed by the German Association of the Automotive Industry supplies that level of trusted security
standards for the industry.
70 Argentina PDPA
In accordance with the Argentine National Constitution, the Argentina Personal Data Protection Act
25,326 aims to protect personal information recorded in data files, registers, banks, and elsewhere to
help protect the privacy of individuals, and also provide a right of access to the information that may be
recorded about them. In a data transfer agreement available to customers, Microsoft contractually
commits that Azure in-scope services have implemented the applicable technical and organizational
security measures stated in Regulation 11/2006 of the Argentine Data Protection Authority. Moreover,
50
Microsoft Azure Compliance Offerings
Microsoft makes additional important commitments regarding notifications, auditing of our facilities,
and use of subcontractors.
71 Australia IRAP
The risk management framework used by the Australian Cyber Security Center (ACSC) Information
Security Manual (ISM) draws from National Institute of Standards and Technology (NIST) Special
Publication (SP) 800-37 Rev. 2, Risk Management Framework for Information Systems and
Organizations: A System Life Cycle Approach for Security and Privacy. Within this risk management
framework, the identification of risks and selection of security controls can be undertaken using a
variety of risk management standards, such as International Organization for Standardization (ISO)
31000:2018, Risk management – Guidelines. Broadly, the risk management framework used by the ISM
has six steps: define the system, select security controls, implement security controls, assess security
controls, authorise the system and monitor the system.
The Information Security Registered Assessor Program (IRAP) provides a comprehensive process for the
independent assessment of a system’s security against the ISM controls and is the mechanism for cloud
services to assess security controls within their platforms. An IRAP assessment has been completed for
the Azure in-scope services for the processing of government data up to and including at the
PROTECTED level in Microsoft Australian-based public cloud. Additional compensating controls are to
be implemented on a risk-managed basis by individual agencies prior to agency authorisation and
subsequent use of these cloud services. The ACSC encourages adoption of a risk-managed approach
with respect to the controls listed in the Australian Government Information Security Manual (ISM) and
Protective Security Policy Framework (PSPF).
Through the previous Australian Government certification process, Azure was IRAP assessed and
certified by the ACSC at both the Unclassified Dissemination Limiting Markings (DLM) and PROTECTED
levels. This resulted in Azure being included on the Certified Cloud Services List (CCSL) which was used to
identify cloud services that had successfully completed an IRAP assessment and awarded certification by
the ACSC. Azure remains on the CCSL for services that have been previously assessed by the ACSC.
Microsoft will continue to have services IRAP assessed, and agencies will conduct the approval process.
Agencies can engage the ACSC through their normal channels for assistance in that approval process. To
assist customers with their authorisation decision, Microsoft makes our IRAP assessment report and
supporting documents available to customers and partners on an Australia-specific page of
the Microsoft Service Trust Portal.
Also available to customers is the Australia PROTECTED Blueprint Guidance that consists of reference
architecture for IaaS and PaaS applications, threat model, and control implementation guidance. For
more information, see the AU-PROTECTED Blueprint landing page on Service Trust Portal. This Blueprint
enables customers to deploy Azure solutions that are suitable for processing, storage, and transmission
of sensitive and official information that is classified up to and including PROTECTED. Additional
documents and configuration guidance for operating at PROTECTED are available from the Azure
Australia Microsoft Docs page.
51
Microsoft Azure Compliance Offerings
To assist Canadian customers with cloud adoption, Microsoft published a guidance document titled
“Microsoft Cloud – Checklist for Financial Institutions in Canada” that can be downloaded from the
Service Trust Portal (see Compliance Guides section). This document contains:
Compliance Checklist can be used as a tool to measure compliance against a regulatory framework and
to help customers conduct their own risk assessment.
Ultimately, the responsibility and ownership of personal data lies with our business customers, per the
Online Services Terms. However, Microsoft contractually commits that Azure in-scope services have
implemented security safeguards to help them protect the privacy of individuals, based on established
industry standards such as ISO 27001 and SOC 2 Type 2. We have assessed our practices in risk, security,
and incident management; access control; data integrity protection; and other areas relative to the
recommendations from the Office of the Privacy Commissioner of Canada and have determined that the
in-scope services are capable of meeting those recommendations.
73 China GB 18030:2005
GB 18030 is the Chinese ideographic character set and encoding standard mandated by the Chinese
government. Microsoft Azure operated by 21Vianet is certified as compliant with the mandatory part of
this standard by the China Electronics Standardization Institute (CESI).
52
Microsoft Azure Compliance Offerings
75 China TCS
Trusted Cloud Service Evaluation is a band of cloud service evaluation under China Academy of
Information and Communications Technology (CAICT). It is a serial of quality evaluation system
organized by the Trusted Cloud Service Workgroup of Open Source Cloud Alliance for Industry (OSCA)
under the guide of Ministry of Industry and Information Technology of China (MIIT). Trusted Cloud
Service Evaluation is also the authoritative evaluation system for cloud computing services in China. The
evaluation aims to cultivate the Chinese public cloud service market, enhance users’ confidence on
cloud services, and protect certified cloud service providers. Microsoft Azure operated by 21Vianet has
passed the evaluation and obtained Trusted Cloud Service Evaluation of Virtual Machine, Cloud Storage,
Cloud Database, Load Balancing, Cloud Engine and Cloud Backup.
76 DESC
The United Arab Emirates (UAE) Dubai Electronic Security Center (DESC) was founded in 2014 with the
aim to develop and implement information security practices across the Dubai Emirate. The Cloud
Service Provider (CSP) Security Standard produced by DESC sets out requirements and guidance for CSPs
and those organizations using any cloud services. Compliance with this standard is mandatory for all
CSPs wishing to offer cloud services for Dubai government and semi government entities.
Microsoft was the first global cloud services provider to obtain the DESC CSP Security Standard
certification. Microsoft retained an independent third-party auditing firm (certification body) accredited
by DESC to perform the CSP Security Standard certification of Microsoft Azure and Dynamics 365
including the physical inspection of datacenter facilities in two Azure UAE regions. Following the
completion of these activities, Microsoft was granted the CSP Security Standard certification.
53
Microsoft Azure Compliance Offerings
77 EU EN 301 549
Accessibility requirements suitable for public procurement of ICT products and services in Europe (EN
301 549) is a set of standards for information and communications technologies (ICT) products and
services, including websites, software, and digital devices. EN 301 549 was published in 2014 by the
European Telecommunications Standards Institute (ETSI) in response to a request from the European
Commission and is intended for use in procurement by government and public-sector organizations.
78 EU ENISA IAF
The European Network and Information Security Agency (ENISA) Information Assurance Framework
(IAF) is a set of assurance criteria that organizations can review with cloud service providers to ensure
they have sufficient protections in place around Customer Data. The IAF is intended to assess the risk of
cloud adoption and reduce the assurance burden on cloud service providers.
Microsoft Azure aligns to the IAF by way of Azure’s self-assessment to the Cloud Security Alliance (CSA)
STAR program. Azure maintains STAR registry submissions based on both the Cloud Controls Matrix
(CCM) and Consensus Assessments Initiative Questionnaire (CAIQ). The CCM maps to the IAF. Azure
also maintains formal CSA STAR Certification and CSA STAR Attestation as documented in the STAR
registry. Customers can download the “Azure Standard Response to Request for Information – Security,
Privacy, and Compliance” from the Service Trust Portal (see FAQ and White Papers section).
79 EU Model Clauses
European Union (EU) data protection law regulates the transfer of EU customer personal data to
countries outside the European Economic Area (EEA), which includes all EU countries and Iceland,
Liechtenstein, and Norway. Microsoft offers customers the EU Standard Contractual Clauses (EU Model
Clauses) that provide specific guarantees around transfers of personal data for in-scope services.
Microsoft provided its Standard Contractual Clauses to the EU's Article 29 Working Party for review and
approval. The Article 29 Working Party includes representatives from the European Data Protection
Supervisor, the European Commission, and each of the 28 EU Data Protection Authorities (DPAs). The
group determined that implementation of the provisions in Microsoft agreements was in line with their
stringent requirements.
The EU Model Clauses ensure that any personal data leaving the EU will be transferred in accordance
with EU data protection law and meet the requirements of the EU Data Protection Directive 95/46/EC.
Microsoft makes the EU Model Clauses available to customers as described in the Online Services Terms.
54
Microsoft Azure Compliance Offerings
81 GDPR
The General Data Protection Regulation (GDPR) is a European privacy law that became effective in May
2018. It imposes new rules on organizations that offer goods and services to people in the European
Union (EU) or that collect and analyze data belonging to EU individuals. The GDPR requires that data
controllers (such as organizations using Azure) only use data processors (such as Microsoft) that provide
sufficient guarantees to meet key requirements of the GDPR. Microsoft provides customers with a
contractual commitment regarding the GDPR in the Online Services Terms (OST), which can be found in
Attachment 4 to the OST, at the end of the document.
Microsoft provides tools and documentation to support customer’s GDPR accountability including
support for Data Subject Requests, Data Protection Impact Assessments, and Data Breach Notification,
as described in Getting Started: Support for GDPR Accountability. Additional Azure online
documentation and white papers are available to help customers meet their own GDPR compliance
obligations, including specific documentation for Data Subject Requests, Data Protection Impact
Assessments, and Data Breach Notification. Azure Security and Compliance GDPR Blueprint can assist
customers in building and deploying cloud applications that meet GDPR requirements, including
guidance and common reference architecture designed to simplify Azure adoption in support of GDPR
compliance initiatives. Finally, customers can have transparent access to Azure controls in support of
GDPR obligations via the Service Trust Portal Compliance Manager.
82 Germany C5
The Cloud Computing Compliance Controls Catalogue (C5) outlines minimum security requirements that
cloud service providers should meet for cloud services offered to customers. C5 was developed in 2016
and revised in 2020 by the Federal Office for Information Security (BSI) as an auditing standard. It is
intended for cloud service providers, their auditors, and customers of the cloud service providers.
55
Microsoft Azure Compliance Offerings
The catalog consists of 122 requirements across 17 domains, and it is based on established standards,
including ISO 27001, Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM) version 3.01, AICPA Trust
Services Principles and Criteria 2014, and others. However, C5 adds additional transparency controls to
provide information on data location, provision of services, place of jurisdiction, existing certifications,
and information disclosure obligations towards government agencies.
According to Section 3.3 “Connection to Other Audits” (see Page 22 in the C5 Catalogue), a SOC 2 audit
can be leveraged as attestation vehicle for C5 requirements. Microsoft Azure maintains a SOC 2 Type 2
attestation report that customers can download from the Service Trust Portal or from the Azure Security
Center Regulatory Compliance Portal. This document details an audit assessment performed by a third-
party independent auditor on controls relevant to security, availability, processing integrity, and
confidentiality trust principles (SOC 2), Cloud Controls Matrix (CCM) criteria, and Cloud Computing
Compliance Controls Catalogue (C5).
84 India MeitY
In November 2017, Microsoft became one of the first global Cloud Service Providers (CSPs) to achieve
full accreditation by the Ministry of Electronics and Information Technology (MeitY) for the Government
of India. MeitY provides accreditation (referred to by MeitY as empanelment) of CSPs, which enables
public sector organizations to select empaneled cloud services though the government Cloud Services
Directory.
MeitY accreditation was the result of a systematic audit process conducted by the Standardization
Testing and Quality Certification (STQC) Directorate, a government organization that provides quality
assurance services. The evaluation framework is based on the Meghraj Cloud initiative, established by
the Government of India, which governs the implementation of public sector IT services. MeitY’s
accreditation enables government agencies and departments in India to choose Microsoft Azure to
56
Microsoft Azure Compliance Offerings
advance their digital transformation and optimize IT operations. More details can be found on the
MeitY site.
JASA developed the Authorized Information Security Audit System (AISAS), which specifies the audit of
approximately 1,500 controls that needs to be performed by an independent auditor authorized by
JASA. Microsoft Azure completed a rigorous audit by a JASA-certified auditor and received CS Mark Gold
accreditation for in-scope services. Customers can download the accreditation (in Japanese) from JASA
web site.
While the responsibility and ownership of personal data is with our customers, per the Online Services
Terms, Microsoft contractually commits that Azure in-scope cloud services have implemented technical
and organizational security safeguards to help our customers protect individuals’ privacy. These
safeguards are based on established industry standards, such as ISO 27001 and SOC 2 Type 2.
Furthermore, Microsoft does not have standing access to My Number data stored in these in-scope
cloud services, so companies do not need to supervise handling of data by Microsoft (as outlined in Q3-
12). Nonetheless, companies are required to take appropriate safety measures to protect My Number
data stored in the cloud (Q3-13).
57
Microsoft Azure Compliance Offerings
Microsoft retained an independent, third-party auditing firm to analyze the extent to which current
Azure certifications and attestations (such as ISO 27001 and SOC 2 Type 2) cover the part of BIR 2012
that Microsoft is responsible for. The resulting BIR 2012 Coverage Report provides a mapping of these
existing certifications and attestations to the controls listed in the BIR 2012 standard. Customers can use
the report as a tool to help adopt Azure in a BIR 2012 compliant way. The report clearly demonstrates
which BIR 2012 controls are covered by Microsoft and which controls remain to be covered by the
customers. The “Microsoft Cloud – Azure and Office 365 BIR 2012 Baseline Coverage” report can be
downloaded from the Service Trust Portal GRC Assessment Reports section. Also available for download
from the Service Trust Portal Compliance Guides section is the “Microsoft Cloud – Azure and Office 365
BIR 2012 Baseline Coverage User Guide” (in Dutch).
To help agencies undertake their analysis and evaluation of Microsoft enterprise cloud services,
Microsoft New Zealand has produced a series of documents showing how its enterprise cloud services
address the questions set out in the Cloud Computing ISPC by linking them to the standards against
which Microsoft cloud services are certified. These certifications are central to how Microsoft assures
both public and private sector customers that its cloud services are designed, built, and operated to
effectively mitigate privacy and security risks and address data sovereignty concerns. The Azure
response to Cloud Computing IPSC is available to customers for download.
The MTCS builds upon recognized international standards such as ISO 27001. It includes a total of 535
controls and it addresses different levels of security, covering basic security in Level 1, more stringent
governance and tenancy controls in Level 2, and reliability and resiliency for high-impact information
systems in Level 3.
After a rigorous assessment conducted by the MTCS Certification Body, Microsoft Azure was granted
certification at Level 3. A Level 3 certification means that in-scope Azure services can host high-impact
data for regulated organizations with the strictest security requirements. It’s required for certain cloud
solution implementations by the Singapore government. Azure MTCS certificate and MTCS cloud service
provider self-disclosure can be downloaded from the IMDA web site for certified cloud services. Aside
from Azure services listed in Appendices A, Virtual Agents, Microsoft Graph, Microsoft Power BI,
Microsoft Cloud App Security, Power Automate, Microsoft Intune, Microsoft PowerApps, Microsoft
Stream and Microsoft Service Map online services are also included in the Azure MTCS certificate.
90 Singapore OSPAR
The OSPAR framework was established by the Association of Banks in Singapore (ABS), which
formulated IT security guidelines for outsourced service providers (OSPs) that seek to provide services to
Singapore’s financial institutions. The ABS Guidelines are intended to assist financial institutions in
understanding approaches to due diligence, vendor management, and key technical and organizational
controls that should be implemented in cloud outsourcing arrangements, particularly for material
workloads. The OSPAR attestation requires a rigorous audit of security capabilities through an
independent third party.
Microsoft Azure has achieved the OSPAR attestation in the Asia Pacific (Singapore) Region. You can
download the detail OSPAR assessment report in Service Trust Portal. Aside from Azure services listed in
Appendix A, the following online services are also included in OSPAR attestation report: Intune,
Microsoft Graph, Microsoft Stream, Power Apps, Power Automate, Power BI and Power Virtual
Agents.
91 Spain DPA
The Spanish Data Protection Agency (Agencia Española de Protección de Datos – AEPD) has examined
Microsoft Online Services Terms with specific focus on international data transfers and protection of
59
Microsoft Azure Compliance Offerings
personal data belonging to Spanish citizens. Following the assessment, the agency issued a resolution
stating that Azure provides adequate protection for personal data to comply with Spanish Data
Protection Law (Ley Orgánica de Protección de Datos – LOPD). The resolution covers the export of data
to Microsoft Corporation in the United States and, through the EU Model Clauses provisions, the
possibility of onward transfer to subcontractors in other countries where Microsoft operates. The
resolution affirms Microsoft’s commitment to helping Azure customers meet their LOPD compliance
requirements.
Moreover, Microsoft has retained an independent third-party auditing firm in Spain to assess Azure
compliance with LOPD. The resulting certificate and audit report (in Spanish) can be downloaded from
the Service Trust Portal GRC Assessment Reports section.
The framework establishes core policies and mandatory requirements that both government agencies
and their service providers must meet. It defines a set of security controls, many of which align directly
with ISO 27001. The sensitivity of the information—Low, Intermediate, or High—determines the security
measures that must be applied to protect it. The framework prescribes an accreditation process that is
voluntary for systems handling information of Low sensitivity, but mandatory for systems handling
information at an Intermediate or High level of sensitivity. An audit is performed by an accredited
independent auditor; the report is then reviewed as part of a certification process before risk-
management controls are approved in the final accreditation step.
Microsoft Azure has completed a rigorous assessment by an accredited independent auditor and has
obtained an official statement of compliance indicating a Favorable ruling at the ENS High level for the
final audit report. Customers can download the Azure ENS Certificate and Audit Assessment Report
from the Service Trust Portal GRC Assessment Reports section.
93 TruSight
TruSight is a third-party risk-assessment utility created by leading US banks for the collective benefit of
financial institutions, their suppliers, partners, and other third parties. TruSight simplifies assessments
60
Microsoft Azure Compliance Offerings
by executing best-practice, standardized evaluations once and making them available to many—
enabling financial institutions to gain greater visibility into potential risks and manage third-party
relationships more efficiently and effectively. The foundation of TruSight’s methodology is the robust,
standardized Best Practices Questionnaire (BPQ) created by TruSight’s founding banks and updated in
partnership with their customers and industry experts. Its 27 diversified control domains are designed to
meet the industry’s evaluation needs across the categories of information and cyber security, privacy,
business resiliency, and other operational risk domains. For Microsoft, TruSight conducted a rigorous
and comprehensive onsite assessment of Microsoft Azure validate the design and implementation of
controls according to BPQ requirements. The comprehensive validation procedures included structured
inquiries, policy and procedure inspections, reviews with supporting evidence, and onsite dynamic
control observations.
• Cyber Essentials is the first level and includes a self-assessment for organizations to check the
most important IT security controls of their IT infrastructure. The responses are independently
reviewed by an external certifying body.
• Cyber Essentials Plus offers the same controls coverage as Cyber Essentials and also includes
additional assurance by carrying out systems tests of implemented controls through an
authorized third-party certifying body.
Microsoft Azure has attained the Cyber Essentials Plus badge and meets the requirements outlined in
the Cyber Essentials Scheme Assurance Framework. Azure production systems are frequently tested and
audited to provide evidence of a world-leading compliance portfolio. The Azure Cyber Essentials Plus
certification is available to customers for download. Customers can also download the Azure Cyber
Essentials Plus compliance report from the Service Trust Portal GRC Assessment Reports section.
95 UK G-Cloud
Government Cloud (G-Cloud) is a UK government initiative to ease procurement of cloud services by
government departments and promote government-wide adoption of cloud computing. G-Cloud
comprises a series of framework agreements with cloud services suppliers (such as Microsoft), and a
listing of their services in an online store—the Digital Marketplace. This approach enables public-sector
organizations to compare and procure cloud services without having to do their own full review process.
61
Microsoft Azure Compliance Offerings
The G-Cloud appointment process requires cloud service providers to self-certify and supply evidence in
support of the UK National Cyber Security Centre (NCSC) 14 Cloud Security Principles. Every year,
Microsoft Azure prepares documentation and submits evidence to attest that its in-scope cloud services
comply with the principles, giving potential G-Cloud customers an overview of its risk environment. A
GDS accreditor then performs several random checks on the Microsoft assertion statement, samples the
evidence, and makes a determination of compliance.
The appointment of Microsoft Azure to the Digital Marketplace means that UK government agencies
and partners can use in-scope services to store and process UK OFFICIAL government data, which
comprises the vast majority of government data. The following documents are available to customers
for download from the Service Trust Portal GRC Assessment Reports section:
Customers should also review a white paper that describes how Azure addresses the UK government 14
cloud security principles. Moreover, the Azure Security and Compliance Blueprint provides guidance
and automation scripts to deliver an Azure based architecture appropriate for handling many workloads
classified as OFFICIAL. A set of Azure Resource Manager templates can be used to deploy an
environment that aligns to the NCSC 14 Cloud Security Principles and the Center for Internet Security
(CIS) Critical Security Controls. More information is available from the UK OFFICIAL Blueprint landing
page on Service Trust Portal.
96 UK PASF
Microsoft Azure can support UK law enforcement IT customers who require Police Assured Secure
Facilities (PASF) audit assurance. The Home Office’s National Policing Information Risk Management
Team (NPIRMT) has completed a comprehensive review of Azure UK datacenter physical infrastructure
security and concluded that there were no compliance issues or necessary remedial actions identified as
a result of this assessment. Risks identified during PASF audits are managed according to the National
Policing Accreditation Policy as stated in the National Policing Information Risk Management Policy. The
NPIRMT PASF assessment is available from the Home Office to policing customers when conducting
their own risk assessment related to the use of cloud services.
62
Microsoft Azure Compliance Offerings
Singapore OSPAR
ISO 22301:2019
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 27701:2019
Australia IRAP
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI 3DS
PCI DSS
K-ISMS
Azure Service
API Management ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
App Service: API Apps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
App Service: Mobile Apps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
App Service: Web Apps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
App Service: Static Web Apps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Application Gateway ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Application Insights ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Appsource ✓ ✓ ✓ ✓
Automation ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Active Directory (Free and Premium P1 + P2) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Active Directory B2C ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Active Directory Domain Services ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Advanced Threat Protection ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Advisor ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Analysis Services ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Applied AI Services ✓ ✓ ✓ ✓
Azure Healthcare API (previously API for FHIR) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure App Configuration ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Arc enabled servers ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
63
Microsoft Azure Compliance Offerings
Singapore OSPAR
ISO 22301:2019
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 27701:2019
Australia IRAP
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI 3DS
PCI DSS
K-ISMS
Azure Service
64
Microsoft Azure Compliance Offerings
Singapore OSPAR
ISO 22301:2019
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 27701:2019
Australia IRAP
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI 3DS
PCI DSS
K-ISMS
Azure Service
65
Microsoft Azure Compliance Offerings
Singapore OSPAR
ISO 22301:2019
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 27701:2019
Australia IRAP
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI 3DS
PCI DSS
K-ISMS
Azure Service
66
Microsoft Azure Compliance Offerings
Singapore OSPAR
ISO 22301:2019
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 27701:2019
Australia IRAP
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI 3DS
PCI DSS
K-ISMS
Azure Service
67
Microsoft Azure Compliance Offerings
Singapore OSPAR
ISO 22301:2019
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 27701:2019
Australia IRAP
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI 3DS
PCI DSS
K-ISMS
Azure Service
68
Microsoft Azure Compliance Offerings
Singapore OSPAR
ISO 22301:2019
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 27701:2019
Australia IRAP
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI 3DS
PCI DSS
K-ISMS
Azure Service
Container Registry ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Content Delivery Network ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Customer Lockbox for Microsoft Azure ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Data Catalog ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Data Factory ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Data Lake Analytics ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Event Grid ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Event Hubs ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Guest Configuration ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
HDInsight ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Intelligent Recommendations ✓ ✓ ✓ ✓
Key Vault ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Logic Apps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Lustre as a Service ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Machine Learning Studio (Classic) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Microsoft Autonomous Development Platform ✓ ✓ ✓ ✓
Microsoft Azure Attestation ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Microsoft Azure Portal ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Microsoft Cloud for Financial Services ✓ ✓ ✓ ✓
Microsoft Genomics ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Multi-Factor Authentication ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
69
Microsoft Azure Compliance Offerings
Singapore OSPAR
ISO 22301:2019
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 27701:2019
Australia IRAP
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI 3DS
PCI DSS
K-ISMS
Azure Service
Network Watcher ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Notification Hubs ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Power BI Embedded ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Scheduler ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Service Bus ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Storage: Archive Storage ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Storage: Blobs (incl. Azure Data Lake Storage Gen 2) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Storage: Disks (incl. Managed Disks) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Storage: Files ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Storage: Queues ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Storage: Tables ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
StorSimple ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Time Series Insights ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Traffic Manager ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual Machine Scale Sets ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual Machines (incl. Reserved Instances) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual Network ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual Network Address Translation (NAT) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual WAN ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
VPN Gateway ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Virtual Desktop ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
70
Microsoft Azure Compliance Offerings
Singapore OSPAR
ISO 22301:2019
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 27701:2019
Australia IRAP
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI 3DS
PCI DSS
K-ISMS
Azure Service
4 Service operates under the same infrastructure that powers Microsoft Teams. As such, please refer to O365’s compliance offerings that this service adheres with (LINK).
5
Certifications for edge devices (such as Azure Data Box and Azure Stack Edge) apply only to Azure online services component of the service which support on-premises,
customer-managed devices.
71
Microsoft Azure Compliance Offerings
ISO 20000-1:2018
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 9001:2015
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI DSS
Azure Government Service
API Management ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
App Service: API Apps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
App Service: Mobile Apps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
App Service: Web Apps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
App Service: Static Web Apps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Application Gateway ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Application Insights ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Automation ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Active Directory (Free and Basic) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Active Directory (Premium P1 + P2) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Active Directory Domain Services ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Advanced Threat Protection ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Advisor ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Analysis Services ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Healthcare API (previously API for FHIR) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure App Configuration ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Arc enabled Kubernetes ✓ ✓ ✓ ✓ ✓
Azure Arc enabled servers ✓ ✓ ✓ ✓ ✓ ✓
Azure Bastion ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
72
Microsoft Azure Compliance Offerings
ISO 20000-1:2018
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 9001:2015
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI DSS
Azure Government Service
Azure Blueprints ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Bot Service ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Cache for Redis ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Cognitive Search ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Container Service ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Cosmos DB ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Cost Management and Billing ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
2
Azure Data Box ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
2
Azure Stack Edge (formerly Data Box Edge) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Data Explorer ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Data Lake Storage Gen1 ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Data Share ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Database for MariaDB ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Database for MySQL ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Database for PostgreSQL ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Database Migration Service ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Databricks ✓
Azure DDoS Protection ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Dedicated HSM ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Defender for IoT ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure DevTest Labs ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
73
Microsoft Azure Compliance Offerings
ISO 20000-1:2018
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 9001:2015
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI DSS
Azure Government Service
Azure DNS ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure ExpressRoute ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure File Sync ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Firewall ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Firewall Manager ✓
Azure Front Door ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Functions ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure HPC Cache ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Import/Export ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Information Protection ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure IoT Central ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure IoT Hub ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Kubernetes Configuration Management ✓ ✓ ✓ ✓
Azure Kubernetes Service (AKS) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Lab Services ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Lighthouse ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Load Balancer ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Machine Learning ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Managed Applications ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Maps ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Media Services ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
74
Microsoft Azure Compliance Offerings
ISO 20000-1:2018
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 9001:2015
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI DSS
Azure Government Service
Azure Migrate ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Monitor ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure NetApp Files ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Peering Service ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Policy ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Private Link ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Public IP ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Resource Graph ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Resource Manager ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Resource Mover ✓
Azure Security Center ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Sentinel ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Service Fabric ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Service Health ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Service Manager (RDFE) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure SignalR Service ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Signup Portal ✓ ✓ ✓ ✓
Azure Site Recovery ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure SQL ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Stream Analytics ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Synapse Analytics ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
75
Microsoft Azure Compliance Offerings
ISO 20000-1:2018
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 9001:2015
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI DSS
Azure Government Service
ISO 20000-1:2018
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 9001:2015
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI DSS
Azure Government Service
ISO 20000-1:2018
ISO 27018:2019
ISO 27001:2013
ISO 27017:2015
ISO 9001:2015
Germany C5
HIPAA BAA
SOC 1, 2, 3
HITRUST
PCI DSS
Azure Government Service
Storage: Files ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Storage: Queues ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Storage: Tables ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
StorSimple ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Traffic Manager ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual Machine Scale Sets ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual Machines (incl. Reserved Instances) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual Network ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual Network Address Translation (NAT) ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Virtual WAN ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
VPN Gateway ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Azure Virtual Desktop ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
1
For the Azure FedRAMP High, DoD SRG, CJIS, IRS 1075, NIST CSF, and NIST SP 800-171 Scope please refer to the following site.
2
Certifications for edge devices (such as Azure Data Box and Azure Stack Edge) apply only to Azure online services component of the service which support on-premises,
customer-managed devices.
78