Seclore for Microsoft Sensitivity Labels 1.0.0.0

1. Introducing Seclore for Microsoft Classification?integrating Seclore with Microsoft sensitivity labels.
1. You can now use Microsoft sensitivity labels to protect Office 365 documents with Seclore. Simply configure sensitivity labels with Seclore's protection policies and protect documents by selecting the configured labels.
2. As soon as you select a sensitivity label that's mapped to Seclore's protection policies and close the document, it gets protected.
3. This feature is available with Office 365 (with sensitivity labels) and Windows 10 only.

Policy Server 3.11.2.0

1. Fixed the issue where protected files wouldn't open from SharePoint On-Premises in a certain scenario.
1. Before the fix: To open a protected file, when users click on 'Open with Seclore' in SharePoint On-Premises and click 'Use a different account' in the Seclore authentication page, an error would show up.
2. After the fix: This issue is now resolved.
2. Fixed the issue where the name of the sender (Seclore Admin) wouldn't appear in the 'From' field in some system-generated emails.
1. Before the fix: The 'From Email ID' would appear as the name of the sender in the 'From' field in some system-generated emails.
2. After the fix: This issue is now resolved.
3. Fixed the issue where some protected emails (.smail files) wouldn't open in a browser. This issue was observed in Policy Server 3.10.1.0 (Seclore 3.16.1.0) to Policy Server 3.11.1.0 (Seclore 3.18.2.0).

Seclore for Mac 3.6.0.0

1. Added support in Mac with M1 processors for editing protected documents in Office applications.

Seclore for Windows 3.14.0.0

1. Added support for opening universal file formats (mp4, mp3, wma, dwg, etc.) in desktop applications from Microsoft Teams.
1. Expected behavior: Some applications like Adobe Photoshop, Notepad, etc. don't lock files when in use. Changes made to such files after four minutes of inactivity won't be synced back to Teams. A local desktop copy would get created instead.
2. Additionally, users would see a notification, 'Hang on... opening file on desktop', when they try to open a protected file from Teams in a desktop application.
3. Expected behavior: It would appear as a slide-in notification at the bottom-right of the desktop. It won't appear in the notifications pane.
2. Fixed the issue where timestamps wouldn't appear correctly for protected files in a certain scenario.
1. Before the fix: Files protected and HTML-wrapped manually with the Right-click > Seclore It option would show incorrect 'Created' and 'Modified' date and time.
2. After the fix: This issue is now resolved.

Seclore for O365 3.5.2.0

1. Added support for programmatically enabling Seclore IRM in SharePoint sites using applications token/scripts. You may contact your customer success manager to deploy this feature.
2. Fixed the issue where protected Office files wouldn't open in certain scenarios.
1. Before the fix: Office files uploaded to IRM-enabled document libraries would get protected. However, these files would show an error when opened in Seclore Online or in the desktop applications.
2. After the fix: This issue is now resolved.

Seclore Online 3.4.0.0

1. Added support for opening files with universal protection (mp4, mp3, dwg, etc.) in desktop applications.
2. Made changes to the product architecture to enable faster opening of files in desktop applications.
3. Fixed the issue where animated GIFs wouldn't open in Seclore Online.
1. Before the fix: HTML-wrapped animated GIF files wouldn't open in Seclore Online when dragged to a browser or opened from the Policy Server portal.
2. After the fix: This issue is now resolved.
4. Fixed the issue where graphs and charts wouldn't work in Seclore Online in certain rare scenarios.
1. Before the fix: Graphs and charts wouldn't open or get inserted in .docx and .pptx files when opened in Seclore Online. This would happen when Seclore Online and Document Server are in different domains.
2. After the fix: This issue is now resolved.
5. Fixed the issue where the timestamp for some activities would appear incorrectly in the Policy Server portal.
1. Before the fix: Edit and Print activities logged for files opened in Seclore Online would show an incorrect time stamp in the Activities tab in the Policy Server portal. This happened due to different time zones in the computers hosting the Policy Server and Seclore Online.
2. After the fix: This issue is now resolved.

Hot Folder 3.2.4.0

1. Made changes to the buffer file for desktop applications.
1. In some cases, users see the Seclore's buffer file when they open a protected file on their desktop. The buffer file contains the enterprise's logo and a customized URL of a webpage that helps users with ways to open the protected file.
2. To enable faster deployment of the Policy Server for new Seclore customers, we've removed the enterprise logo from the buffer file and added a generic URL of a file opening app that will help users open the protected file.
3. Buffer files for existing Seclore customers will remain unaffected.
2. Fixed the issue where timestamps would appear incorrectly for files in Hot Folders with HTML-wrapping enabled.
1. Before the fix: Files protected and HTML-wrapped in hot folders would show an incorrect creation and modification date and time.
2. After the fix: This issue is now resolved.

Sample Apps 3.0.0.0

1. Added support for Sample Apps to work with version 3 integration of Seclore Online.

Policy Server 3.11.1.0

1. Fixed the issue where system-generated emails wouldn't get sent in a certain scenario.
1. Before the fix: When the email address is changed in the 'From Email ID' field in the Policy Server configurations, some system-generated emails wouldn't get sent to users. This issue was observed in cloud setups only.
2. After the fix:This issue is now resolved.
2. Fixed the issue where multiple groups (domain level groups, repository level groups, and all users group) would appear in search results while assigning permissions to users.
1. After the fix, users would see only one group in search results, that is, All Repository_name Users. This will prevent any issue that may occur if Seclore Identity Management is migrated to Active Directory.
3. Fixed the issue where Repository details wouldn't get updated in a certain scenario.
1. Before the fix: Users couldn't update repository details if the status of the repository is 'Not initialized'. The 'Not initialized' status appears when incorrect details have been added to the repository.
2. After the fix: This is issue is now resolved. Users would be able to update details for non-initialized repositories as well.
4. Fixed a minor issue in the UI for assigning and changing permissions. This issue was observed in Safari 14.1.x only.
5. Installation Guide and Migration guide now contain steps to customize your logo in the Policy Server portal.
6. Apache Tomcat upgraded to version 9.0.43.

Seclore for Windows 3.13.3.0

1. Fixed the issue where PDFs generated from protected Office files wouldn't open correctly.
1. Before the fix: When an Office file (Word, Excel, PowerPoint) is converted to PDF using File > Export > Create Adobe PDF or Create PDF/XPS Document, the converted file would show the Seclore buffer file.
2. After the fix:
3. In case of File > Export > Create Adobe PDF, the converted file would get exported and can be opened manually.
4. In case of File > Export > Create PDF/XPS Document, the converted file opens as a protected file and shows the original content.
2. Fixed the issue where Office applications would shut down unexpectedly in certain rare scenarios.
1. Before the fix: Office applications would shut down when unprotected files are opened from the 'File > Home > Shared with me' section. This issue was observed in Office 365 applications.
2. After the fix: This issue is now resolved.
3. Fixed the issue where PDF files wouldn't open correctly in Adobe Acrobat DC in certain rare scenarios.
1. Before the fix:
2. Protected PDF files opened in Adobe Acrobat DC would show the Seclore buffer file instead of the original content when 'Enable Protected mode at startup' is checked.
3. Adobe Acrobat DC would shut down unexpectedly when unprotected files are opened with 'Enable Protected mode at startup' checked.
4. These issues were observed in Adobe Acrobat DC 2021.001.20145.
5. After the fix: These issues are now resolved.
4. Fixed the issue where unprotected Excel and Word files wouldn't open correctly in certain rare scenarios.
1. Before the fix:
2. When a protected Excel or Word file is open, and an unprotected attachment is opened from the 'File > Home > Shared with me' section in protected view, the unprotected file would open with the Seclore buffer file instead of showing the original content. The original content would appear after clicking on 'Enable editing'.
3. This issue was observed in Word and Excel with Office 365.
4. After the fix: This issue is now resolved.

Seclore for Forcepoint DLP 3.0.2.0

1. Fixed the issue where files wouldn't get protected in a certain scenario.
1. Before the fix: Files wouldn't get protected when Administrative Shares (C$, D$, etc.) are disabled.
2. After the fix: This issue is now resolved.

Repository Adaptor Migration Tool 2.0.0.0

1. Added support for migrating Seclore Identity Management to local (on-premises) Active Directory and Azure Active Directory.

Seclore for Windows 3.13.2.0

1. Fixed the issue where Seclore-protected Excel files wouldn't open in a certain rare scenario.
1. Before the fix:
2. Seclore-protected Excel files in a mapped drive wouldn't open when the same file is already opened and locked by another user from a mapped/unmapped drive on another computer.
3. This issue was observed in Microsoft O365 Excel files that are not html-wrapped.
4. After the fix: Users would see a message that the file is locked by another user along with an option to open the file in read-only mode.
2. Fixed the issue where the Jet Reports plugin in Excel wouldn't work in a certain scenario.
1. Before the fix: When the Jet Reports plugin is run on a protected Excel file, it would work. However, after this action, other protected and unprotected Excel files would open with an error and the Jet Reports plugin would get disabled.
2. After the fix: This issue is now resolved.

Seclore Online 3.3.1.0

1. Fixed the issue where file name would appear incorrectly when opened in Seclore Online in a certain scenario.
1. Before the fix: After an html-wrapped protected file is renamed, the original file name would appear when opened in Seclore Online.
2. After the fix: This issue is now resolved.
2. Fixed the issue where file names would appear incorrectly in the Activities tab in the Policy Server portal in a certain scenario.
1. Before the fix: When a renamed Seclore-protected file is accessed, the original file name would get displayed in the File Activities tab in the Policy Server portal.
2. After the fix: This issue is now resolved.

Seclore for O365 3.5.1.0

1. Added support for policy federation through Modern Groups in Microsoft 365.
1. Now, permissions changed or revoked for a user in Modern Groups will instantly apply to the protected files downloaded by the user.
2. For example, if a user's permission is revoked on a file, they'll instantly lose access to that file even if it's downloaded.
3. Similarly, when permissions are changed in Modern Groups for a user, it'll immediately apply during the next file access by the user.

Policy Server 3.11.0.0

1. Introducing two-factor authentication (2FA) with Time-based One-time Password (TOTP) for Seclore FIM.
1. Enterprises can now enable two-factor authentication for internal users and external collaborators and partners.
2. Users would be prompted to register their TOTP app when they try to log in for the first time after 2FA is enabled for an enterprise. Any TOTP app can be used for this purpose.
3. Users would then be prompted to enter the code generated by their authenticator app as a second factor of authentication every time they try to log in.
4. 2FA can be enabled by System Administrators from the Repositories section of the System Administrator portal.
2. Introducing support for OpenID Connect.
1. Enterprises can now enable user authentication with any authentication provider that supports OpenID Connect protocol.
2. Apart from the Google and Microsoft authentication options available earlier, enterprises can set up other authentication providers like Okta, PingFederate, other out-of-the-box or custom applications that support OpenID Connect.
3. Enterprises can now choose to disable the default log-in fields (Email ID and Password fields shown by Seclore) and only show the third-party authentication options such as Google, Microsoft, or any other supported authentication provider.
4. Enterprises can now enable user authentication in Seclore FIM with only email-based one-time passwords (OTP).
1. This feature can be enabled by System Administrators in the 'Repository Details' section in the 'Repositories' tab.
2. Once it's enabled, new users wouldn't get an option set a password. They'll receive an OTP on email every time they try to log in.
5. Activities performed by enterprise applications will be logged in the Policy Server with the enterprise application's name.
1. During content scanning, enterprise applications may protect, unprotect, or share files. Such activities will now be logged in the Policy Server with the enterprise application's name, unlike earlier, when it was logged with the file owner's name.
2. Only System Administrators will be able to see the logs of activities performed by enterprise applications.
3. The file access summary sent daily to file owners won't contain the activities performed by enterprise applications.
6. Made changes to the buffer file for desktop applications.
1. In some cases, users see the Seclore's buffer file when they open a protected file on their desktop. The buffer file contains the enterprise's logo and a customized URL of a webpage that helps users with ways to open the protected file.
2. To enable faster deployment of the Policy Server for new Seclore customers, we've removed the enterprise logo from the buffer file and added a generic URL of a file opening app that will help users open the protected file.
3. Buffer files for existing Seclore customers will remain unaffected.
7. Fixed the issue where copies of edited files wouldn't get sent to the user.
1. Before the fix: Users wouldn't receive their copies of files edited online. This issue was observed in Seclore 3.16.1.0 and later versions.
2. After the fix: This issue is now resolved.
8. Fixed the issue where an email notification wouldn't get sent to users after they reset their Seclore password.
9. Fixed the issue where Seclore-protected files wouldn't open in Seclore Online in certain rare scenarios.
1. Before the fix: Seclore-protected files wouldn't open in Seclore Online when opened from SharePoint On-Premises 2019. This issue was observed in Policy Server 3.10.3.0 with Seclore 3.16.1.0.
2. After the fix: This issue is now resolved.
10. Fixed the issue where an email notification wouldn't get sent to users after they reset their Seclore password.
11. Fixed the issue where edits made to a protected file online wouldn't get saved back in certain scenarios.
1. Before the fix: Edits made to a protected file 15 minutes after it's opened online wouldn't get saved back. This issue was observed in Policy Server 3.10.1.0 with Seclore 3.16.1.0 and later versions.
2. After the fix: This issue is now resolved.

Seclore for Mac 3.5.0.0

1. Made changes to the buffer file for desktop applications.
1. In some cases, users see the Seclore's buffer file when they open a protected file on their desktop. The buffer file contains the enterprise's logo and a customized URL of a webpage that helps users with ways to open the protected file.
2. To enable faster deployment of the Policy Server for new Seclore customers, we've removed the enterprise logo from the buffer file and added a generic URL of a file opening app that will help users open the protected file.
3. Buffer files for existing Seclore customers will remain unaffected.
2. Fixed the issue where Seclore-protected files wouldn't open on Mac devices with M1 processors.
1. Before the fix: Seclore-protected files wouldn't open on Mac devices with M1 processors.
2. After the fix:
3. We've introduced the Seclore Document Viewer that lets you open Seclore files in read-only mode, print, and search for content in such files.
4. You can double-click on an html-wrapped protected file to open it in the Document Viewer. You can also select 'Seclore Lite' in the 'right-click' > 'Open with' menu to open the file in the Document Viewer.
5. To open a protected file that isn't html-wrapped, use the 'right-click' > 'Open with' menu and select 'Seclore Document Viewer'.

Seclore for Windows 3.13.1.0

1. Made changes to the buffer file for desktop applications.
1. In some cases, users see the Seclore's buffer file when they open a protected file on their desktop. The buffer file contains the enterprise's logo and a customized URL of a webpage that helps users with ways to open the protected file.
2. To enable faster deployment of the Policy Server for new Seclore customers, we've removed the enterprise logo from the buffer file and added a generic URL of a file opening app that will help users open the protected file.
3. Buffer files for existing Seclore customers will remain unaffected.
2. Fixed the issue where the option to insert an excel spreadsheet in a protected Word file was disabled.
1. Before the fix: The option to insert an excel spreadsheet with Insert > Table > Excel Spreadsheet was disabled in protected Word files.
2. After the fix: The option is now enabled with Seclore for Windows 3.13.1.0 Admin and Adminless versions.

Seclore for O365 3.5.0.0

1. The Seclore tab in Microsoft Teams will now be automatically available in all your Teams channels.

Server SDK - Java 4.4.7.0

1. Made changes to the native buffer file.
1. In some cases, users see the Seclore's buffer file when they open a protected file on their desktop. The buffer file contains the enterprise's logo and a customized URL of a webpage that helps users with ways to open the protected file.
2. To enable faster deployment of the Policy Server for new Seclore customers, we've removed the enterprise logo from the buffer file and added a generic URL of a file opening app that will help users open the protected file.
3. Buffer files for existing Seclore customers will remain unaffected.

Policy Server 3.10.4.0

1. Users would now see an enhanced buffer page while opening a Seclore-protected file from a Microsoft Teams channel on Android devices. The buffer page guides users on ways to open the files.
2. Fixed the issue where options to sign in with Google and Microsoft wouldn't work in the Seclore add-in pane in Outlook on the web.
1. Before the fix: An error would show up when users tried to sign in with Google or Microsoft. This issue was observed in Policy Server 3.10.1.0 and later.
2. After the fix: Login options will now appear in a separate pop-up when users click on 'Sign in' in the Seclore add-in pane. Options to sign in with Google and Microsoft will work in the pop-up.
3. Introducing Microsoft Azure single sign-on (SSO) for Seclore add-in in Outlook on the web.
1. Users can now click on 'Sign in' in the Seclore add-in pane and log in using their Microsoft Azure credentials.
2. Thus, users who are already logged in with their Microsoft credentials would be automatically logged in to the Seclore add-in without entering their credentials

Seclore for Mac 3.4.12.0

1. Fixed the issue where the 'Seclore It' button wouldn't appear in Outlook in a certain scenario.
1. Before the fix: The 'Seclore It' button wouldn't appear in Outlook 16.46 due to an architectural change done by Microsoft.
2. After the fix: This issue is now resolved.

Seclore for O365 3.4.0.0

1. Extending automatic protection in SharePoint Online to files already existing in the Document Library.
2. Introducing support for opening Seclore-protected files from Microsoft Teams with the new Seclore tab.
1. This feature is available in Microsoft Teams desktop app and Teams on the web.
2. Here's what the new Seclore tab in a Microsoft Teams channel offers:
3. The 'S' button lets users open, edit, and save Seclore-protected files in the Seclore Online editor if they have the right permissions.
4. Windows 10 users can click on the file name and open, edit, and save the file in the native application.
5. Mac users and other Windows OS users can click on the file name and open, edit, and save the file in the Seclore Online editor.
3. Enhanced Seclore's buffer page with guided instructions on ways to open Seclore-protected files from Microsoft Teams on Android devices.
4. Fixed the issue where files wouldn't get automatically protected in SharePoint Online in certain rare scenarios.
1. Before the fix:
2. When two unprotected files are uploaded to two Document Libraries (DLs) simultaneously, both files get protected as usual. However, when an unprotected file is uploaded to one of the DLs after the simultaneous upload, the file doesn't get protected.
3. After Seclore IRM is enabled in a Document Library, unprotected files uploaded to that library after several days of inactivity wouldn't get protected.
4. After the fix: These issues are now resolved.
5. Apache Tomcat upgraded to 9.0.38.
6. Added support for SQL Server 2019.
7. Upgraded Microsoft Graph SDK to version 2.7.1.

Seclore for Windows 3.13.0.0

1. Introducing support for opening Seclore's HTML-wrapped protected files directly from Microsoft Teams in native applications.
1. This feature is available in Microsoft Teams desktop app and Teams on the web.
2. Windows 10 users can click on the file name in the Seclore tab in Teams, and open, edit, and save the file in the native application. The changes will be synced back to Teams.
2. Users would now see a notification requesting them to sign in to Seclore after they install Seclore for Windows (Admin and Adminless versions).
1. Users who are not logged into Seclore, will be prompted to sign in every time they log into their system.
2. User would see this notification periodically if they've ignored earlier notifications.
3. Users can also use the newly introduced 'Sign in' option when they right-click the Seclore icon in the Windows system tray.
4. The sign-in prompt after installation and the 'Sign in' option in the system tray is available in Windows 7, 8.1, and 10.
5. The periodic 'Sign in' notifications are available in Windows 10 only.
3. Fixed the issue where Seclore-protected files with ampersand in the file name wouldn't open when the user's machine is not connected to the internet.
4. In Seclore for Windows, the 'View File Details' and 'View Activity Logs' options are removed from the Property Sheet of Seclore-protected files. These actions can be performed using the right-click menu.
5. Fixed the issue where HTML-wrapped protected Word and Excel files wouldn't open when opened from the recent files list using File>Open>Recent.
6. Fixed the issue where user authentication doesn't work with some firewalls.

Seclore Online 3.3.0.0

1. Introducing Cloud File Access on Desktop.
1. Added support in Seclore Online to open and edit Seclore-protected files in native applications through Seclore for Windows and Seclore for Mac apps.
2. Added support to save edited files back to the source.
2. Enhanced the error message displayed when users try to open an unprotected file using the 'Open with Seclore' option in SharePoint Online and OneDrive. The message now clearly conveys that unprotected files shouldn't be opened using the aforementioned option.
3. Users would now see Seclore's buffer page while opening a Seclore-protected file from a Microsoft Teams channel on Android devices. The buffer page guides users on ways to open the files.
4. Fixed the issue where protected files with .pptx extension wouldn't open in a certain scenario.
1. Before the fix: Protected files with .pptx extension wouldn't open in the native application once the file is opened from Microsoft Teams in Seclore Online, and thereafter, edited, saved, and closed.
2. After the fix: This issue is now resolved.
5. Fixed the issue where the 'Request Access' feature wouldn't work in a certain scenario.
1. Before the fix: An error would get displayed when a new user opened a Seclore-protected html-wrapped file.
2. After the fix: New users would see the option to request access from the owner after completing authentication.
6. Fixed the issue where Seclore-protected files wouldn't open in Seclore Online if the file name contains curly brackets {}.

Server SDK - Java 4.4.6.0

1. Fixed the issue where IBM JDK wouldn't work with Seclore Server SDK - Java.

Seclore for Android 3.5.0000.0

1. Seclore Lite for Android is now Seclore for Android. The application now appears as 'Seclore' in the Google Play Store.

Seclore for Android-BlackBerry 3.5.0000.1

1. Seclore Lite for BlackBerry is now Seclore for BlackBerry.

Seclore for Android-Intune 3.5.0000.4

1. Seclore Lite for Intune is now Seclore for Intune.

Seclore for iOS 3.8.0000

1. Minor changes made to one of the in-app alerts.

Seclore for iOS-BlackBerry 3.8.0001

1. Minor changes made to one of the in-app alerts.

Seclore for iOS-Intune 3.8.0004

1. Minor changes made to one of the in-app alerts.

Policy Server 3.10.3.0

1. Updated the App Integration section in the System Administrator and Global Security Administrator portals with the latest product functionalities.
1. Added 'Email Decrypter' and 'File Decrypter' in the list of enterprise applications to choose from.
2. Updated the tooltip and placeholder text for Online Viewer and Online Editor configuration in the System Administrator portal.
3. Updated Apache Tomcat to version 9.0.41.

Seclore for Mac 3.4.11.0

1. Fixed the issue where Seclore-protected files wouldn't open in Microsoft Office in certain rare scenarios.
1. Before the fix:
2. When an unprotected PowerPoint file is opened after opening and closing a protected PowerPoint file from a OneDrive sync folder, watermark would get displayed on the unprotected file.
3. When a protected PowerPoint file is opened (via Open in app) from OneDrive/SharePoint Online, watermark would get displayed on the buffer file. This would happen after a protected file is opened and closed from any location.
4. After the fix: These issues are now resolved.
2. Fixed the issue where Seclore text editor would shut down unexpectedly in certain rare scenarios.
1. Before the fix: Seclore text editor would shut down unexpectedly when a protected .txt file is opened by a user with no permissions and the 'Request Access' feature is disabled in the Policy Server.
2. After the fix: The user would see an error telling them to contact the owner of the file for permissions.

Seclore for Windows 3.12.4.0

1. Fixed the issue where older versions of unprotected PowerPoint files wouldn't get saved (via Save As) when opened from SharePoint Online.
2. Fixed the issue where the complete file name wouldn't appear in the UI when the file path is more than 260 characters.

Email Auto Protector 3.3.2.0

1. With this version, Email auto protector is supported on CentOS 7.8 and Red Hat Enterprise Linux 7.8 and 8.3 only.
2. Upgraded Apache Tomcat to version 9.0.41.

Server SDK - Java 4.4.4.0

1. Fixed the issue where Seclore-protected files wouldn't get HTML-wrapped with Server SDK - Java 4.4.3.0.

Seclore for Android 3.5.0

1. Added support for Seclore-protected files to open from third party applications such as Microsoft Teams, using the 'Share' option.
2. Added support for PDF files to open in Seclore Online.

Seclore for Intune 3.5.0004

1. Added support for Seclore-protected files to open from third party applications such as Microsoft Teams, using the 'Share' option.
2. Added support for Microsoft Intune wrapping in Android 10.
3. Added support for PDF files to open in Seclore Online.

Policy Server 3.10.2.0

1. Added support for Files, Activities, and Policies tabs for the Global Security Administrator (GSA) role.
1. GSAs (Security Administrators with access to all repositories) can now manage files, activities, and policies for the entire enterprise.
2. The Files tab allows GSA to search for protected files, view permissions, monitor authorized/unauthorized activities, transfer ownership of files, revoke access, and replicate or replace users on a file.
3. The Activities tab allows GSAs to search for all activities on protected files.
4. The Policies tab allows GSAs to manage and create policies for end users.
2. Furthermore, we've enhanced the UI for GSAs.
1. The 'Files', 'Activities', and 'Policies' tabs will be available on the home page.
2. The 'App Integration' and 'Hot Folder Cabinets' tabs will be available under the 'Configurations' tab.
3. The 'Audit Log' and 'Licenses' tabs will be available under the newly added 'More' tab.
4. With these enhancements, the UI for GSAs now looks similar to the UI for Security Administrators.
3. Updated the System Administrator and Security Administrator homepage and Audit Logs page with the latest product functionalities.
4. Added support for OpenDJ 4.4.7 for Policy Server on Windows.
5. Updated System Administrator configurations to support the default Receiver-only mode.
6. Enhanced the user search functionality.
1. Now, users can be searched by entering their complete first name and the first letter of their middle name or last name.
2. The search would also work with the first three letters of the first name followed by the first three letter of the middle name or last name.
7. Removed logo from online help manuals (help center for administrators).

Seclore for Windows 3.12.3.0

1. Introducing the new and improved Receiver-only mode for Seclore for Windows (adminless).
1. Seclore now offers an adminless agent with the Receiver-only mode turned on by default.
2. The Receiver-only mode allows users to access Seclore-protected emails and attachments, share such emails and attachments with other users, and track and revoke access.
3. This mode also allows users to view the permissions widget while accessing Seclore-protected files in native applications.
4. It offers only recipient features and not protection features.
2. Fixed the issue where users were unable to send inline image attachments with Seclore-protected emails in certain rare scenarios.
3. Fixed the issue where 0utlook would shut down unexpectedly in certain rare scenarios.
1. Before the fix: When composing an email in Outlook in RTF (without clicking on 'Seclore It') with an unwrapped protected attachment and an inline image attachment, Outlook would shut down unexpectedly or the email would get sent with an error in the header in some cases.
2. After the fix: This issue is now resolved.
4. Fixed the issue where the web single sign-on (Web SSO) feature wouldn't work in certain scenarios.
1. Before the fix: While accessing the Policy Server URL after 15 minutes of inactivity (that is, no activity with protected files/emails), the Web SSO feature wouldn't work and users would be asked to log in again.
2. After the fix: Web SSO would work even after 15 minutes of inactivity.
3. This mode also allows users to view the permissions widget while accessing Seclore-protected files in native applications.
5. Fixed the issue where URLs wouldn't open from a custom application (Spectrum) when Seclore for Windows is installed.

Seclore for Mac 3.4.10.0

1. Fixed the issue where watermark and permissions widget would show up in unprotected Office files in certain rare scenarios.
2. Fixed the issue where Seclore-protected files wouldn't open on Microsoft Office in certain scenarios.
1. Before the fix: Protected files wouldn't open on Microsoft Office (version 16.44) due to architectural changes introduced by Microsoft.
2. After the fix: This issue is fixed for all Mac computers running on Intel processors.

Seclore for Mac 3.4.9.0

1. Fixed the issue where protected email files with .smail extension wouldn't open when downloaded.
1. Before the fix: A protected email body is sent to a recipient as a secure email file with .smail extension. The recipient would see an error when they download and open the file.
2. After the fix: This issue is now resolved.
2. Fixed the issue where protected files wouldn't open in native applications in certain rare scenarios.
1. Before the fix: When users try to open a protected file (that is not HTML-wrapped) from OneDrive/SharePoint Online using the Open > Open in app option, the file wouldn't open in the native application. A buffer page with the option to open the file in the browser would appear.
2. Before the fix: Furthermore, opening the file would trigger an 'Auto Save' event, thereby replacing the content in the protected file with the content in the buffer page.
3. After the fix: The protected content will not be replaced due to the file getting saved automatically.
3. Fixed the issue where Outlook profile manager would shut down unexpectedly.
1. Before the fix: Outlook profile manager would shut down unexpectedly when opened from the Applications folder. This issue was observed in Mojave, Catalina, and Big Sur operating systems.
2. After the fix: This issue is now resolved with the latest version of Seclore for Mac (3.16.2.0).

Policy Server 3.10.1.0

1. Fixed the issue where HTML-wrapped files wouldn't open using native applications in certain rare scenarios.
1. Before the fix: HTML-wrapped files in shared folders on a network wouldn't open when dragged and dropped on Chrome with the intent of opening them in the native application using the 'Open Seclore' button.
2. After the fix: This issue is now resolved.
2. Changes to make Seclore Online a completely independent agent of the Policy Server for better scalability and performance.
1. Seclore Online is now an independent offering that opens Seclore-protected files online without processing them in the Policy Server.
2. Consequently, configuration fields for the Lite Online Viewer and Editor have been replaced with fields for Seclore Online in the Policy Sever.
3. Seclore Policy Server upgraded to Apache Tomcat 9.0.38.
4. Seclore's Right Click > Classify feature is now configurable.
1. Earlier, 'Right Click > Classify' was available as a default feature for all enterprises.
2. Now, this feature is disabled by default for all enterprises with Seclore for Windows 3.12.2.0; however, it can be enabled if enterprises need it.
3. To enable this feature, it will need to be explicitly enabled during the installation or upgrade process.
5. Fixed the issue where downloading the Seclore agent from Seclore Online Editor would show an error in certain rare scenarios.
1. Before the fix: Clicking on the 'Download app' button in the Seclore Online Editor showed an error. This impacts only older HTML-wrapped files.
2. After the fix: This issue is now resolved.
6. Language Pack upgrade for Spanish, French and Russian.

Seclore Decrypter for Email 1.1.0.0

1. Enhanced the Seclore Decrypter for Email to simplify the email routing workflow and rules to be configured on email systems.

Seclore for 0365 3.3.0.0

1. Added compatibility for Microsoft Teams with Seclore Online.
1. Now, Seclore for O365 ensures seamless access of Seclore-protected files in Seclore Online directly from Microsoft Teams.
2. It lets you open Seclore-protected files from Microsoft Teams in Seclore Online, edit, and save it back.
3. This feature is supported in the Windows and Web application of Microsoft Teams.

Seclore for Windows 3.12.2.0

1. Seclore's Right Click > Classify feature is now configurable.
1. Earlier, 'Right Click > Classify' was available as a default feature for all enterprises.
2. Now, this feature is disabled by default to allow enterprises to work seamlessly with third party classification solutions; however, it can be enabled if enterprises need it.
3. To enable this feature, it will need to be explicitly enabled during the installation or upgrade process.
2. Fixed the issue where protected files wouldn't open in certain rare scenarios.
1. Before the fix: Protected files wouldn't open from a location where the file path along with the file name would exceed 260 characters.
2. After the fix: These issues are now resolved.

Seclore Online 3.2.0.0

1. Seclore Online now works completely independent of the Policy Server.
1. Earlier, Seclore Online used the Policy Server to open Seclore-protected files in the secure browser-based editor or viewer. Now, Seclore Online can do it independently.
2. Furthermore, Seclore Online now supports opening OpenOffice file formats (ODT, ODS, and ODP) in 'view only' mode.
3. This requires Policy Server version 3.16.1.0 or higher.
2. Seclore Online no longer supports SSL 3.0, TLS 1.0, and TLS 1.1.
3. Apache Tomcat for Seclore Online upgraded to 9.0.38.

Seclore Lite for Android 1.3.0.0

1. Minor changes made to be compatible in the new Seclore Online 3.0.
2. With this release, we have discontinued support for Android 7.0 (Nougat) and lower versions.

Seclore Lite for BlackBerry in Android 3.7.001

1. Minor changes made to be compatible in the new Seclore Online 3.0.
2. Added support for BlackBerry SDK 8.1.

Seclore Lite for iOS 3.7.0000

1. Minor changes made to be compatible in the new Seclore Online 3.0.

Seclore Lite for BlackBerry in iOS 3.7.001

1. Minor changes made to be compatible in the new Seclore Online 3.0.
2. Added support for BlackBerry SDK 8.1.

Seclore for Windows 3.12.1.0

1. Introducing browser-based login for Seclore for Windows.
1. Now, you can login to the Seclore agent on Windows with your default browser.
2. While logging in you'll be directed to an authentication page on your browser.
3. All other login features remain the same.
2. Fixed the issue where protected PDF files wouldn't open in certain rare scenarios.
1. Before the fix: Protected PDF files wouldn't open with Adobe Acrobat Pro when McAfee Endpoint Security is installed.
2. After the fix: This issue is now resolved.
3. Fixed the issue where a Seclore message shows the file path instead of the file name in certain rare scenarios.
1. Before the fix: Upon trying to edit and close a Seclore-protected file with only 'Read' permission, Seclore shows a message telling the user that they do not have permission to edit the document. This message would show the file path instead of the file name.
2. After the fix: This issue is now resolved.
4. Fixed the usability issue where the Policy Server name would reflect incorrectly in the 'About' dialog box of the agent.
1. Before the fix: The Policy Server URL link would reflect the name of the Policy Server in the 'About' dialog box which could not be changed.
2. After the fix: Now the URL would simply reflect the term 'Policy Server'.

Policy Server 3.10.0.0

1. Introducing integration with Azure AD for end-to-end identity federation from the Microsoft Cloud.
1. Enterprises can now use Azure AD for both authentication and authorization services in Seclore.
2. Seclore Policy Server directly connects to the Microsoft Azure cloud service, and no longer needs to connect to the on-premise AD.
3. All Seclore features like user provisioning, assigning user permissions, assigning user licenses, etc. are now available directly from Azure AD.
4. This feature is available for internal enterprise users of the organization.
2. Enhanced authentication with Microsoft Azure AD for external users.
1. Earlier, only internal users in the organization's Azure AD could authenticate in Seclore using the 'Sign in with Microsoft' option.
2. Now, all external users can authenticate with their personal, work, or school account.
3. Fixed the issue where HTML-wrapped files did not open using Seclore Online in certain rare scenarios.
1. Before the fix: HTML-wrapped files would not open in Seclore Online due to certain policy server configuration in the System Admin portal.
2. After the fix: This issue is now resolved.
4. Seclore Azure tool to be no longer available in the Policy Server package.
1. Before the fix: The Seclore Azure tool would display an error when opened.
2. After the fix: The tool is deprecated, and manual steps will be provided to register the Seclore Azure application.

Seclore for Mac 3.4.8.0

1. Fixed the issue where Outlook shuts down unexpectedly after opening when upgraded to Big Sur Public Beta 6 (20A5395g).
1. Before the fix: Outlook would crash after being opened on macOS Big Sur Public Beta 6 Release Version: 20A5395g released on October 16,2020.
2. After the fix: This issue is now resolved.

Repository Adaptor Migration Tool 1.0.0.0

1. Introducing the Repository Adaptor Migration tool-it supports your migration from Local (On-Premise) AD Repository Adaptor to Azure AD Repository Adaptor in the Seclore Policy Server.
1. This tool updates the user ID references in the Policy Server.
2. Before running the tool, the Policy Server stores Local (On-Premise) AD references of user ID.
3. After running the tool, the Policy Server stores the Azure AD references of the same user ID.
4. The tool contains a pre-migration checklist that specifies the impact of the migration from Local AD Repository Adaptor to Azure AD Repository Adaptor.

Seclore for Windows 3.12.0.0

1. Enhanced the user experience of the error/success message screens for desktop protection.
1. Completely re-designed the error/success message screens that are displayed when the user invokes Right-click > Seclore It for protecting files.
2. Messages are now wrapped with a more intuitive layout to enhance usability.
2. Added support to retain classification metadata information in Seclore-protected files when they are edited and saved using the Seclore agent.
3. Fixed the issue where Outlook was shutting down unexpectedly in certain rare scenarios.
1. Before the fix: Outlook would shut down randomly, when composing an email in RTF (Rich Text Format) format and attaching another Outlook email (or any Outlook item) as an attachment.
2. After the fix: Protecting an email in RTF format with any Outlook item as an attachment, now works as expected.
4. Fixed the issue where the Word app shuts down unexpectedly in certain rare scenarios.
1. Before the fix: Word would shut down unexpectedly when a user selects some text in a protected Word document and then clicks elsewhere while another unprotected document was open in the background. This issue occurs only in Office 365 version 2007 (Build 13029.20308) or later, i.e., August 2020 release.
2. After the fix: This issue is now resolved.
5. Fixed the issue which occurs in Seclore-protected Excel files in certain rare scenarios.
1. Before the fix: When opening a Seclore-protected Excel file that has reference links to any other file, it works the first time, but doesn't work on the 2nd attempt. This happens with standalone Office 2013 or 2019 versions only, but not with O365 versions.
2. After the fix: This issue is now resolved.

Policy Server 3.9.3.0

1. Updated System Admin configuration validations on the System Admin homepage with the latest product functionalities.
2. Fixed the issue of "Sign in with Microsoft" not working when proxy is enabled.
1. Before the fix: An error page is displayed while signing in with Microsoft when proxy is enabled.
2. After the fix: "Sign in with Microsoft" is successful, and the error is no longer displayed even when proxy is enabled.
3. Fixed the issue of inconsistent signatures in email notifications.
4. Fixed the error preventing users from opening protected files from SharePoint Server (On-Premise) using Seclore Online.
1. Before the fix: Users were encountering an unexpected error while opening protected files from SharePoint Server using Seclore Online.
2. After the fix: Users can now successfully open the document from SharePoint On-Premise using Seclore Online.
5. Added support to retain classification metadata information in HTML buffer file when protected documents are edited and saved with Seclore Online.

Seclore for Mac 3.4.7.0

1. Enhanced the user experience of the error/success message screens for desktop protection.
1. Completely re-designed the error/success message screens that are displayed when the user invokes Right-click Seclore It for protecting files.
2. Messages are now wrapped with a more intuitive layout to enhance usability.
2. Added support to retain classification metadata information in Seclore-protected files when they are edited and saved using the Seclore agent.
3. Added support for HTML wrapping of files protected using the endpoint SDK.

Data Protection Portal 3.1.1.0

1. Added support for Microsoft SQL Server 2012, 2014, 2016 and 2017 Database Server.
2. Added support for Tomcat 9.0.31.

Seclore Decrypter for Email 1.0.0.0

1. Launched the new Seclore Decrypter for Email that provides decryption as a service for Seclore protected emails to email discovery solutions like DLPs, CASBs, Secure Email Gateways, content discovery tools etc.
1. This new universal email decrypter can be integrated with any on-premise or cloud-based email service to decrypt Seclore protected emails for content inspection.
2. It can decrypt emails that are sent outside the enterprise domain.
3. It ensures email is decrypted only for the content inspection solution to inspect sensitive content and delivers the same original protected email to all recipients.

Seclore for Boldon James 3.2.0.0

1. Added support to store and retain classification metadata in documents protected using classification-driven protection.
1. Before the fix: Content discovery solutions like DLPs were unable to read classification metadata for documents protected using classification-driven protection with Boldon James.
2. After the fix: Now, DLP or any other discovery solution can read classification metadata for documents protected using classification-driven protection.
2. Introducing support for HTML wrapping for Advance protection.
1. Before this change, documents classified through Boldon James using File classifier or Office classifier and protected through Seclore did not get HTML wrapped.
2. Now, documents once classified and protected will get HTML wrapped automatically.
3. Requires
1. Policy Server 3.9.3.0 or higher
2. Seclore Desktop Client 3.12.0.0 or higher
3. Seclore for Mac 3.4.7.0 or higher

Server SDK - Java 4.4.3.0

1. Added support to retain classification metadata within HTML buffer files for discovery solutions like DLPs to read.
2. Added support for Mac Operating System.
1. Enterprises and integrating partners can now build integrations using Seclore Server SDK-Java on Mac OS.

Desktop Client 3.11.2.0

1. Fixed the usability issue where the message box that pops up for save intimation while closing MS PowerPoint after editing, displays complete file path as name.
1. Before the fix: When the user closed a MS PowerPoint file, the save intimation popup that appears displays the location of the file rather than the file name.
2. After the fix: Now When the user closes a MS PowerPoint file, the save intimation popup that appears displays the file name.
2. Fixed the authentication issue that arises due to difference in time between the client and server machine.
1. Before the fix: If there was a time difference between client and server machines, user authentication would fail intermittently.
2. After the fix: Now if there is as time difference between client and server machines, user authentication will not fail.

Seclore for macOS 3.4.6.0

1. Fixed the OneDrive Sync Agent issue which prevents the user from saving an unprotected Office file.
1. Before the fix: When an unprotected Office file is opened from OneDrive online or a sync agent location, edited, and saved, an "Upload failed" error used to show up. Consequently, the edits were not saved.
2. After the fix: Such files are now saved without any error and the edits are uploaded to the online repository.

Hot Folder Server 3.2.3.0

1. Removed unused Add and Edit button displayed under credential section of Hot Folder Enterprise Manager.
1. Earlier, when Hot Folder Enterprise Manager was launched, Add and Edit buttons were always in disabled state under the credentials section.
2. Now, these unused buttons have been removed.

Desktop Client 3.11.1.0

1. Fixed the issue where protected files opened from folders configured with OneDrive Sync Agent do not open with MS Office 2016.
1. Before the fix: MS Office files protected without html wrapping, when opened from the local One Drive Sync folder fail to open in Standalone Office 2016.
2. The issue is observed only for natively protected files and not HTML wrapped files.
3. After the fix: The protected file should open without any issue.

Desktop Client 3.11.0.0

1. Introducing the In App-protection for Microsoft Office apps.
1. Seclore presents the "Seclore It" button in all Microsoft Office apps for single-click protection from within the open file.
2. User can enable the button while editing an unprotected document.
3. Once the user closes the unprotected file with the Seclore It button enabled, the file gets protected and the user is prompted to change the file permissions and add recipients.
4. File permissions can also be added to the protected file while emailing, using Smart Sharing.
2. Extending Seclore's email protection capability to third-party tools.
1. Third-party tools can now integrate with Seclore's email protection interface in Outlook allowing them to leverage end-to-end security for emails and attachments in collaboration with their product features.
3. Introducing HTML preserve feature for files protected using Universal Protection.
1. Now files protected using Universal Protection will open directly in the edit mode when opened using the native app.
2. Users can edit and save changes directly in such files without the need for unprotecting and opening them in the native app for editing.
4. Introducing Share and Protect + Share feature in the Endpoint SDK along with notification module.
5. Incorporated the new HTML buffer file, that displays user instructions for file open in the Raw HTML content. This is useful in scenarios where the Seclore Protected file is opened in a 3rd party viewer that cannot render HTML content.
6. Fixed the issue where the PS login page was displayed instead of a prompt asking the user to allow login using the credentials logged into the Desktop Client.
1. Before the fix: When the user was already logged into the Desktop Client and opens the PS URL in the chrome browser, a prompt was displayed asking the user to allow login using SSO of the Desktop Client.
2. Instead the PS Login page was displayed, and the user had to login again using his credentials.
3. After the fix: Now the user will be directed to the SSO prompt allowing to login directly using the Desktop Client login.
4. The Policy Server URL must be the same as the one logged in using the Desktop Client.

Seclore for Mac 3.4.5.0

1. Incorporated the new HTML buffer file, that displays user instructions for file open in the Raw HTML content. This is useful in scenarios where the Seclore protected file is opened in a 3rd party viewer that cannot render HTML content.
2. Introducing editing and saving of HTML wrapped Seclore protected PowerPoint files.
1. Now, when you open an HTML wrapped protected PowerPoint file by double-clicking on it, it will open in the Microsoft PowerPoint.
2. After editing in Microsoft PowerPoint if you click Save, the content is updated in the HTML wrapped file itself.
3. When you close the file, the HTML wrapping is preserved.
4. The closed HTML wrapped file will be the latest version.
5. If you close an HTML wrapped protected file opened in Microsoft PowerPoint after editing, the Save dialog box prompts you to save the file before closing the application.
3. Fixed the issue where an error was displayed on saving unwrapped protected PowerPoint files after editing.
4. Fixed the issue where while opening protected word and excel files, an error was displayed if Seclore login took more than 20 to 30 seconds.

Policy Server 3.9.2.0

1. Introducing Security Admin role in Policy Server.
1. This new role allows administrators to manage key security features like Enterprise Application integrations, Hot Folder Cabinets, Classification labels, rules in Email Auto-Protector etc.
2. Admins configured to manage all enterprise user repositories would be able to manage these key security features
3. All other admins managing a specific organizational unit will continue security policies for thier assigned OU
2. Incorporated the new HTML buffer file, that displays user instructions for file open in the raw HTML content. This is useful in scenarios where the Seclore Protected file is opened in a 3rd party viewer that cannot render HTML content.
3. Fixed the issue where a protected file opened even after the user logged out of the client instead of prompting the user to log in.
4. Enhanced the speed of opening and protected files.

Hot Folder Server 3.2.2.0

1. Introducing changes in Hot Folder Server installation.
1. Earlier, while installing Hot Folder Server, the installer checked if Seclore Desktop Client was installed in the system or not.
2. If Seclore Desktop Client was installed, the Hot Folder Server installation was aborted.
3. Now, this check is removed. The Hot Folder Server can be installed even if Desktop Client already is installed in a system.

Seclore Server SDK Java 4.4.2.0

1. Updated HTML buffer file to display user instructions in raw HTML content. This is useful in scenarios where Seclore Protected file is opened in a 3rd party application that cannot render HTML content.

Seclore O365 Service - 3.2.1

1. Incorporated the new HTML buffer file, that displays user instructions for file open in the Raw HTML content. This is useful in scenarios where the Seclore Protected file is opened in a 3rd party viewer that cannot render HTML content.
2. Fixed an intermittent issue where changes made to large protected files (>8-9 MB), in Seclore Online were not saved back to SharePoint Online through the Save Back Flow.
1. Before the fix: In some cases, when a protected file (> 8 MB) was edited on SharePoint and saved back, the changes were not updated in the file.
2. After the fix: The changes will be saved back on SharePoint even for files with sizes 8 MB or above.
3. Introduced multithreading in file protection flow. With this, multiple files will be processed together for protection resulting in improved multi-file protection time.
4. Updated the connector to use a different API to determine if the SharePoint File is locked for editing. The new API provides more accurate results and helps Seclore connector to get hold of the file earlier to protect it after upload.
5. Changes to support multitenancy of Seclore online.
1. Currently, there is one to one mapping between policy server and Seclore online component.
2. With introduction of multitenancy in Seclore online (part of roadmap), single Seclore online would be able to support multiple policy servers.
6. Fixed the issue where, in some cases, the first file uploaded after the Document Library was Seclore IRM enabled, was not getting protected.
1. Before the fix: In some instances, the first file upload after IRM enabling the document library was not getting protected.
2. After the fix: The first file that is uploaded will now be protected in all the cases.
7. Updated support for Database to be in sync with other components.
1. Added support for Oracle 18c, Oracle 19c and SQL 2017
2. Deprecated support for Oracle 9i, Oracle 10g, Oracle 11g

Desktop Client 3.10.1.0

1. Introducing OAuth based improved authentication architecture.
2. Enhancements in Endpoint SDK
1. Introducing HTML wrapping with Endpoint SDK for Advanced Protection.
2. Introducing Endpoint SDK in the Adminless Seclore for Windows.

Seclore for Mac 3.4.4.0

1. Introducing OAuth based improved authentication architecture.
2. Fixed the issue where a protected file was incorrectly named after convert to native and unprotect actions on the file.
1. Before the fix: When a protected file was renamed and converted to native format, the resulting file was named incorrectly.
2. Similarly, when a protected file was renamed and unprotected, the unprotected file was named incorrectly.
3. After the fix: The files will be named as expected even after renaming and Convert to Native and Unprotect actions.
3. Fixed the issue where while opening protected files with names in some languages other than English, an error was displayed.
1. Before the fix: When a protected HTML-wrapped file with name in few specific languages other than English is opened, an error was displayed.
2. After the fix: The file will open successfully.
3. After the fix: The files will be named as expected even after renaming and Convert to Native and Unprotect actions.
4. Fixed the issue where error was displayed when an already opened protected file from a network location is opened again.
1. Before the fix: When an already opened protected file from a network location is opened again, an error was displayed.
2. After the fix: The file will open in read-only mode in this case.

Desktop Client 3.10.0.0

1. Introducing a new Adminless agent for Windows
1. The user has an option to download and install either Admin or Adminless mode of the new agent.
2. Now there is no need for an IT admin to intervene while installing and operating the Adminless version for Desktop Client on Windows
3. This client will provide all the capabilities that are available for the agent in the Admin mode.
4. Users can download both the versions of the Desktop Client from the Online Access tab of the Policy Server.
5. The option to download both the modes of Desktop Client will be available in the Policy Server version 3.9.1.0 onwards.
6. Additionally, when you click the Download the Seclore app option in the buffer file for agentless access, you will be prompted to download the Adminless Desktop Client instead of Seclore Lite for Windows.
7. On updating Seclore Lite for Windows version 3.3.5.0, the Desktop Client in the Adminless mode will be installed in the system.
2. Introducing the capability of printing the watermark over large images in protected PDF files.
1. In case of protected PDF files containing large or scanned images, printing the files with the watermark behind the image makes the purpose of the watermark redundant.
2. Seclore has enabled the capability of printing the watermark over the content and images of a protected PDF file, if the PDF file contains large images.
3. This feature is enabled if the image covers more than 50% of the page. This percentage of page size is set by default.
4. The percentage can also be configured as per requirement.
5. If the protected PDF files do not contain large images, the watermark will appear behind the content and smaller images on printing.
6. This feature will be disabled in the Desktop Client, by default.
3. Fixed the issue where watermark was not displayed for decrypted in-line protected email body in Outlook.
1. Before the fix: If the user was logged in to the Desktop Client and had access to a protected email body, the email was displayed in-line in Outlook without the watermark.
2. After the fix: The decrypted in-line email body with the watermark will now be displayed for protected emails.
4. Fixed the issue where the buffer file was not properly displayed when an HTML-wrapped file was opened in the browser for the first time.
1. Before the fix: When an HTML-wrapped file was opened in a browser, the buffer file was not displayed properly.
2. Instead an error message was displayed stating that the client was unable to connect to the Policy Server.
3. After the fix: The buffer file will be displayed successfully.
5. Fixed the issue where in certain cases Outlook stopped functioning when user forwarded or replied to unprotected emails containing inline attachments.
1. Before the fix: When a user opened an unprotected email with inline attachments on a new window (double-click or pop-out) in Outlook and clicked on either Reply/Forward, he was prompted to download the external content before sending.
2. On clicking No, Outlook stopped functioning.
3. This was observed when Desktop Client of version 3.9.0.0 or above was installed in the system.
4. This happens when inline attachments are not downloaded before Reply or Forward action
5. After the fix: Outlook will remain functional and the email will be forwarded, or the reply will be sent successfully.

Seclore for Mac 3.4.3.0

1. Introducing editing and saving of HTML wrapped Seclore-protected files.
1. For files protected using Advanced Protection:
2. Now, when you open an HTML wrapped protected file by double-clicking on it, it will open in the native application.
3. After editing in the native application if you click Save, the content is updated in the HTML wrapped file itself.
4. When you close the file, the HTML wrapping is preserved.
5. The closed HTML wrapped file will be the latest version.
6. If you close an HTML wrapped protected file opened in the native application after editing, the Save dialog box prompts you to save the file before closing the application.
7. This works on all file formats except for Microsoft PowerPoint, PDF, image and text file formats.
8. For such formats, .html wrapped files will open in read-only mode.
9. The user will be able to make changes to the file by saving it locally using "Save As".
10. For files protected using Universal Protection:
11. For files protected using Universal Protection, the HTML wrapped file will open in the native application as well.
12. However, on saving after changes, the Save As dialog box appears.
13. On saving, an unprotected file is saved on your machine.
14. For such formats, .html wrapped files will open in read-only mode.
2. Fixed the rare issue where in certain cases Microsoft Office applications stopped functioning on opening in the presence of Seclore for Mac.
1. Before the fix: When a user opened any Microsoft Office application, it stopped functioning instead of opening successfully.
2. This was observed in certain systems with macOS 10.14 (Mojave).
3. After the fix: The Microsoft Office applications will now open as expected.

Policy Server 3.9.1.0

1. Introducing a new Adminless agent for Windows.
1. The user has an option to download and install either Admin or Adminless mode of the new agent.
2. Now there is no need for an IT admin to intervene while installing and operating the Adminless version for Desktop Client on Windows.
3. This client will provide all the capabilities that are available for the agent in the Admin mode.
4. Users can download both the versions of the Desktop Client from the Online Access tab of the Policy Server.
5. The option to download both the modes of Desktop Client will be available in the Policy Server version 3.9.1.0 onwards.
6. Additionally, when you click the Download the Seclore app option in the buffer file for agentless access, you will be prompted to download the Adminless Desktop Client instead of Seclore Lite for Windows.
7. On updating Seclore Lite for Windows version 3.3.5.0, the Desktop Client in the Adminless mode will be installed in the system.
2. Introducing changes in the Policy Server UI
1. You can now open HTML wrapped files in Seclore Online from the Online Access tab.
2. On the Online Access tab:
3. Download Seclore for Windows (Adminless mode) by clicking on the Seclore for Windows or Install Desktop App link.
4. Download the Seclore for Windows (Admin mode) by clicking the Admin Version link.
5. Download Seclore for Mac by clicking on the Seclore for Mac link (when accessed from macOS).
6. You can now open HTML wrapped files in Seclore Online from the Online Access tab.
7. In the Installer and Patch Management page, the tabs will now be Windows (Admin), Windows and Mac.
8. UI improvements in Enterprise Application Section:
9. Introduced a new Branded Enterprise Application option for 'Seclore for Microsoft 365'.
10. Updated the logos and subtitle text for the existing Branded Enterprise Application option.
3. Added 'Convert to HTML format' flag in the Hot Folder Cabinet UI in Policy Server.
1. The Convert to HTML format flag is added in the HolFolder Cabinet page UI.
2. On the Policy Server UI, this flag displays if conversion to HTML wrapping for standard file formats is enabled or not in Hot Folder Enterprise Manager.
3. If this is enabled, all standard files will be HTML wrapped on protection on placing in Hot Folder of that particular Hot Folder Cabinet.
4. This flag can be only be updated from Hot Folder Server Enterprise Manager client.
5. HTML wrapping needs to be mandatorily enabled in the Policy Server Configuration page for this feature to work.
4. Introducing changes in the User Sign Out flow in the Policy Server.
1. Before this change, a logged in user, on clicking sign out, was redirected to the Sign in page.
2. Now, a logged in user, on clicking Sign out, will be redirected to the newly introduced screen.
3. This screen will inform that the user has successfully signed out from the Seclore Policy Server.
4. It also displays a Sign in again button.
5. On clicking this, the user will be redirected to the Sign in screen where user can sign in again to the Policy Server.
6. The above-mentioned flow is applicable to System Admins as well.
7. In cases of SSO integration, clicking on Sign in again will redirected the user to the SSO solution which the user had used to login earlier.
8. If the user is already authenticated in the SSO system, the user will be logged in automatically on clicking on Sign in again.
5. Removed Screen Capture option from the Select Activity Type filter from the Activities tab of Policy Server.
6. Fixed the issue where the Seclore plugin had stopped working in Outlook Web App.
1. Before the fix: When a user clicked on the Seclore It! option while composing an email from the Outlook Web App, an error was displayed instead of the Seclore panel.
2. Due to this error, user was unable to drag and drop documents and protect them using Seclore on OWA.
3. After the fix: The panel opens as expected and users can successfully add and protected files before sending them using OWA.
4. Fix is applicable to Cloud deployments of Outlook Web Access (OWA).
7. Added the capability of automatically onboarding a new user in Seclore (SIM), at the time of file open through Seclore Online Integration, if the user has permissions on document through Policy Federation, but the user does not yet exist in Seclore (SIM).
8. Fixed the rare issue where the user was asked to login for every activity on the Policy Server if the user logged in using the Microsoft option from the Desktop Client.
1. Before the fix: When a user logged in using the Microsoft option on Desktop Client, and tried to perform different activities, the user was prompted to login before every activity.
2. This was observed in certain cases.
3. After the fix: User can now successfully login using the Microsoft option on the Desktop Client once and perform all the activities without being prompted to login repeatedly.
9. Updated language support for PS messages in Spanish, French and Russian.
10. Updated the Policy Server Installation guide with the latest information.
11. System upgrades.

Seclore for O365 3.2.0.0

1. Introducing Automated Protection and Policy Federation in Seclore for Microsoft 365.
1. Now enable automated protection in your SharePoint Online Document Libraries with the click of a Seclore It' button.
2. Once a Document Library is enabled for Automatic protection, every document uploaded in, moved to or created within the Document Library will be automatically protected
3. Policy Federation will ensure that permissions defined in SharePoint Online get automatically extended to the Seclore-Protected documents even after they are download and accessed or shared.
4. If use's permissions are changed or revoked in SharePoint Online, the same would be reflected on the downloaded or synced copies of the document.
5. This ensures that there is a single source of truth for document security in SharePoint Online.
6. Users can securely share documents with internal and external users, through Automated protection and Policy Federation capabilities, without separately defining Security Policies in the Seclore Policy Server.
7. Requires Policy Server 3.9.1.0 or higher and Seclore Online 3.1.1.0 or higher.

Server SDK - Java 4.4.1.0

1. Fixed the issue where in certain cases an error message was displayed when an HTML wrapped file was opened in a browser.
1. Before the fix: When a HTML wrapped protected file was opened in a browser, an error message was displayed instead of the buffer file due to delay in response from the Policy Server.
2. After the fix: While opening a HTML wrapped protected file in the browser, the buffer file is successfully displayed without any error.

Desktop Client 3.9.4.0

1. Fixed the issue where on clicking F12 key from the keyboard, a protected Word (O365) document was displaying an error instead of getting saved.
1. For a Seclore-protected document, users with Edit permissions on Word documents can save it after editing by using the shortcut F12 key from the keyboard.
2. Before the fix: When a user, with Edit permission, tried to save a protected Word document using the F12 shortcut key, an error was displayed.
3. The error prompted the user to use File >> Save As to save the document instead.
4. After the fix: A protected Word document can now be saved as a new file using the F12 shortcut key.
2. Fixed the rare issue where Microsoft Outlook stopped functioning when an email containing Microsoft AIP protected attachments and inline attachments was selected in the inbox.
1. Before the fix: When a user selected an email containing Microsoft AIP protected documents and inline attachments, Outlook stopped functioning.
2. This also occurred when Outlook is started and there are emails of the above-mentioned nature in the inbox.
3. After the fix: When such emails are selected, Outlook will work as expected.
4. Users can view emails containing Microsoft AIP protected attachments in Outlook.
3. Fixed the issue where the Learn More URL for Universal Protection in the Seclore Email Protector in Outlook redirected the user to a blank page in the Seclore Online help.
4. Fixed the issue where a newly added signature was not saved in a protected PDF file.
1. Before the fix: When a user opened a protected PDF file and added a signature (Fill and Sign option), the signature did not appear on saving the PDF file.
2. signature did not appear even on Save As or closing and opening the PDF file after adding the signature.
3. After the fix: A newly added signature in a protected PDF file gets added and saved successfully on saving the PDF file.

HotFolder Server 3.2.1.0

1. User was unable to open a HTML wrapped file from a Hot Folder that was created in C: drive of a machine.
1. Before the fix: A Hot Folder was configured in the C: drive of a machine and files were protected, and HTML wrapped by placing in it.
2. User was unable to open a HTML wrapped file from the same Hot Folder.
3. This issue was not observed with non-wrapped protected files.
4. After the fix: All files protected using Hot Folders created in any drive of a machine including the C: drive can be opened successfully.
2. When an HTML wrapped file was deleted from a Hot Folder and the original file was placed again in the same Hot Folder, a replace prompt was displayed.
1. Before the fix: An HTML wrapped file was deleted from a Hot Folder.
2. If the original unprotected or protected file was placed in the same Hot Folder again, a replace prompt was displayed.
3. After the fix: When a HTML wrapped file is deleted from a Hot Folder and the original file is placed again in the same Hot Folder, the replace prompt will not be displayed.

Desktop Client 3.9.3.0

1. Introducing editing and saving of HTML wrapped Seclore-protected files.
1. Now, when you open an HTML wrapped protected file by double-clicking on it, it will open in the native application.
2. After editing in the native application if you click Save, the content is updated in the HTML wrapped file itself.
3. When you close the file, the HTML wrapping is preserved.
4. If you close an HTML wrapped protected file opened in the native application after editing, the Save dialog box prompts you to save the file before closing the application.
5. For files protected using Universal Protection, the HTML wrapped file will open in the native application as well.
6. However, on saving after changes, the Save As dialog box appears.
7. On saving, an unprotected file is saved on your machine.
8. This works on all file formats with the exception of image and text file formats.
2. Fixed the issue where incorrect error messages in the local language of the user was displayed on opening a file in certain cases.
1. Before the fix: Incorrect error message for invalid PS certificates while opening a file, was displayed in the local language of the user.
2. After the fix: The correct error message in English will be displayed in the above-mentioned case.
3. Fixed the issue where if a file with read permission was opened from a network location, another file from the network failed to open.
1. Before the fix: The user opened a protected file from a network location with read permission.
2. When the user tried to open another protected file of the same native application from a network location, it failed to open.
3. After the fix: Protected files from network locations open successfully one after the other.
4. Fixed the issue where the Open With window was displayed instead of opening a protected PDF file directly with right-click >> Seclore's Open With Adobe Acrobat Reader DC option.
1. Before the fix: When user opened a protected PDF file using right-click >> Seclore's Open With Adobe Acrobat Reader DC, the Open With window was displayed instead of opening the file directly.
2. This happened when both Adobe Acrobat XI and Adobe Acrobat Reader DC were present in the system.
3. After the fix: The file will directly open in Adobe Acrobat Reader DC.
5. Discontinued support for Adobe Reader X.

Seclore for iOS 3.5.000

1. Introducing support for opening universally protected file on iOS devices.
1. Once you receive a universally protected file on email, click on the protected attachment (HTML-wrapped).
2. You will be prompted to open it with any of the applications in your device. Select Seclore for iOS app.
3. Post authentication, the user will be asked to select a native application that supports the file.
2. Fixed the issue where password protected files did not open on iOS devices.
1. Before the fix: When a protected file, with password protection, was opened in Seclore for iOS, the file did not open.
2. After the fix: A prompt will ask for a password when such files are opened. After the user enters the password the file will open.

Policy Server 3.9.0.0

1. Enhanced the 'Download Unprotected Copy' feature to work for files opened in the read-only mode in Seclore Online Editor or if a read-only file format is opened in the Seclore Online Editor.
1. The user will require Seclore Full control permissions on the file to see this option in the Seclore Online Editor.

HotFolderServer 3.2.0.0

1. Introducing Universal Protection and HTML wrapping of standard file formats in Hot Folders..
1. Earlier, non-standard file formats were protected and given .seclore extension when placed in a Hot Folder.
2. Files protected with .seclore extension could only be opened in Seclore Desktop Client.
3. Now with the support of Universal Protection, non-standard file formats will be HTML wrapped and given the .html extension when placed in a Hot Folder allowing them to be consumed in all Seclore agents.
4. The files previously protected and given .seclore extension will be HTML wrapped and given the .html extension as well.
5. Additionally, there will be a provision to automatically HTML wrap standard file formats placed in Hot Folders.
6. Requires i. Policy Sever version 3.8.2.0 or above. ii. Universal Protection and HTML wrapping feature to be enabled in Policy Server

Desktop Client 3.9.2.0

1. Introducing automatic HTML wrapping when files are protected using the Seclore agent.
1. After this release, when a user protects a file using right-click >> Seclore It!, the file gets protected as well as HTML wrapped automatically.
2. This will remove the additional step of HTML wrapping a file after protecting it.
3. HTML wrapping must be enabled in the Policy Server configuration page.
4. This ensures consistency with files protected using Universal Protection files which are HTML wrapped automatically.
5. If HTML wrapping is disabled, the file will only get protected and HTML wrapping will not be applied to it.
6. In the right-click context menu, the 'Convert to agentless format' option is changed to 'Convert to HTML format'.
7. To convert an HTML wrapped file to the native format, 'Convert to native format' option is added in the right-click context menu.
8. This feature will not be available in the presence of Boldon James classification or Seclore-classification based protection.
2. Introducing Universal Protection for Symantec and Forcepoint Endpoint DLP based protection.
1. Earlier, files with standard formats were discovered by Symantec and Forcepoint DLPs and protected using Seclore.
2. Files with non-standard formats were not protected.
3. After this release, non-standard file formats will be protected using Universal Protection when discovered by Symantec and Forcepoint Endpoint DLPs.
4. These files will be protected with full control to the authorized user and they will be HTML wrapped automatically after protection.
3. Adding GDPR compliance to Seclore.
1. When user logs in on the Policy Server or agents, the 'Terms of Service' and 'Privacy Policies' will be available to the user to view.
2. These will inform the user of the kind of information Seclore will collect and how it will be used.
3. If the user agrees, they can enable the check box on the login page and proceed to login.
4. Fixed the issue when a protected Word or Excel file was saved as unprotected when saving to OneDrive using the AutoSave option.
1. Before the fix: The user opened a protected Word or Excel file with less than Full Control permission.
2. When the user clicked the AutoSave option and configured it to be saved on OneDrive, the file was saved as an unprotected file.
3. After the fix: The AutoSave option will be disabled for protected Word and Excel files.
4. The user will have to upload and save such files manually (File >> Save/Save As).
5. Made the error messages informative in case the Seclore agent is not able to process a user action.
1. Now the user will be able to know the nature of the error from the error message itself.
2. This will help the users and system administrators to resolve the issue at the earliest for uninterrupted use of Seclore.
6. Fixed the issue where the Seclore icon was not visible on the taskbar when the agent was active on the Desktop.
1. Before the fix: The Seclore icon on the taskbar appeared black when the agent was active on the Desktop.
2. After the fix: The Seclore lock icon will be visible on the taskbar when the agent is active on the Desktop.
7. Fixed the issue where the users with no access or expired access could view the buffer file or the data itself after RAR.
1. Before the fix: For a user who did not have access to a protected file, the RAR dialogue box appeared.
2. After the user requested access permission to the protected document, the buffer file was displayed.
3. For a user with expired access, after RAR the document opened with the data.
4. After the fix: After RAR, in both the scenarios mentioned above, the document will close.
5. Users will have access to the document and can view it only after the owner of the protected file assigns or renews permissions.

Seclore for Mac 3.4.2.0

1. Introducing automatic HTML wrapping when files are protected using the Seclore agent.
1. After this release, when a user protects a file using right-click >> Seclore It!, the file gets protected as well as HTML wrapped automatically.
2. This will remove the additional step of HTML wrapping a file after protecting it.
3. HTML wrapping must be enabled in the Policy Server configuration page.
4. This ensures consistency with files protected using Universal Protection files which are HTML wrapped automatically.
5. If HTML wrapping is disabled, the file will only get protected and HTML wrapping will not be applied to it.
6. If Seclore agent is not available, the file opens in Seclore Online.
7. In the right-click context menu, the 'Convert to agentless' option is changed to 'Convert to HTML'.
8. To convert an HTML wrapped file to the native format, 'Convert to native format' option is added in the right-click context menu.
2. Introducing Universal Protection for Endpoint protection.
1. Earlier, files with standard formats were discovered by Endpoint and protected using Seclore.
2. Files with non-standard formats were not protected.
3. After this release, non-standard file formats will be protected using Universal Protection when discovered by Endpoint scanner.
4. These files will be protected with full control to the authorized user and they will be HTML wrapped automatically after protection.
3. Adding GDPR compliance to Seclore.
1. When user logs in on the Policy Server or agents, the 'Terms of Service' and 'Privacy Policies' will be available to the user to view.
2. These policies will inform the user of the kind of information Seclore will collect and how it will be used.
4. Adding support for capturing product metrics for right-click >> Seclore It! and for advanced and universal protection in case of protection through Seclore button in Outlook.
5. Fixed the issue where a new Word document was saved as a protected file when created after opening a protected Word document.
1. Before the fix: The user opened a protected Word document.
2. He opened a new document by either using File >> New or Cmd+N shortcut.
3. The new document opened with the same watermark as the open protected document.
4. On editing and saving the new document, it was saved as a protected document.
5. After the fix: The new document will be created without a watermark and will be saved as an unprotected document after edit and save.

Policy server 3.8.2.0

1. Adding GDPR compliance to Seclore.
1. When user logs in on the Policy Server, the 'Terms of Service' and 'Privacy Policies' will be available to the user to view.
2. These will inform the user of the kind of information Seclore will collect and how it will be used.
3. If the user agrees, they can enable the check box on the login page and proceed to login.
2. Introducing the capability of downloading an unprotected copy of a protected file open in the Seclore Online Editor.
1. When a protected file is opened in the Seclore Online Editor and the user clicks on the download icon, 'Download Unprotected Copy' option will be available in the drop down.
2. On selecting this option, the unprotected copy of the file will be downloaded.
3. This option will be available only if the 'Download Unprotected' flag is enabled in the Policy Server.
4. The user must also have Full Control on the protected file to download an unprotected copy.
3. Fixed the issue where error page was displayed in certain cases when the user tried to login to the Policy Server using Microsoft credentials.
1. Before the fix: When the user opened a protected file from Microsoft application like SharePoint Online, an error page was displayed when Microsoft based authentication was either disabled or not configured.
2. After the fix: The Policy Server login page will now be displayed in the above-mentioned scenario.
4. Now create an enterprise application for Digital Guardian DLP Encryptor from the Custom Application option.
1. Earlier, you could directly select the Digital Guarding DLP Encryptor from the Select Enterprise Application Type window.
2. Starting this release, you'll have to select the Custom Application from the Select Enterprise Application Type window for creating a Digital Guarding DLP Encryptor.
5. Added support for Oracle 18c and 19c database versions.

Desktop Client 3.9.1.0

1. Fixed the rare issue where protected image files were not opening using MS Paint in presence of Boldon James classification.
1. Before the fix: When the user, with Boldon James classification installed, right clicked on a protected image file and selected Open with >> MS Paint, the image did not open.
2. This was observed with the Desktop Client version 3.8.12.0 and above.
3. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location)
4. After the fix: The protected image files opened in MS Paint, as expected.
2. Fixed the issue where protected files with multiple '%s' in the filename stopped working on opening or unprotecting in offline mode.
1. Before the fix: Protected files having multiple (either consecutive or separated) '%s' in their filenames stopped working when opened.
2. Also, when user tried unprotecting such a file (Right click >> Advanced >> Unprotect), the file did not function as expected.
3. After the fix: Users will be able to open and unprotect protected files in offline mode with multiple '%s' in their filenames successfully.
3. Fixed the issue where the Undo action did not work after editing and saving a protected Excel file.
1. Before the fix: After a user opened, edited and saved a protected Excel file, the Undo action did not work like it should in case of an unprotected Excel file.
2. After the fix: Undo changes can be performed even after saving changes in a protected Excel file.
4. Fixed the issue where a protected file lost all the attributes after it was HTML wrapped.
1. Before the fix: When a protected file was HTML wrapped, the file lost all its attributes.
2. These attributes included Read Only mode, hidden attribute, change in creation date, etc.
3. After the fix: Protected files, when HTML wrapped, will retain the above-mentioned attributes.
5. Fixed the issue where in case of cloned Windows machines, the installation report of the Seclore Desktop Client displayed only a single entry.
1. Before the fix: When a machine was cloned and Desktop Client was installed in the cloned machine, it replaced the installation entry of the previous machine.
2. Due to this, the installation report did not record the actual number of installations of the Seclore Desktop Client.
3. After the fix: The installation report will display the installation of Desktop Client in the cloned machine as a separate entry.
4. This will ensure that the actual number of installations of the Desktop Client is recorded in the installation report.

Policy Server 3.8.1.0

1. Fixed the issue where error occurred when a user changed the permission on a file protected using a new classification.
1. Before the change: Seclore provides five default classifications.
2. User can create new classifications in the Policy Server and protect files using these classifications
3. When the user changed the permission on such files as mentioned in the above point, an error is displayed.
4. After the change: User can change permission on any protected file with any classification without any error.
2. Fixed the issue where the installation report displayed only a single entry for machines with same SID.
1. Before the fix: When a machine was cloned and Desktop Client was installed in the cloned machine, it replaced the installation entry of the previous machine.
2. Due to this, the installation report did not record the actual number of installations of the Seclore Desktop Client.
3. After the fix: The installation report will display the installation of Desktop Client in the cloned machine as a separate entry.
4. This will ensure that the actual number of installations of the Desktop Client is recorded in the installation report.
3. Fixed the issue where the direction of Arabic text in Seclore Online Viewer did not appear properly.
1. Before the change: Arabic text is written from right to left unlike other languages that are written from left to right.
2. When a document written in Arabic and protected was opened in Seclore Online Viewer, it's direction and orientation did not appear as expected.
3. After the change: The direction of Arabic will remain unchanged in Seclore Online Viewer.
4. Fixed the issue where disk space was getting used up when files were accessed through SharePoint.
1. Before the change: When protected files were opened through SharePoint, disk space was getting used up and a warning was displayed.
2. This was rectified after the application was restarted.
3. After the change: Now user can open and work on protected files from SharePoint without encountering disk space warning messages.
5. Updated language support for PS messages in Spanish, French and Russian.
1. Now all PS based message will be displayed in the language configured for the user.

Lite for Mac 3.4.1.0

1. Change in the integration approach with third party applications to comply with the notarisation pre-requisites announced by Apple on February 3rd, 2020.

Email Auto Protector 3.3.1.0

1. Fixed the issue where the mail routed through Seclore Email Auto Protector were not displayed in email search results.
1. Before the change: When a user sends an email with an attachment that fulfills certain rules, it is routed through the Seclore Email Auto Protector.
2. The Email Auto Protector either protects or unprotects an email depending on rules set in the rules console.
3. When the recipient searches their mailbox using a keyword, the emails routed through Seclore Email Auto Protector did not appear in the results even if they fulfilled the search criteria.
4. After the change: Emails routed through Seclore Email Auto Protector will appear in the results if they fulfill the search criteria.

Desktop Client 3.9.0.0

1. Introducing Universal Protection for protecting any file format with sensitive enterprise information.
1. Earlier, a user could protect only a limited number of file formats using Right-click >> Seclore It or the 'Seclore It' button in Outlook.
2. With this new feature, users can now protect any file format on their desktop or in Outlook.
3. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).
4. For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
5. When an authorized recipient opens a file with Universal Protection, he/she is granted Full Control permission.
6. The Universal Protected file opens in read-only mode and if the user edits and tries to save the file, he/she will be prompted to 'Save As'.
7. Authorized recipients can also Unprotect these files.
8. Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html.
9. This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature.
10. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.
11. Requires Policy Server 3.8 or higher.
2. End of Advanced Protection support for certain outdated file extensions.
1. Certain file formats will not be supported by Seclore for Advanced Protection, going forward.
2. These file formats will be included under Universal Protection and the permissions granted for Universal Protection will be applicable.
3. When the Policy Server is updated and the Desktop Client is not updated, files in these formats, which were previously protected using Advanced Protection, will continue to grant the previously applied permissions.
4. When the Desktop Client is updated, files in these formats, which were previously protected using Advanced Protection, will prompt the user to get the file re-protected using Universal Protection from the owner on access.
5. This is regardless of the Policy Server being updated or not.
3. Fixed the issue where the PowerPoint files (protected and unprotected) stopped functioning when a user moved through a list of files in the File Explorer with the Preview Pane enabled.
1. Before the change: When a user enabled the Preview Pane (View >> Preview Pane) in the File Explorer and moved through a list of files, PowerPoint files open in the background stopped functioning.
2. This particular behaviour was not observed for other Microsoft Office file formats as preview is disabled for file formats like Word and Excel.
3. After this change: PowerPoint files will function and remain open as expected even with the Preview Pane enabled in the File Explorer.
4. Fixed the issue where the default browser icon was displayed for a HTML wrapped file.
1. Before the change: When Desktop Client was installed in the system, the original file format icon (Word, Excel, PowerPoint, etc.) was not displayed for HTML-wrapped files.
2. Instead, the default browser (for example, Chrome icon) was displayed.
3. This usually occurred after restarting the system.
4. This was previously rectified by running the Repair Installation tool of the Desktop Client (Click on the Seclore tray icon >> Repair Installation >> OK).
5. After the change: The default file format icon will be displayed for HTML-wrapped files throughout.
6. Exception: Files with .smail extensions will continue to display the default browser icon or HTML icon.
5. Fixed the issue where the default file format icon was not displayed for HTML-wrapped files when a copy of the file was created or when an HTML-wrapped file was downloaded multiple times.
1. Instead, the default browser icon was displayed.
6. Fixed the issue where the lengthy email IDs of the file owners spilled over the permission widget of an open protected file.
1. Before the change: When the user clicked the 'S' button in an open protected document, the email ID of the owner spilled over the permission widget.
2. After the change: For lengthy email IDs, part of the email ID is visible, and three dots are added after that.
3. The user can hover over the dots and view the complete email ID as a tooltip.
7. Fixed the issue where Outlook stopped functioning when the user clicked on the 'Seclore It' button for protecting emails and attachments.
1. Before the change: While composing an email from the Outlook application when the user clicked on the 'Seclore It' button from the Menu ribbon, Outlook stopped functioning.
2. This issue was observed for users with Policy Server version 3.7.4.0 and above.
3. After the change: When the user clicks the 'Seclore It' button on the Menu ribbon in the Outlook application, the Seclore options will be displayed, as expected.

Seclore Lite for Mac 3.4.0.0

1. Introducing Universal Protection for protecting any file format with sensitive enterprise information.
1. Earlier, a user could protect only a limited number of file formats using Right-click >> Seclore It or the 'Seclore It' button in Outlook.
2. With this new feature, users can now protect any file format on their desktop or in Outlook.
3. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).
4. For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
5. When an authorized recipient opens a file with Universal Protection, he/she is always given Full Control permission.
6. The Universal Protected file opens in read-only mode and if the user edits and tries save the file, he/she will be prompted to 'Save As'.
7. Authorized recipients can also Unprotect these files.
8. Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html.
9. This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature.
10. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.
11. Requires Policy Server 3.8 or higher.
2. Fixed the issue where emails sent from Outlook using 'Seclore It' were sent unprotected, if the HTML wrapping feature was disabled in the Policy Server.
1. Before the change: When the HTML wrap feature is disabled in the Policy Server, if the user invokes the 'Seclore It' option in Outlook, the email and attachments are always sent unprotected.
2. After the change: In this scenario, attachments will be sent protected, as expected.
3. Note: The option to protect the email body is not available when the HTML wrapping feature is disabled in the Policy Server.
3. Fixed the issue faced where creating a new Microsoft Excel workbook from a template was not working as expected.
1. Before the change: When the user created a new Workbook from a template, the application would shut down unexpectedly.
2. After the change: This issue has now been fixed.
4. Fixed the issue where a protected and HTML-wrapped file got unwrapped if an unauthorized user unprotects it.
1. Before the change: When an unauthorized user attempts to unprotect a file with HTML-wrapping, it removes the HTML format. i.e. Sample.docx.html converts to Sample.docx, even though it doesn't get unprotected.
2. After the change: The issue has been fixed and the HTML format is retained..
5. Fixed the rare issue where certain file formats (docm, docx, xlsm and xlsx) were not getting protected from a network shared folder.
1. Before the change: Sometimes when the user performs a Right-click >> Seclore It on an individual file in a certain format (i.e. docx, docm, xlsx or xlsm), stored on a network shared folder, it would not get protected.
2. If the user tries to a Right-click >> Seclore It on the parent folder containing these files, they were still getting protected.
3. After the change: The files get protected, as expected.
6. Fixed the issue where protected files placed on network shared folders were not getting converted to Agentless format (HTML-wrapped).
1. Before the change: If the user does a Right-click >> Convert to Agentless Format on a protected file stored on a network shared folder, it would not work as expected.
2. After the change: The files are successfully HTML-wrapped.
7. Fixed the rare issue where the Seclore operations returned an error message when performed on some network shared folders.
8. Fixed the issue where the agent becomes unresponsive if the user tries to protect a file that is already open.
1. Before the change: When a user does a Right-click >> Seclore It on an open, unprotected file, the file would not be protected.
2. The agent also became unresponsive to any further commands.
3. After the change: The file gets protected and the agent works as expected.

Policy Server 3.8.0.0

1. Introducing Universal Protection for protecting any file format with sensitive enterprise information.
1. Earlier, a user could protect only a limited number of file formats using Right-click >> Seclore It or the 'Seclore It' button in Outlook.
2. With this new feature, users can now protect any file format on their desktop or in Outlook.
3. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).
4. For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
5. When an authorized recipient opens a file with Universal Protection, he/she is granted Full Control permission.
6. The Universal Protected file opens in read-only mode and if the user edits and tries to save the file, he/she will be prompted to 'Save As'.
7. Authorized recipients can also Unprotect these files.
8. Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html.
9. This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature.
10. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.
2. Introducing collaboration of MS O365 and Seclore for enhanced security of your documents on the cloud.
1. Now, you can edit and save your changes (if you have the required permissions) in the documents shared through SharePoint Online and OneDrive.
2. No need to download to edit shared documents from SharePoint Online and OneDrive.
3. External users can also edit documents if they have Edit permission from the document links shared with them.
3. Introducing the new and improved Seclore Online Editor with enhanced UI.
1. The look and feel of the new Seclore Online Editor are similar to the corresponding Microsoft Office applications.
2. Important functional buttons such as Save, Print, Undo and Redo are moved to the Only Office title bar for better visibility.
3. In addition to the Only Office title bar, another title bar will be visible for Seclore-protected documents.
4. This new title bar will display the customer logo, Read-only (in case of read-only files), Edit button (for integration workflows) and the download button.
5. The Edit button appears only when a file is opened in the Read-only mode in case of integration workflows like opening protected files from SharePoint online.
6. The Edit button is not visible in the Edit mode.
7. For non-integration workflows, documents open in the view depending on the granted permission.
8. The download button is moved from the inside of the document to the Seclore title bar.
9. In Read-only mode, only the option to download the Seclore agent is visible on clicking the download button.
10. In Edit mode, the options to download the Seclore agent and to download the protected copy of the file.
4. Now, the online help package is released separately from the Policy Server package and needs to be downloaded and placed in the PS package.
1. This will ensure the latest online help for the Seclore products with the latest feature explained.
2. If the online help package is not downloaded and available, an error message is displayed.
5. Fixed the issue where Seclore Lite for Mac installation package was downloaded on iPad after clicking on Download Seclore in the buffer file.
1. Before the fix: If a user does not have Seclore app for iOS installed in their iPad and opened a protected file from email, the buffer file was displayed in the browser.
2. On clicking the Download Seclore option, Seclore Lite for Mac was downloaded instead of redirecting the user to the App store.
3. This was observed in the iPadOS 13.
4. After the fix: The user is redirected to the App store from where they can download the Seclore Lite app for iOS or iPadOS.
6. Fixed the issue where the owner of the excluded Hot folder was not changed once the owner of the parent Hot Folder changed.
1. Before the fix: When the owner of a parent Hot Folder was changed, the exclude Hot Folder inside the parent Hot Folder was still tagged to the previous owner.
2. After the fix: The parent of the excluded Hot Folder changes automatically to the owner of the parent Hot Folder.
7. Fixed the alignment of all the columns in the Activities tab, Files tab, Hot Folder Cabinets list and List Enterprise Application page.
1. Before the fix: The alignment was affected when zoomed in or out.
2. In case of large Activity IDs and File IDs, the number spilled in the neighbouring column.
3. After the fix: The alignment is adjusted according to the screen size and resolution, and large values do not overlap or spill in the neighbouring columns.
8. Removed the Active Directory Operating System Version field from the AD Configuration page as it does not accept any other values apart from 2000, 2003 and 2008.
1. As the field is now obsolete and did not accept any other value, it has been removed from the page.
9. Fixed the issue where the UI of the error page, stating that the browser is unsupported, was not properly displayed.
10. Fixed the issue where when a file owner searched for a file in the Policy Server using the File ID, an error message was displayed instead of successfully displaying the file in the results.
11. Fixed the issue where a redistributor was able to approve access request even after the rights of the redistributor on the protected file had expired.
1. Before the fix: When an unauthorized user requests for access to a protected file, the request is sent to the owner as well as redistributors of the file.
2. The redistributor, with expired rights on the protected file, was able to approve such access request.
3. This resulted in the expiration of the link for the owner and other redistributors with rights to the file.
4. Additionally, the requestor did not receive access to the file.
5. After the fix: The redistributor, with expired rights on the protected file, cannot approve access request on a protected file.
6. An error message will be displayed instead.
12. Fixed the issue where the user was able to see the buffer file in an Unsupported Browser with the options to either open the protected file or download the agent.
1. Before the fix: When a user opened an HTML wrapped file in an unsupported browser, the buffer file was displayed with options to open the file in the Seclore Online Editor or to download the agent.
2. After clicking either of the two options, the Unsupported Browser page was displayed.
3. After the fix: The Unsupported Browser page is displayed when a user tries to open an HTML wrapped protected file in an unsupported browser.

Seclore for O365

1. Introducing collaboration in Seclore for O365.
1. You can now edit documents online and save your changes directly into SharePoint Online and OneDrive. No need to download documents anymore.
2. This works for users external to the organisation too, if they have the required permissions.
3. Requires Policy Server 3.8.0.0 or higher
4. Requires Seclore Online 3.1.0.0 or higher

Email Auto Protector 3.3.0.0

1. Support for protection of non-standard file formats (Universal Protection).
1. Admins can include non-standard file formats while creating rules in the Email Auto Protector rule console.
2. These files will be provided with full control and they will be HTML wrapped for added protection.

Mail Portal 3.1.0.0

1. Introducing Universal Protection for protecting any file format with sensitive enterprise information.
1. Earlier, among the file sent by an external user, only a limited number of file formats were received by the internal user as protected.
2. With this new feature, all file formats will be received by the internal user protected and HTML wrapped.
3. For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).
4. For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
5. When an authorized recipient opens a file with Universal Protection, he/she is granted Full Control permission.
6. The Universal Protected file opens in read-only mode and if the user edits and tries to save the file, he/she will be prompted to 'Save As'.
7. Authorized recipients can also Unprotect these files.
8. Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html.
9. This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature.
10. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.

Seclore Decryption Server 3.1.0.0

1. Support for non-standard file formats (Universal Protection).
1. Non-standard file formats will also be unprotected in addition to the standard file formats.

PST Decryption Server 1.1.0.0

1. Support for non-standard file formats (Universal Protection)
1. Non-standard file formats will also be unprotected in addition to the standard file formats.

Server SDK 4.4.0.0

1. Fixed the issue where email was sent with unprotected attachments when HTML wrap feature was disabled in the Policy Server and email body protection was enabled in Email Auto Protector rules.
1. Before the change: When an email with attachments were protected and sent with the HTML wrap feature disabled in the Policy Server and email body protection enabled in Email Auto Protector ruled, the email was sent but with the attachments unprotected.
2. After the change: The email is sent in such a scenario with the email body unprotected and the attachments protected but unwrapped.
2. Introducing support for Universal Protection where non-standard file formats will be protected using full control rights and HTML wrapped for added security.
3. Support for updated HTML buffer files.

Desktop Client 3.8.12.0

1. Introducing the tracking for Close activities of Seclore-protected files.
1. Starting now, the close activity for Seclore-protected files will be logged in the Policy Server.
2. You can calculate the time a recipient has spent on a file using the feature.(Time between Open and Close activities).
3. This feature is enabled for Seclore-protected file opened in Offline mode as well.
4. This feature must be enabled in the Policy Server, the default being disabled.
2. Fixed the issue where if a file with "%S" characters in its file name is attached to an email in Outlook, the Outlook app stopped functioning as expected.
3. Fixed the issue where Outlook stopped functioning as expected when an email group contained the ID of an ex-employee (deactivated email ID).
1. After this fix, the email will be sent to the remaining recipients of the email group.
2. In case the ex-employee is the only recipient of the email, a delivery failure message will be received by the sender.
4. Fixed the issue where the cross-referencing option in a protected Word document was disabled.
5. Updated the tooltips for file protection options in Outlook, providing precise and clear description for each Seclore option in Outlook.
6. Fixed the issue where if a Seclore-protected PDF file is unable to open, the buffer file was displayed and on saving data loss occurred.
1. Before the fix: The buffer file is opened and on saving data loss occurred for the Seclore-protected PDF file.
2. After the fix: The buffer file is opened in Read-only mode and on saving the Save-As prompt will be displayed to the user.
7. Fixed the issue where an error was displayed if the user tried to login using Google authentication from the tray.

Seclore Lite for Mac 3.3.11.0

1. Fixed the issue where a blank icon was being displayed for '.html' and '.htm' file extensions, on macOS 10.4 (Mohave) and below in certain cases
2. Modified the icon displayed in various dialogs and message boxes, to show a generic icon in place of a Seclore application icon (i.e. Red colored 'S' icon).
3. Fixed the issue, where agent updates were not happening immediately after installation in certain cases.
1. Before the fix: In certain cases, updates would not happen immediately after installation and would happen only the next day.
2. After the fix: Once a new installation is complete, the agent updates itself immediately if there are any additional patches on the Policy Server.
4. Fixed the issue where protected HTML-wrapped read-only documents from a network location were opening in edit mode and users could edit and save the changes.
1. Before the fix: Opening a read-only file from a network location, would open the document in edit mode and would allow the user to make changes and save it.
2. However, the original read-only file was never updated with the changes.
3. After the fix: After editing a read-only HTML-wrapped document, the user will be forced to save it as a different document. The original read-only document is not affected.

Desktop Client 3.8.11.0

1. Discontinued the image viewer that was packaged along with the Seclore agent.
1. Seclore now uses the built-in image rendering capabilities of Windows to open Seclore-protected image files.
2. This reduces the size of the agent installer by a few MB.
2. Fixed the random issues that were observed when opening protected documents in certain scenarios
1. In certain case when Adobe Reader or Acrobat was uninstalled and reinstalled on a desktop, the user was facing issues with opening protected PDF documents.
2. For other formats, a similar issue was seen in certain cases when a user was opening a protected file using 'Right-click > Open with' in Windows Explorer.
3. Fixed the rare issue where protected documents didn't open as expected when the user is a Built-in Administrator
1. In certain rare cases (usually on server-based virtual machines), the logged in user maybe a part of the Built-in Administrators group.
2. In certain cases, such a user may not be able to open protected documents as expected.
3. He/she may see only the Buffer page or in certain cases the Office app (Word, Excel or PowerPoint) may shut down unexpectedly.
4. Fixed the issue where the HTML Wrapper page was not displayed as expected on iOS 13 devices
1. Before the fix: Opening HTML-wrapped documents from Apple Mail or any other app on iOS 13 devices was not displaying the file opening instructions that are embedded in the HTML wrapper page.
2. After the fix: An updated version of the HTML Wrapper file is now packaged with the Desktop Client to fix this issue.
3. Files protected with this new version of the agent will now display the HTML Wrapper page as expected on iOS 13 devices as well.

Seclore Lite for Mac 3.3.10.0

1. Fixed the issue where both protected and unprotected file icons for .htm and .html file formats displayed the Seclore icon instead of a format specific icon.
1. After the change: A new OS icon is now displayed for all .htm and .html files that depicts the HTML file format.
2. This is an issue only for macOS 10.15 (Catalina).
2. Fixed the issue where the HTML Wrapper page was not displayed as expected on iOS 13 devices.
1. Before the fix: Opening HTML-wrapped documents from Apple Mail or any other app on iOS 13 devices was not displaying the file opening instructions that are embedded in the HTML wrapper page.
2. After the fix: An updated version of the HTML Wrapper file is now packaged with the Mac agent to fix this issue.
3. Files protected with this new version of the agent will now display the HTML Wrapper page as expected on iOS 13 devices as well.
3. Added support for standalone licenses of Office 2016 (16.16.1 onwards)

Policy Server 3.7.6.0

1. New and improved user interface for Seclore Online to enhance the user experience for opening protected documents in the browser.
1. Users opening, editing and saving Seclore-protected documents in the browser will now have more intuitive menus, formatting options and command buttons.
2. The new UI is similar to the Microsoft Online editors for Word, Excel and PowerPoint.
3. This will be available for Office formats, PDF and text formats.
2. Providing seamless integration with Microsoft Office O365, to open Seclore-protected documents directly from SharePoint Online and OneDrive in Seclore Online
1. Users with access to a protected document can open it directly from SharePoint Online or OneDrive within the browser itself.
2. In SharePoint Online users have the option to click on the file name or a custom button provided by Seclore.
3. In OneDrive users can click on the file name to open it directly in Seclore Online.
4. Additionally, users can open Seclore-protected documents with one-click from reference links shared via emails or any other mechanism.
3. Added Single Sign-On (SSO) with Azure AD to help users seamlessly authenticate and access Seclore-protected documents from SharePoint Online and OneDrive.
4. Fixed the issue where the HTML Wrapper page was not displayed as expected on iOS 13 devices.
1. Opening HTML-wrapped documents from Apple Mail or any other app on iOS 13 devices was not displaying the file opening instructions that are embedded in the HTML wrapper page
2. An updated version of the HTML Wrapper file is now packaged with the Policy Server to fix this issue.
3. Files protected or edited with this version of the Policy Server will now display the HTML Wrapper page as expected on iOS 13 devices as well.
5. Fixed the issue where the user search while protecting a file was not functioning consistently.
6. Fixed the issue in Seclore Online that occurs when the file name contains certain uncommon characters
1. In certain cases when the file name contains non-ASCII characters and it is opened, edited and saved in Seclore Online, the file name was getting corrupted.
2. This was happening in the downloaded file as well as the email received by the user from Seclore Online.
7. Fixed the content on the page that was displayed to the user when accessing the Policy Server from an unsupported operating system or browser. This is now much simpler and more intuitive to the user.
8. Fixed the issue where the redistributor was unable to approve Request Access on Seclore-protected documents, if the file owner's email ID is not defined.
9. Fixed the issue where the redistributor was unable to approve a request for access on a Seclore-protected document if the File Owner's email ID was not available.

Seclore Server SDK Java 4.3.4.0

1. Incorporated the latest version of the HTML Wrapper to ensure the user sees the file opening instructions on iOS 13 devices.

Seclore Plugin for Forcepoint DLP Network Discover 3.0.0.0

1. Added support for Forcepoint DLP versions 8.6 and 8.7.
2. Enhanced the Auto Protector for Forcepoint DLP to protect sensitive files on Linux File Servers and NAS Filers.
1. Before this release: Forcepoint DLP Network Discover component could invoke Seclore protection for sensitive files and documents found only on Windows File Servers.
2. After this release: Forcepoint DLP Network Discover component can invoke Seclore protection also on Linux File Servers and NAS Filers as well.
3. Discontinued support for Forcepoint DLP versions 8.3, 8.4, 8.5.

Seclore for O365 3.0.0.0

1. This module is currently responsible for opening Seclore-protected files in Seclore Online from O365 Apps (SharePoint Online and One Drive Portal)
2. It achieves 'Click to Open' functionality through multiple ways:
1. Click on the file name in SharePoint Online and One Drive Portal
2. Clicking on the 'Open' Option in the Command Bar
3. Clicking on a New Seclore button displayed for Seclore Protected file
4. Click on 'Open with Seclore' Option in the Command Bar
5. Click on the file link shared with a user through SharePoint Online
3. Limitations/Points to note:
1. Only SharePoint Online and OneDrive Portal considered in Scope. No other O365 apps like Teams or Yammer etc.
2. New Seclore Button and 'Open with Seclore' Option in Command bar is visible for SharePoint Online and not on OneDrive Portal
3. Opening Seclore protected files through click on file name in SharePoint Online and One Drive Portal is supported for only HTML Wrapped files
4. Opening Seclore protected files through click on file link shared with user is applicable for only HTML Wrapped files
4. Requires Minimum Policy Server version 3.7.6.0.

Desktop Client 3.8.10.0

1. Added support for the latest Google Chrome browser version 76 and above for Auto-login to the Policy Server in the browser when the user is already logged in to the Desktop Client.
2. Fixed two issues that occur in the latest version of Microsoft Excel 1909 or later:
1. The login page was not displayed as expected when the user is not already logged in.
2. The Seclore badge (displaying user permissions) was not visible after the file was opened
3. Minor fixes in the UI for the newly updated Desktop Client UI.
4. Fixed the minor issue where the file name was appearing in upper case in certain activities logged on the Policy Server.

Seclore Lite for Mac 3.3.9.0

1. Fixed the issue where re-installing the agent in 'receiver-only' mode was not working as expected.
1. Before the fix: 'Receiver-mode' is used in certain rare cases when the enterprise does not want the Seclore protection options to show in Finder (Right-click) and Outlook ('Seclore It' button).
2. If the agent was first installed in normal mode, then uninstalled and re-installed in 'receiver-only' mode, the Seclore It button was still showing in Outlook, which was not expected.
3. After the fix: The Seclore It button is not seen in Outlook in receiver-only mode.
2. Fixed the issue where the Seclore icon was displayed instead of the respective application icon for protected and unprotected documents in macOS 10.15 (Catalina).
3. Fixed the issue where the agent was not getting installed on macOS 10.15 (Catalina).
4. Fixed the issue in Office 16.28 and above, where the protected email body was not displayed when a user with Share permission, was Replying or Forwarding it in Outlook.
5. Fixed the issue where the user was not able to open an HTML wrapped protected document if the watermark was not configured in the Policy Server.

Seclore Lite for Windows 3.3.5.0

1. Fixed the issue where Outlook stopped responding when the user tries to access any folder in Outlook after clicking on the inline protected email body.
2. Fixed the Outlook performance issue that is observed when sending an email to a very large Distribution List.
1. Before the fix: Sending an unprotected email to a very large Distribution List, would sometimes put the Outlook application into a non-responding state.
2. After the fix: This issue is now resolved.

Email Auto Protector 3.2.1.0

1. Added support for the new HTML Wrapper pages.
1. New emails protected by the Seclore Email Auto-protector will use the new HTML wrapper pages.
2. Requires Seclore Policy Server 3.7.5 or higher.

Desktop Client 3.8.9.0

1. Significantly enhanced the user experience for Agentless access of protected documents by revamping the content and behavior of the HTML pages displayed in the browser.
1. Enhanced the messaging and visual layout to make it more intuitive for first time users when opening protected documents directly in the browser.
2. Added special handling for users of the Chrome browser to open protected documents in the native app when the agent is installed.
3. Requires Seclore Policy Server 3.7.5 or higher.
2. Enhanced the Seclore tray by improving the visual design and dropping unused options.
1. Before the change: When user left clicked on the Seclore icon in the notification area, a small screen was displayed with options that were not utilized by the user.
2. After the change: Only the important options are displayed now, when the user right-clicks on the Seclore icon. The left-click is disabled.
3. Enhanced the user experience and functionality of the Error Reporting Tool.
1. Revamped the user interface with better design and aesthetics.
2. Added the capability for the user to give consent before system details and application logs are captured by the tool.
3. Enhanced the processing performance.
4. Fixed the issue where protected documents open in the background, if opened from any folder other than the Desktop, when the user is already logged in.
1. This issue occurred while opening Word, PowerPoint and PDF documents.
2. This issue did not occur, if user is not logged in and performs explicit authentication while opening a file, if communication to the Policy Server was slower and for large files.
5. Fixed the issue where Outlook stopped responding when the user tries to access any folder in Outlook after clicking on the inline protected email body.
6. Changed the error message for unsaved Microsoft Word and Microsoft Excel files to convey a clear and short message to the user for saving the file.
1. Before the change: The message was lengthy and complex. It did not convey the actual steps to manually save the protected file before closing it.
2. After the change: A more intuitive dialog box with clearer message stating to manually save the document before closing it.

Seclore Lite for Mac 3.3.8.0

1. Significantly enhanced the user experience for Agentless access of protected documents by revamping the content and behavior of the HTML pages displayed in the browser.
1. Enhanced the messaging and visual layout to make it more intuitive for first time users when opening protected documents directly in the browser.
2. Added special handling for users of the Chrome browser to open protected documents in the native app when the agent is installed.
3. Requires Seclore Policy Server 3.7.5 or higher
2. Fixed the issue where the user was unable to open protected Microsoft PowerPoint files natively in PowerPoint, as expected.
1. This issue was occurring for Microsoft Office version 16.25, 16.26 and 16.27 with the macOS 10.14.
2. After the change: User can open the MS PowerPoint files with the watermark and widget.

Seclore Policy Server 3.7.5.0

1. Significantly enhanced the user experience for Agentless access of protected documents by revamping the content and behavior of the HTML pages displayed in the browser.
1. Enhanced the messaging and visual layout to make it more intuitive for first time users when opening protected documents directly in the browser.
2. Added special handling for users of the Chrome browser to open protected documents in the native app when the agent is installed.
2. Improved the end user experience when downloading the Desktop Client package from the Policy Server portal.
1. Before the change: On the Lite Online tab in the Policy Server portal, when the user clicks on the button to download the Desktop Client, the user was first taken to another page before the package could be downloaded.
2. After the change: The Desktop Client package now downloads immediately when clicking on the download button on the Lite Online tab.
3. Removed Data Classifier option from the Enterprise Application List as it is no longer required.
4. Fixed the issue where Smart Sharing was not working for email IDs representing a user group.

Seclore Server SDK - Java 4.3.2.0

1. Added support for the new HTML Wrapper pages.
1. Requires Seclore Policy Server 3.7.5 or higher.

Seclore Email Auto-protector 3.2.1.0

1. Added support for the new HTML Wrapper pages.
1. New emails protected by the Seclore Email Auto-protector will use the new HTML wrapper pages.
2. Requires Seclore Policy Server 3.7.5 or higher.

Desktop Client 3.8.8.0

1. Added system controls in the Desktop Client to discontinue support for Windows Server 2008 R1
1. Any Desktop Client installed on Windows Server 2008 R1 will not be upgraded automatically by the regular patch upgrade mechanism.
2. The agent will be frozen on the last supported version i.e. Desktop Client 3.8.7.
3. To continue agent upgrades, install a newer OS version i.e. Windows Server 2008 R2 or higher.
4. Desktop Clients that are frozen at version 3.8.7.0 will be clearly indicated in the Agent Installation Report that is available to the System Admin in the Seclore Policy Server.
5. Microsoft discontinued Mainstream support for Windows Server 2008 in 2015.

Desktop Client 3.8.7.0

1. Fixed the issue where downloading and opening a protected document from the Chrome browser's download bar was not opening in the native application, as expected.
1. When the Seclore agent is installed, the user expects a protected document to open locally in the native application.
2. Before the change: When a user downloaded an HTML-wrapped protected file in Chrome and attempts to open it directly from the download bar, it was opening in the browser, instead of opening locally in the native application.
3. This was happening because Google's Chrome browser attempts to open HTML files in its own preview rather than allowing the operating system to open them.
4. After the change: Documents opened from the Google download bar will now be redirected to the local agent to open them directly in the native application.
5. Expected Behavior: For this feature to work, the Policy Server needs to be reachable and JavaScript needs to be enabled in Chrome.
2. Improved the performance of protecting emails using the 'Seclore It' button in Outlook.
3. Improved the error message displayed in Outlook when a user right-clicks on a document and selects 'Send to > Mail recipient' with Seclore Data Classification enabled.
1. When Outlook is configured as the default Mail app in Windows, the user can right-click on a document and select 'Send to > Mail recipient' to automatically compose a new email in Outlook and attach the document.
2. In the above case, if the user has auto-protection with Seclore Data Classification enabled, the email doesn't get automatically protected as expected.
3. Due to a technical limitation in Outlook, the email cannot be sent.
4. Before the fix: In the above case, the system was displaying a generic error message that was not very helpful to the user.
5. After the fix: The new error message will clearly inform the user that this method of composing an email is not supported.
6. The message will also instruct the user to always compose emails using the 'New Email' button in Outlook.
4. Fixed the issue where, A Copy of the already opened file opens again, on selecting 'Restore' option shown in a second PDF file that is opened.
1. The 'Restore' option should not appear at all when a user opens a second PDF file while the first is already open.
2. Before the change: In case of an unprotected file, when the user clicked on the 'Restore' option in the second Adobe window, a copy of the first open file was displayed. In case of a protected file, when the user clicked on the 'Restore' option in the second Adobe window, the buffer file was displayed.
3. This issue was consistent on Continuous track May 2019 release of Adobe.
4. After the change: The 'Restore' pop-up and option does not appear when opening two PDF document one after the other on Adobe Acrobat Standard DC Continuous, Adobe Acrobat Pro DC Continuous and Adobe Acrobat Reader DC Continuous.
5. Added support for rarely used versions of Adobe Acrobat Reader, Acrobat Standard and Acrobat Pro.
1. Adobe Reader 2015 (Classic).
2. Adobe Reader 2017 (Classic).
3. Acrobat Pro 2015 (Classic).
4. Acrobat Pro 2017 (Classic).
5. Acrobat Standard DC (Continuous)

Seclore Lite for Windows 3.3.4.0

1. Fixed the issue where downloading and opening a protected document from the Chrome browser's download bar was not opening in the native application, as expected.
1. When the Seclore Lite is installed, the user expects a protected document to open locally in the native application.
2. Before the change: When a user downloaded an HTML-wrapped protected file in Chrome and attempts to open it directly from the download bar, it was opening in the browser, instead of opening locally in the native application.
3. This was happening because Google's Chrome browser attempts to open HTML files in its own preview rather than allowing the operating system to open them.
4. After the change: Documents opened from the Google download bar will now be redirected to the local agent to open them directly in the native application.
5. Expected Behavior: For this feature to work, the Policy Server needs to be reachable and JavaScript needs to be enabled in Chrome.

Seclore Lite for Mac 3.3.7.0

1. Fixed the issue where downloading and opening a protected document from the Chrome browser's download bar was not opening in the native application, as expected.
1. When the Seclore Lite is installed, the user expects a protected document to open locally in the native application.
2. Before the change: When a user downloaded an HTML-wrapped protected file in Chrome and attempts to open it directly from the download bar, it was opening in the browser, instead of opening locally in the native application.
3. This was happening because Google's Chrome browser attempts to open HTML files in its own preview rather than allowing the operating system to open them.
4. After the change: Documents opened from the Google download bar will now be redirected to the local agent to open them directly in the native application.
5. Expected Behavior: For this feature to work, the Policy Server needs to be reachable and JavaScript needs to be enabled in Chrome.
2. Added support for Exchange Shared Mailbox groups in the Email Protector for Outlook.
1. Before this change: If a protected email was sent from a Shared Mailbox (i.e. the Mailbox group is the Sender), it was not accessible to the other members of the group.
2. After this change: Any email that is either sent to or sent from a Shared Mailbox, will always be accessible to all its group members.
3. Fixed the issue where the recipients of a Shared Mailbox did not have access to the protected email and attachments, if one of the users was not created or resolved.

Policy Server 3.7.4.0

1. Fixed the issue where downloading and opening a protected document from the Chrome browser's download bar was not opening in the native application, as expected.
1. When the Seclore agent is installed, the user expects a protected document to open locally in the native application.
2. Before the change: When a user downloaded an HTML-wrapped protected file in Chrome and attempts to open it directly from the download bar, it was opening in the browser, instead of opening locally in the native application.
3. This was happening because Google's Chrome browser attempts to open HTML files in its own preview rather than allowing the operating system to open them.
4. After the change: Documents opened from the Google download bar will now be redirected to the local agent to open them directly in the native application.
5. Expected Behavior: For this feature to work, the Policy Server needs to be reachable and JavaScript needs to be enabled in Chrome.
2. Enhanced the user experience for the Request Access approval email that is sent to the Owner and Sharer of a protected document.
1. Before the fix: The Request Access approval email sent to the Owner or Sharer of a protected document shows the requester's name only if some comments have been provided by the requester.
2. If no comments are provided, there is no way for the approver to know who has submitted the request.
3. After the fix: The requester's name always appears in the approval email.
3. Provided the capability to extract Agent Installation details for analysis purposes, using a backend database View.

Server SDK - Java 4.3.1.0

1. Configuration to make "Federal Information Processing Standards (FIPS)" optional.

Seclore Plugin for Symantec DLP Network Discover 1.0.0.0

1. Introducing Auto Protector for Symantec DLP that automatically protects files with sensitive content, discovered on file servers.
1. This plugin integrates with the Symantec DLP Network Discover to enable automatic protection of content discovered by Symantec.
2. The Administrator can configure DLP rules to automatically protect documents with a Seclore Policy.
3. Symantec Network Discover will scan network file servers and detect any sensitive content that matches the rule.
4. Once a Rule is triggered, the document is protected with the Seclore Policy configured in that rule.
5. Requires: Symantec DLP Server 14.6, 15.1, 15.5 or higher and Windows Server 2012 or 2016
6. Supported File Formats: All standard file formats supported by Seclore (Microsoft Office, RTF, CSV, PDF, Text, Open Office and Images).
7. Expected Behavior: Documents contained within a zipped (archived) will not be auto-protected by Seclore

Seclore Protector for Network Discover 1.0.0.0

1. Provides encryption as a service to protect files discovered by DLP Network Discover.
1. This component needs to be registered as an enterprise application in the Seclore Policy Server.
2. Includes Seclore Event Server to store requests received from DLP system and Seclore Encryption Server to protect files.
3. Seclore Event Server requires: Windows Server 2012, 2016 or higher, Java 11 or higher and Tomcat 9 or higher.
4. Seclore Encryption Server supports Windows Server 2012, 2016 or higher, Java 11 or higher and Tomcat 9 or higher.
5. Supported Network File Servers are Windows, Linux and NAS Filers.

Desktop Client 3.8.6.0

1. Fixed the rare issue that impacts the usage of a protected document in certain versions of Word 2016, when it is opened directly from a shared network drive.
1. Before the fix: If the user opens a protected document directly from a shared network drive, all the application controls get disabled.
2. This is observed only in certain versions of Word 2016 that are operating with a one-time volume license. O365 and other subscription-based licenses do not present this same issue.
3. After the fix: This issue is now resolved.
2. Fixed the Microsoft Outlook issue where the application goes into a non-responding state in certain rare cases.
1. Before the fix: This issue occurs when a user has a protected email body open inline within his/her Outlook application window and selects some text, then clicks on Reply or Reply All or Forward.
2. In some cases, the application goes into a non-responding state.
3. After the fix: This issue is now resolved.
3. Fixed the Outlook performance issue that is observed when sending an email to a very large Distribution List.
1. Before the fix: Sending an unprotected email to a very large Distribution List, would sometimes put the Outlook application into a non-responding state.
2. After the fix: This issue is now resolved.

Seclore Lite for Mac 3.3.6.0

1. Enhanced support for Agentless access by preserving the HTML Wrapper even when the document is accessed using an agent.
1. Before this change: Whenever a user having a Seclore agent opens a protected document that is HTML Wrapped, the HTML Wrapper is removed, before it is opened.
2. For example, if a protected document 'sample.docx.html' is opened using the Desktop Client, the HTML Wrapper will first be removed, and the document will be renamed to 'sample.docx' before it is opened.
3. After this change: When sample.docx.html is opened, the HTML Wrapper will NOT be removed, and the document will open in Read-only mode.
4. This document can be shared further with anyone who can easily access it without an agent installed.
5. Preserving the HTML Wrapper helps to keep it more accessible to external users who can directly open it in the browser without an agent.
6. Only if the user edits and saves the document, the updated version will be saved without the HTML Wrapper.
2. Added support for Dark Mode in Outlook on macOS 10.14 and higher.
1. In macOS 10.14 Apple had launched a new system wide setting called Dark Mode which would display all system windows and menus in black or dark grey color.
2. Over successive releases, Dark Mode has since been gradually adopted by Microsoft Office apps as well.
3. In Outlook, the 'Seclore It' button and permission options displayed in the Ribbon menu at the top, are now be compatible with Dark Mode.
4. Also fixed the Login window issue where the option 'Is this your computer?' was not displaying as expected in Dark Mode.
3. Enhanced the user experience of the Smart Sharing feature by switching ON the Smart Sharing button every time a new email is composed.
1. Before this change: If a user switched OFF Smart Sharing in an email and sent it, the next time he/she composes a new email, Smart Sharing would still be OFF.
2. Since Smart Sharing is switched OFF only in the rarest of cases, this would require the user to remember to switch it ON when composing the next email.
3. After this change: Every time a new email is composed, the Smart Sharing switch will always be ON.
4. Fixed the rare issue where the user is unable to print a protected document even though he/she has the Print permission.
1. Before the fix: This issue was observed only on a 'Brother' printer, where a user was unable to print a protected document even when he/she had the Print permission.
2. This was observed only after the 'Watermark in printouts' feature was released in version 3.3.4.
3. After the fix: This issue has now been resolved.

Lite for Windows 3.3.3.0

1. Added support for Exchange Shared Mailbox groups in the Email Protector for Outlook.
1. Before this change: If a protected email was sent from a Shared Mailbox (i.e. the Mailbox group is the Sender), it was not accessible to the other members of the group.
2. After this change: Any email that is either sent to or sent from a Shared Mailbox, will always be accessible to all its group members.
2. Enhanced the user experience of the Smart Sharing feature by switching ON the Smart Sharing button every time a new email is composed.
1. Before this change: If a user switched OFF Smart Sharing in an email and sent it, the next time he/she composes a new email, Smart Sharing would still be OFF.
2. Since Smart Sharing is switched OFF only in the rarest of cases, this would require the user to remember to switch it ON when composing the next email.
3. After this change: Every time a new email is composed, the Smart Sharing switch will always be ON.
3. Optimized the login process for authenticating with the Policy Server in the Email Protector for Outlook. .
4. Re-designed and enhanced the intuitiveness of the user prompt in Email Protector for Outlook that reminds users to click on the Seclore It button.
5. Fixed the issue where Right-click > Seclore It was not working in some rare cases where the Windows Temp folder was set to some very specific value.
1. Before the fix: In case the Temp folder was set to a value like 'C:\' or 'D:\', the Right-click > Seclore It feature was not working as expected.
2. After the fix: This issue has now been resolved.
6. Fixed the issue where a document could not be opened in Offline mode in certain rare cases. .
1. Before the fix: A protected document could not be opened in Offline mode i.e. without connectivity to the Policy Server, if the Policy Server ID contained an ampersand.
2. After the fix: This issue is now resolved.

Email Auto Protector 3.2.0.0

1. Added a new feature to set expiry of protected emails and attachments as 'number of days from protection'.
1. Before the change: In a rule, it was only possible to set expiry as a specific date. e.g. Expires on May 9, 2019.
2. After the change: In addition to the above, administrator can now set expiry as 'number of days from protection'.
3. e.g. The rule to protect payroll data, can be configured to expire the email and attachments after '10 days' from protection.
2. Added support to automatically grant permissions to the email recipients on attachments that were protected before they were attached to the email.
1. Before the change: Auto-Protection Rules do not have any effect on emails and attachments that were protected before they were received by the Email Auto-Protector.
2. After the change: Auto-Protection Rules now grant permissions to recipients even on emails and documents that were protected before they were received by Email Auto-Protector..
3. Other Fixes.

Policy Server 3.7.3.0

1. Bug fixes

Java SDK 4.3.0.0

1. Added multi-lingual support.

Lite for Mac 3.3.5.0

1. Added automatic end user authentication via Windows Activity Directory (AD).
1. Before this change: Mac users were required to explicitly login to the Seclore agent at least once before accessing a protected document.
2. After this change: If a user is already logged in to a Mac computer using a Windows AD account, he/she will be automatically logged in to the Seclore agent as well.
3. Requires: The Mac computer to be registered in the enterprise Windows AD domain.
2. All new integration mechanism for protecting documents by native applications on the local computer.
1. New end point SDK provided to allow native applications on the local computer (like Classification tools) to protect documents using the Seclore agent.
2. Documents are protected with the logged-in user becoming the File Owner.
3. Added the ability to configure default protection permissions for protected content.
1. The following options can be configured: i) Default permissions for protected files and email attachments, and ii) Whether to protect the email body (for Email Protector).
2. These options can be configured in the Policy Server and can be changed by the protector before protecting files and emails.
3. Requires Policy Server 3.7.0.0.
4. Fixed the issue where protected messages were not displayed within the Outlook Window itself if the sender's email address had a capital letter.
1. Before the fix: If the sender's email address contains a capital letter e.g. John.doe@yourcompany.com, the protected email message (body) would not be displayed within the Outlook pane itself.
2. After the fix: This issue is now resolved.
5. Fixed the issue where an email message protected in Outlook on Mac was not displayed as expected within the message pane in Outlook on Windows.
1. Before the fix: If a user protected an email message i.e. email body, in Outlook on Mac and if the recipient accessed it in Outlook on Windows, it was not displayed as expected, within the Outlook pane itself.
2. After the fix: This issue is now resolved.
6. Fixed the rare issue where a file would not get protected if the logged in user had some special characters in the integrated identity management system integrated with Seclore.
1. Before the fix: In some rare cases, the user identity management system (Windows Active Directory, Tivoli etc.) integrated with Seclore had special characters in the additional fields like Organization Name, Department Name, Description etc.
2. In some cases these specific characters like ampersand , double quotes , single quotes etc. were causing a conflict with the Seclore integration.
3. After the fix: This issue is now resolved.
7. Other fixes.

Desktop Client 3.8.5.0

1. Added support for Exchange Shared Mailbox groups in the Email Protector for Outlook.
1. Before this change: If a protected email was sent from a Shared Mailbox (i.e. the Mailbox group is the Sender), it was not accessible to the other members of the group.
2. After this change: Any email that is either sent to or sent from a Shared Mailbox, will always be accessible to all its group members.
2. Enhanced the user experience of the Smart Sharing feature by switching ON the Smart Sharing button every time a new email is composed.
1. Before this change: If a user switched OFF Smart Sharing in an email and sent it, the next time he/she composes a new email, Smart Sharing would still be OFF.
2. Since Smart Sharing is switched OFF only in the rarest of cases, this would require the user to remember to switch it ON when composing the next email.
3. After this change: Every time a new email is composed, the Smart Sharing switch will always be ON.
3. Optimized the login process for authenticating with the Policy Server in the Email Protector for Outlook.
4. Re-designed and enhanced the intuitiveness of the user prompt in Email Protector for Outlook that reminds users to click on the Seclore It button.
5. Enhanced the user experience for opening unprotected documents in LibreOffice.
1. Before this change: When opening any document, the same system process was invoked that would reload the document content.
2. After this change: Unprotected documents will not be reloaded and will now open faster.
6. Fixed the issue where Right-click > Seclore It was not working in some rare cases where the Windows Temp folder was set to some very specific value.
1. Before the fix: In case the Temp folder was set to a value like 'C:\' or 'D:\', the Right-click > Seclore It feature was not working as expected.
2. After the fix: This issue has now been resolved.
7. Fixed the issue where a document could not be opened in Offline mode in certain rare cases. .
1. Before the fix: A protected document could not be opened in Offline mode i.e. without connectivity to the Policy Server, if the Policy Server ID contained an ampersand.
2. After the fix: This issue has now been resolved.

Policy Server 3.7.2.0

1. Added support for multi-lingual content in the HTML Wrapper when protecting emails in the Secure Email Viewer and Outlook on the Web (OWA).
2. Fixed the login issue for Hot Folder Server Admin console on Windows 2012 R2 and 8.1 with the latest March 2019 update from Microsoft.
1. Before the fix: A recent Windows patch update for Windows 2012 R2 and Windows 8.1, impacted the Admin login to the Hot Folder Server Enterprise Manager
2. This March 2019 Microsoft update for Windows 2012 R2 and 8.1 contained a change in the Microsoft encryption library that was used to login to the Hot Folder Server Enterprise Manager.
3. c) For more information refer to: https://support.microsoft.com/en-us/help/4489881/windows-8-1-update-kb4489881
4. After the fix: The changes have been made as per Microsoft recommendation and the issue is now resolved.
3. Fixed a rare issue in the Email Auto Protector Rule Console that was preventing some Rules to be displayed in the Rule List.

Seclore for Forcepoint DLP - Endpoint Protector 3.0.0.0

1. Significantly enhanced the user experience by making the logged-in user the File Owner of the protected document.
2. Requires:
1. Forcepoint DLP 8.5.2, 8.6 or higher, Windows 7, 8.1 or 10 and Seclore Desktop Client 3.8.3.0 (Seclore 3.10.3.0) or higher.
3. Expected Behavior:
1. Forcepoint DLP Discover is currently not able to scan content in documents larger than 100MB. So, Seclore protection will also not be invoked for these large documents.
2. Documents in a zipped archive file cannot be protected with Seclore, as of now.

Desktop Client 3.8.4.0

1. Fixed the issue in Outlook Email Protector when emails were Smart Shared, where recipients were not getting registered as new users if their email ID contained a single quote.

Lite for Windows 3.3.2.0

1. Enhanced support for Agentless access by preserving the HTML Wrapper even when the document is accessed using an agent.
1. Before this change: Whenever a user having a Seclore agent opens a protected document that is HTML Wrapped, the HTML Wrapper is removed, before it is opened.E.g. if a protected document sample.docx.html is opened using the Seclore Lite, the HTML Wrapper will first be removed, and the document will be renamed to sample.docx before it is opened
2. After this change: When sample.docx.html is opened, the HTML Wrapper will NOT be removed, and the document will open in Read-only mode.
3. This document can be shared further with anyone who can easily access it without an agent installed.
4. Preserving the HTML Wrapper helps to keep it more accessible to external users who can directly open it in the browser without an agent.
5. Only if the user edits and saves the document, the updated version will be saved without the HTML Wrapper.

Lite for Mac 3.3.4.0

1. Significantly enhanced the security of protected documents by supporting watermarks in printouts.
1. Earlier even though a watermark was displayed on screen when viewing a protected document, it was not available on the printout.
2. Now onwards printouts of protected documents will always print the same watermark that is displayed on screen.

Lite for Windows 3.3.1.0

1. On a periodic basis, Seclore will discontinue support for older and obsolete platforms and applications to ensure that the risk to enterprise data is always under control.
1. Older versions of Operating Systems and Office applications that are no longer being supported by Microsoft are often a security threat to the enterprise.
2. At the appropriate time, Seclore discontinues support of such obsolete software components to ensure that they do not pose a threat to the enterprise data security program.
2. Added system controls in the Desktop Client to discontinue support for obsolete Operating System versions.
1. Discontinued support for Windows XP, Windows Vista and Windows Server 2003.
2. Any Desktop Client installed on either of the above-mentioned operating systems will not get upgraded automatically by the regular patch upgrade mechanism.
3. The agent will be frozen on the last supported version i.e. Desktop Client 3.8.
4. To get the Desktop Client to start upgrading again, install a newer (supported) Operating System and the latest version of the Desktop Client
5. Desktop Clients that are frozen at version 3.8 will be clearly indicated in the Agent Installation Report that is available to the System Admin in the Seclore Policy Server
6. Microsoft discontinued support for Windows XP in April 2014 and Vista in April 2017. Vista was also Microsoft's least accepted Windows version of all time
7. Microsoft discontinued support for Windows Server 2003 in July 2015

Desktop Client 3.8.3.0

1. Enhanced support for Agentless access by preserving the HTML Wrapper even when the document is accessed using an agent
1. Before this change: Whenever a user having a Seclore agent opens a protected document that is HTML Wrapped, the HTML Wrapper is removed, before it is opened.
2. E.g. if a protected document 'sample.docx.html' is opened using the Desktop Client, the HTML Wrapper will first be removed, and the document will be renamed to 'sample.docx' before it is opened.
3. After this change: When sample.docx.html is opened, the HTML Wrapper will NOT be removed, and the document will open in Read-only mode.
4. This document can be shared further with anyone who can easily access it without an agent installed
5. Preserving the HTML Wrapper helps to keep it more accessible to external users who can directly open it in the browser without an agent
6. Only if the user edits and saves the document, the updated version will be saved without the HTML Wrapper
2. Enhanced the new end point SDK released in version 3.8 to support integration with applications that run as a system process
1. New integration mechanism for protecting documents on the end point by applications like DLP and file scanning tools that run as background process at the system level.
2. Provides a better user experience by making the logged-in user the File Owner.
3. Fixed the issue where an unnecessary error message was being displayed when opening unprotected text and OpenOffice documents in Microsoft Office applications.
1. Before the fix: When a user attempts to open an unprotected text or OpenOffice document in Microsoft Word or Excel, an error message is displayed saying 'Seclore does not support viewing and processing of '.TXT' format in Microsoft Office'.
2. Simple workaround: Just clicking on the 'OK' button opens the file as expected.
3. After the fix: No such error message is displayed.
4. Minor UI alignment adjustment in the 'Seclore It' Outlook permission labels and checkboxes.
5. Added support for Russian language in the Issue Reporting tool.

Lite for Mac 3.3.3.0

1. Added support for the latest versions of Office 16.21 or higher, installed on the latest version of macOS 10.14 or higher.
2. Added multi-lingual support for the HTML buffer page that is embedded within the protected document.
1. Whenever a protected file is wrapped with HTML, the language of the embedded HTML page will depend on the local agent's language setting.
2. The Seclore agent's language is set during the installation process.
3. Fixed the issue where the Seclore icon in the menu bar was not showing as expected when the system restores from sleep (hibernate) mode.
4. Enhanced the message displayed to the user to set Seclore as the default browser.
1. Setting Seclore to the default browser helps to automatically open HTML-wrapped protected files in the native application, rather than redirecting the HTML file to the browser
2. The message displayed in the system prompt sounded a bit alarming to certain users who would hesitate to allow Seclore to be the default browser
3. The new message is much more intuitive, and users should have no hesitation to allow Seclore to be the default browser.

Policy Server 3.7.1.0

1. Enhanced the security of the password-based authentication process by increasing the minimum length of the user-defined password from 6 to 8 characters.
1. Before this release: New external users created in the Seclore Identity Management system have the option of setting a password after they verify their email address at least once.
2. Until this release, the minimum length of the password was 6 characters.
3. After this release: The user-defined password must now be a minimum of 8 characters.
4. Other mandatory requirements of at least 1 upper-case character, 1 special character and 1 number remain unchanged.
2. Added a new column in the Agent Installation Report to indicate if the Desktop Client is running on an obsolete version of the Windows operating system.
1. Before this release: The Seclore Desktop Client now has the capability to automatically de-activate itself if the Windows operating system (OS) version is not supported by Seclore.
2. Microsoft periodically discontinues the support of older Windows versions and stops providing patches and security updates.
3. Desktops that are running such obsolete OS versions are a threat to the security of the entire enterprise.
4. Seclore now ensures that agents installed on very old and obsolete versions of the Windows OS are automatically de-activated.
5. These desktops cannot be used to open Seclore-protected documents and will not be upgraded using the standard patch upgrade mechanism of the Seclore agents.
6. After this release: A new column is provided in the Agent Installation Report called 'Desktop Client Discontinued Status'.
7. Desktops that are running on a discontinued version of the Windows OS will show the value as 'Discontinued' in this column
3. Fixed the issue where setting the Watermark to a blank value was not supported.
4. Fixed the issue where the content in the HTML Wrapper was not being displayed in the user's language when the protected file is accessed in the Edge or Internet Explorer Browser.
1. Before the fix: Users with Spanish language enabled in their Edge or Internet Explorer Browser, were seeing the English version of the content in the HTML Wrapper.
2. After the fix: Spanish users will now see the Spanish version of the content in the HTML Wrapper, even when accessing it from Edge or Internet Explorer.

Identity Manager 3.1.3.0

1. Upgraded to the latest version of the LDAP directory server - OpenDJ 4.4.1

Seclore for Symantec DLP - Endpoint Protector 3.0.0.0

1. All new Seclore DLP connector that automatically protects sensitive content discovered by Symantec DLP on end user desktops.
1. This new component integrates with the Symantec DLP Endpoint Discover so that sensitive content identified by Symantec can be automatically protected by Seclore.
2. The Administrator can configure a DLP Rule to automatically protect documents with a Seclore Policy.
3. Symantec Endpoint Discovery agents will continuously scan end user desktops and detect any sensitive content that matches the Rule.
4. Once a Rule is triggered, the document is protected with the Seclore Policy configured in that Rule.
5. The logged-in user becomes the File Owner of the protected document.
6. Seclore protection can be tracked via the incident logs in the DLP Admin console.
2. Requires:
1. Symantec DLP Server 14.6, 15.1, 15.5 or higher
2. Symantec DLP Endpoint Agent 14.6, 15.1, 15.5 or higher
3. Windows 7, 8.1 or 10
4. Seclore Desktop Client 3.8.3.0 (Seclore 3.10.3.0) or higher
3. Supported File Formats:
1. Protection will only support the standard file formats supported by Seclore: Microsoft Office, RTF, CSV, PDF, Text, Open Office and Images.
4. Product Compatibility and Support:
1. Support is now discontinued for all earlier versions of this component.
2. Migration from older version is not possible.
5. Expected Behaviour:
1. Documents contained within a zipped (archived) will not be auto-protected by Seclore.

Desktop Client 3.8.2.0

1. On a periodic basis, Seclore will discontinue support for older and obsolete platforms and applications to ensure that the risk to enterprise data is always under control
1. Older versions of Operating Systems and Office applications that are no longer being supported by Microsoft are often a security threat to the enterprise.
2. At the appropriate time, Seclore discontinues support of such obsolete software components to ensure that they do not pose a threat to the enterprise data security program.
2. Added system controls in the Desktop Client to discontinue support for obsolete Operating System versions
1. Discontinued support for Windows XP, Windows Vista and Windows Server 2003.
2. Any Desktop Client installed on either of the above-mentioned operating systems will not get upgraded automatically by the regular patch upgrade mechanism.
3. The agent will be frozen on the last supported version i.e. Desktop Client 3.8.
4. To get the Desktop Client to start upgrading again, install a newer (supported) Operating System and the latest version of the Desktop Client
5. Desktop Clients that are frozen at version 3.8 will be clearly indicated in the Agent Installation Report that is available to the System Admin in the Seclore Policy Server
6. Microsoft discontinued support for Windows XP in April 2014 and Vista in April 2017. Vista was also Microsoft's least accepted Windows version of all time
7. Microsoft discontinued support for Windows Server 2003 in July 2015
3. Added system controls in the Desktop Client to discontinue support for Microsoft Office 2003.
1. Users will not be able to open Seclore-protected documents in Office 2003 applications.
2. Any newer version of Microsoft Office can be installed on the same desktop to open Seclore-protected documents.
3. Microsoft discontinued support for Office 2003 in April 2014. Office 2003 is also not compatible with Windows 8 or higher.
4. Added system controls in the Desktop Client to discontinue support for Adobe Acrobat Reader 8 and 9.
1. Users will not be able to open Seclore-protected PDF documents in Acrobat Reader 8 or 9.
2. Adobe discontinued support for Acrobat Reader 9 in June 2013 and version 8 even earlier.

Desktop Client 3.8.1.0

1. Fixed the installation issue that occurs when the operating system language is set to anything other than English.

Desktop Client 3.8.0.0

1. All new end point SDK provided to simplify the end point protection process and make it more efficient.
1. New integration mechanism for protecting documents on the end point by applications like Classification and DLP tools
2. Provides a better user experience by making the logged-in user the File Owner.
3. Simplifies the integration process for any end point application to protect with Seclore.
2. Updated Seclore Email Protector for Outlook to make it compatible with Seclore Protector for Data Classification 3.1.0.0, which can automatically protect documents classified using Boldon James Email Classifier.
3. Added the ability to configure default protection permissions for protected content.
1. The following options can be configured: i) Default permissions for protected files and email attachments, and ii) Whether to protect the email body (for Email Protector)
2. These options can be configured in the Policy Server and can be changed by the protector before protecting files and emails.
3. Requires Policy Server 3.7.0.0.
4. Fixed the rare issue where an unprotected Excel file could not be opened from a folder synced to OneDrive.
5. Fixed the issue where only the first few pages of very large, multi-page PDF documents would be printed.

Seclore Protector for Data Classification 3.1.0.0

1. Launched the all new Seclore Integration Component for automatically protecting documents classified by the Boldon James Email Classifier.
1. Once an email is classified, both email and attachments can be protected automatically, by configuring a Seclore Policy mapped to the Classification label.
2. The user composing/replying/forwarding the email (i.e. the one logged-in to Desktop Client) becomes the owner of the email and attachments.
3. Introduced a new protection type called 'self' (which if mapped to classification label) will make the email sender the Owner and assign permissions to the email recipients (if Smart Sharing is ON).
2. Launched the all new Seclore Integration Component for automatically protecting documents classified by the Boldon James File Classifier.
1. Once a document is classified using Right-click > Classify, it can be protected automatically, by configuring a Seclore Policy mapped to the Classification label.
2. The user classifying the document (i.e. the one logged into Desktop Client) becomes the File Owner.
3. Introduced a new protection type called 'self', which if mapped to the Classification label, will make the logged-in user the File Owner. No other users will have permissions on the document unless it is explicitly Shared with them.
3. Enhanced the Seclore Integration Component for automatically protecting documents classified by the Boldon James Office Classifier.
1. The user classifying the document (i.e. the one logged into Desktop Client) becomes the File Owner.
2. Introduced a new protection type called 'self', which if mapped to the Classification label, will make the logged-in user the File Owner. No other users will have permissions on the document unless it is explicitly Shared with them.
4. Requires:
1. Boldon James Classifier Administrator 3.14 or higher.
2. Microsoft .NET Framework 4.7.1 or higher.
3. Office Classifier and Email Classifier 3.14 or higher.
4. File Classifier 3.11.1 or higher.
5. Windows 7, 8, 8.1 or 10.
6. Microsoft Office 2010 or higher.
7. Seclore Desktop Client 3.8 (Seclore 3.10) or higher.
5. Supported File Formats:
1. For integration with Email and File Classifier: All Microsoft Office files, PDF files, Image files, and Open Office files supported by Seclore.
2. For integration with Office Classifier: All Microsoft Office files supported by Seclore.
6. Expected Behavior:
1. Documents classified before Seclore Protector for Data Classification is deployed will be auto protected whenever they are opened and closed.
2. A user needs a Classification license to Classify documents and a Protector license for them to be automatically protected. Without a Protector license, documents will not be protected.
3. Changing the Classification for protected documents or emails will not change protection parameters.

Seclore Lite for Windows 3.3.0.0

1. Added the ability to configure default protection permissions for protected content.
1. The following options can be configured: i) Default permissions for protected files and email attachments, and ii) Whether to protect the email body (for Email Protector).
2. These options can be configured in the Policy Server and can be changed by the protector before protecting files and emails.
3. Requires Policy Server 3.7.0.0.
2. Fixed the rare issue where the on-screen watermark was not displayed for protected documents of TXT and other ASCII-based formats.
3. Fixed the issue where only the first few pages of very large, multi-page PDF documents would be printed.

Policy Server 3.7.0.0

1. Provided the capability to set the default Permissions used in all the protection screens.
1. Before this release, the Permissions (Read, Edit etc.) displayed by default when protecting a new email/document or adding a user to a Policy, were fixed.
2. These default permissions are now configurable in the Admin console.
3. While protecting a new email/document or adding a new user to a Policy, the initial Permissions displayed on the screen will be as per the Admin configuration.
4. Enterprises can change these default Permissions whenever required, as per their business needs.
5. Product screens that automatically display the default permissions based on the Admin configuration include: Right-click > Protect, Right-click > Change Permissions, Email Protector ('Seclore It' button in Outlook), Email Protector in Outlook on the Web (OWA) and the Policy Definition page.
6. Features that give Permissions automatically to users will also use these default permissions. These include: Request Access Permissions and Smart Share.
2. Provided the capability to set 'Protect Body' checkbox to 'On' by default in Email Protector for Outlook.
1. Before this release, the 'Protect Body' checkbox in the Email Protector for Outlook, was always Off by default.
2. This default value is now configurable in the Admin console.
3. By keeping this On, Enterprises can enable end users to protect the Body of their email messages with just One-click i.e. 'Seclore It'.
3. Added the capability to filter out certain users when syncing users from a Windows Active Directory to the Policy Server.
1. Before this release, it was not possible to filter out users when syncing user data from a Windows Active Directory (AD).
2. Now it is possible to define attribute level filters to ignore users and groups when syncing them from Windows AD.
4. Migrated Google Authentication from the Google+ APIs to the newly recommended Google APIs.
1. Google is shutting down the Google+ service and the Google+ Authentication APIs.
2. They have recommended all existing applications to migrate to their new Google APIs.
3. Now onwards the Seclore Policy Server will authenticate with the recommended Google APIs.
4. On-premise installations using Google Authentication will need to be re-configured to ensure they continue to function as expected.
5. Cloud installations will be migrated automatically.
6. Contact Seclore Support (support@seclore.com) for help on this front.
5. Added multi-lingual support for the content displayed in the HTML Wrapper for any protected document.
1. Before this release, the instructions displayed to a recipient for opening a Seclore-protected document in the browser, were dependent on the locale settings of the Protector.
2. Now onwards the instructions will be displayed based on the locale and language settings of the Recipient.
6. Fixed an issue in the Rule Console for the Email Auto Protector, where the date expiry value was getting dropped from a Rule when it was being used with any language other than English.
7. Minor corrections in the Russian translation for content displayed in the end-user web portal.

Seclore Email Auto Protector 3.0.0.0

1. Fixed an issue where Email protection fails when Sender does not exist in the repository.
1. Email is protected even if the Sender does not exist in the repository and default owner is made the owner.
2. Email sender is given Full control access on the protected email..
2. Fixed performance issues due to number of threads available for change of permissions by using new restructured SDK.
3. Provided support to identify protected email body attachments while forwarding an email protected through Seclore Email Auto Protector from Outlook with Seclore agent to avoid usability issues.
4. Changed activity comment from 'protected by Exchange connector' to 'protected by Seclore Email Auto Protector'.
5. Fixed an issue with expiry date when set Default Owner becomes the owner of the email protected through Seclore Email Auto-Protector.

Seclore for Symantec DLP : Content Scanner 3.0.0.0

1. Added support for Symantec DLP Detection Server installed on Linux.
1. Before this release, content scanning was supported only for Symantec Detection Server installed on Windows.
2. Now, Symantec Detection Server installed on Linux is also supported.
2. Requires:
1. Symantec DLP Detection Server 14.6, 15.1 or higher.
2. Windows Server 2012 R2, 2016 or higher.
3. Red Hat Enterprise Linux 6.8 or higher.

Seclore Decryption Server 3.0.0.0

1. Added support to provide decryption as a service for Seclore protected documents on Linux.
1. Before this release, decryption as a service was supported only on Windows.
2. Now, decryption as a service is also supported on Linux.
2. Decryption Server now supports the following operating systems:
1. Windows Server 2012R2, 2016 and higher.
2. Red Hat Enterprise Linux (RHEL) 7.6 and higher.
3. CentOS 7.6 and higher.
4. Java 11 and higher.
5. Tomcat 9 and higher.
3. Requires: Policy Server 3.6 or higher

Server SDK : Java 4.2.1.0

1. Improved performance by optimizing system memory utilization.

Desktop Client 3.7.3.0

1. Fixed the issue where Outlook meeting invites were not sent on synchronization when the 'Send immediately when connected' option was unchecked.
1. Before the fix: When the 'Send immediately when connected' option is OFF, the meeting invite was not sent even after synchronization.
2. After the fix: Users will now be able to send meeting invites even when this option is turned OFF.
2. Fixed the rare issue where the Compose window continued being displayed even after a protected email was sent.
3. Fixed the issue where Seclore Email Protector callout tutorial in the Outlook Compose window becomes transparent in the presence of existing text in the background (email body).

Lite for Windows 3.2.4.0

1. Fixed the issue where Outlook meeting invites were not sent on synchronization when the 'Send immediately when connected' option was unchecked.
1. Before the fix: When the 'Send immediately when connected' option is OFF, the meeting invite was not sent even after synchronization.
2. After the fix: Users will now be able to send meeting invites even when this option is turned OFF.
2. Fixed the rare issue where the Compose window continued being displayed even after a protected email was sent.
3. Fixed the issue where Seclore Email Protector callout tutorial in the Outlook Compose window becomes transparent in the presence of existing text in the background (email body).

Lite for Mac 3.3.2.0

1. Bug fixes.

Policy Server 3.6.2.0

1. Fixed the issue where the predictive user search did not work as expected if the search results exceeded 1000 users.
1. Before the fix: The search results were not displayed - and an incorrect message was displayed instead - if the search results exceeded 1000 users.
2. After the fix: There is no maximum limit to the displayed search results.

Identity Manager 3.1.1.0

1. Bug fixes.

Lite for Mac 3.3.1.0

1. Fixed the issue in Outlook version 16.18 and above where the Email Protector options were not displayed as expected.
1. Before the fix: Microsoft had released an update (version 16.18) in October 2018, that caused a conflict with the Seclore Email Protector plugin.
2. Due to this, end users were not seeing the 'Seclore It' button in Outlook when composing a new email.
3. After the fix: This has now been fixed and is working as expected.
2. Fixed the issue in the latest Office version 16.20 released on 26th of November where protected files were not opening as expected.