AWS IDR documentation change
Summary
Completely restructured the incident reporting process with clearer steps, added optional file attachments, and removed illustrations
Security assessment
The changes improve incident reporting procedures but don't address specific security vulnerabilities or weaknesses. While incident response is security-related, these are process clarifications without evidence of fixing security flaws.
Diff
diff --git a/IDR/latest/userguide/inbound-incident-idr.md b/IDR/latest/userguide/inbound-incident-idr.md index d31a4cf10..a703b70d0 100644 --- a//IDR/latest/userguide/inbound-incident-idr.md +++ b//IDR/latest/userguide/inbound-incident-idr.md @@ -21 +21 @@ To request an Incident Response for an incident that's actively impacting your w - 1. Open the [AWS Support Center Console](https://console.aws.amazon.com/support/home#/), and then choose **Create case**. +To request an incident response, complete the following steps: @@ -23 +23 @@ To request an Incident Response for an incident that's actively impacting your w - 2. Choose **Technical**. + 1. Open the [AWS Support Center Console](https://console.aws.amazon.com/support/home#/) to create a new support case. @@ -25 +25 @@ To request an Incident Response for an incident that's actively impacting your w - 3. For **Service** , choose **Incident Detection and Response**. + 2. For **Subject** , enter a brief summary of the incident. For example, `AWS Incident Detection and Response - Active Incident - workload_name`. @@ -27 +27 @@ To request an Incident Response for an incident that's actively impacting your w - 4. For **Category** , choose **Active Incident**. + 3. For **Description** , enter the details of the incident. We recommend that you include the following details in your support case: @@ -29 +29 @@ To request an Incident Response for an incident that's actively impacting your w - 5. For **Severity** , choose **Business-critical system down**. + * Affected AWS resource ARN(s), workload name and its function @@ -31 +31 @@ To request an Incident Response for an incident that's actively impacting your w - 6. Enter a **Subject** for this incident. For example: + * Description of impact to the business @@ -33 +33 @@ To request an Incident Response for an incident that's actively impacting your w -AWS Incident Detection and Response - Active Incident - workload_name + * (Optional) Your preferred conference bridge URL. If you don't provide bridge details, AWS Incident Detection and Response creates an AWS conference bridge and sends you an invitation with the bridge URL. @@ -35 +35 @@ AWS Incident Detection and Response - Active Incident - workload_name - 7. Enter the **Problem Description** for this incident. Add the following details: + 4. (Optional) Attach files that can help describe the incident, such as screenshots or log excerpts. @@ -37 +37 @@ AWS Incident Detection and Response - Active Incident - workload_name - * **Technical Information:** + 5. Configure the following case classification fields: @@ -39 +39 @@ AWS Incident Detection and Response - Active Incident - workload_name -Workload Name + * **Case type** : **Technical** @@ -41 +41 @@ Workload Name -Affected AWS Resource ARN(s) + * **Service** : **Incident Detection and Response** @@ -43 +43 @@ Affected AWS Resource ARN(s) - * **Business Information:** + * **Category** : **Active Incident** @@ -45 +45 @@ Affected AWS Resource ARN(s) -Description of impact to the business + * **Severity** : **Business-critical system down** @@ -47 +47 @@ Description of impact to the business -[Optional] Customer Bridge Details + 6. Provide additional context to help AWS Incident Detection and Response engage AWS experts faster, such as the impacted AWS service, impacted AWS Region, business impact, impact start time, and affected resources. @@ -49 +49 @@ Description of impact to the business - 8. To help us engage AWS experts faster, provide the following details: + 7. Choose **Submit**. @@ -51,25 +51 @@ Description of impact to the business - * Impacted AWS service - - * Additional Service(s) / Other Impacted - - * Impacted AWS Region - - 9. In the **Additional contacts** section, enter any email addresses that you want to receive correspondences about this incident. - -The following illustration shows the console screen with the **Additional contacts** field highlighted. - - - - 10. Choose **Submit**. - -After submitting an Incident Response request, you can add additional email addresses from your organization. To add additional addresses, reply to the case, and then add the email addresses in the **Additional contacts** section. - -The following illustration shows the **Case details** screen with the **Reply** button highlighted. - - - -The following illustration shows the case Reply with the **Additional contacts** field and **Submit** button highlighted. - - - - 11. AWS Incident Detection and Response acknowledges your case within five minutes and engages you on a conference bridge with the appropriate AWS experts. + 8. AWS Incident Detection and Response acknowledges your case within five minutes and engages you on a conference bridge with the appropriate AWS experts.