AWS prescriptive-guidance documentation change
Summary
Changed 'multi-tenant authorization' to 'multi-tenant isolation' in business outcomes/section header, removed document history date, and shortened author affiliation
Security assessment
Terminology change from 'authorization' to 'isolation' emphasizes tenant separation but doesn't address specific security vulnerabilities. Editorial changes to authorship and dates have no security impact.
Diff
diff --git a/prescriptive-guidance/latest/saas-multitenant-api-access-authorization/introduction.md b/prescriptive-guidance/latest/saas-multitenant-api-access-authorization/introduction.md index 43e7f106f..f40da79fc 100644 --- a//prescriptive-guidance/latest/saas-multitenant-api-access-authorization/introduction.md +++ b//prescriptive-guidance/latest/saas-multitenant-api-access-authorization/introduction.md @@ -7 +7 @@ -Targeted business outcomesTenant isolation and multi-tenant authorization +Targeted business outcomesTenant isolation and multi-tenant isolation @@ -11,3 +11 @@ Targeted business outcomesTenant isolation and multi-tenant authorization - _Tabby Ward, Thomas Davis, Gideon Landeman, and Tomas Riha, Amazon Web Services (AWS)_ - -_May 2024_ ([document history](./doc-history.html)) + _Tabby Ward, Thomas Davis, Gideon Landeman, and Tomas Riha, Amazon Web Services_ @@ -57 +55 @@ This prescriptive guidance describes repeatable design patterns for authorizatio -## Tenant isolation and multi-tenant authorization +## Tenant isolation and multi-tenant isolation