AzPolicyAdvertizer

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

Microsoft Managed Control 1374 - Incident Response Assistance | Regulatory Compliance - Incident Response

Azure BuiltIn Policy definition

Source Azure Portal
Display name Microsoft Managed Control 1374 - Incident Response Assistance
Id cc5c8616-52ef-4e5e-8000-491634ed9249
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 cc5c8616-52ef-4e5e-8000-491634ed9249
Additional metadata Name/Id: ACF1374 / Microsoft Managed Control 1374
Category: Incident Response
Title: Incident Response Assistance
Ownership: Customer, Microsoft
Description: The organization provides an incident response support resource, integral to the organizational incident response capability that offers advice and assistance to users of the information system for the handling and reporting of security incidents.
Requirements: For all asset types, Azure implements both internal and external sites which offer advice and assistance to Azure personnel and customers for handling and reporting of security incidents. Azure sites are supported on SharePoint and internal access is granted to appropriate personnel. Internal Azure policies and procedures are distributed and published to a central SharePoint repository and are accessible to all Azure personnel. The Azure Security Response Team provides regular updates around event triage and incident management which are available to all applicable Azure incident management personnel. Azure use the services of the Cyber Defense Operations Center (CDOC) to manage incident questions and reporting by Microsoft personnel. Microsoft personnel can report incidents using the email alias “cdoc@microsoft.com” or via Incident Management (IcM) which is then routed to the appropriate Azure team. Internal web pages offer advice and assistance to service teams for the handling and reporting of security incidents. These web pages provide the following information to Azure personnel: * What are security incidents * How to identify such incidents * How to escalate the security incidents * List of sample security incidents * Who to contact in the event of a security incident The Azure Security Response Team also posts a phone number and email alias on their internal website. This contact information is provided for service team personnel to use when required to file a security incident. Additionally, security contact information is available as part of IcM. Depending on the nature of the incident, Azure may engage subject matter experts (SMEs) from other organizations within Microsoft to facilitate investigative needs. External The Azure Trust Center describes how to submit a security incident in Azure. The Microsoft Developer Network (MSDN) webpage also provides support to customers and links them to a wide variety of web pages which provide guidance around information security incidents related to their cloud environment and customer support, if needed. Customers can report security events at any time through the customer support website handled by Customer Support Services (CSS). CSS routes it to appropriate service team. In addition, possible security incidents and abuse can be reported on . These reports are received by the Online Services Security and Compliance Security team and then routed to the appropriate service team to investigate and correct the event. There is also a dedicated phone line that is available on a twenty-four (24) hours a day, seven (7) days a week basis to report events at 1-866-676-6546. Working with the C+AI Security Response Team, external parties such as law enforcement, Information Security Programs (ISPs), and other partners can identify security issues. For example, the Global Infrastructure Alliance for Internet Security (GIAIS) utilizes the Microsoft Security Response Alliance to feed security concerns to Microsoft’s online services which is then routed to the appropriate Azure service teams.
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 1374 - Incident Response Assistance' (cc5c8616-52ef-4e5e-8000-491634ed9249)
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