AWS Security ChangesHomeSearch

AWS whitepapers documentation change

Service: whitepapers · 2026-06-19 · Documentation low

File: whitepapers/latest/aws-security-incident-response-guide/aws-security-incident-response-guide.md

Summary

Removed entire Security Incident Response Guide content including abstract, table of contents, and Well-Architected Framework references

Security assessment

This deletes the main incident response guide documentation but contains no indicators of security vulnerability remediation. The removed material was general guidance without references to specific security flaws or patches.

Diff

diff --git a/whitepapers/latest/aws-security-incident-response-guide/aws-security-incident-response-guide.md b/whitepapers/latest/aws-security-incident-response-guide/aws-security-incident-response-guide.md
index 46348fea9..8b1378917 100644
--- a//whitepapers/latest/aws-security-incident-response-guide/aws-security-incident-response-guide.md
+++ b//whitepapers/latest/aws-security-incident-response-guide/aws-security-incident-response-guide.md
@@ -1 +0,0 @@
-[View a markdown version of this page](security-incident-response-guide.md)
@@ -3,68 +1,0 @@
-[](/pdfs/security-ir/latest/userguide/sir-ug.pdf#security-incident-response-guide "Open PDF")
-
-[Documentation](/index.html)[Security Incident Response](/security-ir/index.html)[](what-is.html)
-
-AbstractAre you Well-Architected? 
-
-# AWS Security Incident Response Technical Guide
-
-###### Contents
-
-  * Abstract
-
-  * Are you Well-Architected?
-
-  * [Introduction](./introduction.html)
-
-  * [Preparation](./preparation.html)
-
-  * [Operations](./operations.html)
-
-  * [Post-incident activity](./post-incident-activity.html)
-
-  * [Conclusion](./conclusion.html)
-
-  * [Contributors](./contributors.html)
-
-  * [Appendix A: Cloud capability definitions](./appendix-a-cloud-capability-definitions.html)
-
-  * [Appendix B: AWS incident response resources](./appendix-b-incident-response-resources.html)
-
-  * [Notices](./notices.html)
-
-
-
-
-## Abstract
-
-This guide presents an overview of the fundamentals of responding to security incidents within a customer’s Amazon Web Services (AWS) Cloud environment. It provides an overview of cloud security and incident response concepts and identifies cloud capabilities, services, and mechanisms that are available to customers who respond to security issues. 
-
-This guide is intended for those in technical roles and assumes that you are familiar with the general principles of information security, have a basic understanding of security incident response in your current on-premises environments, and have some familiarity with cloud services. 
-
-## Are you Well-Architected?
-
-The [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/) helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the [AWS Well-Architected Tool](https://aws.amazon.com/well-architected-tool/), available at no charge in the [AWS Well-Architected Tool console](https://console.aws.amazon.com/wellarchitected), you can review your workloads against these best practices by answering a set of questions for each pillar. 
-
-For more expert guidance and best practices for your cloud architecture—reference architecture deployments, diagrams, and whitepapers—refer to the [AWS Architecture Center](https://aws.amazon.com/architecture/). 
-
-![Warning](https://d1ge0kk1l5kms0.cloudfront.net/images/G/01/webservices/console/warning.png) **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)
-
-Service Quotas
-
-Introduction
-
-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.