Technical Reference Manual
Introduction
Companies across industries, such as automotive, aviation, high tech, and even fashion, create and manage their intellectual property (IP) based on drawings. These drawings are created digitally using computer-aided design (CAD) applications and are shared with users outside the organization owing to business considerations. It's essential to understand the potential risks associated with sharing business information. By implementing comprehensive security measures you can significantly reduce the risks and safeguard your data.
How does HaloCAD Protect your Data?
HaloCAD effortlessly integrates Microsoft Purview Information Protection (MPIP), formerly known as Microsoft Information Protection (MIP), the leading technology for Enterprise Digital Rights Management (EDRM). It acts as a shield for your CAD files by automatically labeling them with MPIP and manages data assets across your environment. 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 they take 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.

HaloCAD Add-on for CAD applications
About this Manual
This guide describes how to set up your environment, the technical requirements for HaloCAD, and in-depth explanations to enable administrators to install and configure the HaloCAD Add-on successfully.
This is the main document that administrators should read before installing the HaloCAD add-on. Following that, read the installation and operations manuals.
Features
Business infrastructure: HaloCAD connects effortlessly with existing infrastructure, making it simple to use and manage.
CAD: HaloCAD add-on seamlessly extends MPIP security to CAD files.
Usage rights: Both template-based (or static) labels and user-defined (custom permissions) labels are integrated for seamless protection.
Data security: Sensitive information is protected persistently regardless of where it is moved, including mobile and cloud platforms.
Data Access and Usage: Policy enforcement for managing sensitive file access and usage.
Policies specify who has access to sensitive files and what actions they can do with them.
Furthermore, it specifies how data may be used, such as restrictions on viewing, editing, copying, printing, exporting, relabeling, or modifying the rights. Watermarks can be applied to documents that contain sensitive information.
Quick Start Installation Summary
The following image shows the high-level idea of setting up HaloCAD.

HaloCAD quick start installation steps
Reference Manuals
The table below describes where to obtain information in the HaloCAD documentation set.
For information on | Name of the Reference |
---|---|
| Please refer to the current manual. |
How to install HaloCAD Add-on. | Refer to the Installation Manual for the add-on you purchased. |
HaloCAD features and troubleshoot if you face any issues. | Refer to the Operations Manual for the add-on you purchased. |
What’s new, fixed, and known issues. | Refer to the Release Notes for the add-on you purchased. |
HaloCAD documentation
HaloCAD Architecture
HaloCAD is available in three variants:
HaloCAD Add-on for CAD—A standalone solution that contains the HaloCAD PROTECT feature. It enables CAD applications to use MPIP directly with user interaction.
HaloCAD for PLM—This solution includes HaloCAD PROTECT and MONITOR capabilities and interacts with the respective PLM application. HaloCAD for PLM actively monitors file access, upload, and download events while running in the background. During a file upload, HaloCAD examines to see if the file is already encrypted, and if so, it decrypts and then allows the file to get check-in to the PLM Vault. In the event of a file access/download, the selected file is automatically protected. HaloCAD operates independently throughout the check-in and check-out process following the rules stated in the Classification Engine.
For comprehensive details, please refer to the respective manuals as per your PLM environment:
If your environment is integrated with Windchill PLM, you must refer to the HaloCAD for Windchill Installation Manual.
If your environment is integrated with Teamcenter PLM, you must refer to the HaloCAD for Teamcenter Installation Manual.
If your environment is integrated with Autodesk Vault PLM, you must refer to the HaloCAD for Autodesk Vault Installation Manual.
If your environment is integrated with SOLIDWORKS PDM, you must refer to the HaloCAD for SOLIDWORKS PDM Installation Manual.
HaloCAD Extension—HaloCAD extends its support to read the MPIP-protected files through a free-of-charge standalone HaloCAD Reader Add-on.
HaloCAD Add-on for CAD
HaloCAD Add-on for CAD leverages Microsoft Purview Information Protection solution to provide persistent document security. During the process of creating a new CAD file, the user downloads MPIP labels using valid credentials, selects a suitable label, and applies it to the file. In the standalone add-on, there is no automation available here as setting labels takes place manually. Protected files can only be opened and modified by authorized users and thus, protection remains even when the file is accessed by multiple users. The user’s rights are governed by pre-established policies. The following figure shows the HaloCAD Add-on for CAD as a standalone add-on.

HaloCAD as a standalone add-on
HaloCAD Reader Add-on for CAD
Secude offers a standalone reader add-on for the CAD application that allows you to view MPIP-protected files containing sensitive data. It enforces ‘read-only’ privileges to all users and thus even authorized users cannot sneak sensitive information out by copying it or taking a screenshot. Additionally, it does not support the setting or modification of labels. The following figure shows the HaloCAD Reader Add-on for CAD. Note: When a HaloCAD MPIP-protected file is shared with partners/suppliers, they don't need to install HaloCAD Add-on for CAD on their machines, instead just this simple reader add-on is sufficient.

HaloCAD Reader Add-on for CAD
Microsoft documentation
This manual assumes that you already have a complete setup of Microsoft Purview Information Protection and you are familiar with using the Microsoft Purview portal and related concepts. If you are new, you can refer to Microsoft's online documentation for setup and configuration.
Prerequisites
The prerequisites and dependencies for installing and configuring the HaloCAD add-ons are summarized in this section.
Register an Application in Microsoft Entra ID
This section will guide you through the steps of registering an application, obtaining the Client ID and Directory ID, and assigning permissions to the application.
Microsoft documentation
Any application to authenticate via Microsoft Entra ID must be registered in its directory. The information in the Microsoft documentation overrides any information published in this section. Please refer to Microsoft documentation for a comprehensive description.
For demonstration purposes, an application is created in the Azure portal; alternatively, you may create an application using https://entra.microsoft.com.
Create an Application
Follow the instructions below to register an application:
Sign in to the Microsoft Azure portal using an account with administrator permission.
On the portal's Home page, under Azure services, or on the left side of the navigation pane, choose Microsoft Entra ID.
Selecting Microsoft Entra ID
On the Overview page, in the left navigation pane, click App registrations.
On the App registrations page, select New registration or Register an Application (this button appears only if no applications have already been created).
New application registration
On the Register an application page, enter your application's registration information.
Public client application details
In the Name section, enter a meaningful application name.
Under Supported account types, select which account you would like your application to support. For detailed information on these types, please see Microsoft documentation.
To target only accounts that are internal to your organization, select Accounts in this organizational directory only.
To target only business or educational customers, select Accounts in any organizational directory.
To target the widest set of Microsoft identities and to enable multitenancy, select Accounts in any organizational directory and personal Microsoft accounts.
To target the widest set of Microsoft identities, select Personal Microsoft account only.
Under Redirect URI: Select Public client/native (mobile & desktop), and then type a valid redirect URI for your application. For example,
https://localhost
.When finished, click Register.
An overview page for the new application registration is created and displayed.
Application ID and Tenant ID
The following values are shown on the portal once registration is complete. To copy and save the ID value in a text editor, hover your cursor over it and click the Copy to clipboard icon.
Application ID – It is also referred to as Client ID.
Directory ID – It is also referred to as Tenant ID.
Save the authentication parameters
In a text editor (such as Notepad), copy the values of Application (client) ID, Directory (tenant) ID, and Redirect URI, and save it for initializing the HaloCAD application. Directory (tenant) ID is needed only for single-tenant applications.
Add Required Permissions
To protect content using MIP SDK, you need to provide the following API permission(s) for the created application ID.
In the sidebar of the new application page, select API permissions. The API permissions page for the new application registration will appear.
Click Add a permission button. The Request API permissions page will appear.
Under the Select an API setting, select APIs my organization uses. A list appears, containing the applications in your directory that expose APIs.
Type in the search box or scroll to find the required API that is mentioned in the below table “Required Permissions”.
For example, type "Microsoft Information Protection Sync Service". You can see the API listed as shown in the below figure:
Searching permissions
Now, click on the displayed API. You can see two permissions on the page − Delegated permissions and Application permissions.
Click Delegated permissions button and then, under the Permission section, select the check box against "Read all unified policies a user has access to".
Adding permission
Click Add permissions. (Repeat the steps outlined above to add the other required permissions listed in the table below.)
You will return to the API permissions page, where the permissions have been saved and added to the table.
API Required permissions
Click Grant admin consent for your company button. You will be prompted to accept the consent confirmation; click Yes to the question.
The following table lists the required permissions.
API / Permission name | Display Name | Type | Description |
---|---|---|---|
Azure Rights Management Services (Microsoft Rights Management Services) |
| Delegated | Create and access protected content for users |
Microsoft Graph |
| Delegated | Sign in and read user profile (will be added by default) |
Microsoft Information Protection Sync Service |
| Delegated | Read all unified policies a user has access to. |
Required permissions
Create and Configure the Sensitivity Labels
As an administrator, you can create, configure, and publish sensitivity labels for various levels of content sensitivity based on your organization's classification taxonomy. Use names or terms that are familiar to your users. Consider starting with label names like Personal, Public, General, Confidential, and Highly Confidential if you don't already have a taxonomy in place. For more details, please refer to Microsoft online documentation.
Office 365 Subscription Details
Fully configured Microsoft Purview Information Protection.
An Azure subscription is required to use Azure RMS and the MPIP functionality.
A working Microsoft Entra ID service must be available.
Transport Layer Security (TLS) 1.2 or higher must be enabled to ensure the use of cryptographically secure protocols at all client workstations. Please refer to the section “Enable Support for TLS 1.2 at the Client Workstation for Microsoft Entra ID”.
To avail revoke access feature, the user should be assigned to Microsoft Purview Information Protection Premium P1/P2 license. (Not required for reader add-on)
Audit logging: Your Azure subscription must include Log Analytics on the same tenant as Microsoft Entra ID.
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 endpoints to bypass the proxy. View a list of endpoints at “Microsoft Online Documentation”. However, Microsoft recommends the following:
Addresses | Ports |
---|---|
| TCP 443 |
| TCP 443 |
For event logging
| TCP 443 |
National Cloud | Microsoft Entra ID authentication endpoint |
Microsoft Entra ID for the US Government |
|
Microsoft Entra ID (global service) For details on Microsoft Entra ID endpoints, please refer to “Microsoft Online Documentation”. |
|
Recommended endpoints
Secude License Manager for HaloCAD
To communicate with Secude License Manager for HaloCAD, the following URL and port must be whitelisted in the customer's proxy:
Address | Port |
---|---|
License API - api.licensespring.com | TCP 443 |
Recommended license manager endpoint
Enable Support for TLS 1.2 at the Client Workstation for Microsoft Entra ID
To improve the security posture of the tenant, and to remain in compliance with industry standards, Microsoft Entra ID stopped supporting the following Transport Layer Security (TLS) protocols and ciphers:
TLS 1.1
TLS 1.0
3DES cipher suite (TLS_RSA_WITH_3DES_EDE_CBC_SHA)
In order for the HaloCAD for CAD add-on to be able to authenticate to Microsoft Entra ID, TLS 1.2 must be activated on the respective client workstation. Please see this Microsoft article to enable TLS 1.2.
Microsoft documentation
The information in the Microsoft documentation overrides any information published in this section.
Secude is not liable for changes to the content of this section because it was extracted from the Microsoft article at the time when the HaloCAD manual was prepared. Do check the most recent updates in this regard from the Microsoft documentation.
In summary, the following steps must be performed:
Update the Windows Operating System
Update .NET Framework
Set the following registry settings:
S.No | Windows Registry | Values |
---|---|---|
1 |
|
|
2 |
|
|
Registry entries
License Activation
A license for a product is necessary for access to features and support, legal compliance, security, and reliability. The primary Secude licensing method uses a Key-based license that regulates and allows access to the application's features. Therefore, to enable features, we suggest obtaining the license key from Secude support before installing HaloCAD.
Key-based License
Upon purchase or registration with Secude, a special "license key" is provided to the user to control the use of the application. The license key, which is an alphanumeric code, must be provided by the administrator when the application is installed or activated. By entering this key, the entire functionality of HaloCAD is unlocked, and the user's authorization to use it is validated.
This document does not cover all the specifics of purchasing a license. Please contact Secude’s representative for additional details.
The following methods are available to activate the license in HaloCAD.
Tool-based automatic initialization and license activation: This includes generating an encrypted configuration file with the license key and Azure application details. Using this file, the installer will complete the installation, application initialization, and license activation automatically. Refer to the section “Secure Installation” for more information.
UI-based manual license activation: This provides a straightforward installation method without automatic license activation. The license must be manually activated by the administrator. Refer to the section “UI-based Manual License Activation” for more information.
License activation through silent mode command line parameters:
Uses the encrypted configuration file to initialize the application and activate the license automatically.
Installation without the configuration file, in which the application is initialized and the license is manually activated.
For additional information on silent mode, see the section "Silent Mode" in the HaloCAD Installation Manual.
License activation via System Center Configuration Manager (SCCM): For deploying and activating the HaloCAD add-on throughout an organization, an encrypted configuration file (containing the license key information and Azure application details) is used together with the installer. Refer to the section “System Center Configuration Manager” for more information. For additional information on SCCM, please refer to the HaloCAD Installation Manual.
The following is a high-level diagram that illustrates license activation.

License activation
Secure Installation (Recommended)
As a best practice, any application secrets should not be shared with end-users, third parties, or any trusted vendors. However, to avail of HaloCAD features (standard add-on and reader add-on) there is a need to share such sensitive information for a successful installation.
To overcome this challenge, Secude offers an admin utility tool that can write and encrypt data including Azure application specifics (Application ID, Tenant ID, and Redirect URI), Cloud type details, and a license key in an encrypted configuration file. It uses the RSA algorithm for cryptography, allowing only the HaloCAD installer to access the configuration file with the private key during the initialization process, effectively masking the Initialization screen from the user.
An administrator can create an encrypted JSON file using this admin tool and share it with internal/external parties without disclosing the original tenant details.
HaloCAD Admin Utility Tool
The HaloCAD product package comprises an additional component—hc.admintool.exe
.
Prerequisites: Before executing the admin tool, make sure you have the necessary information.
Azure application details for initialization
Cloud type details
A license key
How to Encrypt the Configuration File
From the product package, move the admintool folder to your preferred location. For example,
C:\Users\superdocs\Desktop\admintool
.Open the Command Prompt with elevated rights (Run as Administrator).
Navigate to the directory of the admintool folder and type
hc.admintool.exe
and press Enter.Admin tool command
Enter the required details. For example,
Cloud type: Commercial -hc.admintool.exe v6ca776-c74e-437d-98ef-662ecb5751tt https://localhost 9c1cfc28-1ec6-44ea-bec6-e3492ef0cd16 B27N-CMTO-LWGH-AKEQ Commercial
Cloud type: US_DoD -hc.admintool.exe v6ca776-c74e-437d-98ef-662ecb5751tt https://localhost 9c1cfc28-1ec6-44ea-bec6-e3492ef0cd16 B27N-CMTO-LWGH-AKEQ US_DoD
Cloud type: Custom -hc.admintool.exe v6ca776-c74e-437d-98ef-662ecb5751tt https://localhost 9c1cfc28-1ec6-44ea-bec6-e3492ef0cd16 B27N-CMTO-LWGH-AKEQ Custom https://api.aadrm.com/ https://dataservice.protection.outlook.com/
The output window will now look as follows:
Admin tool output
Admin tool output with ECTR integration (only for Creo add-on)
Results:
The JSON file
hc.conf.json
will be replaced by an encrypted filehc.conf.enc
.Now, you can share the configuration file with external users. Using this file, users can install the HaloCAD add-on on their workstations seamlessly with no additional details.
Always make sure to create the configuration file using the
hc.admintool.exe
that is included in the installation package. Any configuration file created by prior releases will not work.
What to do next
Place the encrypted file
hc.conf.enc
along with the HaloCAD installer.To begin the interactive installation, double-click the installer and follow the instructions as mentioned in the Installation Manual of your purchased add-on.
By reading data from the
hc.conf.enc
file, the installer activates the license and bypasses the "Initialization" screen where it would ask for Azure details.
UI-based Manual License Activation
This section describes how to activate a license using the HaloCAD user interface.
Prerequisite: Make sure that the HaloCAD installation is complete as explained in the section “Graphical Mode”.
To complete the license activation, carry out the following steps:
Open the CAD application.
HaloCAD programmatically sends a license validation request to Secude's License Manager, and the following warning message appears:
HaloCAD license warning message
Click OK.
Go to the HaloCAD tab and click About to see the status of your license. Note: If None is displayed, your license has not yet been activated.
License status - None
Click Activate.
The HaloCAD License Activation screen will appear.
HaloCAD activation screen
Enter the license key provided for the standard add-on. Ensure that you enter the license key given for the reader add-on when using the reader add-on. Interchanging license keys results in activation failure.
Click Activate.
Results:
You will receive the below confirmation message:
Activation success message
Click OK.
As a result, the License Status in the About screen will become Active.
License status - Active
Related tasks:
If you click on the pencil icon (Click to change label) to label the file, HaloCAD will prompt you about the Microsoft Sign-In Assistant. Click OK and sign in with your credentials.
After successfully authenticating, the labels can be retrieved from the Azure RMS, and the HaloCAD Ribbon is activated. For more details, please refer to the Operations Manual.
License Expiry
The license will expire once the date is reached, and launching the CAD application will result in the following HaloCAD warning message: "The license is invalid." After clicking OK, you will get another warning message stating “User has no valid license. Please contact your administrator”. Therefore, you must acquire a new license to renew it.
Prerequisite: Before reactivating it, ensure that you have a new license key from Secude.
Option 1 - Using the admin tool (automatic activation)
Run the admin tool with the new license key, as explained in the section “How to Encrypt the Configuration File”.
Navigate to the configuration directory containing the old
hc.conf.enc
file and replace it with the one created in the previous step.Restart the application.
Results:
The HaloCAD license key is now automatically activated.
You can start protecting CAD files.
Option 2 - Using the About UI (manual activation)
Open the CAD application.
Go to the HaloCAD tab and click About.
Click Activate.
Enter the new key that Secude has provided.
Results:
The HaloCAD license key is now manually activated.
You can start protecting CAD files.
Appendix
Open-source Software
Third-party software/code is included or bundled with Secude's products according to its appropriate license. Secude conducts testing to make sure the third-party products are compatible with and perform as intended with Secude applications. The third-party libraries and dependencies used by the HaloCAD Add-on for CAD are shown in the table below.
Library | Version | Source Code | License Link |
---|---|---|---|
Mhook | 2.5.1 | ||
Protobuf Library | 3.15.6 | https://github.com/protocolbuffers/protobuf/blob/master/LICENSE | |
OpenSSL | 3.2 | ||
Rapidxml | 1.13 | https://sourceforge.net/projects/rapidxml/files/latest/download | |
JSON Parser | 3.11.3 | ||
MSAL | 4.59.0 | https://github.com/AzureAD/microsoft-authentication-library-for-dotnet | https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/blob/master/LICENSE |
ConfuserEx | 1.0.0.0 | ||
WTL | 9.0.4140 | ||
MIP SDK | 1.15.94 | https://learn.microsoft.com/en-us/information-protection/develop/version-release-history | https://docs.microsoft.com/en-us/information-protection/develop/ |
Licensespring | 7.28.1 | - | - |
Open-source software