Fixed Issues In Release 104.0.0
Fixed Issues In Release 104.0.0
Here is the list of fixed issues in this release.
|249639||API Data Protection||Exposure calculation in Google Drive will not take into account admin console sharing settings. Exposure calculation will be based only on the collaborators present on the file.|
|246185||API Data Protection||Fixed the issue with incorrect file owner in the Object Current Details section in the Incidents > DLP page.|
|231479||API Data Protection||Fixed the issue with “Object Owner (on the Incident Listing page)” and “File Owner (on the Incident Detail page)” showing different information. This is now fixed and both the entities point to the owner of the file.|
|252085||CASB Real-time Protection||Fixed an issue where View All activity was not detected for Gmail App when used over “IPAD + Chrome”.|
|239146||CASB Real-time Protection||Fixed the issue with file ‘downloads’ not being detected in SharePoint via Reverse Proxy.|
|249946||CASB Real-time Protection||Fixed the issue with preventing downloads of Zoom installer based on filetype.|
|245440||CASB Real-time Protection||In Office, Home > Recent tab Power BI links were not getting rewritten. This issue has been fixed. Now the Power BI URLs are rewritten.|
|245845||CASB Real-time Protection||It was observed with Power BI that there are some traffic changes that led to users reaching a blank Home page while accessing the application through un-managed devices.|
|246098||CASB Real-time Protection||Fixed an issue where ‘channel type’ had blank values and was added in policy data without selection.|
|245080||CASB Real-time Protection||Fixed an issue where there was a deletion error when deleting a URL from an App Definition.|
|252233||Data Protection||Fixed an issue where events and incidents emitted by DLP reflect the wanted action instead of the action actually taken. This disparity occurs when there is a timeout while waiting for DLP to process a file. DLP continues and completes the scan, but due to the aforementioned timeout, the wanted action (upon DLP match) cannot be taken by the client (introspection, inline, and so on).|
With this change the events/incidents will have a default action or no action specified when such a timeout occurs.
In most circumstances repeated scans will have the correct action taken due to DLP results cache.
|247860||Data Protection||File Owner in the Incidents > DLP detail page will be mapped only to the ‘owner’ field in ClickHouse. No more fallbacks will happen to ‘user’ field.|
|250315||Endpoint DLP (EDLP)||Fixed an issue where the Endpoint DLP uninstaller in older versions could result in the Windows USB stack from failing to start, due to a failure to unregister the epdlp_dev_ctrl.sys driver from the USB stack. This may occur during upgrade or uninstall.|
|246272||Endpoint DLP (EDLP)||A race-condition in the Endpoint DLP agent could prevent from communication the agent to the backend. The problem was related to loading certificates used to secure the communication with the backend services.|
|245122||Endpoint DLP (EDLP)||An issue is fixed that would prevent content-control policy updates to take effect. The local result cache was not invalided correctly when policy changes occurred.|
|243852||Endpoint DLP (EDLP)||Fixed an issue that could prevent the Endpoint DLP agent from starting correctly. Third-party software that installs file system drivers may cause extraneous volume mount notifications to the EPDLP driver which caused extra shadow directories to be created. This slows startup of Endpoint DLP.|
|204343||Endpoint DLP (EDLP)||Fixed Last Action Fields in Incident which was sometimes empty.|
|240336||Endpoint DLP (EDLP)||Fixed User notifications (user alert/block messages) that did not work when connected to the endpoint via RDP.|
|243417||Endpoint DLP (EDLP)||In previous versions, Endpoint DLP policies default to “Disabled” when created. The toggle must be changed to “Enabled” before the new policies can be used. This is reversed now, new policies default to “Enabled”.|
|238647||Netskope Secure Web Gateway (NG SWG)||This release onwards the Host port will be accounted for when serializing the request for explicit proxy case.|
|238993||Netskope Secure Web Gateway (NG SWG)||Fixed whitespaces at the end of ‘cs-uri’ and ‘cs-uri-query’ which could happen in a rare case.|
|240618||Netskope Secure Web Gateway (NG SWG)||Fixed an issue where policies a TSS rule or DLP rule could prevent other content inspection policies from matching for traffic where the activity matches the rule but is not supported by the selected scan type. |
For example, a TSS rule with all categories selected can be created with the Send activity, but TSS is not supported for the Send activity with Gmail. In this case, a transaction for Gmail with a Send activity would not be scanned but could prevent a lower priority DLP rule configured with the Send activity for Webmail from matching.
With this fix, a TSS or DLP rule for an activity that is not supported for the application will not prevent lower priority rules from matching.
|214221||Netskope Secure Web Gateway (NG SWG)||In previous release, some users experienced connection timeouts if following conditions were met:|
|240373||Netskope Private Access (NPA)||This fix enables you to effectively delete private apps from WebUI, if a prior transaction failed,|
|244696||Netskope Private Access (NPA)||Resolved a crash on Android client that surfaced when SWG Tunnel was disconnected and the client was trying to set NPA rules.|
|244997||Netskope Private Access (NPA)||An issue with handling DNS resolution with OPT record type is now resolved.|
|11458||Remote Browser Isolation (RBI)||Fixed an issue that prevented users from seeing the correct inactivity timeout template presented by RBI for expired isolation sessions. In some circumstances, after an inactivity timeout (no user interaction with the isolated web page), the Timeout template title was visible, but the header and description text of the template were not shown due to two templates overlapping.|
After this fix users will see the complete template, including the message describing the situation and instructions to load the page again.
|11399||Remote Browser Isolation (RBI)||Fixed an issue in RBI, where users browsing in isolation could see some websites missing specific resources if they accessed the web page following (clicking on) a link in the isolated session. |
Some redirections were not being evaluated correctly as exit criteria, leading to mixed results in such webpages and incomplete content presented in isolation. After this fix, resource redirection is correctly applied, and these websites are presented correctly.
|223762||Skope IT||Fixed an issue where Object ID column was displaying values from the field Asset ID. Object ID was added as a filterable field and display column, while Asset ID field values are now displayed in Event Details panel as Resource ID.|
|245553||Traffic Steering||Upgraded third-party libraries OpenSSL and curl used in the new iOS application.|
|232880||Traffic Steering||This fix addresses issues caused after ChromeOS R109 installation. IdP enrollment on ChromeOS where Access Denied messages were shown in the browser after IdP enrollment successful. Sometimes, the IdP enrollment failed and NS Client app stayed in Waiting for Config state. These issues were fixed so that IdP can go through successfully on ChromeOS R109 or newer version..|
|236150||Traffic Steering||Fixed proxy duplication issue when the proxy name was in upper case.|
|251960||Traffic Steering||Fixed an issue related to a special network environment when a fully qualified domain name (FQDN) was resolved for both IPv4 and IPv6 but the actual IPv6 connectivity did not work. |
With the fix, IPv6 connectivity is taken into consideration when processing DNS packets. This way connectivity issue reported by some apps can be prevented.
|245775||Traffic Steering||Fixed registry opening issue on Windows 11 when the client checks device classification rule.|
|254890||Traffic Steering||Fixed a crash issue while handling proxy packet.|
|239650||Traffic Steering||Fixed GDI resource leak for specific situations on Windows.|
|239790||Traffic Steering||Fixed an issue where Netskope client on macOS tunnels DNS over TCP traffic to public DNS server via Netskope Cloud firewall in “All traffic” steering mode.|