Netskope Global Technical Success (GTS)

LinkedIn - Block 'Jobs' Page

Netskope Cloud Version - 127

Objective

Block LinkedIn ‘Jobs’ page only

Prerequisite

Netskope SWG or Next-Gen SWG license

Context

How to block access to LinkedIn ‘Jobs’ page only via Realtime Protection Policy

Do You Know?

• Netskope acknowledges LinkedIn as a Cloud Application and provides a pre-defined cloud app connector.
• As of July 06, 2025 with Netskope’s LinkedIn predefined connector, customers can exercise control over the following activities:

• Netskope categorizes LinkedIn.com under the ‘Professional Networking' web category.
• When you navigate to the ‘Jobs’ section on LinkedIn, you are redirected to the following URL: https://www.linkedin.com/jobs/

Author Notes

I'm sure some readers are thinking, 'Just create a custom URL category—problem solved.' Unfortunately, it's not that simple.

Why?

• LinkedIn is a modern web application. The URL https://www.linkedin.com/jobs/ is the user-friendly address you interact with in the browser. It loads the react-based interface that dynamically fetches data to render the jobs page. Let me explain - 

LinkedIn uses Client-side rendering (CSR). CSR is a method used in web development where most of the page’s content is generated in the browser using JavaScript, rather than being pre-rendered on the server.

When the end-user clicks on ‘Jobs’, LinkedIn does not reload the entire page. Instead, the browser displays a spinner (loading indicator) while the already-loaded JavaScript fetches job data from the ‘voyager/api/graphql’ endpoint. Once the data is received, the JavaScript dynamically renders the job listings into the page.

‘a.’ API Query to ‘voyager/api/graphql’ endpoint.

‘b.’ xhr - XHR stands for XMLHttpRequest. It is a JavaScript API used to make HTTP requests from a web browser to a server, allowing dynamic updates to a webpage without requiring a full page reload.

API Query - queryId=voyagerJobsDashJobsFeed.9e0e1ef53da252046e52e1ea6f0b35dc

• Blocking https://www.linkedin.com/jobs/ alone won't solve the issue. You also need to identify and block the API request that's responsible for fetching the job details.

Configuration

• Create a Custom URL Category

Path: Netskope Tenant UI >>> Policies >>> Profiles - - - URL Lists >>> New URL Lists

.*linkedin.com.*job

linkedin\.com.*voyagerJobsDashJobsFeed

linkedin\.com.*voyagerSearchDashClusters

Path: Netskope Tenant UI >>> Policies >>> Profiles - - - Custom Categories >>> New Category

• Create a Realtime protection policy

Path: Netskope Tenant UI >>> Policies >>> Real-time Protection >>> New Policy

Verification

Access LinkedIn Jobs

Terms and Conditions

• All documented information undergoes testing and verification to ensure accuracy.
• In the future, it is possible that the application's functionality may be altered by the vendor. If any such changes are brought to our attention, we will promptly update the documentation to reflect them.

Notes

• This article is authored by Netskope Global Technical Success (GTS).
• For any further inquiries related to this article, please contact Netskope GTS by submitting a support case with 'Case Type – How To Questions'.