---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Disable GlideRecord Scope Fencing Legacy Behavior \[New in Security Center 1.3 and updated in 1.5 and 2.0\]

# Disable GlideRecord Scope Fencing Legacy Behavior \[New in Security Center 1.3 and updated
in 1.5 and 2.0\] {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

The glide.record.legacy_cross_scope_access_policy_in_script property disables scope fencing allowing scoped apps to access global script interfaces. It was created as a patch to GlideRecord's cross scope
access.
GlideRecord provided cross scope create/update access to tables that were not configured
with that level of access. In order to prevent customers from having applications broken
when this scoped access behavior was patched, the property
glide.record.legacy_cross_scope_access_policy_in_script was created.
When true, cross scope access falls back onto legacy behavior (insecure). This property
disables scope fencing, allowing scoped apps to access global script interfaces.

It is best security practice to have scope fencing restrictions in place. Scoping ensures
applications can only access resources with explicit access or within their scope, following
the principle of least privilege. Disabiling this feature could lead to confidentiality,
availability, and integrity impacts.

Set the Glide Property
glide.record.legacy_cross_scope_access_policy_in_script to false.
When not present in the sys_properties table, the default value is true.

## More information {#sc-enable-gliderecord-scope-fencing-legacy-behavior__section_qhx_1b1_xwb}

{#sc-enable-gliderecord-scope-fencing-legacy-behavior__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | glide.record.legacy_cross_scope_access_policy_in_script |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | false |
| Default value | true (when the property does not exist in the sys_properties table.) |
| Category | [Architecture, design, and threat modeling](https://servicenow-prod.fluidtopics.net/GP7csKl7x_IoFFA7nE_oew "This broad control addresses high level design considerations and key elements to implement a secure application. This covers the tenants of availability, confidentiality processing integrity, non-repudiation and privacy. Additionally, elements of a secure software development lifecycle are included.") |
| Security risk | * Severity score: 5 * CVSS score: Medium * Security risk details: Scoping ensures applications can only access resources with explicit access or within their scope following the principle of least privilege. Disabling this feature could lead to confidentiality, availability, and integrity impacts. {#sc-enable-gliderecord-scope-fencing-legacy-behavior__ul_g1g_3sf_xwb} |
| Dependencies and prerequisites | None |
[ ]

{#sc-enable-gliderecord-scope-fencing-legacy-behavior__table_ajc_b43_3kb}