Known Issues In Hotfix Release 116.1.0

Known Issues In Hotfix Release 116.1.0

Here is the list of known issues in this release.

Issue Number CategoryDescription
349259Advanced AnanlyticsWhen a dashboard is in Edit mode, adding a new widget from the ‘Add Widget’ button triggers browser pop-up, that prompts user to ‘Stay on Page’ or ‘Leave Page’. If ’Stay on page’ or ‘Cancel’ is selected (depending on your browser) it cancels the action of adding the widget, while selecting ‘Leave Page’ or ‘Leave Site’ allows to add widget.
463284Behavior AnalyticsCustom UBA policies are triggered for scan type Real-time protection when access method is CASB API (Next Gen).
463283Behavior Analytics CASB API (Next Gen) does not appear under app instances selection for Standard UEBA behavior analytics policies.
399307CASB Real-time ProtectionFix for users who were having problems in viewing presentations while using reverse proxy while on a MS Teams call.
132227CASB Real-time ProtectionIn Google Calendar, the downloaded bigger files are not getting the file size policies.
434756,434880,434730Endpoint DLP (EPDLP)Printer Content Control encounters errors when printing to Canon MG3600-series printers.
435431Endpoint DLP (EPDLP)Printer Content Control incidents are missing the corresponding DLP Alert for content matches.
423457Netskope Secure Web Gateway (NG SWG)Rules with filefilter conditions might not be considered when they followed a content inspection rule with a traffic action.
21008Remote Browser Isolation (RBI)Under some circumstances Netskope does not meet the requirements for the Cloudflare Bot Detection System which results in the checks failing.
301400Traffic SteeringNetskope Client status is not updated because of the incorrect format.
225028Traffic SteeringTo enable DNS security in web mode, Netskope client tunnel should be re-established. Netskope client detects the DNS traffic enable flag from web UI and then checks for the CFW availability on tunnel establishment. If CFW is available then the Netskope client starts the DNS security. Netskope Client also re-established the tunnel upon machine restart, shutdown, network change and enable/disable of Netskope client.
466448Traffic SteeringWith self protection enabled, when the tokens change in a tenant, the MSIEXEC command (for example, msiexec /I NSClient.msi mode=peruserconfig host= <tenant-name>.goskope.com token=<token ID> enrollauthtoken=<new authentication ID> enrollencryptiontoken=<new encryption ID>) failed to update the tokens while repeating the Client installation using the new tokens. As a workaround, use nsdiag to update the secure enrollment tokens.
438566Traffic SteeringNetskope does not support TCP/DNS response handling when DNS responses are received through the tunnel when the DNS Security is enabled.
Share this Doc

Known Issues In Hotfix Release 116.1.0

Or copy link

In this topic ...