ServiceNow

ServiceNow lets administrators restrict access by source IP, through IP Address Access Control across the instance and through REST API Access Policies scoped to specific APIs. Both apply to non-interactive REST integration accounts, not just human logins. An integration on Heroku, AWS Lambda, or another cloud platform egresses from a rotating address, which the allowlist rejects even when the credentials are valid.

QuotaGuard gives that integration a fixed network identity from a single environment variable.

- One-Variable Setup: Set your QuotaGuard connection URL as an environment variable on your integration's host, then route the ServiceNow REST API calls through it. Add your two IPs to ServiceNow once.

- Two Static IPs That Are Yours: A load-balanced pair assigned to your account. Add both to ServiceNow's allowed set so your integration stays connected through maintenance and redeploys.

- Works With the Table API, OAuth, and Basic Auth: The proxy carries both the token request and the API calls, so every request to ServiceNow exits from your two static IPs with no change to the auth flow.

- Both Directions: Outbound for your calls to ServiceNow, and a static inbound IP for ServiceNow outbound REST messages or Flow actions that call your application.

- Any Integration Host: Heroku, AWS Lambda, containers, serverless, or your own server. The proxy is read by your HTTP client, so nothing host-specific is required.

- Shield for Regulated Data: If your ServiceNow data includes regulated records, QuotaGuard Shield uses SSL passthrough so QuotaGuard never decrypts the traffic.

Scope note: this is for ServiceNow REST API integration access. MID Server connectivity uses a different model.

Setting it up? See the step-by-step ServiceNow static IP guide.