April 2023

Enhancements

• Users can now scan Zendesk Ticket Parts, Ticket Body, and Attachment for violations. A Scan Ticket Parts option has been introduced to the General tab of Zendesk settings, allowing users to scan specific areas of a ticket

• Users can now receive monthly Risk Scan reports in PDF format, containing high-level risk snapshots for the GitHub, Google Drive, Google Drive Enterprise, Slack, and Slack Enterprise platforms
• Enhanced user experience on the Home > Audits > Violations page. Users can now see the following details of a violation:
  • Location of violation
  • Date and time of violation detected
  • Date and Time of the event happening
  • Violation count
  • Type of violation (Rules Violated)
  • User Response to the violations

 

Bug fixes

• Same internal rule now listed once on the Home > Data Security > Policies > Rules tab
• On the Home > Data Security > Policies > Logical Rules tab, logical rules created with an NLP constraint now detecting violations
• On the Home > Data Security > Policies > Logical Rules tab, logical rules are now listed in alphabetical order

 

March 2023

Enhancements

• Enhanced user experience for violation messages in Slack Enterprise. Users can now see the following details of a violation:

  • Tracking mode (Silence, Alert, Remediate) icon

  • Violation message

  • Location of violation (Slack channel)

  • Date and time of violation

  • Violation count

  • Type of violation (Rules Violated)

 

Bug fixes

• Tool-tip icon now showing in the Policy Groups panel heading on the Data Security > Policies > Policy Groups tab

• For a user’s externally or publicly shared file in Google Drive Enterprise, permission type external_sharing or public_sharing is now listed under in Rule sidebar under the Rules Violated section of the Violation Details tab

• In the Communication panel under the Available Connections section of the Connections page, Slack and Slack Enterprise have different icons now

• Violations filters for users search on the Audits > Violations > Filter tab now also looks for external users

• When the connection select bar of the Audits > Violations page's filter is clicked, platforms are now listed alphabetically

 

February 2023

New features

• Alert & Remediate DLP Modes for Zendesk
  • Alert DLP Mode for Zendesk

    • When no sensitive data is detected in a ticket, users receive the in-app alert: “No sensitive data was found based on your organization’s data policies.”

• • • When sensitive data is detected in a ticket, users receive the in-app alert: “A message was sent that might violate your organization’s data policies. Please review.”, and a list of potential violations

      • Sensitive data is not shown in the alert

• • Remediate DLP Mode for Zendesk

    • When no sensitive data is detected in a ticket, users receive the in-app alert: “No sensitive data was found based on your organization’s data policies.”

• • • When sensitive data is detected in a ticket, users receive the in-app alert: “A message was sent that might violate your organization’s data policies. Sensitive data has been hidden.”, and a list of potential violations

 

Enhancements

• Prior versions of Polymer DLP for Zendesk only monitored violations for New tickets by default. Now, Open, Closed, and Pending tickets are being monitored for violations by default. Users can change this setting in Settings > General under Allowed Statuses by removing the ticket statuses that should not be monitored

• In Audits > Violations, hover text indicating “Detection date” now displays to clarify that Date is the data and time when Polymer detected the violation

• The Violation Details tab now displays:

  • The Date (date and time when Polymer detected the violation) and the Event Date (date and time when the violation happened)

• For Google Drive violations, hover text for indicating “Last user to edit file” now displays to clarify that User is the last user to edit the file which may/may not be the user who caused the violation

 

Bug fixes

• GitHub Enterprise pre-commit hooks are now working for files that contains spaces in their name

• Clicking “Select Multiple Rules” on the Settings > Repositories > Rescan > Select Rules for GitHub Enterprise does not show disabled rules and created constraints

• Test monitoring on the Settings > Monitoring page for an installed platform is now working for Webhook and Syslog when Slack is not installed

• When the Silence DLP Mode for Jira is enabled, the Advance tab on the Settings page is now operational

 

January 2023

New features

• Polymer DLP for Zendesk

  • Installation

    • Users can install Polymer DLP for Zendesk quickly and easily. See below:

      • In Polymer Hub, open Connections

      • Open Customer Service

      • Click on the Zendesk icon

• • • From the pop-up window, copy the URL in the parentheses after “Enter Redirect URLs”

• • • Create an Oauth Client in Zendesk

      • Open Zendesk Admin Center

      • Open Apps and integrations > APIs > Zendesk API > OAuth Clients

      • Click Add OAuth client

      • Enter Client name (e.g. Polymer DLP OAuth)

      • Enter Company

      • Enter Unique identifier (e.g. polymer_dlp)

      • Paste URL copied in previous step into the Redirect URLs field

      • Click Save

• • • Click Copy next to the Secret field to copy the secret token generated

• • • In the Polymer Hub pop-up window, enter Workspace and Unique Identifier, and paste the Secret copied in the previous step 

• • • Create private app in Zendesk:
      • Open Zendesk Admin Center
      • Open Apps and integrations > Apps > Zendesk Support apps
      • Click Upload private app

• • • Enter App Name as Polymer DLP for Zendesk
    • Download this App File

• • • Click Choose File and select the App File you downloaded

• • • Click Upload

 

• • • Click Install

• • • In the Polymer Hub pop-up window, click Continue with Authorization Steps

 

• Functionality

  • Polymer DLP for Zendesk tracks violations in Zendesk tickets—both messages and files uploaded to a ticket

 

Enhancements

Jira is now integrated with every project that is created under a Jira account

• In Data Security > Groups > Policies, if a rule—custom or default—is overridden (set active) in any user group policy and that same rule is assigned to a newly created policy, then then this rule is set as overridden (active) in the newly created policy as well

• Added platform logos for the Integrated Connections on the Connections page

 

Bug fixes

• Policy override is working properly now. In Data Security > Groups > Policies, policy rules that are not overridden (disabled) in a user group are shown as redacted in the message reporting the violation

• Violations are now reported in files attached to Jira's comments section

•  Previously detected violations are no longer reported when a new violation is detected in Jira's comment section after it has been updated

 

December 2022

New features

•  Polymer DLP for Jira

  • Installation

    • Users can install Polymer DLP for Jira quickly and easily. See below:

• • Functionality

    • Polymer DLP for Jira detects violations in Jira tickets—titles, descriptions, and files uploaded

Date in Title, SNN and IP Address in Description
Person Name and Street Address in uploaded File

• Users can now receive violation notifications in Slack from all Integrated Platforms

• New UI for all Integrated Connections settings

• Users can access Release Notes in the Polymer Hub user menu

• Data Intelligence
  • Users will be able to access anew analytics dashboard for violations and risk soon. This dashboard will help organizations make informed decisions about protecting and securing their data.

A snapshot of what will be reported is shown below

• Polymer DLP for Microsoft OneDrive

  • Installation

    • Users can install Polymer DLP for Microsoft OneDrive quickly and easily. See below:

• • Functionality

    • Polymer DLP for Microsoft OneDrive detects violations in Microsoft OneDrive—when files are created, uploaded, modified, and shared

 

Enhancements

• UI Enhancements for Users Group page

• New search functionality has been introduced for the Files Tracking

Bug fixes

• Translation Box now correctly displays on laptop screens in Connections > Settings > Advanced 

• Slack channels not listed in the channels select box are now visible and can be accessed via Connections > Settings > Monitoring

• Deleted external groups are not displayed in Data Security > Groups

• Webhook URLs save in Connections > Settings > Monitoring after adding workspace and channel for Slack monitoring

• Dropdown box for the Connect button on the Connections page is working properly

 

November 2022

New features

• A new feature to monitor detected violations was released 

  • Logs can be delivered via Webhook and Syslog from Home > Connections > Settings > Monitoring 

    • Webhook

      • Events are reported to the page for which a URL is provided

    • Syslog

      • Events are sent to a logging server by providing Host IP, Port Number and Protocol

Enhancements

• Business email addresses are now required for the Polymer Risk Scans

Bug fixes

• Missing translations for GitHub Enterprise pre-commits hook are now showing and editable in Home > Connection > GitHub Enterprise > Advance 

• Files are now showing in Home > Audits > Files when filtered for GitHub, GitHub Enterprise, and Bitbucket

• Inactive filter tab now opens in Home > Security Policies > Users 

 

October 2022

Enhancements

• Standardized template for all of Polymer's outgoing emails
• Installation instructions are added when installing integrations from Connections in the Dashboard

Bug fixes

• User name updates everywhere when it is updated in the User Overview
• Files deep links and filters working properly
• Scan reports are now sent monthly for all integrations in which Polymer is installed
• The User Risk Score arrow is working properly instead of showing zero on the Home page dashboard

 

September 2022

New features

• Polymer Risk Score
  • Users can measure the risk level for data leakage based on the amount of sensitive data shared across all SaaS apps. It is calculated using real-time interactions. Polymer assigns employees a Risk Score based on their individual behavior. This factors in:
    • Frequency – Number of violations
    • Severity – amount of sensitive data in each violation
    • Age – Recent violations carry more weight than past violations
    • Suspicious Activity (coming soon)

• Users can now see a list of files that have PII in Home > Audits > Files
• Users can now see a list of events that violate security policy in Home > Audits > Violations

Enhancements

• Slack Risk Scan now scans the previous six months

Bug fixes

• Pagination for Violations, Events, and Files working properly