--- title: Disable unauthenticated published reports description: Deactivate this property to prevent the user from publishing or accessing reports. This property disables the published reports feature in reporting. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/instance-security-hardening-settings/sc-disable-unauthenticated-published-reports.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: [Architecture, design, and threat modeling, Hardening settings, Platform Security] --- # Disable unauthenticated published reports Deactivate this property to prevent the user from publishing or accessing reports. This property disables the published reports feature in reporting. If the **glide.report.published\_reports.enabled** system property is not set to the recommended value of **false**, then reports stored on the instance can be made visible without authentication. Ensure that the **glide.report.published\_reports.enabled** system property exists in the System Properties \[sys\_properties\] table and is set to the value **false**. If the property does not appear in the sys\_properties table, add a new record. ## More information
| Attribute | Description |
|---|---|
| Configuration name | **glide.report.published\_reports.enabled** |
| Configuration type | System Properties \(/sys\_properties\_list.do\) |
| Data type | Boolean |
| Recommended value | false |
| Default value | <none> |
| Fallback value | true |
| Category | [Architecture, design, and threat modeling](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-architecture-design-threat-molding.md) |
| Security risk | - Severity score: 6.5 - CVSS rating: Medium - Security risk details: Allowing unauthenticated access to sensitive data can cause inadvertent information disclosure to a malicious actor. |
| Functional impact | The user cannot publish reports. |
| Dependencies and prerequisites | None |