Traditional code signing workflows often depend on physical USB tokens or hardware devices to protect private keys. While secure, these hardware-based approaches can introduce operational challenges — especially for remote teams, distributed developers, and modern CI-oriented environments.

Cloud-based code signing is becoming an increasingly popular alternative.

This article walks through how sslTrus Cloud Code Signing works and how users can complete a full signing workflow without relying on physical tokens.

What Is Cloud Code Signing?

Cloud code signing allows developers to sign applications through a centralized cloud-based signing infrastructure instead of storing private keys locally on USB tokens or developer machines.

With sslTrus Cloud Code Signing:

• Certificates are managed centrally

• Signing access is authenticated using AccessKey and AccessSecret credentials

• Signing operations are completed through a dedicated signing client

• Developers can sign files from Windows or macOS environments

This model simplifies certificate usage while reducing dependency on hardware devices.

Step 1: Purchase a Code Signing Certificate

The first step is to purchase:

• A code signing certificate

• A corresponding signature package

Users can complete the order through the:

• NicSRS Console

After purchase, the certificate application information must be submitted for issuance.

Step 2: Download the Signing Tool

Once the certificate has been issued, users can download the sslTrus signing client.

Download page:

• sslTrus Signing Tool Download Center

The tool currently supports:

• Windows

• macOS

After downloading:

• Extract the files

• Launch the application

• Switch the interface language if needed

For macOS users, the guide also provides a command to bypass the default quarantine restriction during first launch.

Step 3: Generate Access Credentials

Instead of using a USB token, sslTrus Cloud Code Signing uses:

• Access Key

• Access Secret

to authenticate signing requests.

Users can generate credentials from:

My Code Signing Certificate → Detail → Security

After entering the NicSRS account password, the platform generates the required authentication credentials.

Step 4: Configure the Signing Tool

Open the signing client and navigate to:

Settings

Then enter:

• Access Key

• Access Secret

Once configured, the signing tool can securely communicate with the cloud signing platform.

Step 5: Sign Files

To sign an application or executable:

1. Open the signing tool

2. Select Create Sign Task

3. Choose the target file

4. Select the corresponding certificate

5. Click Sign

After signing is completed successfully, the signed file is generated automatically in the same directory.

Step 6: Manage Certificates and Signing History

The signing tool also includes basic management capabilities.

Users can:

• View valid cloud code signing certificates

• Check signing task history

• Review signing status and timestamps

This provides a more centralized signing experience compared to traditional hardware-token workflows.

Why More Organizations Are Exploring Cloud Code Signing

As development environments become more distributed, many organizations are looking for alternatives to:

• shipping physical USB tokens

• local private key storage

• device-specific signing limitations

Cloud-based signing workflows offer:

• simpler credential management

• remote accessibility

• centralized certificate usage

• multi-platform flexibility

For teams looking to modernize their signing workflows, cloud code signing is becoming an increasingly practical option.

Learn More

The sslTrus Cloud Code Signing User Guide provides detailed instructions covering:

• certificate application

• signing tool setup

• AccessKey configuration

• signing workflows

• certificate management

Interested readers are welcome to contact us to request a copy of the guide and learn more about sslTrus Cloud Code Signing.