AzPolicyAdvertizer

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

Microsoft Managed Control 1360 - Incident Handling | Regulatory Compliance - Incident Response

Azure BuiltIn Policy definition

Source Azure Portal
Display name Microsoft Managed Control 1360 - Incident Handling
Id be5b05e7-0b82-4ebc-9eda-25e447b1a41e
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 Incident Response 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 be5b05e7-0b82-4ebc-9eda-25e447b1a41e
Additional metadata Name/Id: ACF1360 / Microsoft Managed Control 1360
Category: Incident Response
Title: Incident Handling - Required Components
Ownership: Customer, Microsoft
Description: The organization: Implements an incident handling capability for security incidents that includes preparation, detection and analysis, containment, eradication, and recovery;
Requirements: Azure implements a standardized incident handling framework derived from multiple incident handling methodologies including NIST SP 800-61 Rev. 2, Computer Security Incident Handling Guide, ISO/IEC 27035:2011, and the SANS Institute publication Computer Security Incident Handling. The Azure C+AI Incident Management process includes multiple stages throughout the resolution of an incident. Incidents may be managed with the Crisis Management or Security Customer Reportable Security or Privacy Incident sub-processes of the overarching Incident Management process. When incidents become triaged as a high severity event (Severity 1 or higher, Severity 0 being the highest) they are managed with the Customer Reportable Security or Privacy Incident sub-process. The process includes steps for preparation, detection and analysis, containment, eradication, and recovery and post-incident activity. Full investigations are conducted by the Security Response Team investigators and are overseen by a Security Incident Manager; this is accomplished through the forensic retrieval of data from affected assets and/or retrieval of relevant event data. Azure ensures individuals that are part of the Security Response Team meet personnel security requirements commensurate with the criticality and sensitivity of the information being processed, stored, and transmitted in Azure. Azure actively plans and implements sustainable security incident management capabilities. incident management activities are reviewed regularly and improvements for infrastructure protection are identified to improve incident management capabilities. Azure ensures individuals that are part of the Security Response Team meet personnel security requirements commensurate with the criticality and sensitivity of the information being processed, stored, and transmitted in Azure. Additionally, Azure reports confirmed security and availability incidents to DoD, US-CERT and affected customers in accordance with applicable policies and procedures.
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 2 compliance controls are associated with this Policy definition 'Microsoft Managed Control 1360 - Incident Handling' (be5b05e7-0b82-4ebc-9eda-25e447b1a41e)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
NIS2 IR._Incident_Response_2 NIS2_IR._Incident_Response_2 NIS2_IR._Incident_Response_2 IR. Incident Response Incident handling n/a Where essential or important entities become aware of a significant incident, they should be required to submit an early warning without undue delay and in any event within 24 hours. That early warning should be followed by an incident notification. The entities concerned should submit an incident notification without undue delay and in any event within 72 hours of becoming aware of the significant incident, with the aim, in particular, of updating information submitted through the early warning and indicating an initial assessment of the significant incident, including its severity and impact, as well as indicators of compromise, where available. A final report should be submitted not later than one month after the incident notification. The early warning should only include the information necessary to make the CSIRT, or where applicable the competent authority, aware of the significant incident and allow the entity concerned to seek assistance, if required. Such early warning, where applicable, should indicate whether the significant incident is suspected of being caused by unlawful or malicious acts, and whether it is likely to have a cross-border impact. Member States should ensure that the obligation to submit that early warning, or the subsequent incident notification, does not divert the notifying entity’s resources from activities related to incident handling that should be prioritised, in order to prevent incident reporting obligations from either diverting resources from significant incident response handling or otherwise compromising the entity’s efforts in that respect. 27.12.2022 EN Official Journal of the European Union L 333/99 In the event of an ongoing incident at the time of the submission of the final report, Member States should ensure that entities concerned provide a progress report at that time, and a final report within one month of their handling of the significant incident 34
op.exp.7 Incident management op.exp.7 Incident management 404 not found n/a n/a 103
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
Spain ENS 175daf90-21e1-4fec-b745-7b4c909aa94c Regulatory Compliance GA BuiltIn unknown
History none
JSON compare n/a
JSON
api-version=2021-06-01
EPAC