Skip to main content

Products · Code signing

Two certificates. Most publishers need the first.

Both are issued by Certum, a certificate authority on the EU Trusted List, and both keep the private key in Certum’s hardware security module — there is no USB token to ship or lose. The difference is how much of your company gets verified, and what that unlocks.

The two code signing certificates

  • Standard · Organisation validation

    Certum Standard Code Signing

    For companies that publish Windows software and want the install dialog to name them, not “Unknown publisher”.

    €159net / year
    • Signs .exe, .dll, .msi, .msix, .appx, .cab, PowerShell scripts and Office macros
    • Certum verifies your company against the public registry and the person you name
    • The usual choice: pick EV only when a driver or a policy demands it
    See Standard
  • EV · Extended validation

    Certum EV Code Signing

    For companies that sign kernel-mode drivers, submit to the Windows Hardware Developer Program, or answer to a policy that names EV.

    €289net / year
    • The only level accepted for kernel-mode driver submissions
    • Certum verifies the business independently and calls back on a listed number
    • More validation work for a specific requirement — not a better certificate
    See EV

Why Klarseal

  • Issued by Certum
  • On the EU Trusted List
  • Norwegian company
  • No USB token

If nobody has asked you for EV, buy Standard

EV used to be worth paying for on reputation alone. It is not any more. Since March 2024 the instant SmartScreen treatment is gone, so both certificates start with no reputation and build it the same way — through real downloads of files you signed. Reputation attaches to the certificate, so it carries across releases either way. What EV still does, and Standard cannot, is sign kernel-mode drivers and satisfy a policy that names it.

Since March 2024Resellers still advertising instant warning removal for EV are describing the old behaviour.

What actually differs

Standard (OV) compared with EV code signing, row by row
PropertyStandard (OV)EV
ValidationOrganisation (OV)Extended (EV)
What it provesYour company published the fileYour company, verified from more independent sources
User-mode apps, installers, scriptsSigns themSigns them
Kernel-mode driversNot acceptedRequired
Windows Hardware Developer ProgramNot acceptedRequired
SmartScreen reputationBuilds with downloadsBuilds with downloads
Key storageCertum HSM, no USB tokenCertum HSM, no USB token
What Certum checksThe registry record and the named personThe registry record, an independent check on the business, a directory callback and the named person
Subscriber agreementOrder confirmationSigned by an authorised representative
Maximum validity459 days459 days

Sources: Certum product documentation; CA/Browser Forum code-signing baseline requirements; Microsoft Windows Hardware Developer Program documentation.

Choosing between them

Answered in full here. If your case is not covered, email support@klarseal.com and a person answers.

Which one do I need?

Standard, unless something specific pushes you to EV: you sign kernel-mode drivers, you submit through the Windows Hardware Developer Program, or a customer or internal policy names EV. Standard signs the same user-mode applications, installers, packages and scripts, and asks less of your company during validation.

Does EV clear the SmartScreen warning faster?

No. Since March 2024 Microsoft no longer grants EV certificates instant reputation. Both levels start with none and build it as your signed files are downloaded, and reputation attaches to the certificate, so it carries from release to release. What signing changes immediately is the name in the dialog: your verified company instead of "Unknown publisher".

What does Certum check differently for EV?

For organisation validation, Certum verifies that the company exists and matches the public registry, and checks the identity of the person named on the order. For extended validation it goes further: an independent confirmation that the business is operating, a callback on a phone number published in a directory it trusts rather than one you supply, and a subscriber agreement signed by someone authorised to bind the company.

Does either one need a USB token?

No. Both are cloud certificates: the private key is generated inside Certum’s hardware security module and never leaves it, and you sign from your own machine through the SimplySign app. Nothing is shipped, so there is no customs delay and nothing to lose.

How long does it take to get a certificate?

Ordering takes a few minutes. After that the clock belongs to Certum’s checks and to the identity check of the person you name, so we do not promise a date. What we control is that the application enters complete — we pull your registry record, verify the person ordering, and have Certum confirm the application before you pay.

Can I buy as a private person?

Klarseal sells to businesses — Norwegian companies and registered sole traders with an organisation number. As a private person you can buy the same certificate directly from Certum.

Your name on your software

One year, one price, either level. We check the application with Certum before you pay, and refund in full if the certificate cannot be issued.