In the scenario where CASB traffic steering is enabled using the Netskope Client without a Real-time Protection policy being activated, the default behavior of the traffic is to allow and log it (B). This means that the traffic will not be blocked; instead, it will be permitted to pass through and will be recorded for monitoring and analysis purposes. This default setting ensures visibility into the traffic and user activities without immediately enforcing a block, allowing for a period of observation and policy tuning before potentially more restrictive actions are taken1.

To allow traffic from a website with a self-signed certificate that is being blocked by Netskope with an SSL error, the correct action is to configure a Do Not Decrypt SSL Decryption rule. This rule will allow the traffic to pass without being decrypted, thus bypassing the SSL error caused by the self-signed certificate. This is a common practice for handling traffic from trusted internal applications or specific external sites that use self-signed certificates1.

When verifying that Google Drive traffic is being tunneled to Netskope using Chrome and the Netskope Client, you would expect to see log entries indicating that the traffic is being directed through Netskope's proxy. Specifically, Option A is correct as it shows the process "google drive" being tunneled to nsProxy. The log entry for Option A indicates that a TLS tunneling flow from a local address and process (Google Drive) is being directed to a host (play.googleapis.com) and then to Netskope's proxy (nsProxy). This is consistent with how Netskope tunnels specified traffic for security and policy enforcement1.

When IPsec tunnels are used to steer HTTPS traffic from end-user devices to Netskope, the Netskope platform performs SSL inspection as part of its inline proxy function. This requires that the Netskope root and intermediate SSL certificates be trusted by the endpoint devices connecting through the tunnel. When these certificates are not installed in the device's trusted certificate store, the SSL inspection process causes certificate errors, rendering the inspected applications non-functional. Installing the Netskope certificate chain on the affected devices resolves this issue by allowing the device to trust the Netskope-generated certificates presented during SSL decryption. This is a standard requirement for any transparent SSL proxy deployment and is explicitly documented in Netskope's certificate management guidance.

Admin Role and File Content Viewing: By default, an admin role does not prevent admins from downloading and viewing file content. Admins have access to view and download file content unless specific restrictions are applied.
Role Privileges Default to Read Only: All role privileges in Netskope default to Read Only for all functional areas. This means that admins can view information but cannot make changes unless explicitly granted additional permissions.
Obfuscation: Obfuscation can be applied to specific functional areas, but it is not a default behavior for all areas. Reference:
Netskope Security Cloud Introductory Online Technical Training
Netskope Security Cloud Operation & Administration (NSCO&A) - Classroom Training