--- title: Enable Anti-CSRF Token for Userperf description: Use a system property to ensure CSRF \(Cross-Site Request Forgery\) protection is enforced when setting user preferences. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/instance-security-hardening-settings/sc-enable-anti-csrf-token-for-userperf.html release: australia product: Instance Security Hardening Settings classification: instance-security-hardening-settings topic_type: reference last_updated: "2026-03-12" reading_time_minutes: 1 breadcrumb: [Architecture, design, and threat modeling, Hardening settings, Platform Security] --- # Enable Anti-CSRF Token for Userperf Use a system property to ensure CSRF \(Cross-Site Request Forgery\) protection is enforced when setting user preferences. Use the **glide.security.userpref\_csrf\_check.enable** system property to enforce CSRF \(Cross-Site Request Forgery\) protection when setting user preferences to the User Preference Definitions \[sys\_user\_preference\_definition\] table via URI parameters. If the property isn't set to the recommended value of `true`, then the **CSRF token required** flag is overridden when set on individual preferences, and preferences can be set via URI parameters without requiring a CSRF token. Ensure the **glide.security.userpref\_csrf\_check.enable** system property is set to `true`. ## More information
Attribute Description
Configuration name **glide.security.userpref\_csrf\_check.enable**
Configuration type System Properties \(/sys\_properties\_list.do\)
Data type Boolean
Recommended value true
Default value true
Fallback value false
Category [Architecture, design, and threat modeling](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-architecture-design-threat-molding.md)
Security risk - Severity score: 4.3 - CVSS score: Medium - Security risk details: Failure to implement CSRF protection exposes the instance to unauthorized actions performed on behalf of authenticated users.
Functional Impact Users or integrations that previously set certain preferences via URL parameters without a CSRF token may now fail if those preferences require a token.
Dependencies and prerequisites None
References  
**Parent Topic:**[Architecture, design, and threat modeling](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-architecture-design-threat-molding.md)