# Ensure buckets have object versioning enabled

- Source: https://support.icompaas.com/support/solutions/articles/a_1786022842143824-ensure-buckets-have-object-versioning-enabled
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Utho Cloud](https://support.icompaas.com/support/solutions/c_1786022244474917) › [Utho Checks](https://support.icompaas.com/support/solutions/folders/utho-checks)
- Last updated: 2026-08-12
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

This check verifies that Utho Cloud Object Storage buckets have object versioning enabled. Object versioning maintains previous versions of objects when they are modified or deleted, helping organizations recover from accidental deletion, overwrites, or unintended changes.

  

Rationale:

Without object versioning, an overwritten or deleted object may not be recoverable.

This check helps:

-   Recover accidentally deleted objects.
    
-   Restore previous versions of modified objects.
    
-   Protect against unintended data changes.
    
-   Improve data recovery and operational resilience.
    

  

Impact:

-   Provides an additional layer of protection against accidental data loss.
    
-   Allows previous versions of objects to be recovered.
    
-   Increases storage consumption because multiple object versions may be retained.
    
-   May increase storage costs if old versions are not managed using lifecycle policies.
    

  

Default Value:

Object versioning should be enabled on Utho Cloud Object Storage buckets where data recovery and protection against accidental deletion or modification is required.

A bucket is considered non-compliant if object versioning is disabled.

  

Pre-requisites:

-   Utho Cloud account.
    
-   Permissions to view Object Storage buckets and their configuration.
    
-   Access to the Utho Cloud Console or Utho API.
    
-   Object Storage buckets configured in the account.
    

  

Test Plan:

1.  Sign in to the Utho Cloud Console.
    
2.  Navigate to Object Storage.
    
3.  Select each bucket.
    
4.  Open the bucket's settings or configuration.
    
5.  Check the Object Versioning setting.
    
6.  Verify that versioning is enabled.
    

  

Using the Utho API:

curl -s -H "Authorization: Bearer $UTHO\_API\_TOKEN" \\  
https://api.utho.com/v2/object-storage/buckets

  

Retrieve the configuration of an individual bucket:

curl -X GET "https://api.utho.com/v2/objectstorage/innoida/bucket/bucket-qerb764d" \\  
  -H "Authorization: Bearer $UTHO\_API\_TOKEN" \\  -H "Content-Type: application/json" | jq

  

Fail if the bucket's versioning configuration is disabled. Pass if object versioning is enabled.

  

Implementation Plan:

Note: We can enable versioning by using the UTHO console; we can implement it by using the UTHO API

  

Using the Utho API:

If supported by the Utho API, enable versioning for the bucket:

curl -X POST "https://api.utho.com/v2/objectstorage/innoida/bucket/bucket-qerb764d/version" \\  
  -H "Authorization: Bearer $UTHO\_API\_TOKEN" \\  -H "Content-Type: application/json" | jq

  

curl -X GET "https://api.utho.com/v2/objectstorage/innoida/bucket/bucket-qerb764d" \\  
  -H "Authorization: Bearer $UTHO\_API\_TOKEN" \\  -H "Content-Type: application/json" | jq

  

Confirm the exact Utho API endpoint and versioning field supported by the target Utho API before implementing this command.

  

Backout Plan:

Note: We can disable versioning by using the UTHO console; we can implement it by using the UTHO API

  

curl -X DELETE "https://api.utho.com/v2/objectstorage/innoida/bucket/bucket-qerb764d/version" \\  
  -H "Authorization: Bearer $UTHO\_API\_TOKEN" \\  -H "Content-Type: application/json" | jq

  

References:

-   [Utho Cloud REST API – Object Storage Versioning](https://utho.com/rest-api/?utm_source=chatgpt.com)
    
-   [Utho Cloud Documentation – Object Storage](https://utho.com/docs/products?utm_source=chatgpt.com)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.