AWS whitepapers documentation change
Summary
Removed entire content of the preparation page including incident response domains (People, Process, Technology), navigation elements, and user feedback sections.
Security assessment
The change deletes documentation content but provides no evidence of addressing a specific security vulnerability. While the topic relates to security incident response, the removal itself doesn't indicate a security fix or vulnerability mitigation.
Diff
diff --git a/whitepapers/latest/aws-security-incident-response-guide/preparation.md b/whitepapers/latest/aws-security-incident-response-guide/preparation.md index c350b6c4b..8b1378917 100644 --- a//whitepapers/latest/aws-security-incident-response-guide/preparation.md +++ b//whitepapers/latest/aws-security-incident-response-guide/preparation.md @@ -1 +0,0 @@ -[View a markdown version of this page](preparation.md) @@ -3,40 +1,0 @@ -[](/pdfs/security-ir/latest/userguide/sir-ug.pdf#preparation "Open PDF") - -[Documentation](/index.html)[Security Incident Response](/security-ir/index.html)[](what-is.html) - -# Preparation - -Preparing for an incident is critical for timely and effective incident response. Preparation is done across three domains: - - * **People** – Preparing your people for a security incident involves identifying the relevant stakeholders for incident response and training them on incident response and cloud technologies. - - * **Process** – Preparing your processes for a security incident involves documenting architectures, developing thorough incident response plans, and creating playbooks for consistent response to security events. - - * **Technology** – Preparing your technology for a security incident involves setting up access, aggregating and monitoring necessary logs, implementing effective alerting mechanisms, and developing response and investigative capabilities. - - - - -Each of these domains are equally important for effective incident response. No incident response program is complete or effective without all three. You will need to prepare people, processes, and technologies with tight integration in order to be prepared for an incident. - - **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) - -Introduction - -People - -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.