--- title: Enforce Scope Access Controls on New Tables description: Use a system property to enforce cross-scope access checks for newly created tables. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/instance-security-hardening-settings/sc-enforce-scope-access-controls-on-new-tables.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] --- # Enforce Scope Access Controls on New Tables 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 `false`, 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 `true` in the System Properties \[sys\_properties\] table. ## More information
| 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-access-control.md) |
| 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. |
| 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 |