NSK300 practice question 9 of 15

You have an NG-SWG customer that currently steers all Web traffic to Netskope using the Netskope Client. They have identified one new native…

Full set: 60 questions
You have an NG-SWG customer that currently steers all Web traffic to Netskope using the Netskope Client. They have identified one new native application on Windows devices that is a certificate- pinned application. Users are not able to access the application due to certificate pinning. The customer wants to configure the Netskope Client so that the traffic from the application is steered to Netskope and the application works as expected. Which two methods would satisfy the requirements? (Choose two.)
Answer options
A: Bypass traffic using the bypass action in the Real-time Protection policy.
B: Configure the SSL Do Not Decrypt policy to not decrypt traffic for domains used by the native application. Correct answer
C: Configure domain exceptions in the steering configuration for the domains used by the native application.
D: Tunnel traffic to Netskope and bypass traffic inspection at the Netskope proxy. Correct answer
Correct Answer:
B. Configure the SSL Do Not Decrypt policy to not decrypt traffic for domains used by the native application.; D. Tunnel traffic to Netskope and bypass traffic inspection at the Netskope proxy.
Explanation

The core issue with certificate-pinned applications is that they will reject connections if the server certificate is altered, which occurs during Netskope's SSL decryption process. The goal is to steer the application's traffic to Netskope for visibility and control without performing decryption.
1. SSL Do Not Decrypt Policy (B): This method steers the traffic to the Netskope Security Cloud, but a specific policy instructs the proxy not to perform SSL inspection for the application's domains. The original certificate is passed to the client, satisfying the application's pinning requirement while maintaining traffic visibility in Netskope.
2. Tunnel to Netskope and Bypass Inspection (D): This method involves configuring the steering profile to explicitly tunnel the application's traffic (e.g., by process name) to the Netskope Cloud Firewall (CFW). A corresponding CFW policy can then allow this traffic without subjecting it to deep SSL inspection, thus preventing the certificate pinning error.

Why Incorrect

A. A Real-time Protection policy "Bypass" action is evaluated after the TLS handshake. The certificate pinning error causes the handshake to fail, so the policy is never reached.
C. Configuring a domain exception in the steering configuration causes the Netskope Client to bypass the Netskope cloud entirely for that traffic, which violates the requirement to steer it.

References

1. Netskope Official Documentation, "Add an Exception for a Certificate Pinned Application": This document explicitly details the two primary methods for handling certificate-pinned applications.

For Option B: Under the section "Add a Policy-based Exception," it states, "You can create a policy-based exception to not decrypt traffic for certificate pinned applications... Go to Policies > SSL Decryption. Click New Policy... For Action, select Do Not Decrypt." This directly validates using an SSL Do Not Decrypt policy.

For Option D: The document describes steering non-standard traffic to the Cloud Firewall. It states, "For applications that use non-standard ports, you can add the process name of the application in the steering configuration to steer its traffic to Cloud Firewall." This traffic is then managed by CFW policies, which can allow it without inspection, aligning with the description in option D.

2. Netskope Official Documentation, "SSL Decryption": This document explains the function of the "Do Not Decrypt" action. It clarifies that this action allows the proxy to pass encrypted traffic through without inspection, which is the required behavior for certificate-pinned applications while still steering the traffic through the Netskope cloud. (Section: "Creating an SSL Decryption Policy").

Scroll to Top