AWS mwaa documentation change
Summary
Clarification of permission language in confused deputy explanation
Security assessment
Change from 'should not' to 'does not' improves accuracy of security concept description but doesn't introduce new security features or address specific vulnerabilities
Diff
diff --git a/mwaa/latest/userguide/cross-service-confused-deputy-prevention.md b/mwaa/latest/userguide/cross-service-confused-deputy-prevention.md index 0481e7571..8636da903 100644 --- a//mwaa/latest/userguide/cross-service-confused-deputy-prevention.md +++ b//mwaa/latest/userguide/cross-service-confused-deputy-prevention.md @@ -7 +7 @@ -The confused deputy problem is a security issue where an entity that doesn't have permission to perform an action can coerce a more-privileged entity to perform the action. In AWS, cross-service impersonation can result in the confused deputy problem. Cross-service impersonation can occur when one service (the _calling service_) calls another service (the _called service_). The calling service can be manipulated to use its permissions to act on another customer's resources in a way it should not otherwise have permission to access. To prevent this, AWS provides tools that help you protect your data for all services with service principals that have been given access to resources in your account. +The confused deputy problem is a security issue where an entity that doesn't have permission to perform an action can coerce a more-privileged entity to perform the action. In AWS, cross-service impersonation can result in the confused deputy problem. Cross-service impersonation can occur when one service (the _calling service_) calls another service (the _called service_). The calling service can be manipulated to use its permissions to act on another customer's resources in a way it does not otherwise have permission to access. To prevent this, AWS provides tools that help you protect your data for all services with service principals that have been given access to resources in your account.