| Source | Azure Portal | ||
| Display name | Microsoft Managed Control 1559 - System And Services Acquisition Policy And Procedures | ||
| Id | 45692294-f074-42bd-ac54-16f1a3c07554 | ||
| Version | 1.0.0 Details on versioning |
||
| Versioning |
Versions supported for Versioning: 0 Built-in Versioning [Preview] |
||
| Category | Regulatory Compliance Microsoft Learn |
||
| Description | Microsoft implements this System and Services Acquisition control | ||
| Additional metadata |
Name/Id: ACF1559 / Microsoft Managed Control 1559 Category: System and Services Acquisition Title: System And Services Acquisition Policy And Procedures - Creating Policy And Procedures Ownership: Customer, Microsoft Description: The organization: Develops, documents, and disseminates to personnel with system and services acquisition roles and responsibilities: A system and services acquisition policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls; and Requirements: Azure addresses the system and services acquisition policy as part of the Microsoft security policies, of which there are two sets: the Microsoft Security Policy (MSP) that is applicable to all personnel, and the Microsoft Security Program Policy (MSPP), which is applicable to all personnel that have a responsibility for security. The Microsoft Information Risk Management Council (IRMC) is the governance body with review and approval responsibility for the MSP and MSPP. Within Azure, the MSPP specifically applies to all personnel involved in designing, building, and operating Azure and across all information and processes used in the conduct of Microsoft business. All Azure personnel are accountable and responsible for complying with these guiding principles within their designated roles. The policy addresses the following: * Ownership of third-party relationships * Security Development Lifecycle (SDL) * Introduction of new hardware, software, or services Additionally, the policy addresses the purpose, scope, roles, responsibilities, compliance requirements, and required coordination among the various Microsoft organizations that provide some level of support to all services. The policies indicate Microsoft management’s commitment and are a component of the risk management strategy which provides Azure personnel with a current set of clear and concise information security requirements. The MSP is available to all Microsoft personnel on the Microsoft Policy website on the Microsoft intranet, and the MSPP and Security Standards are available through the Liquid tool, also on the Microsoft intranet. The Azure SOPs are stored in the Azure Security, Privacy & Compliance SharePoint site. This SharePoint site is accessible to all Azure personnel. To meet controls for system and services acquisition, Azure maintains teams with responsibilities to procure professional services, review contracts to Microsoft corporate standards, and procure assets for the delivery of Azure services. Multiple standards, processes, and SOPs are maintained by individual Azure teams to support the implementation and adherence to the MSPP section on Supplier Relationships. Microsoft system and services procurement activities are managed through a companywide team. All external suppliers of services or systems must be approved by the Global Procurement Group (GPG) and have a signed contract on file. The contract includes sections outlining security requirements and service level monitoring to be enforced. GPG requires the external suppliers of services to comply with all applicable Microsoft security policies and implement security procedures to prevent disclosure of Microsoft Confidential information. Microsoft includes provisions in the MSA and any associated Statements of Work (SOW) with each vendor addressing the need to employ appropriate security controls. Additionally, vendors that handle high business impact data must be in annual compliance with the Microsoft Vendor Privacy Assurance (VPA) program. Statements of Work (SOW) and Purchase Orders (PO) can only be submitted for suppliers who have approved contracts. The GPG team as well as Microsoft’s Corporate, External, and Legal Affairs (CELA) review these documents before being approved. These materials are formally documented and stored within each team’s internal Azure SharePoint site as a central repository. Only individuals with authorized credentials, adequate levels of permission, legitimate need to know, and specific roles/responsibilities are given access to the material. |
||
| Mode | Indexed | ||
| Type | Static | ||
| Preview | False | ||
| Deprecated | False | ||
| Effect | Fixed audit |
||
| RBAC role(s) | none | ||
| Rule aliases | none | ||
| Rule resource types | IF (2) Microsoft.Resources/subscriptions Microsoft.Resources/subscriptions/resourceGroups |
||
| Compliance | Not a Compliance control | ||
| Initiatives usage | none | ||
| History | none | ||
| JSON compare | n/a | ||
| JSON |
|