* A. Import the root certificate for your internal certificate authority into Netskope:
* This step ensures that Netskope recognizes and trusts SSL certificates issued by your company's internal certificate authority. By importing the root certificate, you enable proper SSL inspection and validation for internal sites.
* B. Bypass SSL inspection for the affected site(s):
* Since the intranet site uses your company's internal certificate authority, bypassing SSL inspection for this specific site allows users to access it without encountering SSL errors.
* D. Change the SSL Error Settings from Block to Bypass in the Netskope tenant:
* Adjusting the SSL Error Settings to "Bypass" allows users to proceed past SSL errors, including self-signed certificate errors. This ensures uninterrupted access to the intranet site. References:
* Netskope Security Cloud Introductory Online Technical Training
* Netskope Security Cloud Operation & Administration (NSCO&A) - Classroom Training
* Netskope Cloud Security Certification Program

When deploying Netskope and steering all traffic, if you find that the Real-time Protection policies for Microsoft OneDrive are not being enforced, the likely issue is with the default steering exceptions. To resolve this, you should remove the default steering exception for domains . This is because the default exceptions may include domains related to Microsoft services, which could prevent the Real-time Protection policies from being applied to traffic directed towards OneDrive. By removing these exceptions, you ensure that all traffic, including that to OneDrive, is subject to the policies you have set up.

In Netskope's Advanced Analytics, merged reports combine data from two separate data sets using a join operation. However, visualizations within the platform are subject to a system-imposed rendering limit of
5,000 rows. When Report A contains 3,000 rows and Report B contains 6,000 rows, the merged output would theoretically contain up to 9,000 rows; however, only 5,000 rows will be displayed in the visualization. This is not a deduplication behavior or a viewing restriction but a hard system limit on how many rows a visualization tile can render at one time. Understanding this limit is critical when designing Advanced Analytics reports intended to surface large DLP incident data sets, as significant data may be silently truncated without a clearly visible warning to the administrator.

Netskope supports integration with third-party Data Loss Prevention engines that communicate using the Internet Content Adaptation Protocol (ICAP). The Netskope Adapter is the platform component that enables this integration by acting as an ICAP server, receiving content from Netskope's inline proxy and forwarding it to the external DLP engine for inspection. The Adapter then receives the DLP response and relays the enforcement decision back to the Netskope platform. This is distinct from Cloud Exchange, which handles log and threat intelligence sharing workflows, and the Secure Forwarder, which is used to steer traffic from on- premises environments without a client. The On-Premises Log Parser (OPLP) is used for ingesting log data from on-premises firewalls or proxies into Netskope telemetry.

The reason for using Netskope Cloud Risk Exchange in this scenario is toautomate service tickets from alerts of interest. Netskope Cloud Risk Exchange (CRE) is designed to ingest user, device, and application risk scores, creating a dashboard view of contributors to your company's overall risk score and trend. One of the key functionalities of CRE is to trigger risk-reducing actions through business rules that are tuned to a weighted score.Automating service tickets from alerts of interest is a part of this functionality, as it allows for the automatic creation of tickets in response to specific alerts, streamlining the process of addressing potential security issues12.
The use cases for Netskope Cloud Risk Exchange, including the automation of service tickets, can be found in the official Netskope resources1.Further information on how to integrate and utilize Netskope Cloud Risk Exchange for automating service tickets can be found in the Netskope Knowledge Portal3.