Code Signing

Code Signing

  • New Requirements related to Private Key protection for CodeSigning Certificates

    Feb 12, 2024

    The Certificate Authority/Browser (CA/B) Forum has introduced updates to Baseline Requirements (BRs) for issuing CodeSigning Certificates. Effective 1st June 2023, a private key should be generated and protected in a FIPS 140‐2 Level 2 or Common Criteria EAL 4+ compliant devices for both Standard and EV CodeSigning Certificates. This would mean for Standard CodeSigning Certificate users, the key pair must be generated and stored in a hardware crypto module that meets or exceeds the requirements of FIPS 140-2 level 2 or Common Criteria EAL 4+. In addition, the updates stipulates specific ways on how CA should ensure that private key is generated and protected on the compliant device.

    Read More
  • Initialize Safenet Token

    Feb 22, 2024

    This article will walk you through initializing your Safenet Token. This is a requirement when you first set up your token. It may also be used in the event you forget the password to your token.

    Read More

GlobalSign System Alerts

View recent system alerts.

View Alerts

Atlas Discovery

Scan your endpoints to locate all of your Certificates.

Sign Up

SSL Configuration Test

Check your certificate installation for SSL issues and vulnerabilities.

Contact Support