AWS connect documentation change
Summary
Updated product name from 'Amazon Connect' to 'Connect Customer' throughout PCI compliance best practices document. Maintained security recommendations including MFA enforcement and KMS key usage.
Security assessment
Changes are branding updates rather than security fixes. Existing security recommendations (MFA, KMS usage) remain valid but were not modified except for product name references. No evidence of addressing specific vulnerabilities.
Diff
diff --git a/connect/latest/adminguide/compliance-validation-best-practices-PCI.md b/connect/latest/adminguide/compliance-validation-best-practices-PCI.md index ec041baaa..bc54eb615 100644 --- a//connect/latest/adminguide/compliance-validation-best-practices-PCI.md +++ b//connect/latest/adminguide/compliance-validation-best-practices-PCI.md @@ -7 +7 @@ -# Best practices for PCI compliance in Amazon Connect +# Best practices for PCI compliance in Connect Customer @@ -9 +9 @@ -Following this list of best practices can help you ensure your Amazon Connect contact center is PCI-compliant. +Following this list of best practices can help you ensure your Connect Customer contact center is PCI-compliant. @@ -19 +19 @@ Following this list of best practices can help you ensure your Amazon Connect co - * Enable multi-factor authentication (MFA) for any access to PCI as Amazon Connect is a public endpoint. + * Enable multi-factor authentication (MFA) for any access to PCI as Connect Customer is a public endpoint. @@ -25 +25 @@ Following this list of best practices can help you ensure your Amazon Connect co - * Use your own KMS key when ingesting data in Amazon Connect Customer Profile domains. + * Use your own KMS key when ingesting data in Connect Customer Customer Profile domains.