Bucket names are unique across all tenants of the provider (on Azure this applies to the storage account name rather than the container), so when a bucket is deleted its name may be registered by any other tenant. Configuration, code, replication rules, or links that still reference the name then resolve to a bucket under another tenant's control, and data is written to or read from it. This results in a loss of confidentiality, integrity, and availability of the data routed through the reclaimed name.
Deleted Bucket Names are Reclaimed by Other Tenants
CCC.ObjStor.TH10
Related Capabilities
| ID | Title | Description |
|---|---|---|
| CCC.ObjStor.CP01 | Storage Buckets | The service always provides buckets as uniquely identifiable containers in which objects are stored and to which access policies and configuration are applied. |
| CCC.ObjStor.CP07 | Delete Stored Objects | The service always allows a user to delete an object from a bucket given the object key. |
| CCC.Core.CP08 | Data Replication | The service automatically replicates data across multiple deployments simultaneously with parity, or may be configured to do so. |
Related Controls
| ID | Title | Description |
|---|---|---|
| CCC.ObjStor.CN14 | Restrict Bucket Access to Organization-Owned Accounts | Ensure that requests from within the trust perimeter only reach buckets owned by accounts the organization controls, so that a reclaimed or look-alike bucket name cannot receive or serve the organization's data. |