Known Issues In Release 114.0.0

Known Issues In Release 114.0.0

Here is the list of known issues in this release.

Issue NumberCategoryDescription
349259Advanced AnalyticsWhen 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.
399307CASB Real-time ProtectionIt is a known issue that using reverse proxy on a Microsoft Team call created issues while viewing presentation.
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.
434187Endpoint DLP (EPDLP)USB4 devices on Windows 11 are not controlled with Device Control and Content Control. Older devices (USB3 and earlier) are controlled when plugged into USB4 ports.
435431Endpoint DLP (EPDLP)Printer Content Control incidents are missing the corresponding DLP Alert for content matches.
367850Netskope Secure Web Gateway (NG SWG)RT policy for isolated session (traffic generated by RBI) is configured with “Block/Alert/Allow” as action and “Device Classification” present in the source criteria is not being applied properly.
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.
301400Traffic SteeringNetskope Client status is not updated because of the incorrect format.
441039Tunnel SteeringIf the name of an IPSec site contains an uppercase letter, editing and saving configuration of that IPSec site is not allowed.

As a workaround, temporarily change the name of the IPSec site to a different one, edit and save the configuration as desired. Afterwards, the site name can be reverted to the originally desired name.
Share this Doc

Known Issues In Release 114.0.0

Or copy link

In this topic ...