--- title: Enforce application specific ACLs only for application data description: Avoid unauthorized or undesired access to application data by enforcing application-specific access control lists \(ACLs\) only for application data. locale: en-US canonical_url: https://www.servicenow.com/docs/r/platform-security/instance-security-hardening-settings/sc-enforce-application-specific-acls-only-for-application-data.html release: brazil product: Instance Security Hardening Settings classification: instance-security-hardening-settings topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 2 breadcrumb: [Access control, Hardening settings, Platform Security] --- # Enforce application specific ACLs only for application data Avoid unauthorized or undesired access to application data by enforcing application-specific access control lists \(ACLs\) only for application data. Enforce application-specific ACLs for application data residing in primary tables outside the application. When these properties have a value of **true**, only the application-specific ACLs are evaluated for access to the application data residing in these tables. Not all applications are designed to work in this configuration or use a System Property \[sys\_properties\] record for this purpose. These system properties use the **glide.enforce\_security\_scope.<scope>** naming format. For example, use the **glide.enforce\_security\_scope.sn\_hr\_sp** property for the Employee Center Core \(sn\_hr\_sp\) scope. The following application scopes contain this property:
| - sn\_doc - sn\_egd\_act - sn\_egd\_core - sn\_egd\_goals - sn\_em - sn\_gsm - sn\_gsm\_info\_req - sn\_gsm\_lic\_prmt - sn\_gsm\_lic\_prmt\_ex - sn\_gsm\_soc\_bnfts | - sn\_hc\_professional - sn\_hr\_agent\_ws - sn\_hr\_ai\_agents - sn\_hr\_awa - sn\_hr\_core - sn\_hr\_ef - sn\_hr\_er - sn\_hr\_gen\_ai - sn\_hr\_hc - sn\_hr\_le - sn\_hr\_ra | - sn\_hr\_le\_ent - sn\_hr\_mii\_base - sn\_hr\_na\_galileo - sn\_hr\_pad - sn\_hr\_pj - sn\_hr\_sp - sn\_hr\_va - sn\_hr\_ws - sn\_imt\_health\_test - sn\_imt\_tracing - sn\_imt\_vaccine | - sn\_ja - sn\_jny - sn\_lg\_contracts - sn\_lg\_matter - sn\_lg\_ops - sn\_opp\_market - sn\_professional - sn\_svc\_appl\_info - sn\_svc\_appl\_pgm\_mg - sn\_talent\_aia - sn\_uni\_req - sn\_uni\_task - sn\_egd\_lh - sn\_ecn - sn\_ni\_core - sn\_hr\_voice\_aia - sn\_tf - sn\_lco\_cmn |
| Attribute | Description |
|---|---|
| Configuration name | **glide.enforce\_security\_scope.<scope>** |
| Configuration type | System Properties \(/sys\_properties\_list.do\) |
| Data type | Boolean |
| Recommended value | true |
| Default value | true |
| Category | [Access control](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-access-control.md) |
| Functional impact | Users who aren't actively using the application may not have access to application data residing in scope main tables. Not all applications are designed to work in this configuration or include a **sys\_properties** record for this feature. |
| Security risk | - Severity score: 4.1 - CVSS score: Medium - Security risk details: When these properties don’t have a value of **true**, the ACLs on the primary table are still evaluated for access, potentially allowing unauthorized or undesired access to application data. |
| Dependencies and prerequisites | None |