forked from aws-samples/aws-iam-access-key-auto-rotation
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Tracy
committed
Jan 14, 2021
1 parent
24552b1
commit 352aab1
Showing
2 changed files
with
42 additions
and
25 deletions.
There are no files selected for viewing
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,25 +1,42 @@ | ||
| To all application owners, | ||
|
|
||
| Security is the top-most priority of any organization. To ensure continued success in our drive to design and architect a secure infrastructure, we are implementing a 90-day automatic rotation of all AWS IAM User Access Keys. This will begin on DATE HERE. | ||
|
|
||
| Why is this important and how does fixing this help you? | ||
| Rotating Identity and Access Management (IAM) credentials periodically will significantly reduce the chances that a compromised set of access keys can be used without your knowledge to access certain components within your AWS account. | ||
|
|
||
| What this means for you: | ||
| You will need to update your applications every 90-days with the new Access Key pair. These can be found in AWS Secrets Manager in a secret accessible by your application’s AWS IAM User only. You will have a grace period of 10 days after rotation before old Access Keys are disabled. There will be another 10-day grace period before old Access Keys are deleted. Until they are disabled, old Access Keys can be used to programmatically retrieve the new Access Keys from AWS Secrets Manager. | ||
|
|
||
| Enabling this setting will also help you align with the following compliance standards: | ||
| • The Center of Internet Security AWS Foundations Benchmark | ||
| • APRA | ||
| • MAS | ||
| • National Institute of Standards and Technology (NIST) | ||
| • AWS Well-Architected Framework | ||
|
|
||
| AWS Resources with Violations Detected: | ||
| [insert-violations-here] | ||
|
|
||
| Should you have any questions, please reach out to EMAIL ADDRESS HERE. As always, thank you for continuing to strive for a secure work environment. | ||
|
|
||
| Sincerely, | ||
|
|
||
| INFO HERE | ||
| <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> | ||
| <html> | ||
| <head> | ||
| <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> | ||
| <meta http-equiv="Content-Style-Type" content="text/css"> | ||
| <title></title> | ||
| <meta name="Generator" content="Cocoa HTML Writer"> | ||
| <meta name="CocoaVersion" content="1894.6"> | ||
| <style type="text/css"> | ||
| p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica} | ||
| </style> | ||
| </head> | ||
| <body> | ||
| <p class="p1"> | ||
| To all application owners,<br> | ||
| <br> | ||
| Security is the top-most priority of any organization. To ensure continued success in our drive to design and architect a secure infrastructure, we are implementing a 90-day automatic rotation of all AWS IAM User Access Keys. This will begin on 2/1/20201.<br> | ||
| <br> | ||
| Why is this important and how does fixing this help you?<br> | ||
| Rotating Identity and Access Management (IAM) credentials periodically will significantly reduce the chances that a compromised set of access keys can be used without your knowledge to access certain components within your AWS account.<br> | ||
| <br> | ||
| What this means for you:<br> | ||
| You will need to update your applications every 90-days with the new Access Key pair. These can be found in AWS Secrets Manager in a secret accessible by your application’s AWS IAM User only. You will have a grace period of 10 days after rotation before old Access Keys are disabled. There will be another 10-day grace period before old Access Keys are deleted. Until they are disabled, old Access Keys can be used to programmatically retrieve the new Access Keys from AWS Secrets Manager.<br> | ||
| <br> | ||
| Enabling this setting will also help you align with the following compliance standards:<br> | ||
| <br> | ||
| • The Center of Internet Security AWS Foundations Benchmark<br> | ||
| • APRA<br> | ||
| • MAS<br> | ||
| • National Institute of Standards and Technology (NIST)<br> | ||
| • AWS Well-Architected Framework<br> | ||
| <br> | ||
| AWS IAM Access Keys have been rotated for the below:<br> | ||
| [insert-violations-here]<br> | ||
| <br> | ||
| Should you have any questions, please reach out to [email protected]. As always, thank you for continuing to strive for a secure work environment.<br> | ||
| <br> | ||
| Sincerely,<br> | ||
| <br> | ||
| Tracy Pierce;</p> | ||
| </body> | ||
| </html> |