Fixed Issues In Release 118.0.0
Fixed Issues In Release 118.0.0
Here is the list of fixed issues in this release
Issue Number | Category | Description |
---|---|---|
472852 | Behavior Analytics | Increased limit to 400 entries for App, App instance, Sanctioned App picker for Policies > Behavior Analytics custom and standard UEBA policy editor. |
4647,470084 | CASB Real-time Protection | Fixed an issue in the ChatGPT application, where you can send queries to the ChatGPT bot without logging into the user account (like Google, Microsoft etc.). When the user is not logged in, the Instance ID attribute was not displayed. To have user visibility, we define Instance ID as “unauthenticated” for anonymous users using ChatGPT without logging in. |
457998 | Data Protection | Fixed an issue where the “dlp_file” field was not set for incidents associated with non-containerized files such as plain text files. |
480402 | Data Protection | Fixed Header or Subject matching for emails with HTML-only body. |
480024 | Digital Rights Management (DRM) | Fixed an issue by improving response time while loading labels as part of FileFilter. |
472469 | Email DLP | When sending traffic to O-365, out-of-office auto replies were being rejected due to a new requirement imposed by Microsoft. This has been fixed. |
473759 | Netskope Secure Web Gateway (NG SWG) | Fixed an issue where events where being generated for web traffic (non cloud apps) even when traffic steering was only enabled for cloud apps. |
490576 | Netskope Secure Web Gateway (NG SWG) | Fixed an issue where Netskope SWG was keeping the state of internal RBI headers and not deleting them post the session. With this fix, all internal RBI headers will be removed from all requests in the session. |
468141 | Netskope Secure Web Gateway (NG SWG) | Fixed an issue where an incorrect user template was presented to user for block response instead of default block template. |
473311 | Netskope Private Access (NPA) | Fixed an issue where in certain scenarios with prelogon enabled, after a user logs in, a race condition might occur where the client UI connectivity to client service takes longer than the client configuration download for logged in user. This will cause the user tunnel to not establish. |
473903 | Netskope Private Access (NPA) | App discovery rule was inadvertently included for all users when SRP was constructed out of cache. To fix this issue, App discovery rule should be included strictly based on App Discovery settings under any circumstances. |
483583 | Netskope Private Access (NPA) | With this fix using new steering configuration API, NPA service should be able to consume any updated steering configurations in time. |
473204 | Netskope Private Access (NPA) | With this fix local brokers can work with SRPv2-enabled tenants but with SRPv1 infrastructure. SRPV2 is not supported by a local broker. This is a known issue (488897). |
23178 | Remote Browser Isolation (RBI) | The process of upload and download files via RBI was enhanced to more reliably support blocking files fixing an error in how files were blocked. |
21188 | Remote Browser Isolation (RBI) | Fixed an issue where the first downloaded image sets the image type, that can be downloaded later, that is, when an image.png was downloaded, only images with png file type downloads were subsequently allowed. |
22675 | Remote Browser Isolation (RBI) | Resolved an issue where scrolling with the mouse wheel in an isolated website would sometimes result in requesting a full page update, making visualization less fluid in this situation. |
22380 | Remote Browser Isolation (RBI) | Fixed an issue processing URL addresses automatically normalized by the browsing engine, which in some situations resulted in generating a slightly different URL that points to the same navigation address, so the isolated webpage wouldn’t be open properly in isolation. |
476729 | SaaS Security Posture Management (SSPM) | Fixed an error message on the SkopeIT > Alerts page to points to Policies > Security Posture, API-enabled Protection > Security Posture when the user does not have access to Security Posture. Previously the error message was shown incorrectly as Settings > Configure App Access. |
14477 | SaaS Security Posture Management (SSPM) | Fixed an issue where wrong number of findings were shown when primary resource type in the rule was updated. As an outcome of the fix, there are restrictions placed on modifying the primary resource type in the rule. |
480608 | SaaS Security Posture Management (SSPM) | Fixed errors faced when filtering by rule names with single quote (‘) in it. |
472565 | Traffic Steering | In macoS devices, once an auto-upgrade trigger condition is met, the network extension sends a message to the Client UI process to launch the new Client package. In this issue, the network extension attempted to send a message even when there was no Client UI process running(no users logged in). With this fix, whenever there are no users logged in, an upgrade trigger message is not sent from the network extension. |
466281 | Traffic Steering | Rest API /api/v1/clients was not working for the most of the parameters across fields and query. This issue is now fixed and now, the Rest API /api/v1/clients execution for field and query with various parameters appears for Devices under Security Cloud Platform. This issue occurred for a new MP. |
437196 | Traffic Steering | The DPS.json file holds the user configuration path for uninstallation cleanup. When this file is corrupted, it blocks any user data added in the file. With this fix, the DPS.json file is cleared to continue with the subsequent updates. |
419687 | Traffic Steering | Fixed Device Classification Certificate check to verify if the user certificate is available and signed by the CA in addition to the previous checks to verify the presence of CA certificate. |
437047 | Traffic Steering | With this fix, Netskope Client checks certificate digest (unique hash) in addition to the issuer name of the signing certificate for validating integrity of the NS Client installer images. |
486403 | Traffic Steering | When “Steer non-standard ports“ is disabled in Steering Configuration, it resulted in default domain and category exception to be generated unexpectedly. |