AzPolicyAdvertizer

last sync: 2025-Apr-29 17:16:02 UTC

Microsoft Managed Control 1667 - System And Information Integrity Policy And Procedures | Regulatory Compliance - System and Information Integrity

Azure BuiltIn Policy definition

Source Azure Portal
Display name Microsoft Managed Control 1667 - System And Information Integrity Policy And Procedures
Id d61880dc-6e38-4f2a-a30c-3406a98f8220
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 Information Integrity control
Cloud environments AzureCloud = true
AzureUSGovernment = true
AzureChinaCloud = unknown
Available in AzUSGov The Policy is available in AzureUSGovernment cloud. Version: '1.0.0'
Repository: Azure-Policy d61880dc-6e38-4f2a-a30c-3406a98f8220
Additional metadata Name/Id: ACF1667 / Microsoft Managed Control 1667
Category: System and Information Integrity
Title: System And Information Integrity Policy And Procedures - Reviewing Policy And Procedures
Ownership: Customer, Microsoft
Description: The organization: Reviews and updates the current: System and information integrity policy at least annually; and System and information integrity procedures at least annually or whenever a significant change occurs.
Requirements: The Microsoft Information Risk Management Council (IRMC) organization is the governance body with approval responsibility for the Microsoft Security Policy (MSP) and Microsoft Security Program Policy (MSPP). The IRMC consists of representatives from security and risk management teams across Microsoft including Core Services Engineering and Operations (CSEO), Azure, and Global Security. The Customer Security and Trust: Security Engineering (CST-SE) organization manages the review and approval process and maintains the policies. On an annual basis, the CST-SE conducts a line-by-line review of the MSP and MSPP. The Microsoft Security Policy Governance SOP describes each member’s role, types and frequency of review, escalation paths, approval process, and formal publishing procedures of the security policy. Throughout the year, if necessary, CST-SE may convene with the IRMC to conduct reviews after a significant review or change request. The approved policy update is published within the relevant tool on the Microsoft intranet. If service teams establish service-specific or team-specific policies, the respective service teams update the necessary policies at least annually. The Azure team updates the Azure SOPs at least annually through a formal review process. If needed, the Azure team updates the SOP after a significant change affecting policy execution as well. If established, service-team-specific procedures are updated by their respective teams. The individual service teams review and update their respective SOPs at least annually and when required by a significant change. The Azure team updates the Security Standards at least annually through a formal review process. If needed, the Azure team updates the Standards after a significant change affecting policy execution as well. If established, service-team-specific procedures are updated by their respective teams. The individual service teams review and update their respective SOPs at least annually and when required by a significant change.
Mode Indexed
Type Static
Preview False
Deprecated False
Effect Fixed
audit
RBAC role(s) none
Rule aliases none
Rule resource types IF (2)
Compliance
The following 1 compliance controls are associated with this Policy definition 'Microsoft Managed Control 1667 - System And Information Integrity Policy And Procedures' (d61880dc-6e38-4f2a-a30c-3406a98f8220)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
NIS2 LT._Logging_and_Threat_Detection_1 NIS2_LT._Logging_and_Threat_Detection_1 NIS2_LT._Logging_and_Threat_Detection_1 LT. Logging and Threat Detection Risk analysis & information system security policies n/a Responsibility for ensuring the security of network and information system lies, to a great extent, with essential and important entities. A culture of risk management, involving risk assessments and the implementation of cybersecurity risk-management measures appropriate to the risks faced, should be promoted and developed. In order to avoid imposing a disproportionate financial and administrative burden on essential and important entities, the cybersecurity risk-management measures should be proportionate to the risks posed to the network and information system concerned, taking into account the state-of-the-art of such measures, and, where applicable, relevant European and international standards, as well as the cost for their implementation. 24
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type polSet in AzUSGov
[Preview]: NIS2 32ff9e30-4725-4ca7-ba3a-904a7721ee87 Regulatory Compliance Preview BuiltIn unknown
History none
JSON compare n/a
JSON
api-version=2021-06-01
EPAC