AWS smc documentation change
Summary
Renamed all references from 'AWS Security Hub' to 'AWS Security Hub CSPM' throughout the documentation
Security assessment
The changes are purely terminological updates (adding 'CSPM' to product names). No security vulnerabilities, weaknesses, or incidents are mentioned or addressed. The core functionality remains identical.
Diff
diff --git a/smc/latest/ag/jsmcloud-config-security-hub.md b/smc/latest/ag/jsmcloud-config-security-hub.md index 0de38e82a..f910ecb2b 100644 --- a//smc/latest/ag/jsmcloud-config-security-hub.md +++ b//smc/latest/ag/jsmcloud-config-security-hub.md @@ -5 +5 @@ -# Integrating AWS Security Hub in Jira Service Management Cloud +# Integrating AWS Security Hub CSPM in Jira Service Management Cloud @@ -7 +7 @@ -AWS Security Hub enables users to view security Findings from AWS services such as Amazon Guard Duty and Amazon Inspector, as well as AWS Partner solutions. +AWS Security Hub CSPM enables users to view security Findings from AWS services such as Amazon Guard Duty and Amazon Inspector, as well as AWS Partner solutions. @@ -9 +9 @@ AWS Security Hub enables users to view security Findings from AWS services such -If you use both [AWS Security Hub](https://aws.amazon.com/security-hub/?aws-security-hub-blogs.sort-by=item.additionalFields.createdDate&aws-security-hub-blogs.sort-order=desc) and [ Jira Service Management](https://www.atlassian.com/software/jira/service-management), the AWS Service Management Connector for Jira Service Management allows you to create an automated, bidirectional integration between Security Hub and Jira Service Management. This two-way integration synchronizes your Security Hub Findings and Jira Issues. +If you use both [AWS Security Hub CSPM](https://aws.amazon.com/security-hub/?aws-security-hub-blogs.sort-by=item.additionalFields.createdDate&aws-security-hub-blogs.sort-order=desc) and [ Jira Service Management](https://www.atlassian.com/software/jira/service-management), the AWS Service Management Connector for Jira Service Management allows you to create an automated, bidirectional integration between Security Hub and Jira Service Management. This two-way integration synchronizes your Security Hub CSPM Findings and Jira Issues. @@ -11 +11 @@ If you use both [AWS Security Hub](https://aws.amazon.com/security-hub/?aws-secu -Specifically, as a Jira administrator, you can use this integration to automatically create Jira Issues from AWS Security Hub Findings. When you update those tickets in Jira, the changes are automatically replicated back to the original Security Hub Findings. For example, when you resolve the issue in Jira, the workflow status of the Security Hub finding also changes to `RESOLVED`. This action ensures that Security Hub always has up-to-date information about your security posture. +Specifically, as a Jira administrator, you can use this integration to automatically create Jira Issues from AWS Security Hub CSPM Findings. When you update those tickets in Jira, the changes are automatically replicated back to the original Security Hub CSPM Findings. For example, when you resolve the issue in Jira, the workflow status of the Security Hub finding also changes to `RESOLVED`. This action ensures that Security Hub CSPM always has up-to-date information about your security posture. @@ -15 +15 @@ Specifically, as a Jira administrator, you can use this integration to automatic -If you are aggregating your Security Hub findings to a single management AWS account and have onboarded management to the connector, internal customers and Jira agents updates on the Finding issue will **not** be synched to the finding in Security Hub. +If you are aggregating your Security Hub CSPM findings to a single management AWS account and have onboarded management to the connector, internal customers and Jira agents updates on the Finding issue will **not** be synched to the finding in Security Hub CSPM. @@ -25 +25 @@ Validating AWS Service Catalog integration -Configuring AWS Security Hub integration +Configuring AWS Security Hub CSPM integration