AWS solutions documentation change
Summary
Updated template filenames and resource references from 'aws-sharr-*' to 'automated-security-response-*' naming convention
Security assessment
The changes appear to be rebranding/renaming of CloudFormation templates related to security automation (SHARR to ASR). While the solution is security-focused, there's no evidence these changes address specific vulnerabilities. Updates maintain documentation for security response orchestration features.
Diff
diff --git a/solutions/latest/automated-security-response-on-aws/deployment-stackset.md b/solutions/latest/automated-security-response-on-aws/deployment-stackset.md index c82b6133d..19e3bca4f 100644 --- a//solutions/latest/automated-security-response-on-aws/deployment-stackset.md +++ b//solutions/latest/automated-security-response-on-aws/deployment-stackset.md @@ -76 +76 @@ Step 1: Launch the admin stack in the delegated Security Hub admin account - * Using a self-managed StackSet, launch the `aws-sharr-deploy.template` AWS CloudFormation template into your AWS Security Hub admin account in the same Region as your Security Hub admin. This template uses nested stacks. + * Using a self-managed StackSet, launch the `automated-security-response-admin.template` AWS CloudFormation template into your AWS Security Hub admin account in the same Region as your Security Hub admin. This template uses nested stacks. @@ -80 +80 @@ Step 1: Launch the admin stack in the delegated Security Hub admin account - * Choose an existing Orchestrator log group to use. Select `Yes` if `SO0111-SHARR- Orchestrator` already exists from a previous installation. + * Choose an existing Orchestrator log group to use. Select `Yes` if `SO0111-ASR- Orchestrator` already exists from a previous installation. @@ -91 +91 @@ Wait for Step 1 to complete deployment, because the template in Step 2 reference - * Using a service-managed StackSet, launch the `aws-sharr-member-roles.template` AWS CloudFormation template into a single Region in each account in your AWS Organizations. + * Using a service-managed StackSet, launch the `automated-security-response-member-roles.template` AWS CloudFormation template into a single Region in each account in your AWS Organizations. @@ -102 +102 @@ Step 3: Launch the member stack into each AWS Security Hub member account and Re - * Using self-managed StackSets, launch the `aws-sharr-member.template` AWS CloudFormation template into all Regions where you have AWS resources in every account in your AWS Organization managed by the same Security Hub admin. + * Using self-managed StackSets, launch the `automated-security-response-member.template` AWS CloudFormation template into all Regions where you have AWS resources in every account in your AWS Organization managed by the same Security Hub admin. @@ -166 +166 @@ You can choose to use a Jira API key in place of your password by providing your - 1. Launch the [admin stack](https://solutions-reference.s3.amazonaws.com/automated-security-response-on-aws/latest/aws-sharr-deploy.template), `aws-sharr-deploy.template`, with your Security Hub admin account. Typically, one per organization in a single Region. Because this stack uses nested stacks, you must deploy this template as a self-managed StackSet. + 1. Launch the [admin stack](https://solutions-reference.s3.amazonaws.com/automated-security-response-on-aws/latest/automated-security-response-admin.template), `automated-security-response-admin.template`, with your Security Hub admin account. Typically, one per organization in a single Region. Because this stack uses nested stacks, you must deploy this template as a self-managed StackSet. @@ -181 +181 @@ You can choose to use a Jira API key in place of your password by providing your -Use a service-managed StackSets to deploy the [member roles template](https://solutions-reference.s3.amazonaws.com/automated-security-response-on-aws/latest/aws-sharr-member-roles.template), `aws-sharr-member-roles.template`. This StackSet must be deployed in one Region per member account. It defines the global roles that allow cross-account API calls from the SHARR Orchestrator step function. +Use a service-managed StackSets to deploy the [member roles template](https://solutions-reference.s3.amazonaws.com/automated-security-response-on-aws/latest/automated-security-response-member-roles.template), `automated-security-response-member-roles.template`. This StackSet must be deployed in one Region per member account. It defines the global roles that allow cross-account API calls from the ASR Orchestrator step function. @@ -198 +198 @@ Use a service-managed StackSets to deploy the [member roles template](https://so -Because the [member stack](https://solutions-reference.s3.amazonaws.com/automated-security-response-on-aws/latest/aws-sharr-member.template) uses nested stacks, you must deploy as a self-managed StackSet. This does not support automatic deployment to new accounts in the AWS Organization. +Because the [member stack](https://solutions-reference.s3.amazonaws.com/automated-security-response-on-aws/latest/automated-security-response-member.template) uses nested stacks, you must deploy as a self-managed StackSet. This does not support automatic deployment to new accounts in the AWS Organization.