AWS securityhub documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for terminology consistency
Security assessment
The change only modifies branding terminology (removing 'AWS' prefix from CloudFormation references). No security implications or vulnerability fixes are introduced.
Diff
diff --git a/securityhub/latest/partnerguide/product-readiness-checklist.md b/securityhub/latest/partnerguide/product-readiness-checklist.md index 7f97f45bd..ccc2f6d10 100644 --- a//securityhub/latest/partnerguide/product-readiness-checklist.md +++ b//securityhub/latest/partnerguide/product-readiness-checklist.md @@ -107 +107 @@ These questions are related to the setup and day-to-day function of the integrat -**Does the partner provide an infrastructure-as-code (IaC) template to deploy the integration with Security Hub, such as Terraform, AWS CloudFormation, or AWS Cloud Development Kit (AWS CDK)?** +**Does the partner provide an infrastructure-as-code (IaC) template to deploy the integration with Security Hub, such as Terraform, CloudFormation, or AWS Cloud Development Kit (AWS CDK)?** @@ -112 +112 @@ For integrations that will send findings from the customer account or use CloudW -AWS CloudFormation is preferred, but AWS CDK or Terraform can also be used. +CloudFormation is preferred, but AWS CDK or Terraform can also be used.