Fixed Issues In Release 107.0.0
Fixed Issues In Release 107.0.0
Here is the list of fixed issues in this release.
|223907||Advanced Analytics||Fixed a display error for scheduled dashboards/widgets where skipped days of week displayed empty string. The schedule text was also changed, for example, “Every day at 6:00 am” would become “At 6:00 AM, every day”.|
|288322||API Data Protection||Fixed an issue with CASB-API ServiceNow integration wherein Ongoing Scan policy triggered email notifications that were not generated for specific scenarios.|
|209965||Behavior Analytics||Improved efficacy of Standard UEBA shared credentials policy with updated detection logic.|
|269743||CASB Real-time Protection||Added support for new traffic pattern observed while editing a OneNote Notebook.|
|280106||CASB Real-time Protection||Added support to cover the BatchUpdate traffic for OneDrive Connector.|
|281799||CASB Real-time Protection||Added fix for the from_user value that was getting generated as public-link for activity across the Marketo app.|
|285878||CASB Real-time Protection||Enhanced Lucidchart application connector to address Instance Detection issues.|
|287788||CASB Real-time Protection||Fixed an issue where users were unable to get taskbar for Microsoft Suite. You will be able to load, access and use O365 Word and O365 Excel via Reverse Proxy.|
|278418||Data Protection||Fixed a rendering error with forensic preview in which the keyword used for indexing was found in the forensic data of a customer.|
|289177||Data Protection||Addressed a bug in the response from Cloud DLP to Endpoint DLP Client that allows the client to properly take action on DLP Profile matches, only when the action threshold set in the DLP Rules used by the DLP Profile is met.|
|278201||Data Protection||Improved the detection efficacy of “Expiration Dates (English)” Entity by enhancing several detection criteria. The entity has been constrained to match on dates with 4-year digits between 2010 and 2049 and dates with 2-year digits between “10” and “49”. Months with 2-year digits separated by a dash must be zero-padded to 2 spaces (“mm-yy”; for example, “04-29”), while slash-delimited dates with 2-year digits allows optional zero padding.|
|268001||Endpoint DLP (EPDLP)||Resolved an issue that caused files with certain unicode file paths to raise exceptions, leading to them incorrectly passing file evaluations.|
|288464||Netskope Private Access (NPA)||Fixed an issue with API schema for updating the private application.|
|279662||Netskope Private Access (NPA)||Fixed an issue to support the creation of multiple private apps with parallelism using APIs.|
|286610||Netskope Private Access (NPA)||Fixed an issue on Chromebook to connect to Private Access gateway instead of NS gateway. With this issue users we unable to connect to Private Access.|
|278411||Netskope Private Access (NPA)||Search/filter for publisher names on web UI now supports special characters. Characters include . (dot), _ (underscore), – (hyphen) and spaces.|
|282351||Netskope Secure Web Gateway (NG SWG)||Fixed Transaction Event fields where ‘x-category’ and ‘x-other-category’ were left empty when the traffic was SSL bypassed or was blocked by realtime policy on SSL context evaluation. With this fix, both fields have values.|
|274763||Netskope Secure Web Gateway (NG SWG)||Fixed an issue in RBI flow. Download was not blocked when the download URL copied from an isolated session was pasted in new browser tab.|
|278133||Netskope Secure Web Gateway (NG SWG)||Netskope also uses referrer URL for application lookup to determine telemetry apps. Fixed an issue in the referrer based lookup that caused the XFF header to be inserted in the request based on the application signature of the referrer application even when the host domain is excluded in XFF config.|
|239635||Netskope Secure Web Gateway (NG SWG)||Fixed an issue where an error would be reported in the WebUI when saving a Network Location with the special characters ” or \ in the name. These characters are now supported in Network Location names.|
|289154||Netskope Secure Web Gateway (NG SWG)||Updated All ASCII characters except “;”, ” \n” and “\r” will be permitted in Header insertion Value. Unicode will be blocked.|
|284673||Netskope Secure Web Gateway (NG SWG)||Fixed an issue for the AWS users using NS Proxy, where users were receiving incorrect instance ID’s in certain corner case scenarios.
The issue was caused due to a limitation in the implementation of instance ID extraction where the cached results was corrupted and wrong values were getting updated.
|272520||Traffic Steering||Fixed a crash issue that occurred due to race conditions that resided in proxy, multi-user environment.|
|288639||Traffic Steering||Fixed an issue where NSDIAG incorrectly displayed Failed to download configuration updates since version 106.0.0.|
|236528||Traffic Steering||Fixed the logic of detecting captive portal whenever Fail Close is enabled.|
|286674||Traffic Steering||Earlier, whenever NS and NPA tunnels are enabled and if NS tunnel is disconnected, the NPA tunnel also got affected. However, the UI still showed the NPA tunnel in working state and connected. This issue is now fixed and the disconnected tunnel do not affect the state of the other tunnel.|
|284783||Traffic Steering||Fixed an issue where the non-standard ports bypassing traffic were dropped on Netskope Client for Linux devices.|
|278631||Traffic Steering||Query Service provides support for the advance filters without WebUI control, with the expectation that the pattern should align between the queryservice and WebUI.
An issue occurred while enhancing the code, which is fixed by aligning the format with the queryservice call. The advanced filters will now show the correct result with the right format.
|280075||Traffic Steering||Earlier, whenever an auto-upgrade tries to STOP the existing stAgentSvc, sometimes, it leads to time out and the effort to kill stAgentSvc also fails. Fixed this issue by rolling back the upgrade if it fails to stop or kill the existing stAgentSvc.|
|292886||Traffic Steering||Fixed a connectivity issue. The Netskope Client now connects properly to the optimal POP when the device comes out of standby.|
|273717||Traffic Steering||Earlier, when All Traffic mode was configured on the tenant webUI, All Web mode was displayed on the iOS client UI instead of All Traffic. This issue is now fixed.|
|278530||Traffic Steering||Fixed an issue where the Internet Access on the UI was not displayed whenever the Netskope Client for iOS devices steered traffic and NPA was enabled. This issue was caused by the dynamic steering enhancement issue that hides the Internet Security block inappropriately.|
|283071||Platform Services||Fixed an issue where a custom image for email notifications appeared as its original size instead of a small logo.
This issue was specific to users using older Windows and Outlook versions and only affects the appearance of the logo, email notifications were not impacted.
|13996||Remote Browser Isolation (RBI)||Fixed an issue that was causing the RBI container assigned to the user to crash. Due to this issue, the RBI client was losing the connection with the RBI platform, and the user was presented with the “reconnect” error dialog. With this fix, the user is not presented with this error dialog.|
|14083||Remote Browser Isolation (RBI)||Fixed an issue that was causing RBI to detect Microsoft Edge’s sidebar as an unsupported browser, failing to render the content in isolation. When users tried to perform a search in Microsoft Edge’s sidebar they were presented with the “browser not supported error”. With this fix, Edge’s sidebar is properly identified as an RBI Supported Browser.|
|269366||Threat Protection||Fixed an error condition where Retrohunt API may return a “not authorized to check this sample report” message.|
|274604||UI Platform||The issue with FedRamp/PBMM tenants not being able to update the Idle Timeout from the UI has been resolved. Previously, it was fixed at a constant value of 15 minutes.
However, with this fix, tenants can now configure the Idle Timeout to different values. The default value is set at 15 minutes.