Hardware Program Verification using Azure's Trusted Signing (instead of EV Code Signing Certificate)

Question

Hi,

Is it possible to possible to upload and submit drivers for Microsoft's Hardware Program attestation and getting approved for the program using Azure Trusted Signing, since it requires the same KYC-level verification?

Or do I have to purchase a $300/year EV Code Signing certificate just for the sake of the approval?

Thank you!

Justas

Answer 1

Hello @Justas Urbonas ,

Unfortunately, the short answer is no. You cannot use Azure's Trusted Signing for the Microsoft Hardware Program attestation. You will still need to purchase an EV Code Signing certificate because:

1. Hardware Program Strict Requirements: The Microsoft Hardware Dev Center explicitly requires an Extended Validation (EV) code signing certificate to register your company and to submit drivers (.cab or .hlkx files) for attestation. They do not accept standard code signing certificates.
2. Azure Trusted Signing Limitations: While Azure Trusted Signing provides robust identity verification, the Azure Trusted Signing FAQ clearly states that it currently does not support EV certificates, nor does it support signing Windows drivers.

So yes, to get approved for the program and sign your kernel-mode drivers, purchasing an EV Code Signing certificate is currently the only supported path.

I hope this clarifies the situation. If you found my response helpful, I would greatly appreciate it if you could provide feedback by following this guide.

Thank you.

Answer 2

Azure Trusted Signing cannot currently be used instead of an EV code signing certificate for registration and driver submission in the Windows Hardware Developer/Hardware Dev Center program.

For the Hardware Developer Program and for submitting drivers (including attestation signing) through the hardware dashboard/Dev Portal, an extended validation (EV) code signing certificate is explicitly required:

• To register for the Hardware Developer Program, an EV code signing certificate is required; it must be uploaded on the Manage certificates page for the registration request to be considered for approval.
• To establish a Hardware Dev Center/Partner Center hardware dashboard account (needed for driver signing via the Dev Portal), an EV code signing certificate is required.
• For attestation signing of drivers, the prerequisites explicitly state that an EV code signing certificate is required; if the organization does not have one, it must purchase an EV certificate from a supported certificate authority.

Trusted Signing is not mentioned as an accepted alternative in the Hardware Developer Program registration or driver signing requirements. The documented path for getting approved and submitting drivers is to obtain and use an EV code signing certificate from a supported CA and associate it with the Partner Center hardware account.

---

References:

• Register for the Microsoft Windows Hardware Developer Program
• Manage code signing certificates
• Driver Signing Policy
• Driver code signing requirements
• Attestation sign Windows drivers