Release Notes

Introduction 

This release notes offer brief, high-level descriptions of the new features of HaloSHARE. We recommend looking through these release notes before installing HaloSHARE to understand any current limitations or bugs that apply to this version of the software. 

Product Description

Secude's HaloSHARE streamlines and secures your internal and external business operations by simplifying bulk file management with classification, labeling, encryption, and digital watermarking. HaloSHARE extends Microsoft Purview Information Protection (MPIP) to CAD, MS Office files, and non-office formats, such as text and PDF files stored in shared folders, encrypting sensitive data with customizable sensitivity labels that can be tracked, revoked, and set to expire.

System Requirements

The following system requirements table specifies the minimum and recommended technical specifications, such as software and network resources, necessary to run the product.

Requirements

Recommended URLs, Addresses, and Ports for MPIP

MIP SDK doesn't support the use of authenticated proxies. So, make sure you set the Microsoft 365 service endpoints to bypass the proxy. View a list of endpoints at Microsoft Online Documentation . However, Microsoft recommends the following:

Recommended endpoints

Secude License Manager

To communicate with Secude License Manager, the following URL and port must be whitelisted in the customer's proxy:

Recommended license manager endpoint

Code Quality and Security

Secude focuses on software quality and security. This is accomplished by adhering to and exceeding best practices in development, testing, and quality control. Secude has chosen SonarQube as the first building block for building and implementing a robust continuous code quality assurance (QA). SonarQube is a platform for statical code analysis for continuous inspection of code quality. It performs automatic reviews of code to detect bugs, code smells, unit test coverage, and security issues in 29 programming languages.

SonarQube is utilized throughout the development process at Secude and only the highest marks are accepted for a product to be released. It helps to regulate code quality from the beginning of development, find and repair issues promptly, and improve overall software stability.

Each build report can be found under its relevant version heading in this release notes.

Reliability Rating 

• A = 0 Bugs

• B = at least 1 Minor Bug

• C = at least 1 Major Bug

• D = at least 1 Critical Bug

• E = at least 1 Blocker Bug

Security Rating

• A = 0 Vulnerabilities

• B = at least 1 Minor Vulnerability

• C = at least 1 Major Vulnerability

• D = at least 1 Critical Vulnerability

• E = at least 1 Blocker Vulnerability

Security Review Rating 

The Security Review Rating is a letter grade based on the percentage of Reviewed (Fixed or Safe) Security Hotspots.

• A = >= 80%

• B = >= 70% and <80%

• C = >= 50% and <70%

• D = >= 30% and <50%

• E = < 30%

Maintainability Rating 

A=0-0.05, B=0.06-0.1, C=0.11-0.20, D=0.21-0.5, E=0.51-1

The Maintainability Rating scale can be alternately stated by saying that if the outstanding remediation cost is:

• <=5% of the time that has already gone into the application, the rating is A

• between 6 to 10% the rating is a B

• between 11 to 20% the rating is a C

• between 21 to 50% the rating is a D

• anything over 50% is an E

Build 3.1

This chapter provides an overview of the updates and quality insights included in this release. It covers the fixed issues, improvements, limitations, new features, and known issues, along with a summary of SonarQube’s key parameters to highlight code quality metrics and analysis results.

New Features

This section highlights the new features in the current release.

1. Supports Controlled Unclassified Information (CUI) marking with either Limited Dissemination Control (LDC) or Distribution Statement (DS). Both options cannot be applied to the same file simultaneously; however, either LDC or DS can be applied together with the watermark option. The values for the CUI designation indicator block are populated on the document’s first page based on the configuration settings. HSHARE-273

2. Support for Watermarking in AutoCAD and Revit 2026 files. HSHARE-339

Improvements

This section lists improvements added to the current release.

Previously, HaloSHARE moved all files from the Supplier (Source) folder to the Destination folder, regardless of configuration. With this release, the behavior has been improved, only the configured file types are moved to the Destination folder, while unconfigured files remain in the Source folder. HSHARE-8

Limitations

This section lists the limitations of the current release.

1. A digitally signed PDF cannot be encrypted. This is due to the limitation that the MIP SDK does not support a signed PDF for encryption. Thus, HaloSHARE applies watermark visuals to a file when it is no longer eligible for encryption via the MIP SDK. HSHARE-285

2. HaloSHARE cannot watermark any file type that is password-protected. For example, an XLSX worksheet with a protected sheet or a PDF is password-protected.

3. By default, HaloSHARE-watermarked text appears diagonally on a file, however, the Revit application does not allow diagonal watermarking, therefore, the watermark is displayed horizontally.

4. HaloSHARE supports watermarking in CAD applications; however, as CAD applications do not have a built-in watermark feature, the watermark text will only be visible when a CAD add-on like HaloCAD is used. In this case, we recommend installing the HaloCAD Add-on on a separate system that is not running HaloSHARE. HSHARE-293

5. Many enterprises enforce a Group Policy Objects (GPO) that requires all outbound internet traffic routed through a proxy server. These proxy settings need to be used by both the MIP SDK and the MSAL library for MPIP authentication and functionalities. To use proxy settings for the MSAL library, we need to set the msal_proxy_address in HKEY_LOCAL_MACHINE\SOFTWARE\Secude\HaloSHARE.
   If the above does not work for service-running users, in such cases, set the registry keys ProxyServer and ProxyEnable in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings. For more information, refer to the Proxy Configuration section of the Installation and Configuration Manual. HSHARE-307

6. CUI marking behavior: Currently, CUI marking is updated in the file only when the CUI marking feature is enabled in the license. However, CUI marking values may still appear in the file’s custom properties even if the feature is not enabled. This is the current behavior and will be addressed in the next release. HSHARE-340

Fixed Issues

This section lists the fixed issues in the current release.

Fixed an issue that prevented watermarking text from being applied to PDF/XLSX/PPTX files. HSHARE-169

Known Issues

There are no known issues to list.

Quality Gate Report

Please see the table below for a list of SonarQube's key parameters for this version. Refer to the " Code Quality and Security " section for more information on rating definitions.

Quality Gate report