Fixed Issues In Release 97.0.0
Here is the list of fixed issues in this release.
Issue Number | Category | Description |
|---|---|---|
196492 | API Data Protection | Fixed an issue where policy Quarantine action was failing in case the source application was SlackEnterprise or Slack and the Quarantine destination was SharePoint. |
196346 | API Data Protection | Fixed an issue where SlackEnterprise Alert details failed to show the SlackEnterprise channel name. |
133078 | API Data Protection | Fixed an issue with GoogleDrive Retroscan where the correct exposure of the file was not updated on the Netskope UI after taking the Restrict Access policy action. |
183448 | API Data Protection | Fixed an issue the Microsoft Teams application where team membership changes were not reflected in the Netskope UI. |
191856 | API Data Protection | Fixed an issue where Slack Quarantine or LegalHold channels was not configured to receive Policy action bot notifications when the list of members in the notification details was large. |
189686 | Data Protection | Fixed an issue where forensic data could not be retrieved when viewing incidents involving Data Loss Protection (DLP) fingerprinting rules. |
195378 | Netskope Secure Web Gateway (NG SWG) | In this release, Netskope fixed an issue by applying No SNI action for all access methods, including IPSec and GRE. Prior to this change any traffic routed through IPSec or GRE access methods were bypassed irrespective of No SNI setting. |
195951 | Netskope Secure Web Gateway (NG SWG) | In this release, Netskope fixed an issue where forward to proxy and RBI might not work when CTEP is enabled. With the introduction of policy-less CTEP configuration, the forward to proxy or RBI action might not be affected if CTEP is enabled. With tis fix CTEP is bypassed for forward to proxy and RBI flows. |
182625 | Netskope Secure Web Gateway (NG SWG) | In this release, Netskope fixed an issue where the URL Lookup API might return a blank category for an invalid URL. After this fix, the Uncategorized category will be returned for an invalid URL. |
149807 | Netskope Secure Web Gateway (NG SWG) | Netskope fixed an issue where NRD domain was automatically categorized as a security risk. After this fix, automatic security risk alert is not generated unless explicitly specified to generate alerts or blocks by policy. |
190870 | Netskope Secure Web Gateway (NG SWG) | Fixed an issue where NS Proxy was not generating the Upload activity event and policy lookup. This issue occurred when request body was missing and content-length header in request header was set to zero. |
191623 | Netskope Secure Web Gateway (NG SWG) | Fixed an issue where domain information was missing in events generated for bypass traffic. |
170534 | Netskope Secure Web Gateway (NG SWG) | Netskope fixed an issue where custom URLs (such as www.example.com:80 and www.example.com:443) were considered the same regardless of the port. With this fix, custom URLs get matched only if the URL is accessed via port 80 and 443 respectively. |