Known Issues In Release 123.0.0
Known Issues In Release 123.0.0
Here is the list of known issues in this release
Issue Number | Category | Description |
---|---|---|
572100 | Data Protection | It is a known issue that DLP has a limit on number of matches recorded. In some cases, this limit may be reached before the highest priority Real-time policy and DLP profile are found in the input data. In such scenarios, incidents are not being generated for that matched DLP profile and Realtime policy. |
575364 | Netskope Private Access (NPA) | The outbound tunnel connection from a Client to the Local Broker may encounter instability if there is a conflict between the hostname and IP addresses of the local broker gateway and the scope defined in the Application Discovery configuration. |
566868 | Netskope Secure Web Gateway (NG SWG) | User alert is intermittently ineffective for HTTP2 traffic, when the server sends an informational early hints response before the actual response as it can cause the response to be incorrectly identified as a background request. |
555332 | Justification event with action as “Proceed (Cached)” should not be generated for browse traffic when TSS Scan V3 feature is enabled. | |
546915 | It is a known issue that uploading large video files to https://vimeo.com/ may fail when File Filter profiles and TSS/DLP rules are applied. | |
528750 | Traffic Steering | If the user logs off while the Netskope Client is enabled, the Tunnel Disconnect event is not posted. |
555622 | BSOD issue is observed when the DNS Security feature is enabled in a multi-user environment. | |
466448 | It is a known issue that when self protection is enabled, MSI re-run to update the secure enrollment tokens does not work. Instead, you can use nsdiag to update the secure enrollment tokens. |