AzPolicyAdvertizer

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

Microsoft Managed Control 1371 - Incident Reporting | Regulatory Compliance - Incident Response

Azure BuiltIn Policy definition

Source Azure Portal
Display name Microsoft Managed Control 1371 - Incident Reporting
Id 9447f354-2c85-4700-93b3-ecdc6cb6a417
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 9447f354-2c85-4700-93b3-ecdc6cb6a417
Additional metadata Name/Id: ACF1371 / Microsoft Managed Control 1371
Category: Incident Response
Title: Incident Reporting - Required Timeframe
Ownership: Customer, Microsoft
Description: The organization: Requires personnel to report suspected security incidents to the organizational incident response capability within US-CERT incident categorization and reporting timelines as specified in NIST SP800-61 (as amended); and
Requirements: All Microsoft personnel are required to immediately report events when they believe that a security incident has occurred. Examples of such events include, but are not limited to: * Alerts, notifications, error messages, or other automated warnings that indicate a security incident may have occurred. * Reports of security incidents received from external parties, including customers, members of the press, or the general public. * Personal observations of anomalies or unexpected events that might indicate a security incident has occurred. * Indication of virus, malicious software or hacker activity. Personnel can report incidents by manually entering event related data directly into the incident management ticketing system which is classified in accordance with NIST SP 800-61 standards based on the Classification, Escalation, and Notification (CEN) Matrix and escalated or by sending email to cdoc@microsoft.com. Tickets are routed automatically to the Security Response Team. Any incident that involves the breach of personal information (PII or above) also requires a notification to the Security team at alias cdoc@microsoft.com. Security then loops in the dedicated Privacy team if needed. Incidents that involve the exposure of information covered by Privacy Policy necessitate the involvement of the Privacy team.
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 1371 - Incident Reporting' (9447f354-2c85-4700-93b3-ecdc6cb6a417)
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