AWS whitepapers documentation change
Summary
Removed entire incident response plan documentation including team structure, communication methods, severity definitions, and feedback sections
Security assessment
Deletion of incident response planning content doesn't indicate a security fix. The removed material was preventive guidance, not evidence of vulnerability remediation. No security weaknesses are referenced in the change.
Diff
diff --git a/whitepapers/latest/aws-security-incident-response-guide/develop-and-test-incident-response-plan.md b/whitepapers/latest/aws-security-incident-response-guide/develop-and-test-incident-response-plan.md index a75ed8184..8b1378917 100644 --- a//whitepapers/latest/aws-security-incident-response-guide/develop-and-test-incident-response-plan.md +++ b//whitepapers/latest/aws-security-incident-response-guide/develop-and-test-incident-response-plan.md @@ -1 +0,0 @@ -[View a markdown version of this page](develop-and-test-incident-response-plan.md) @@ -3,46 +1,0 @@ -[](/pdfs/security-ir/latest/userguide/sir-ug.pdf#develop-and-test-incident-response-plan "Open PDF") - -[Documentation](/index.html)[Security Incident Response](/security-ir/index.html)[](what-is.html) - -# Develop and test an incident response plan - -The first document to develop for incident response is the _incident response plan_. The incident response plan is designed to be the foundation for your incident response program and strategy. An incident response plan is a high-level document that typically includes these sections: - - * **An incident response team overview** – Outlines the goals and functions of the incident response team - - * **Roles and responsibilities** – Lists the incident response stakeholders and details their roles when an incident occurs - - * **A communication plan** – Details contact information and how you will communicate during an incident - -It’s a best practice to have out-of-band communication as a backup for incident communication. An example of an application that provides a secure out-of-band communications channel is [AWS Wickr](https://aws.amazon.com/wickr/). - - * **Phases of incident response and actions to take** – Enumerates the phases of incident response – for example, detect, analyze, eradicate, contain, and recover – including high-level actions to take within those phases - - * **Incident severity and prioritization definitions** – Details how to classify the severity of an incident, how to prioritize the incident, and then how the severity definitions affect escalation procedures - - - - -While these sections are common throughout companies of different sizes and industries, each organization’s incident response plan is unique. You will need to build an incident response plan that works best for your organization. - - **Javascript is disabled or is unavailable in your browser.** - -To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. - -[Document Conventions](/general/latest/gr/docconventions.html) - -Process - -Document and centralize architecture diagrams - -Did this page help you? - Yes - -Thanks for letting us know we're doing a good job! - -If you've got a moment, please tell us what we did right so we can do more of it. - -Did this page help you? - No - -Thanks for letting us know this page needs work. We're sorry we let you down. - -If you've got a moment, please tell us how we can make the documentation better.