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


---

# Ensure An Instance is Allowed to Connect to Only Trusted IP Addresses

# Ensure An Instance is Allowed to Connect to Only Trusted IP Addresses {#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 define a list of IP ranges that are appended to the outbound IP allow list.
Use the glide.custom.ip.outbound.authenticate.allow system property to define a list of IP ranges that are appended to the outbound IP allow list of an instance. The property value contains a comma separated
range of IP addresses in IPv4 or IPv6 format. IP ranges are specified using a hyphen (10.0.10.14-10.0.10.19), using CIDR notation (10.0.10.0/24), or consist of a single IP address (10.0.10.5). The instance is allowed to connect to
the IP ranges in this property, unless listed in the IP deny list.  
Hinweis:  
IP ranges in this property are appended to the outbound IP allow list regardless of the value of the glide.ip.authenticate.strict property. The IP Address Access Controls \[ip_access\] table provides an equivalent option to add to both the inbound/outbound allow/deny IP lists of an instance. Refer to the Steps to Configure section in [IP range based authentication](https://servicenow-prod.fluidtopics.net/mDSjjKd5yY5V5zYyoIE_3A "One way to secure a web-based application is to restrict access based on the IP address.").

Ensure that the glide.custom.ip.outbound.authenticate.allow system property value is either an empty, or a comma-separated list containing only trusted IP ranges that your want to allow your instance to
access.

## More information {#sc-ensure-an-instance-is-allowed-to-connect-to-only-trusted-ip-addresses__section_wc1_cqn_phc}

{#sc-ensure-an-instance-is-allowed-to-connect-to-only-trusted-ip-addresses__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | glide.custom.ip.outbound.authenticate.allow |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | String |
| Recommended value | Empty, or a comma-separated list containing only trusted IP ranges that your want to allow your instance to access. |
| Default value | None |
| Fallback value | None |
| 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: 4.3 * CVSS score: Medium * Security risk details: If IP ranges are added to the property, it increases the risk of that an instance may connect to unauthorized or non-essential external services that should otherwise be blocked. This can weaken network-level security. In cases where additional IP ranges are necessary, be careful to include a minimal set of only trusted IPs. {#sc-ensure-an-instance-is-allowed-to-connect-to-only-trusted-ip-addresses__ul_g1g_3sf_xwb} |
| Functional impact | There should be no functional impact. It can only be used to increase your instance's access. |
| Dependencies and prerequisites | None |
[ ]

{#sc-ensure-an-instance-is-allowed-to-connect-to-only-trusted-ip-addresses__table_ajc_b43_3kb}