# Enhanced security for encrypted tenant options

**URL:** <https://community.cumulocity.com/t/enhanced-security-for-encrypted-tenant-options/12233>\
**Category:** Security updates\
**Tags:** security-alert\
**Created:** [May 21, 2025, 1:42pm UTC](https://community.cumulocity.com/t/enhanced-security-for-encrypted-tenant-options/12233 "2025-05-21T13:42:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![c8y\_security](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/c8y_security/32/31990_2.png) [@c8y\_security](https://community.cumulocity.com/u/c8y_security)\
**Post date:** [May 21, 2025, 1:42pm UTC](https://community.cumulocity.com/t/enhanced-security-for-encrypted-tenant-options/12233/1 "2025-05-21T13:42:42Z")

</div>

**Security Alert**

**Title:** Enhanced security for encrypted tenant options  
**Severity:** High  
**Summary:**  
We have introduced a new security feature in the platform to address a potential vulnerability in the handling of encrypted [tenant options](https://cumulocity.com/api/core/#tag/Options) prefixed with `credentials.`. Without this feature, system users with certain roles can decrypt any encrypted tenant option within the tenant, regardless of whether it logically belongs to them or not. This meant that ownership of sensitive configuration was not enforced, potentially exposing credentials across unrelated microservices.

To mitigate this, decryption of `credentials.*` options is now restricted to system users who own the tenant option. You are affected by this change if your microservice tries to read a “credentials.” option that it does not own. Ownership is determined based on the category of the option in the following order:  
-The [settingsCategory](https://cumulocity.com/docs/microservice-sdk/java/#microservice-settings) defined in the microservice manifest.  
-The microservice’s context path.  
-The microservice name.

**Recommended Action** :  
This feature is currently disabled by default, but can be enabled in a tenant via the secure-tenant-options feature toggle through the [API](https://cumulocity.com/api/core/#operation/setCurrentTenantFeatureToggleValue)

> curl --location --request PUT ‘{url}/features/secure-tenant-options/by-tenant’   
> –header ‘Content-Type: application/json’   
> –data '{  
> “active”: true  
> }

⚠ **Important** :  
[This restriction](https://cumulocity.com/docs/change-logs/?change-type=.change-type-api-change#cumulocity-2025-116-0-enhanced-security-for-encrypted-tenant-options) will become mandatory in Q4 2025 for SaaS environments and in 2026 for yearly releases. We strongly recommend that developers review and update their microservices accordingly, especially if their services rely on decrypting **credentials.** \* options in categories not explicitly owned by them.

**Affected Versions** : all versions  
**Fixed in** : Cumulocity core CD release 2025.116.0 and the next annual release in 2026.

**Contact** :  
If you have any questions or need assistance, please contact support.
