Skip to content

ServiceNow third-party & OAuth apps security checks

OAuth grants, marketplace apps, integrations, plugins and automations with standing access to company data — the SaaS-to-SaaS supply chain.

On ServiceNow, Black Cat runs 4 checks in this area on every scan. Each one below lists its severity, how to fix it, and the compliance controls it satisfies where a control applies. See what access the ServiceNow connector needs.

Checks (4)

severity: medium OAuth App Long Token Lifespan fix difficulty: easy #

Reduce the OAuth access token lifespan to 3600 seconds (1 hour) or less

  1. Navigate to System OAuth > Application Registry
  2. Open the flagged OAuth application record
  3. Locate the "Access Token Lifespan" field
  4. Change the value to 3600 or less
  5. Save the record
  6. Notify consuming applications that tokens will expire sooner and must be refreshed

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.d DORA (SaaS Security) DORA-9.12

severity: high OAuth App Insecure Redirect fix difficulty: easy #

Update OAuth application redirect URLs to use HTTPS and avoid wildcard patterns

  1. Navigate to System OAuth > Application Registry
  2. Open the flagged OAuth application record
  3. Locate the "Redirect URL" field
  4. Change the redirect URL to use HTTPS instead of HTTP
  5. Remove any wildcard characters from the redirect URL
  6. Use the most specific URL path possible
  7. Save the record and test the OAuth flow

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.d DORA (SaaS Security) DORA-9.12

severity: medium Insecure Plugin Active fix difficulty: medium #

Deactivate plugins with known security risks that are not required for business operations

  1. Navigate to System Definition > Plugins
  2. Search for the flagged plugin by ID or name
  3. Confirm with the application owner whether the plugin is actively used
  4. If not required, click "Deactivate" to disable the plugin
  5. Test that core functionality is unaffected after deactivation
  6. Document the deactivation decision

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.d DORA (SaaS Security) DORA-9.12

severity: high Integration Using Basic Auth fix difficulty: hard #

Migrate integrations from basic authentication to OAuth or certificate-based authentication

  1. Navigate to System Web Services > REST Message or the relevant integration registry
  2. Open the flagged integration record
  3. Change the authentication type from "Basic" to "OAuth 2.0" or "Mutual Authentication"
  4. Configure the appropriate OAuth client credentials or certificates
  5. Test the integration to confirm it connects successfully with the new authentication method
  6. Remove any stored basic auth credentials from the record

Vendor docs ↗

Satisfies: NIS2 Directive NIS2-21.d DORA (SaaS Security) DORA-9.12

More ServiceNow checks

The information on this page is provided for general informational purposes and is believed to be accurate as of its most recent update. Product names, logos, and trademarks are the property of their respective owners and are used for identification purposes only; their use does not imply any affiliation with or endorsement by those owners. Descriptions of third-party applications and of compliance frameworks are based on publicly available documentation and may change over time.

See these checks run on your stack

Start a free 14-day trial — no credit card required.

Start Free Trial