{"id":80234,"date":"2018-02-26T09:00:04","date_gmt":"2018-02-26T17:00:04","guid":{"rendered":"https:\/\/cloudblogs.microsoft.com\/microsoftsecure\/?p=80234"},"modified":"2023-05-26T15:21:28","modified_gmt":"2023-05-26T22:21:28","slug":"best-practices-for-securely-moving-workloads-to-microsoft-azure","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2018\/02\/26\/best-practices-for-securely-moving-workloads-to-microsoft-azure\/","title":{"rendered":"Best practices for securely moving workloads to Microsoft Azure"},"content":{"rendered":"

Azure is Microsoft\u2019s cloud computing environment. It offers customers three primary service delivery models including infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS). Adopting cloud technologies requires a shared responsibility model for security, with Microsoft responsible for certain controls and the customer others, depending on the service delivery model chosen. To ensure that a customer\u2019s cloud workloads are protected, it is important that they carefully consider and implement the appropriate architecture and enable the right set of configuration settings.<\/p>\n

Microsoft has developed a set of Azure security guidelines and best practices for our customers to follow. These guides can be found in the\u00a0Azure security best practices and patterns documentation<\/a>. In addition, we\u2019re excited to announce the availability of the Center for Internet Security\u2019s (CIS) Microsoft Azure Foundations Security Benchmark, developed in partnership with Microsoft. CIS is a non-profit entity focused on developing global standards and recognized best practices for securing IT systems and data against the most pervasive attacks.<\/p>\n

The CIS Microsoft Azure Foundations Security Benchmark provides prescriptive guidance for establishing a secure baseline configuration for Microsoft Azure. Its scope is designed to assist organizations in establishing the foundation level of security for anyone adopting the Microsoft Azure cloud. The benchmark should not be considered as an exhaustive list of all possible security configurations and architecture but as a starting point. Each organization must still evaluate their specific situation, workloads, and compliance requirements and tailor their environment accordingly.<\/p>\n

The CIS benchmark contains two levels, each with slightly different technical specifications:<\/p>\n