Policy Server

• 01 Nov 2024 (Seclore 3.31.0.0)
• 01 Sept 2024 (Seclore 3.29.0.0)
• 01 July 2024 (Seclore 3.28.6.0)
• 01 April 2024 (Seclore 3.28.2.0)
• 01 Feb 2024 (Seclore 3.28.0.0)
• 01 Jan 2024 (Seclore 3.27.12.0)
• 01 Dec 2023 (Seclore 3.27.10.0)
• 01 Oct 2023 (Seclore 3.27.8.0)
• 01 Aug 2023 (Seclore 3.27.5.0)
• 01 July 2023 (Seclore 3.27.4.0)
• 01 June 2023 (Seclore 3.27.2.0)
• 01 Apr 2023 (Seclore 3.27.0.0)
• Archived Release Notes

01 Nov 2024 (Seclore 3.31.0.0)

Policy Server 3.17.4.0

1. Added support for uploading attachments when users reply to protected emails via browser or mobile devices.
1. When protected files are attached to the email, permissions will be shared via Smart Sharing if the user attaching the file has Share permission.
2. System administrators can configure the permissions to be applied on unprotected files attached to protected emails via Secure Email. i. If the permissions are not defined, users will get Full Control and Share permissions on the attachment. ii. The file owner of these attachments will be the sender of the protected email.
3. Uploading attachments is supported on Seclore for Android 3.10.0000 and above.
2. System Administrators can now configure the Secure Email size limit on the Policy Server portal.
1. The default size limit will be 20 MB.
3. Fixed the issue where activities performed in Taiwan would not appear in the Policy Server portal.
4. Fixed the issue where users were unable to access Seclore protected files from SharePoint on-premises in Seclore Online.
5. Fixed the issue where users were unable to authenticate via Azure Authentication in certain scenarios.
6. Fixed the issue where ‘Copy Data’ permissions could not be applied to newly created protection policies.
7. Added support for Apache Tomcat 9.0.93.
8. Other fixes.

01 Sept 2024 (Seclore 3.29.0.0)

Policy Server 3.17.3.0

1. Users will now be able to give permissions on a protected file to all external users at once.
1. While adding recipients to a policy or during manual protection using Right-click > Seclore It, users can now add a group named ‘Allow any external user to access’.
2. Files protected with this group can be accessed by any user of any external domain.
3. This feature comes in handy when you want to share a file with external users but aren't sure who would eventually need access to it during downstream sharing.
4. This group can also be added while changing permissions or protecting files using the server SDK.
5. However, if a user's domain is added to the denylist, new users from that domain won’t get access unless they are added individually as recipients to the policy or file. i. Similarly, users who already got access due to the group will lose access if their domain is added to the denylist.
2. Fixed the issue where users would not receive unauthorized activity alerts, adoption stats, and daily activity summary in specific scenarios.
3. Added support for Apache Tomcat 9.0.89.
4. Optimized the time taken for opening protected PDF files with offline access enabled for users.
5. Other fixes.

01 July 2024 (Seclore 3.28.6.0)

Policy Server 3.17.2.0

1. Upgraded Java to version 17.0.10+7.
2. Upgraded ServerSDK Java to version 4.4.17.0.
3. Fixed the issue where Global Security Administrators were unable to access the ‘Insights’ tab on the Policy Server portal in a certain scenario.
4. Fixed the issue where the Server Configuration page in the Policy Server portal displayed incorrectly for Global Security Administrators in certain scenarios.
5. Fixed the issue where users were unable to create an Email Auto Protector rule on the Policy Server portal. a. This issue was observed on Ubuntu 22.04.
6. Other fixes.

01 April 2024 (Seclore 3.28.2.0)

Policy Server 3.17.1.0

1. Activities downloaded from Policy Server portal now feature a 'Country' column, offering visibility into the geographical location of user activities.
2. Fixed the issue where Request Access Rights emails were sent to the wrong users when a Shared Mailbox was used to send the protected email.
3. Fixed the issue where an error would be displayed after selecting or updating the owner of a Hot Folder.
4. Fixed the issue where, upon clicking the "Download Seclore" link in Safari browser 17.1 on Mac and other devices, users were incorrectly directed to the App Store link for the Seclore for iOS app.
5. Fixed the issue where an error would be displayed if the number of entities added to a Protection Policy exceeded the maximum allowed limit.
1. After the fix: A warning message will be displayed in such scenarios.
6. Added support for Server SDK Java to 4.4.16.0.
7. Other fixes and enhancements.

01 Feb 2024 (Seclore 3.28.0.0)

Policy Server 3.17.0.0

1. Introducing One-click Access for protected emails.
1. Users can now enjoy a simplified, one-click access experience for opening protected emails online.
2. Email recipients will receive the email body as a link, including the footer message configured by System Admins.
3. Clicking on the link will open the email body in the Secure Email viewer, available on desktop browsers and the Seclore Mobile App.
4. The link will be active for a certain number of days, which is configurable in the Policy Server portal.
5. If the Seclore app is installed on your desktop, the protected email will open within Outlook itself.
2. Global Security Admins (GSA) will now see a pop up after logging in to the Policy Server portal prompting them to agree to enable the One-click Email Access feature.
3. Fixed the issue where certain activities wouldn’t get added to the Risk and Analytics Dashboard.
4. Apache Tomcat upgraded to version 9.0.83.

01 Jan 2024 (Seclore 3.27.12.0)

Policy Server 3.16.6.0

1. Introducing Enhanced Content Policies for Seclore DAC.
1. Global Security Admins (GSAs) can now configure content policies with multiple combinations of custom keywords and regular expressions.
2. GSAs can create content policies with multiple conditions separated with and/or operators and suggest classification labels to end users when a policy is violated.
3. GSAs need to enter keywords and expressions separated by comma and a space. Further, expressions need to be enclosed with slashes / at both ends.
4. d. For example: date of birth, d.o.b, /\b\d\{4}-\d{2}-\d{2}\b/
2. Introducing the option to apply either header or footer (or both) for documents and emails classified with Seclore DAC.
1. When Global Security Admins (GSAs) enable Visual Marking for documents or emails while creating/editing a label, they can now choose to apply either Header or Footer text (or both), with one of them being mandatory.
2. GSAs can continue to disable header and footer for both documents and emails.
3. Fixed the issue where bulk protection of files with long names through Java SDK wouldn’t work in certain scenarios.
4. Fixed the issue where automatic protection couldn’t be enabled for a SharePoint Document Library with a long name.

01 Dec 2023 (Seclore 3.27.10.0)

Policy Server 3.16.5.0

1. Fixed the issue where the geographical activity map wouldn’t appear in the Insights section of the Policy Server portal in a certain scenario.
1. Before the fix: The geographical activity map wouldn’t appear when at least one activity is found from an unknown or private IP address for the selected time period.
2. After the fix: The geographical activity map would appear excluding the data of activities done from unknown or private IP addresses.

In such cases, a note would appear below the map showing the number and percentage of activities excluded from the map.

2. Fixed the issue where searching for a file name with an extension would not show any results on the Activities page in the Policy Server portal.
1. Before the fix: User would have to remove the extension and search the file name.
2. After the fix: User can search a file name along with the extension.
3. Access Request emails sent to file owners or users with share permission will now contain the email address of the requester along with their name.
1. Earlier, such emails only contained the name of the requester.
4. Other upgrades and fixes.

01 Oct 2023 (Seclore 3.27.8.0)

Policy Server 3.16.4.0

1. An endpoint health check URL is now available for you to monitor the connectivity of Seclore API Server with other architectural checkpoints such as the Policy Server, Database, and Elasticsearch.
1. It also monitors the health of Elasticsearch indexes which indicate the robustness of data shown in the Activities and Insights section of the Policy Server portal.
2. You can configure this URL for monitoring and alerts using your load balancer or an external monitoring tool.
2. Fixed the issue where admins were not able to add permissions for some entities in a protection policy if large number of entities were added.
1. Users can now add up to 700 entities to a protection policy if all permissions are selected for all entities.
2. More entities can be added in case all permissions are not selected.
3. Users can now access protected files using Virtual Desktop Infrastructure (VDI) and Remote Desktop Protocol (RDP) without Screen Capture permission.
1. Users with at least Read permission can now open protected files using VDI and RDP.
2. Users will see Seclore’s dynamic watermark when a protected file is opened using VDI or RDP.
4. Microsoft SQL JDBC jar upgraded to version 12.2
1. Discontinued support for Microsoft SQL Server 2012 and earlier versions.

01 Aug 2023 (Seclore 3.27.5.0)

Policy Server 3.16.3.0

1. Introducing Dynamic Watermarking for classified-only files.
1. While configuring a label, Global Security Admins can now select the type of protection for the label – Watermark / EDRM.
2. When Watermark is selected, classification and dynamic watermark will be applied on supported Microsoft Office and Adobe files. EDRM protection won’t be applied.
3. When EDRM is selected, granular EDRM usage controls will be added to files and emails.
4. Watermark content would appear according to the watermark configuration set by System Admins in the ‘Feature Configurations’ section.
2. Introducing an option to protect email body for classified emails.
1. While configuring a label, Global Security Admins (GSAs) can now enable protection for email bodies when the label is selected to classify emails.
2. GSAs will see an option ‘Enable EDRM for Email Body – Yes/No’ when they select ‘EDRM’ as the type of protection.
3. Select ‘Yes’ to enable this feature.
3. Added ‘Seclore SDK’ as a method in the Classification Activities section.
1. ‘Seclore SDK’ will appear as the method of classification for files classified via the ‘Bulk Classification’ feature.
4. Apache Tomcat upgraded to version 9.0.76.
5. Fixed the issue where it may take several seconds to load the list of all users in the Licenses > Licensed Users section of the Policy Server portal in a certain scenario.

01 July 2023 (Seclore 3.27.4.0)

Policy Server 3.16.2.0

1. Seclore will now add an x-header to emails that’ll help applications detect whether an email was protected manually or via Email Auto Protector.
1. Further, the x-header will be retained even when a recipient replies to the email using Secure Email Viewer.
2. An endpoint health check URL is now available for you to monitor the connectivity of some components with your Policy Server.
1. You can configure this URL for monitoring and alerts using your load balancer or an external monitoring tool.
3. Buffer file updated with well-defined steps to help users open Seclore-protected files in mobile devices.
4. Updated the language pack for Spanish, French, Canadian French, and Brazilian Portuguese.
5. Apache Tomcat upgraded to version 9.0.73.
6. AdoptOpenJDK upgraded to version 11.0.19+7.
7. Fixed the issue where users were not able to open protected files in a certain rare scenario.
8. Fixed the issue where classification activities would appear after several hours in the ‘Classification Activities’ section in the Policy Server portal.

01 June 2023 (Seclore 3.27.2.0)

Policy Server 3.16.1.0

1. Added ‘Last Synced’ and ‘Last Saved’ information in the Rule Console of Email Auto Protector in the Policy Server portal.
1. The ‘Last Synced’ date and time will help administrators know if changes made to Email Auto Protector rules have been applied for end users.
2. The ‘Last Saved’ date and time will help them know when rules were last modified.
3. The date and time appear in the time zone of the administrator.
2. Added an option to use end user’s email address in the ‘From’ field for emails sent by Seclore on an end user’s behalf.
1. Earlier, ‘Access Request’ emails and protected email responses sent from Secure Email Viewer had the admin’s email address in the ‘From’ field.
2. Now, the end user’s email address would appear in the ‘From’ field.
3. System Administrators can enable this feature in the Server Configurations section in the Policy Server portal.
3. Fixed the issue where repositories of other tenants would appear while selecting the Hot Folder owner after enabling Seclore in SharePoint On-premises.
1. This would happen when an enterprise had a multi-tenant set up of Seclore.
4. Fixed the issue where users were not able to add recipients while protecting a file in a certain rare scenario.
5. Fixed the issue where users were not able to able to approve access requests in a certain rare scenario.
6. Fixed the issue where administrators would see an error when they refresh certain pages in the Policy Server portal.

01 Apr 2023 (Seclore 3.27.0.0)

Policy Server 3.16.0.0

1. Introducing Seclore Digital Asset Classification (Seclore DAC).
1. Seclore DAC is designed to help users classify digital assets efficiently and ensure compliance with relevant industry standards and regulations.
2. It helps users identify and classify sensitive data, allowing them to apply appropriate security controls and prevent unauthorized access.
3. Global Security Admins (GSAs) can create and customize classification policies and rules to meet the organization’s specific needs.
4. GSAs can also use the new Risk and Analytics Dashboard to identify and mitigate risk.
5. To learn how to use this feature see our Adoption Portal.
2. Improved the message in the ‘No access’ screen with more clarity on why some users may not be able to access files online or on remote machines.
3. Apache Tomcat upgraded to version 9.0.71.
4. Fixed the issue where users were not able to request access on files where Share permission was given to an organization unit as a group or ‘All users’ group.
5. Fixed the issue where Global Security Admins and Security Admins would either see an error or get redirected to another page when they log in after a session time out in the Policy Server portal.
6. Fixed the issue where Global Security Admins were not able to search for policies in the Policies tab using ‘Owner’ as a filter.