---
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


---

# Enforce Scope Access Controls on New Tables

# Enforce Scope Access Controls on New Tables {#ariaid-title1}

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

Use a system property to enforce cross-scope access checks for newly created tables.
The table dictionary attribute `enforce_dot_walk_cross_scope_access=true` enforces dot-walk cross-scope access enforcement for the applicable table. This enforcement applies to dot-walking across scope boundaries
using a reference field to the applicable table. When the glide.script.dot_walk.add_attribute_on_table_create system property is not set to <kbd class="ph userinput">false</kbd>, the attribute is added to the dictionary
element of all new tables. This attribute is only added for new tables created after zBoot.

Ensure that the glide.script.dot_walk.add_attribute_on_table_create system property set to <kbd class="ph userinput">true</kbd> in the System Properties \[sys_properties\] table.

## More information {#sc-enforce-scope-access-controls-on-new-tables__section_anl_kck_xhc}

{#sc-enforce-scope-access-controls-on-new-tables__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | glide.script.dot_walk.add_attribute_on_table_create |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | true |
| Default value | true |
| Fallback value | null |
| Category | [Access control](https://servicenow-prod.fluidtopics.net/xAmazkRh5FKyeb7q4TQGWw "The access control category audits the process of protecting resources from unauthorized access through granting and denying requests based on a permission model. This includes ensuring an entity accessing a resource holds valid credentials to do so, creating and protecting a well-defined set of roles or permissions and ensuring role or permission controls are protected from replay and tampering.") |
| Security risk | * Severity score: 5.3 * CVSS score: Medium * Security risk details: An application can access data in tables outside of it's application scope, leading to information disclosure. {#sc-enforce-scope-access-controls-on-new-tables__ul_g1g_3sf_xwb} |
| Functional impact | Cross-scope access checks are enforced by default for newly created tables. This prevents applications from accessing data outside their scope through a bypass. The behavior could be turned off on a table-by-table basis. |
| Dependencies and prerequisites |   |
[ ]

{#sc-enforce-scope-access-controls-on-new-tables__table_ajc_b43_3kb}