Release Notes

Introduction

The release notes provide brief and high-level descriptions of the new features of HaloCAD. Before installing HaloCAD, it is recommended to read the release notes to understand any current limitations or bugs that may apply to this version of the software.

Product Description

HaloCAD acts as the guardian of your CAD files by automatically protecting them with Microsoft Purview Information Protection (MPIP) labels whenever they leave your secure IT perimeter. As a plug-in for CAD applications, HaloCAD offers access to MPIP-protected files, including label handling and privilege enforcement. CAD users will not notice any differences in the handling of CAD files because protection takes place in the background. By seamlessly attaching MPIP labels to the CAD files while they are being created, it provides end-to-end security for those files.

System Requirements

The following system requirements table outlines the minimum and recommended technical specifications, including software and network requirements, necessary to run the product.

Requirements

Supported CAD applications for HaloCAD Add-ons

You are currently viewing the release notes for the current build. For previous versions, please refer to their respective release notes.

CAD applications and HaloCAD Add-on version

Prerequisites

Before installing the add-on, ensure that the following prerequisites are met:

1. An application is registered with Microsoft Entra ID.

2. An active Office 365 subscription is available.

3. Access to the recommended URLs is enabled.

4. TLS 1.2 or later is enabled on all client workstations to ensure secure communication.

For more information, refer to the Technical Reference Manual.

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 static 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 

1. A = 0 Bugs

2. B = at least 1 Minor Bug

3. C = at least 1 Major Bug

4. D = at least 1 Critical Bug

5. E = at least 1 Blocker Bug

Security Rating

1. A = 0 Vulnerabilities

2. B = at least 1 Minor Vulnerability

3. C = at least 1 Major Vulnerability

4. D = at least 1 Critical Vulnerability

5. 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.

1. A = >= 80%

2. B = >= 70% and <80%

3. C = >= 50% and <70%

4. D = >= 30% and <50%

5. 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 alternatively stated by saying that if the outstanding remediation cost is:

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

2. Between 6 to 10%, the rating is a B

3. Between 11 to 20%, the rating is a C

4. Between 21 to 50%, the rating is a D

5. Anything over 50% is an E

Build 2.4

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

There are no new features to highlight in this release.

Improvements

This section lists the improvements in the current release.

1. Added default values for silent command-line parameters.

2. Added support to display online documentation directly from the installer UI for both the standard and Reader add-on installers. When the Online Help button is clicked, the online documentation now opens in the user's default browser. HCADNX-617

3. Improved token-sharing encryption and FIPS compatibility by ensuring proper OpenSSL FIPS context initialization and preventing failures in child processes during configuration decryption. HCADNX-618

4. In previous releases, asterisks were used in MIP SDK logs to mask Personally Identifiable Information (PII), such as email names and IP addresses. This feature is now extended to HaloCAD logs to also mask information such as label name, label ID, engine ID, policy ID, and watermark text. HCADNX-622

5. Added support for NX version 2506. HCADNX-622

6. Added support for NX version 2412. HCADNX-620

Fixed Issues

This section provides a list of the fixed issues in the current release.

1. Fixed an issue where design contents from a protected part file could be copied to another file. HCADNX-142, HCADNX-159

2. Fixed an issue where label details were not displayed when importing a protected IGS file into a new file using the File → Import option. HCADNX-519

3. Fixed an issue where the HaloCAD Least Permission pop-up was not displayed, and protected assembly files imported using the Assemble option were treated as unprotected, allowing save/export without protection. HCADNX-623

Known Issues

This section describes the known issues with the current release.

1. Standard NX Password-protected files are not supported. HCADNX-21 

2. It is possible to copy or share protected files with view-only rights when using the following options: Copy Geometry to Part and Create Linked Part. HCADNX-212, HCADNX-214

3. Reader: When a protected part file is cloned from an assembly file, the newly cloned part file will not be protected. HCADNX-156

4. When the Assembly Load Option is set to Fully Load in Teamcenter-integrated NX, sensitivity is displayed as “Not Set,” and all editing options are enabled for dependent protected part files.HCADNX-241

5. Exported PDF, DWG, and part files remain protected and can be opened by valid users even after the primary protected document is revoked. HCADNX-288

6. Users can modify a protected assembly file with view rights using the Constraints option. HCADNX-304

7. The Revoke Access button is disabled when opening an NX file from Teamcenter with a Super User account. HCADNX-312

8. An unknown system error occurs when saving an assembly file. HCADNX-335

9. With TLS disabled, the HaloCAD information pop-up repeats, and the Microsoft sign-in dialog does not appear, preventing sign-in. This issue occurs when opening NX with protected files in the Recent Files list. HCADNX-417

10. Intermittently, the HaloCAD Add-on for NX installation fails. Workaround: Clear the MPIP and HaloCAD DLLs from NXBIN. HCADNX-458

11. When a protected file is opened, its label is automatically applied to new files created in the same session with Teamcenter integration. HCADNX-489

12. Screenshot capture is not restricted for protected files accessed from the Recent Documents list. HCADNX-589

Unsupported Versions

Support for NX 2306 and 2312 is removed in this release. HCADNX-619

Function as Designed

The license is activated only for the user who performed the activation and is not shared with other users on the same system. HCADNX-602

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