Policy Server

01 Jan 2025 (Seclore 3.31.2.0)
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)
Archived Release Notes

Policy Server 3.17.5.0

Optimized the time taken to implement policies for Seclore Digital Asset Classification (DAC).

Policy updates made by Global Security Administrators for Seclore DAC will now be applied to end users within 6 hours by default, with the flexibility to reduce it to 60 minutes.

Fixed the issue where admins could not configure and save external location URLs (absolute URLs) in the 'Compliance & Policies' section.
Added support for TLS version 1.3.
Upgraded Java to version 17.0.12.
Other fixes.

Policy Server 3.17.4.0

Added support for uploading attachments when users reply to protected emails via browser or mobile devices.

When protected files are attached to the email, permissions will be shared via Smart Sharing if the user attaching the file has Share permission.
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.
Uploading attachments is supported on Seclore for Android 3.10.0000 and above.

System Administrators can now configure the Secure Email size limit on the Policy Server portal.

Fixed the issue where activities performed in Taiwan would not appear in the Policy Server portal.
Fixed the issue where users were unable to access Seclore protected files from SharePoint on-premises in Seclore Online.
Fixed the issue where users were unable to authenticate via Azure Authentication in certain scenarios.
Fixed the issue where ‘Copy Data’ permissions could not be applied to newly created protection policies.
Added support for Apache Tomcat 9.0.93.
Other fixes.

Policy Server 3.17.3.0

Users will now be able to give permissions on a protected file to all external users at once.

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’.
Files protected with this group can be accessed by any user of any external domain.
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.
This group can also be added while changing permissions or protecting files using the server SDK.
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.

Fixed the issue where users would not receive unauthorized activity alerts, adoption stats, and daily activity summary in specific scenarios.
Added support for Apache Tomcat 9.0.89.
Optimized the time taken for opening protected PDF files with offline access enabled for users.
Other fixes.

Policy Server 3.17.2.0

Upgraded Java to version 17.0.10+7.
Upgraded ServerSDK Java to version 4.4.17.0.
Fixed the issue where Global Security Administrators were unable to access the ‘Insights’ tab on the Policy Server portal in a certain scenario.
Fixed the issue where the Server Configuration page in the Policy Server portal displayed incorrectly for Global Security Administrators in certain scenarios.
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.
Other fixes.

Policy Server 3.17.1.0

Activities downloaded from Policy Server portal now feature a 'Country' column, offering visibility into the geographical location of user activities.
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.
Fixed the issue where an error would be displayed after selecting or updating the owner of a Hot Folder.
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.
Fixed the issue where an error would be displayed if the number of entities added to a Protection Policy exceeded the maximum allowed limit.

Policy Server 3.17.0.0

Users can now enjoy a simplified, one-click access experience for opening protected emails online.
Email recipients will receive the email body as a link, including the footer message configured by System Admins.
Clicking on the link will open the email body in the Secure Email viewer, available on desktop browsers and the Seclore Mobile App.
The link will be active for a certain number of days, which is configurable in the Policy Server portal.
If the Seclore app is installed on your desktop, the protected email will open within Outlook itself.

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.
Fixed the issue where certain activities wouldn’t get added to the Risk and Analytics Dashboard.
Apache Tomcat upgraded to version 9.0.83.

Policy Server 3.16.6.0

Global Security Admins (GSAs) can now configure content policies with multiple combinations of custom keywords and regular expressions.
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.
GSAs need to enter keywords and expressions separated by comma and a space. Further, expressions need to be enclosed with slashes / at both ends.
d. For example: date of birth, d.o.b, /\b\d\{4}-\d{2}-\d{2}\b/

Introducing the option to apply either header or footer (or both) for documents and emails classified with Seclore DAC.

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.
GSAs can continue to disable header and footer for both documents and emails.

Fixed the issue where bulk protection of files with long names through Java SDK wouldn’t work in certain scenarios.
Fixed the issue where automatic protection couldn’t be enabled for a SharePoint Document Library with a long name.

‣