Nobody wants to download something that will affect their computer negatively and Operating Systems are well aware of this. That’s why they’ve gone out of their way to generate warning messages anytime someone attempts to download something that may not come from a trustworthy source.

To software developers and engineers, these messages can mean the difference between someone adopting your software and someone forgetting it in their download folder. And losing users is bad for business—bad for the bottom line. So how do you become a trustworthy source? How do you prevent those messages and alerts from popping up before someone attempts to run YOUR software or code?

Code Signing. 

Individual Validation 

Individual Validation is a little different than Organizational Validation because you’re not proving that you’re a company, but that you’re a single developer. This kind of validation requires that you prove your identity to the CA. There are two methods you can follow to complete this requirement. 

Option 1: Photo ID

This option requires you to submit two documents to Sectigo:

  1. Copy of government-issued photo ID (driver's license, passport, national ID, military ID, etc) including your name and address. The information on this ID must match the info on your certificate request.
  2. Photo of yourself (a "selfie") holding your photo ID. Your face and the information on the ID must be clearly visible for comparison to the copy of the ID.

You will submit these two documents directly to Sectigo by opening a ticket with Sectigo validation support. Select the case type Validation Support and the appropriate Case Reason reason, attach files and complete the form. You will get a reply with the case number you can refer to in any future communication.

Option 2: "Face to Face" form

You should use this method of validation if your photo ID does not include any address or if the address does not match your order. This method does require some additional documentation, and you must take the documents to an authorized notary in your area for signing and notarization. The following notarized documents are required:

  1. Government-issued photo ID (driver's license, passport, military ID, etc)
  2. Financial document in the applicants name, such as a valid credit or debit card, mortgage statement, or bank statement
  3. Non-financial document in the applicants name with address, such as land-line phone bill (not mobile phone), recent utility bill, lease payment statement, birth certificate, tax bill, or court order document.
  4. Face to Face form with Personal Statement Declaration form: click here to download Face to Face form

When you have finished preparing the documentation, submit all forms directly to Sectigo by opening a ticket with Sectigo validation support. Select the case type Validation Support and the appropriate Case Reason reason, attach files and complete the form. You will get a reply with the case number you can refer to in any future communication.

After Validation

Once you have submitted your documentation to Sectigo's validation team, they will review and reach out to you via email to correspond further. When the certificate is approved and issued, you will receive a Collection Email to download the certificate. 

Please check our Code Signing collection articles for further guidance on the collection process, as the steps to complete the process differ depending on whether you submitted your own CSR or used Internet Explorer to create the certificate request.