How Windows hardware developers choose a Code signing certificate type

Code Signing certificate for the Windows Dev Center hardware Dashboard

There are currently two types of code signing certificates available:

Standard Code Signing certificate

1. Provide standard level of authentication

2. Short processing time and low cost are required.

3. All Windows Dev Center Hardware Dashboard services that are available in addition to the LSA and UEFI file signing services.

4. Standard code signing is not available for kernel-mode drivers in Windows Technical Preview Desktop (home, Pro, and Enterprise Editions). For more information about these changes, see Driver Signing changes in Windows 10.

5, Microsoft recommends the purchase of Symantec (VeriSign) or globalsign standard Code signing certificate;

Extended Validation (EV) Code signing certificate

1. Provide the highest level of authentication

2, due to the expansion of the verification process, so the need for longer processing time and high cost

3. Available for all Windows Dev Center Hardware Dashboard services, and is required for LSA and UEFI file signing services

4. In Windows Technical Preview Desktop (home, Pro and Enterprise Editions), all kernel-mode drivers must be signed by the Windows Hardware Dev Center dashboard, and the Windows Hardware Dev Center dashboard requires an EV certificate. For more information about these changes, see Driver Signing changes in Windows 10.

5. Microsoft recommends the purchase of an extended validation (EV) code signing certificate from Symantec (VeriSign) or globalsign

How Windows hardware developers choose a Code signing certificate type