AWS whitepapers documentation change
Summary
Removed entire content including tagging strategy guidance, PDF reference, navigation elements, and feedback sections
Security assessment
The change deletes documentation about tagging strategies for incident response but shows no evidence of addressing a specific security vulnerability. While tagging supports security operations, this removal appears to be routine content reorganization.
Diff
diff --git a/whitepapers/latest/aws-security-incident-response-guide/develop-and-implement-tagging-strategy.md b/whitepapers/latest/aws-security-incident-response-guide/develop-and-implement-tagging-strategy.md index c6f017630..8b1378917 100644 --- a//whitepapers/latest/aws-security-incident-response-guide/develop-and-implement-tagging-strategy.md +++ b//whitepapers/latest/aws-security-incident-response-guide/develop-and-implement-tagging-strategy.md @@ -1 +0,0 @@ -[View a markdown version of this page](develop-and-implement-tagging-strategy.md) @@ -3,31 +1,0 @@ -[](/pdfs/security-ir/latest/userguide/sir-ug.pdf#develop-and-implement-tagging-strategy "Open PDF") - -[Documentation](/index.html)[Security Incident Response](/security-ir/index.html)[](what-is.html) - -# Develop and implement a tagging strategy - -Obtaining contextual information on the business use case and relevant internal stakeholders surrounding an AWS resource can be difficult. One way to do this is in the form of tags, which assign metadata to your AWS resources and consist of a user-defined key and value. You can create tags to categorize resources by purpose, owner, environment, type of data processed, and other criteria of your choice. - -Having a consistent tagging strategy can speed up response times by allowing you to quickly identify and discern contextual information about an AWS resource. Tags can also serve as a mechanism to initiate response automations. For further information on what to tag, refer to the [documentation on tagging AWS resources](https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html). You’ll want to first define the tags you want to implement across your organization. After that, you’ll implement and enforce this tagging strategy. Details on implementation and enforcement can be found in the AWS blog [Implement AWS resource tagging strategy using AWS Tag Policies and Service Control Policies (SCPs)](https://aws.amazon.com/blogs/mt/implement-aws-resource-tagging-strategy-using-aws-tag-policies-and-service-control-policies-scps/). - - **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) - -Develop AWS account structure - -Update AWS account contact information - -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.