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

Autodesk 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

This section lists the new features in the current release.

Added support for Inventor integration with Teamcenter. HCADINV-710, HCADINV-712

Improvements

This section lists the improvements in the current release.

1. Improved handling of library files during protection: Added support to exclude library files referenced in assemblies (from Library and Content Center) from protection. When prompted by HaloCAD, you can choose No to skip protection or Yes to apply protection. HCADINV-703

2. Added default values for silent command-line parameters. HCADINV-709

3. 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. HCADINV-708

4. Improved token-sharing encryption and FIPS compatibility by ensuring proper OpenSSL FIPS context initialization and preventing failures in child processes during configuration decryption. HCADINV-706

5. Enhanced assembly performance by caching MPIP protection information for files with the same ContentId. HCADINV-716

6. Added validation of the encrypted data file after label application to ensure correct labeling and data integrity, with user notification and a relabel prompt if verification fails. HCADINV-704

7. 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. HCADINV-724

Fixed Issues

This section lists the fixed issues in the current release.

1. Fixed an issue where the enablefipsmode flag remained set to true in the registry even after the FIPS option was unchecked. HCADINV-700, HCADINV-731

2. Fixed an issue where files such as DXF, DWG, IGES, STEP, and SAT generated using Flat Pattern → Save Copy As were not protected. HCADINV-722

3. Fixed an issue where DXF export intermittently fails when saving using Flat Pattern → Save Copy As → DXF. HCADINV-721

4. Fixed an issue where an incorrect label was applied to an exported 3D PDF when the file was replaced on disk after opening. HCADINV-717

5. Fixed an issue where the label and status were not updated after successfully protecting exported IGES/STEP files. HCADINV-731

6. Fixed an issue where the Inventor application crashed while exporting an RVT file from a protected or unprotected assembly using the Export option. HCADINV-732

7. Fixed an issue where the label and status were not updated after successfully protecting exported SAT files. HCADINV-734

8. Fixed an issue where files were protected, but the label and status were not updated in STEP/SAT files. Additionally, the top-level label was incorrectly applied to dependent files during export. HCADINV-735

9. Fixed an issue where the Inventor application crashed while opening STL or OBJ files. HCADINV-736

10. Fixed an issue where a protected SMT file opened without the configured label when opened in an assembly using Option mode, while it opened correctly using Multibody Part and Composite Feature Part options. HCADINV-737

11. Fixed an issue where an incorrect HaloCAD pop-up was displayed when saving an assembly file with a custom permission label. HCADINV-739

Known Issues

This section lists the known issues in the current release.

1. It is possible to capture a preview of a protected file (with “view” only rights) using the PrntScrn and Snipping tool. HCADINV-108

2. An error message, “Drawing file is not valid," will appear when trying to import a protected DWG file by clicking the Next button in the DWG/DXF file wizard. HCADINV-402

3. When trying to open a protected file, the Inventor application enters the Not Responding state if the User cache with a Custom cloud type configuration is not accessible. HCADINV-452

4. When attempting to open a protected STL file, the design will not be displayed, and the file will be opened without protection. HCADINV-569

5. When a connected user with Edit/Co-Author permissions saves an Assembly file, the HaloCAD information window does not display, and the top-level Assembly file label is not applied to the newly imported unprotected dependent part file. HCADINV-629

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