--- title: Block Expired Anti-CSRF Tokens description: Block expired CSRF tokens to prevent cross-site request forgery attacks. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/instance-security-hardening-settings/sc-block-expired-csrf-tokens.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: [Access control, Hardening settings, Platform Security] --- # Block Expired Anti-CSRF Tokens Block expired CSRF tokens to prevent cross-site request forgery attacks. The **glide.security.csrf\_previous.allow** system property enables use of an expired secure token to identify and validate incoming requests. This token is used to prevent cross-site request forgery attacks. Ensure that the property **glide.security.csrf\_previous.allow** is set to **false**. ## More information
| Attribute | Description |
|---|---|
| Configuration name | **glide.security.csrf\_previous.allow** |
| Configuration type | System Properties \(/sys\_properties\_list.do\) |
| Data type | Boolean |
| Recommended value | false |
| Default value | false |
| Fallback value | true |
| Category | [Access control](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-access-control.md) |
| Security risk | - Severity score: 6.5 - CVSS rating: Medium - Security risk details: Allowing the use of previous or expired CSRF tokens exposes the application to replay attacks, enabling attackers to reuse valid requests and potentially perform unauthorized actions on behalf of legitimate users. |
| Functional impact | None |
| Dependencies and prerequisites | None |