--- title: Enable UserCookie version 3.1 description: Manage the version of UserCookie that is enabled on your instance to secure the storage of the secret key in the source code. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/instance-security-hardening-settings/sc-enable-usercookie-version-3-1.html release: australia product: Instance Security Hardening Settings classification: instance-security-hardening-settings topic_type: reference last_updated: "2026-03-13" reading_time_minutes: 1 breadcrumb: [Session management, Hardening settings, Platform Security] --- # Enable UserCookie version 3.1 Manage the version of UserCookie that is enabled on your instance to secure the storage of the secret key in the source code. UserCookie v3 is generated only when property **glide.ui.secure.cookies.use\_kmf is disabled** is disabled. UserCookie v3 is not secure due to storing secret key for HMAC in source code and identical for all customers. By setting the property **glide.ui.secure.cookies.use\_kmf** to **true**, UserCookie v3.1 is used and secret key is stored in security storage such as KMF. ## More information
| Attribute | Description |
|---|---|
| Configuration name | **glide.ui.secure.cookies.use\_kmf** |
| Configuration type | System Properties \(/sys\_properties\_list.do\) |
| Data type | Boolean |
| Recommended value | true |
| Default value | false |
| Category | [Session management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-session-management.md) |
| Security risk | - Severity score: 7.1 - CVSS score: High - Security risk details: This creates a significant risk of session hijacking, as attackers who obtain or reverse-engineer the key can forge authentication cookies and impersonate users. |
| Dependencies and prerequisites | None |