This document is provided for informational purposes only. It represents the current product offerings and practices from Amazon Web Services (AWS) as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.
© 2024 Amazon Web Services, Inc. or its affiliates. All Rights Reserved. This work is licensed under a Creative Commons Attribution 4.0 International License.
This AWS Content is provided subject to the terms of the AWS Customer Agreement available at http://aws.amazon.com/agreement or other written agreement between the Customer and either Amazon Web Services, Inc. or Amazon Web Services EMEA SARL or both.
This comprehensive framework and the included documents are provided as templates using non-prescriptive guidance to demonstrate how people (the informed customer) , processes (this playbook framework) , and technology (using open source GitHub) may be aligned to establish an Incident Response Playbook library.
This resource is intentionally incomplete. This allows the customer to adopt a framework while providing enough ambiguity and flexibility to think strategically as they navigate their incident response documentation essentials, wants, and needs. There is no one absolute answer; it is essential to integrate this process with your operational demands, objectives, and outcomes.
The included Bitcoin Template is an example of a playbook for a specific situation. You should make certain the template, and all other materials in this archive, are customized for your environment(s) and resources and test it before implementing for purposes in production. Forking or mirroring this archive is NOT sufficient for a practical execution of an incident response playbook library.
Customers should also use a private GitHub repository in combination with best practices and scanning tools to mitigate and prevent sensitive data exposure. Some examples of resources that could be used include:
- Ten GitHub Security Best Practices
- Scan for Sensitive Information Using Git-Secrets
- Fighting Sensitive Data Exposure with Automation
- Github Credentials Scanner
These playbooks contains translations performed using machine translation with AWS Translate. These playbooks have not been reviewed by a human translator and may contain errors. Please ensure you review the documents before using to ensure correct context and language for your individual use case. If you would like to contribute to correcting errors and reviewing the errors, we welcome that assistance.