Storage / Object / Controls / v2026.11
Bound the Period of Irrevocable Retention Locks
CCC.ObjStor.CN13 · Data Resilience
Ensure that an irrevocable retention lock cannot commit the organization to retaining data for longer than its retention policy permits. No provider bounds the period natively, so a policy-as-code check on lock requests satisfies this requirement.
Related Capabilities
| ID | Title | Description |
|---|
| CCC.ObjStor.CP07 | Delete Stored Objects | The service always allows a user to delete an object from a bucket given the object key. |
| CCC.ObjStor.CP17 | Object Immutability | The service may be configured to lock an object or a bucket so that its objects cannot be overwritten or deleted until a retention period expires, and the lock itself may be made irrevocable. |
| CCC.Core.CP34 | Data Lifecycle Policy | The service may be configured to automatically delete, archive, or transition data or child resources once a user-defined age or condition is reached. |
Related Threats
| ID | Title | Description |
|---|
| CCC.ObjStor.TH09 | Irrevocable Retention Prevents Required Deletion | An irrevocable immutability lock may be applied with an excessive retention period, or to a bucket holding data that is subject to deletion obligations. Neither users nor lifecycle rules can remove the objects until the period expires, and storage cost accrues for the full period. This results in retention of data that should no longer exist, impacting confidentiality and regulatory compliance. |
Assessment Requirements
| ID | Text | Applicability |
|---|
| CCC.ObjStor.CN13.AR01 | When an irrevocable retention lock is applied to a bucket or an object, the service MUST reject a retention period that exceeds an organization-defined maximum. | tlp-clear, tlp-green, tlp-amber, tlp-red |
Guideline Mappings
| Framework | ID | Remarks |
|---|
| CCM | DSP-16 | Data Retention and Deletion |