Fixed Issues In Release 102.0.0
Fixed Issues In Release 102.0.0
Here is the list of fixed issues in this release.
|233362||API Data Protection||An issue where case sensitivity of user email was causing issues is fixed. Web-hook notifications from Google has case sensitive user email is now converted to lower case as a fix.|
|236808||API Data Protection||Netskope now rightly reflects the delete action with the correct notifications for Salesforce application.|
|234614||API Data Protection||Files and Messages that had DLP violations and were “deleted” via the Netskope “Incident” UI were visible/accessible on end-user’s devices. This issue is now fixed. |
Applies to Slack Enterprise, Slack, MSTeams and ServiceNow.
|231706||API Data Protection||Fixed an issue wherein subscription to web-hook notifications for Gmail was not renewed on time causing gaps in triggering of sent email policy based scan.|
|239333||CASB Real-time Protection||This fix enhanced Google Meet Post activity DLP support for custom identifiers where custom DLP rules and policies can be created.|
|232836||CASB Real-time Protection||We can now generate Upload events when files larger than 10MB are uploaded to Microsoft Live Teams.|
|230466||CASB Real-time Protection||We can now detect From User as part Upload events when files greater than 15MB are uploaded.|
|232513||CASB Real-time Protection||InstanceID is now reflected accurately for Application Events from Microsoft 365 Yammer, Todo and Forms|
|231504||CASB Real-time Protection||Fixed an issue to perform DLP inspection for files that are uploaded using Workiva application.|
|231714||CASB Real-time Protection||An issue wherein multiple emails were being mapped to Instance ID for “Google Accounts” app has been fixed.|
|232485||CASB Real-time Protection||A SAML replay attack was fixed by serving Blocked Page for replay of SAML Duplicate Assertion in AuthService.|
|224665||CASB Real-time Protection||Duplicate events are no longer visible while using SSO via reverse proxy for SuccessFactors.|
|235692||CASB Real-time Protection||This fix helps to generate Login Successful activity for LinkedIn.com.|
|234188||Classic Reports||Fixed an issue where Report was not working when “# Block Events” widget was selected along with other attributes.|
|232516||Cloud Confidence Index (CCI)||Earlier the DNS traffic was matched as an Application. The fix now skips DNS from application match workflow.|
|2336418||Data Protection||Fixed an issue where space delimiter was undetected by adding support for space delimited US ATIN and ITIN numbers.|
|232029||Data Protection||An issue was fixed to successfully send large exported reports upon clicking the send Email button.|
|232945||Data Protection||Fixed an issue that prevented incident details from loading successfully if object_id included single quotes.|
|230971||Intrusion Prevention System (IPS)||IPS signature overrides matching default action do not change product behavior and were previously hidden. All overrides created by customers are now visible in the user interface.|
|203509||Incident Management (IM)||Fixed an issue where incidents triggered due to quarantine actions failed to download files since they were fetched from an incorrect location.|
|224332||Netskope Secure Web Gateway (NG SWG)||When dedicated Egress IP is configured for a tenant, the Cert-pinned app traffic will also Egress using the same configured dedicated IP|
|231609||Netskope Secure Web Gateway (NG SWG)||In some cases, the CASB app connector needs to hold the response headers and parse the response body to determine app activity and whether content inspection is needed. |
TSS Scan V3 check determines if, TSS check is required for “browse” as it was interfering with the response body parsing done by the connector.
This is now corrected by TSS Scan V3 delays the check until after the connector parsing is done.
|232696||Netskope Secure Web Gateway (NG SWG)||With block single destination feature enabled, an issue was fixed where native cert pinned app traffic was dropped when tunnel plus bypass traffic was selected.|
|220533||Netskope Secure Web Gateway (NG SWG)||Fixed an issue where Incomplete Certificate Trust Chain and SSL Handshake Error setting displayed a default bypass value but the Block action might be taken instead. |
This issue only affected these two error settings and the correct action was taken if the settings was saved from the UI. After the fix, the action taken and displayed on the UI are same.
|208133||Netskope Secure Web Gateway (NG SWG)||While matching the app id, if multiple applications match initially and subsequent matches are used to determine the app id then the app group was not resetting if the newly matched app did not have an app group. This is now corrected to reset the app group.|
|212785||Netskope Secure Web Gateway (NG SWG)||Hold until proven user justification handling, was added for Client based access with newer method.|
|235637||Netskope Secure Web Gateway (NG SWG)||NS_ACTIVITY activity was not updated properly for all the cases in the code flow. When the activity is unable to access default activity Browse was updated in the code path.|
|232530||Netskope Secure Web Gateway (NG SWG)||Fixed an issue where uploads using the Netskope Encryption feature containing larger files could be buffered in a single socket call (~10KB). This could intermittently overwrite the encryption header during the encryption process, rendering the uploaded encrypted file corrupt and thus un-decryptable.|
|232702||Netskope Secure Web Gateway (NG SWG)||Fixed an issue where the configured Error Bypass settings might not be honored for requests inspected by IPS. If a request was inspected by IPS and an SSL error was detected when connecting to the server, the block action would always be taken even if the bypass action was selected for the tenant.|
The configured error action will now be taken irrespective of IPS inspection.
|237110||Netskope Secure Web Gateway (NG SWG)||NPA now uses case-insensitive validation to compare email and device identifier.|
|230570||Netskope Secure Web Gateway (NG SWG)||Among the new fields in transaction events (format 3), that is in beta, x-policy-action is introduced to reflect the actual policy verdict. |
Before this fix, that value showed “allowed” even for traffic that didn’t hit real-time policy for example, SSL bypassed traffic.
With this fix, the value of x-policy-action field will show “NotChecked” when the traffic does not match real-time policy. For any other traffic that hits real-time policy, the x-policy action filed will show the verdict of policy evaluation.
This feature is in Beta currently. Contact your Sales Representative or Support to enable this feature.
|196676||Netskope Secure Web Gateway (NG SWG)||Fixed an issue where users navigating to a RBI page would see page with error code 503 ERR_EMPTY_RESPONSE if the target page has http to https redirect.|
|10301||Remote Browser Isolation (RBI)||Fixed an issue during the RBI session setup which was preventing users to browse in isolation.|
As a result, a blank screen is displayed for some seconds before getting an RBI error message. This issue was caused by an unhandled internal OS feature related to process management and special characters.
|11901||Remote Browser Isolation (RBI)||Fixed an issue that prevented RBI to properly update the user’s browsing history while browsing in isolation. With this fix, browsing history reflects the browsing activity of the user, delivering the same experience the user is expecting from the browser when browsing outside of isolation.|
|10797||Remote Browser Isolation (RBI)||Fixed an issue where the RBI Context-Menu was showing the Open in new tab option for non links html elements in isolated web pages. |
After this fix, the RBI context menu only shows the Open in new tab option when the user right clicks on any <link> in an isolated web page.
|229977||SkopeIT||An issue was fixed to render Alerts details preview correctly.|
|238444||Traffic Steering||An issue where IPSec gateway did not send DHCP IP in the TLV to CFW due to a regression, is fixed now.|
|230553||Traffic Steering||Fixed a crash issue happening during the IPSec tunnel cleanup when tunnel was created and deleted quickly.|
|227288||Traffic Steering||Fixed a wrong encoding of Windows OS system information in the debug log.|
|228835||Traffic Steering||Fixed a stAgentSVC crash issue when handling a proxy packet.|
|231171||Traffic Steering||Fixed a Linux auto-upgrade issue whose default language was not English.|
Netskope Client side auto-upgrade issue take two release cycles to take effect.
Here is an example:
|236738||Traffic Steering||We added the support of IPv6 only networking environment for Android Client.|
|231667||Traffic Steering||Netskope increase the stAgentSVC OnStop() timeout from 30 seconds to 90 seconds.|
|217359||Traffic Steering||When Netskope Client is used for traffic steering, channel information extracted from Client is used for device name detection.With iOS as OS identified, device mapping iOS to mac device was missed and default name Linux Device was shown. With the fix mapping is corrected.|
|209132||Traffic Steering||Legacy device classification component does not support multi certificate. The newer version is rolled out with newly refactored service that supports this function.|
In the Device Classification webUI, while adding multiple multiple certificates, the new added certificates do not replace the previous certificate device classification rule .
|235162||Traffic Steering||Netskope disabled Action button in Custom Images page for users with only view permission.|
|230071||Traffic Steering||Fixed an issue where exception records displayed incorrectly in Steering Configuration detail page with dynamic steering mode.|