SSL Certificates

Discover the Difference Between OV and EV Certificates

OV (Organization Validation) and EV (Extended Validation) certificates are SSL certs that business websites use to prove identity and secure customer data. OV says, “Hey, we’re a real company,” while EV goes a step further, saying, “We’re not just legit, but also extra secure.” It’s all about different levels of online trust and protection for your sensitive information. Many business websites use entry-level Domain Validation certificates, and there’s nothing wrong with that. However, an OV or EV certificate could be a better solution. This article covers the difference between OV and EV certificates so you can decide whether they’re suitable for your online project. But first, let’s see what an OV vs. EV certificate does regarding encryption and authentication. What Is an OV SSL Certificate? An OV SSL certificate is a digital certificate that provides a high level of authentication for your website, assuring visitors that your site is secure and trustworthy. When you apply for an OV SSL cert, the issuing Certificate Authority (CA) checks your right to use a specific domain name plus additional organization information. They verify your business name, location, and legal existence. This process might seem rigorous, but it establishes your identity and protects customers. OV certificates are a vital choice for e-commerce websites, startups, NGOs, and any online business required by law to prove its identity. But while OV SSL certificates significantly enhance your website’s credibility, they don’t offer the highest level of validation available. That’s where EV SSL certificates come into play. What Is an EV SSL Certificate? An EV SSL certificate is a premium validation option that gives your site the highest level of authentication. It verifies your organization’s identity, operational and physical presence, and the authority of the person requesting the certificate. EV SSL certificates include your company’s official name in the certificate’s information field for everyone to see. Upon inspecting your cert, visitors know they’re dealing with a legitimate business operating in good faith. An EV SSL certificate can boost customer confidence and lead to higher conversion rates, but most importantly, it’s a testament to your high-security standards. EV certs may not be worth the investment for small to medium-sized businesses, but they are the preferred choice for large enterprises, Fortune 500 companies, and financial institutions. Consider them if you’re in the fintech, insurance, or e-commerce industries. What Is the Difference Between OV and EV Certificates? You may wonder what else sets Organization Validation vs. Extended Validation certificates apart. The differences lie in authentication processes, visual cues, business impact, validation timelines, and applicability to wildcard and multi-domain certificates. Here’s an in-depth EV vs OV SSL comparison: Authentication Process The OV process involves verifying your organization’s identity and legal existence. It checks the business name, location (company’s physical address), and domain ownership. On the other hand, the EV SSL verification is more thorough. It includes all steps in the OV certificate order but also requires an enrollment form, at least three years of operational existence, and a more detailed final verification call. As a result, EV authentication is stricter but more transparent and efficient. Visual Cues Initially, Extended Validation certificates stood out by displaying the company’s official name in a unique green address bar next to the URL. However, browsers have evolved and phased out this visual indicator. Google Chrome went even further and removed the SSL padlock in one of its latest updates, citing that HTTPS is now the norm and doesn’t need a separate indicator anymore. As a result, both OV and EV certificates now present users with a standard padlock or “view information” symbol. Clicking it reveals more details about the certificate, including the validation type. Although the EV green bar is gone, users can still find out who is behind the website. Business Impact So, how do OV or EV SSL certificates impact your business? It’s the level of trust they convey to your website visitors. Security-wise, they both offer the same encryption strength and browser compatibility. Where EV certificates excel, that’s in the higher assurance provided by a certificate authority. A more complex vetting process enhances a company’s defense against phishing attacks and reduces the likelihood of users falling victim to fraudulent websites attempting to impersonate the company. Validation Timelines OV and EV certificates require a series of checks to authenticate a business. However, the time it takes to verify the applicant’s information varies. CAs issue OV SSL certificates in 1-2 business days, providing your information is accurate and up-to-date. EV certificates can take between 1 and 7 business days to obtain. If the CA can’t validate your credentials via publicly available databases, you must provide additional paperwork, prolonging your wait. Today, you can speed up the OV and EV SSL certificate validation if your organization has a LEI code. A LEI (Legal Entity Identifier) is a unique 20-character label that provides a standardized and globally recognized way to identify legal entities engaging in financial transactions. Wildcard and Multi-Domain Certificates Wildcard certificates secure unlimited subdomains of a single website, while Multi-Domain certificates secure multiple domain names under one SSL installation. Both types provide Organization Validation, but only multi-domain certs support Extended Validation. Wildcard SSL certificates don’t support Extended Validation due to security considerations and resource challenges. Verifying limitless subdomains becomes logistically complex and time-consuming, compromising the stringent validation process inherent to EV certificates. SSL Warranties An SSL warranty protects your website’s users against data breaches due to a certificate miss-issuance. There’s a noticeable difference between OV and EV SSL certificates that you should consider for your website’s security. OV certificates provide a lower warranty level, typically around $50,000. On the other hand, EV certificates offer generous warranties, often exceeding $1 million. This high warranty level reflects the extensive validation process EV SSL certificates undergo. It’s a strong signal of the superior trust and protection they offer. Pricing Considerations An Extended Validation certificate is more expensive than an OV one because of its thorough validation and better features. The price varies depending on the brand, SSL warranty, and how many domains the certificate secures. The cheapest OV SSL certificate, Comodo Instant SSL, is just $37.33 per year if you get a
Read more

The Difference Between DV and OV SSL Certificates

SSL Certificate is important as it ensures that any data transferred between the two parties cannot be intercepted by anyone else. Three types of SSL certificates exist – Domain Validated (DV), Organization Validated (OV), and Extended Validated (EV) certificates. To choose the right SSL for your website and ensure better security, you need to understand the difference between the 3. This article delves into the DV vs. OV SSL certificate comparison. DV vs. OV SSL Certificates: The Main Differences Level of Authentication for DV vs. OV SSL Certificates  DV certs offer the lowest, most basic level of validation. The entity requesting the certificate must prove their ownership and control over the domain/ URL to be secured by SSL. OV certs offer a higher level of validation. The entity requesting the certificate must prove their control over the domain/ URL to be secured by the SSL and that their organization is a legitimate one. Since the entity must provide legitimate business information and the CA (Certificate Authority) scrutinizes the legitimacy of the organization, So, comparing DV vs. OV SSL, OV certs provide greater levels of trust and legitimacy to the website. Process/ Steps for Validation The process for obtaining a DV SSL is pretty simple and straightforward since the entity must prove domain ownership. The CA will require the entity requesting the certificate to complete email verification, file-based verification, or Domain Registrar’s Information. The OV SSL certificate issuance process is more detailed and involves 5 steps as the entity must prove the legitimacy and identity of their organization along with domain control. Organizational Authentication Locality Presence Telephone Verification Domain Verification Final Verification Call Visible Cues of Protection Provided  While DV and OV SSL certificates both provide visible padlock signs, OV SSL certificates provide additional CA-validated information to demonstrate the legitimacy and identity of the website and the organization that owns it. The DV cert provides only the padlock sign in the address bar and no other CA-validated information. Upon clicking the padlock sign, one can see the connection is a secure message with both certs and the Certificate (Valid) option. A dialog box opens on clicking the Certificate (Valid) option with an OV cert. Click the details tab, and you will find information about the organization to whom the certificate was issued and details about the organization along with information about validity, CA, etc. Further, OV SSL certificates provide dynamic site seals while DV certs-only provide static site seals. The benefit of having a dynamic site seal is that it is clickable with current data, time of the page loading, etc., and real-time status checks. It inspires greater trust among users. Time Taken to Obtain Certification  Comparing DV SSL vs. OV SSL, DV certs take the shortest time to be issued and happen within minutes. This is owing to the straightforward verification process. On the other hand, OV certs may take between 1 and 3 days to be issued by the CA. Costs In the DV vs. OV SSL certificate comparison, DV certs are very inexpensive and often available free of cost. Since it involves a longer validation process and manual verification requirements, OV SSL certs are more expensive. Barriers to Entry  DV SSL certificates have the lowest barriers to entry as the site owner does not have to prove anything else except domain ownership. Plus, the costs are very low. So, anyone can get such a certificate. But obtaining an OV SSL is not as easy or cheap. While DV SSL may benefit some businesses and individual users, it gives SSL access to cybercriminals who can SSL-protect phishing and illegitimate websites. This way, they attract user trust with the padlock sign, and users may end up doing the attacker’s bidding. On the other hand, users may not trust legitimate websites if they do not have dynamic site seals or provide CA-validated information. So, a legitimate business may suffer. Level of Warranty  DV SSL offers extremely low warranties in comparison to OV SSL. The warranties are so low in some cases that they may be insufficient to cover damages in case of any encryption errors or CA-side errors. OV certificates offer higher warranties, adequate to cover any mishaps owing to bad SSL. Who Should and Shouldn’t Choose DV SSL vs. OV SSL? DV is best suited for personal blogs, static websites, and other websites where no transactions are conducted or personal information is collected. DV certs are unsuitable for any other types of websites. OV certificates are best suited for business sites, login screens, medium to large businesses, non-profits accepting donations, websites collecting sensitive information through forms or checkout pages, etc. OV certs, however, are inadequate for dynamic websites, e-commerce sites, large enterprises, fortune 500 companies, banks and financial institutions, healthcare organizations, etc. Such websites must be protected with an EV SSL certificate that offers the highest level of assurance. Conclusion The choice of SSL certificate should be driven by the level of security needed and context. Costs should not dictate the choice of SSL as the DV vs. OV SSL certificate comparison amply highlights. Buy SSL Certificates at Great Prices with 24/7 Local Support
Read more

How to generate CSR in Azure 

Introduction The following article provides step-by-step instructions for generating and importing a Certificate into Microsoft Azure Key Vault. Note: If this is not the solution you are looking for, please search for your solution in the search bar above. Creating Key Vault:  Once logged into the Azure portal, if you do not have a Key Vault setup yet or would like to create a new one click on the “Create a resource”. Click on “Key Vault” icon under “Popular Azure services”.Note: If it does not auto populate you can use the ‘Search services and marketplace’ box, type ‘key Vault’ and it will pop up. Click “Create”. Now you will want to name your Key Vault. Once named choose your subscription preferences (Free Trial or Pay-As-You-Go), Resource group (new or existing), ‘Key Vault name’ Region, Pricing tier.       2. Choose the settings in the Access configuration, Networking, and Tags tabs according to your use case.       3. Click ‘Review + Create’ button and click ‘create’ at the bottom.      4. In a few seconds the Key Vault will be successfully created. Generating CSR and Importing a Certificate into Microsoft Azure Key Vault     1. After you have created and selected your key vault, press the Certificates option on the right-side menu. Then, click Generate/Import button at the top, as shown below.​​​​​       2. On the ‘Create a certificate’ window, fill out the Certificate details.   Note:  a. Certificate Name is friendly name that it will be referred to within the vault, it is not the common name of the actual certificate.  b. Select Type of Certificate Authority: “Certificate issued by a non-integrated CA”.  c. In the subject field enter the Common Name in the format: CN=Common Name.       3. Set ‘Advanced Policy Configuration’ as shown below. Note: a. As per the CAB Forum Guidelines for Code Signing Certificates, from June 2023, all Private Keys for Code Signing Certificates need to be stored in HSM’s which are FIPS 140 Level 2 or 3 compliant. Please make sure that RSA-HSM and EC-HSM option is enabled in your Key-Type and you should select RSA-HSM option as these keys are stored by Azure Key-vault in Managed HSM’s, which are FIPS 140 Level 2 or 3 compliant. b. RSA and EC options are for Software protected keys and they are not compliant with the current guidelines of CAB forum. Please read more about the Keys here.         4. Click ‘OK’ and ‘Create’. Now click on the newly created certificate request.         5. Click on ‘Certificate Operation’ and later ‘Download CSR’ to get a copy of your CSR.         6. You will need to submit the CSR to the GlobalSign Certificate Center (GCC) to download the certificate:        7. Now Download your Digital Certificate and Intermediate certificates:         8. Go back to Azure Key Vault and click on ‘Merge Signed Request’ to import the download Digital Certificate.  
Read more

What Is SSL Certificate? Why You Need It And When To Use It

SSL, Secure Sockets Layer, is known for being a protocol that is put into use for the sake of enabling a user to establish a connection that is both encrypted and secure at the same time. A simple way to understand it would be looking at the green padlock at the web address. While many URLS begin with http://, others start with https://. Now the presence of the ‘s’ in the latter prevents your data from being hacked. The technology that makes all this possible is known as SSL. What is SSL – Secure Sockets Layer SSL, which is also known as the TLS (Transport Layer Security), is basically a protocol that many enterprises or companies use in order to save the information of their users in the process of transfer of information. The benefit of having an SSL certificate is that it makes all the information sent unreadable and hence can’t be interrupted with by any devices from outside. Since the data sent remains unreadable by any device between the original computer and destination server, any sort of outside attacks can be prevented by the SSL. A secure connection is only established when your server has an SSL certificate. Obtaining a secure connection paves the path for the users to submit their confidential information at complete peace of mind. Getting Acquainted With the Types of SSL Certificates The level of security depends on the level of verification performed by the SSL certificate provider. There are basically two types of SSL certifications i.e. basic and extended validation. A basic SSL certificate would simply verify that one has the ownership of the domain. The verification is done with a confirmation email being sent to the email address on record. An Extended Validation (EV) certificate will go an extra mile as they are willing to check the identity of the business or the organization. However, EV certificates take longer time to be approved and may require statements notarized from the authorized attorney depending on the case. Why you need SSL certification: The first and foremost thing that is considered before obtaining an SSL certificate is the urge to make the users feel secure as their data remains confidential. Here are the reasons behind the need of the SSL certificate. Protecting Passwords and data: Passwords are gateway to your dashboard in case of many websites. Since your dashboard is the place where all your information regarding credit card and other relevant information are, you better stay protected. SSL always gives you the scope to protect your usernames and passwords. On the other hand, you have less chances of having your credentials stolen as hackers sniff the Wi-Fi. The principle behind an SSL certificate is that it secures information so that the data being sent is only accessible to the specific recipient. Safeguarding Your Privacy: The top three webmail providers, Hotmail, Yahoo! Mail and Gmail, offer SSL encryption in addition to end-to-end secure HTML connections. Though they may not encrypt your connection automatically, you can secure your settings manually and safeguard your email conversations. Provides Trust: With lock icon or a green bar, your visitors would know their connection is secured and that will give them a reason to select your website above others. Secure Transactions: Having SSL certification enables you to execute any sort of transaction in compliance with the Payment Card Industry Data Security Standard (PCI DSS). Inclusion of SSL certification offers a feel of security to the user as security is involved with online transactions. Improvement in Search Engine Ranking: With Google mentioning that it would boost the ranks of the websites that are SSL certified, SSL looks like a pretty good deal. Thus, SSL doesn’t only protect the asset and information of the users but also benefit your business. Promotion of More Referral Traffic: Referral traffic can be defined as the way in which Google tracks visits to the site originating from outside the search engine. Whenever a user comes to the website via other websites or advertisement, that link is considered as referral data. However, secure referral data is preserved when referral traffic passes to an https site. This is important because this will help you to obtain accurate analysis and predict where the major chunk of visitors is coming from. How to Use SSL Certificate? Before you buy SSL certificate, you can certainly have a talk with your web developer or the hosting company. Purchasing From Verified Seller: The first step is to buy SSL certificate from a trusted SSL vendor whom you can get to know about either from your developer or hosting company. You can find great deals on ssl certificates here – itbrands.pk/ssl-certificates-service-providers-in-pakistan Installing the Certificate: In order to make the https work, the SSL certificate needs to be installed on your server. This is usually handled by the hosting company you work with. Configuration: The next step is configuration. In order to configure your website so that it can use the SSL certificate, you will need to get in touch with the web development company that you are working with. Based upon your need of having SSL certification at certain pages, you can also ask an affordable WordPress developer to do the needful. When to Use SSL Certificate? Since SSL certificates are applicable to many types of websites, it is absolutely mandatory for sites to have SSL certificates especially if they are working with data of users or need users to put in confidential information like credit card details. You can also have a look at the PCI compliance guide in order to know more about the payment information and SSL. Having a world class hosting and encryption is a required condition for your website since it will shower upon you with a diverse range of benefits. Before you get an SSL certificate, you will need to decide what kind of certificates you need and certainly the quantity as well. In case, you just want the SSL certificate for your landing page or transaction page, you
Read more

How to create a CSR in IIS 7

[vc_row][vc_column][vc_column_text] Home Resources SSL Certificates How to Generate a CSR for Microsoft IIS 7 How to Generate a CSR for Microsoft IIS 7  (12 votes, average: 2.08 out of 5, rated) The following instructions will guide you through the CSR generation process on Microsoft IIS 7. To learn more about CSRs and the importance of your private key, reference our Overview of Certificate Signing Request article. If you already generated the CSR and received your trusted SSL certificate, reference our SSL Installation Instructions and disregard the steps below. 1. Open Internet Information Services (IIS) Manager Click Start, Control Panel, Administrative Tools, and then select Internet Information Services (IIS) Manager. 2. Select the server where you want to generate the certificate In the left Connections menu, select the server name (host) where you want to generate the request. 3. Navigate to Server Certificates In the center menu, click the Server Certificates icon under the Security section near the bottom. [/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_single_image source=”external_link” custom_src=”https://www.thesslstore.com/knowledgebase/wp-content/uploads/2017/03/microsoftiis7-step4.gif”][vc_column_text] 4. Select Create a New Certificate In the right Actions menu, click Create Certificate Request.[/vc_column_text][vc_single_image source=”external_link” custom_src=”https://www.thesslstore.com/knowledgebase/wp-content/uploads/2017/03/microsoftiis7-step4.gif”][vc_column_text] 5. Enter your CSR details In the Distinguished Name Properties window, enter in the required CSR details and then click Next.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_single_image source=”external_link” custom_src=”https://www.thesslstore.com/knowledgebase/wp-content/uploads/2017/03/microsoftiis7-step5.gif”][vc_column_text]Note: To avoid common mistakes when filling out your CSR details, reference our Overview of Certificate Signing Request article. 6. Select a cryptographic service provider and bit length In the Cryptographic Service Provider Properties window, select Microsoft RSA SChannel Cryptographic Provider and Bit Length of 2048, then click Next.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_single_image source=”external_link” custom_src=”https://www.thesslstore.com/knowledgebase/wp-content/uploads/2017/03/microsoftiis7-step6.gif”][vc_column_text]Note: Bit Length: 2048 is the current industry standard. You may choose a larger key size, but only if you have a requirement to do so, as longer key lengths increase latency and may reduce compatibility. 7. Save the CSR Click Browse to specify the location where you want to save the CSR as a “.txt” file and click Finish.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_single_image source=”external_link” custom_src=”https://www.thesslstore.com/knowledgebase/wp-content/uploads/2017/03/microsoftiis7-step7.gif”][vc_column_text] 8. Generate the order Locate and open the newly created CSR from the specified location you choose in a text editor such as Notepad and copy all the text including: -----BEGIN CERTIFICATE REQUEST----- And -----END CERTIFICATE REQUEST----- [/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_single_image source=”external_link” custom_src=”https://www.thesslstore.com/knowledgebase/wp-content/uploads/2017/03/microsoftiis7-step8.png”][vc_column_text]Return to the Generation Form on our website and paste the entire CSR into the blank text box and continue with completing the generation process. Upon generating your CSR, your order will enter the validation process with the issuing Certificate Authority (CA) and require the certificate requester to complete some form of validation depending on the certificate purchased.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][/vc_column][/vc_row]
Read more

Digitally Sign Emails – Mozilla Thunderbird

1:: Open a new email window in Mozilla Thunderbird. Go to Tools > Account Settings. 2:: Click the Security tab. Click Select next to the Digital Signing field. 3:: Choose the certificate you intend to use for signing. Click OK. Note: If no certificates are present, it still needs to be imported. Follow these instructions and then return to this article to continue. 4:: You can choose the encryption certificate here as well: 5:: To sign all messages, check Digitally sign messages (by default) under the Digital Signing field: 6:: Click OK to complete. If you are not signing by default, proceed to the next step for instructions on signing a single email. 7:: When composing a new email in Thunderbird, click the Security drop down menu and choose Digitally Sign This Message. Note: To send encrypted messages, you must first receive a digitally signed email message from the recipient.  
Read more

How to Install & Configure SSL Certificates on SAP Web Dispatcher

Step 1: Unzip the certificate files onto the server where you will install the certificate. The ZIP file you downloaded contains the following certificates: SSL certificate (i.e. ssl_certificate.crt) Intermediate CA certificate (i.e. IntermediateCA.crt) Root CA certificate (i.e. Root.crt) Copy the Root CA and Intermediate certificate file onto the server where you will install the certificate. Step 2. Install the SSL Certificate To install an SSL certificate on a SAP Web Dispatcher, follow either one of the following methods: Method 1. Install the SSL Certificate using the Trust Manager If the certificate request dialog is still open, then close it. If the SAP Web Dispatcher’s PSE is not loaded in the PSE maintenance section, then load it by selecting the File node with a double-click and selecting the PSE from the file system. In the PSE maintenance section, choose Import Cert. Response. The dialog for the certificate response appears. Insert the contents of the certificate request response into the dialog’s text box either using Copy&Paste or by loading the file from the file system. The signed public-key certificate (i.e. ssl_certificate.crt, as described in Step 2) is imported into the SAP Web Dispatcher’s PSE, which is displayed in the PSE maintenance section. You can view the certificate by selecting it with a double-click. The certificate information is then shown in the certificate maintenance section. Create a PIN for the PSE.NOTE: It is recommended using a PIN to protect the PSE, especially if the SAP Web Dispatcher is located in your demilitarized zone. Save the data in the trust manager. You are prompted for the location to which to save the PSE. Replace the PSE that you created earlier. If you saved the PSE to a local file on the application server, then copy it to the SECUDIR directory on the SAP Web Dispatcher. Method 2. Install the SSL Certificate using SAPGENPSE Use configuration tool sapgenpse to import the certificate request response into the PSEs. Run the following command: Example: sapgenpse import_own_cert <Additional_options> -p <PSE_file> -c <Certificatefile.crt> -r <Cacertificate.crt> -x <PIN> -p <PSE_Name> Path and file name of the PSE. The path is the SECUDIR directory and the file name is SAPSSLS.pse.for the SSL server PSE or SAPSSLC.pse for the SSL client PSE (if it exists). Path description (in quotation marks, if spaces exist). -c <Cert_file> Path and file name of the certificate request response. Path description (in quotation marks, if spaces exist). -r <RootCA_cert_file> File containing both the Root CA certificate and the Intermediate CA certificate. The Intermediate CAcertificate is to be first followed by the Root CA certificate. Path description (in quotation marks, if spaces exist). For example:Open a Notepad, paste the Intermediate CA certificate (i.e. IntermediateCA.crt as described in Step 2) and Root CA certificate (i.e. RootCA.crt as described in Step 1) in the following order: –BEGIN CERTIFICATE—–[Intermediate 1]—–END CERTIFICATE—–—–BEGIN CERTIFICATE—–[Intermediate 2]—–END CERTIFICATE—–—–BEGIN CERTIFICATE—–[Root CA]—–END CERTIFICATE—– -x <PIN> PIN that protects the PSE Character string. OR By using <strong>> cat intermediate1.crt intermediate2.crt root.crt > ssl-bundle.crt</strong>  
Read more

Multi-year Subscription SSL

Great news to the SSL market! Now most SSL certificates are available for Multi-year Subscription Plans. For security reasons, your certificate will initially be issued with a maximum of 13-months validity. Prior to the expiration, we will contact you to replace your certificate for another maximum duration certificate. You can reissue your certificate at any time and as many times as you like. No more lost days or weeks on single year certificates trying to time a new purchase and re-submission. Industry changes At the CA/Browser (CA/B) Forum in Bratislava, Slovakia, Apple announced that beginning Sept. 1, newly issued publicly trusted TLS certificates are valid for no longer than 398 days. This followed a long history of the CA/B Forum community working to reduce certificate lifetimes and improve security while balancing the needs of business owners in transitioning to shorter validity certificates. Check the official statement and history. When changes applies? Sectigo – starting at 19th August 2020 GoGetSSL – starting at 19th August 2020 DigiCert – starting at 27th August 2020 All other CAs – starting at 1st September 2020. What is the TLS/SSL Multi-year Plan? To help your customers embrace the benefits of shorter certificate lifetimes and make certificate management even easier, GoGetSSL is offering Multi-year Plan TLS/SSL certificates. This new type of multi-year coverage is a time-efficient and cost-effective way to help your customers improve their security by further reducing certificate outages and the hassle of managing shorter certificate lifecycles. As browsers are mandating one-year certificate lifetimes, the Multi-year Plan coupled with automation tools saves you time—and money. Your customers can lock in longer coverage terms provided by the Multi-year Plan, while your cost goes down relative to the longer term lengths you sell. How does it work? When your customer purchases a TLS/SSL certificate with the Multi-year Plan, they’ll receive the initial certificate, valid for up to one year, and entitlement to unlimited certificate reissues during the order period—up to six years. We will need to routinely revalidate customer organizations and domains annually throughout the lifetime of the Multi-year Plan. We would start sending replacement notifications before 30-21-14-7-3-1 days. The SSL will be replaced automatically using the same CSR before 3-days of expiration if users do not replace SSL on their own. Reissued SSL will be sent to the email. Example of SSL subscription There are four different dates now available for all multi-year SSL certificates. Subscription starts the date when the first SSL was issued Subscription ends the date when subscription ends and new orders needs to be created Valid From the date when current active SSL was issued on Valid Till the date when SSL needs to be replaced in order to get new SSL for another 13-months Why should partners offer the TLS Multi-year Plan? When the Multi-Year Plan is combined with automation, your customers can minimize the risk of human error when managing shorter certificate lifecycles. With automation, you can automatically provision and reinstall certificates, and in most environments replace the CSR. Also, customers can easily adapt to any potential certificate lifetime reductions imposed by the industry in the future. Certificate renewals no longer require additional order periods added to the new certificate, because there is no more lost purchase period. The customer can get a new certificate from the day they need the certificate, until the day they want it to expire, within the service period. Due to Baseline Requirements of the CA/Browser Forum, re-validation is necessary at certain certificate intervals to maintain compliance. Multi-year Plan helps your customers efficiently embrace the security benefits of shortened certificate lifecycles and ensures they remain loyal to your brand for many years. Although certificate validation must be renewed annually, certificates can be replaced daily to improve the security posture of any organization. Benefits of the Multi-year Plan for you and your customers Minimized risk of compromised certificates; Minimizes the risk of using weak keys (example SHA1); Ensures yearly validation of identity to prevent potential fraud and spoofing; Easier management of certificates with automation; Using the Multi-year Plan provides more billing flexibility for you with your customers, and allows you to secure more revenue up front, while locking in your customers for longer terms; Improve your average selling price (ASP) on certificate deals by selling longer term lengths. Talking points to promote the Multi-year Plan Streamlined: Remove the hassle of annual billing by taking advantage of the Multi-year Plan. Customizable: Secure your site with coverage for longer periods of time. Secure: The Multi-year Plan allows you to embrace the best practice of shorter TLS certificate lifecycles by minimizing the risk of compromised certificates and changing out weak keys regularly, thus improving the security posture of your web pages. Future-proof: By taking advantage of Multi-year Plan options you also protect yourself from further reduction to certificate lifecycles imposed by the industry.
Read more

DigiCert :: End of Support for Symantec Partner Portal

End of support for Symantec Partner Portal DigiCert will end support for Symantec® Partner Portal on July 31, 2020. If you are still finalizing your migration to CertCentral Partner, contact us and we’ll help you plan your move. Watch our video (48 seconds) on how to migrate certificates from your old account   NOTE:: This article is copyright by DigiCert and we are using is for education or information purposes only. Click Here to visit the official store of DigiCert   in Pakistan 
Read more

Maximum SSL/TLS Certificate Validity is Now One Year

Starting on September 1st, SSL/TLS certificates cannot be issued for longer than 13 months (397 days). This change was first announced by Apple, at the CA/Browser Forum Spring Face-to-Face event in Bratislava back in March.  Then last week, at the CA/B Forum’s Summer event (held virtually), Google announced its intention to match Apple’s changes with its own root program.  There is also a browser-driven ballot that seeks to align the industry’s baseline requirements with the new root program changes. That issue is currently being debated by the Forum. We realize there might be a lot to unpack here, so in the interest of providing a little clarity we’re going to cover it in this blog post.  The reason for shorter SSL/TLS certificate lifespans From a high-level, theoretical standpoint there are two primary benefits for shorter-lived certificates: The first is the technical component – longer lifespans means it takes longer to organically roll out updates or changes. A real-world example would be the SHA1-to-SHA2 transition. Unless you’re going to revoke a whole bunch of certificates and force the customer to re-issue, it can take years before all of the old certificates are replaced. In the case of SHA1, it took three. That creates risk.  The other benefit has to do with identity – how long should the information used to validate an identity stay trusted? The longer between validation, the greater the risk. Google has said that in an ideal world domain validation would occur about every six hours.  Before 2015 you could get an SSL/TLS certificate issued for up to five years. That was reduced to three, and then again in 2018 to two. At the end of 2019, a ballot was proposed at the CA/B Forum that would have reduced it to one year – it was voted down soundly by the Certificate Authorities. So, why are certificate still being reduced to one year? The CA/Browser forum is an industry group that meets to vote on a set of baseline requirements for the issuance of trusted digital certificates. What it is not, however, is a governing body. Even though the CAs expressed concerns and reluctance to decrease max validity again, Apple and Google are well within their right to update the policies for their root programs as they see fit.  We understand that we’ve just thrown a whole bunch of industry terms at you, so let’s step back real quick and make sure the previous paragraph makes sense.  Certificate Authorities and browsers have an interdependent relationship. Browsers need to use certificates to make trust determinations about websites and for help securing connections. On the CA side, what good is a public certificate if it’s not trusted by a browser? The way this is all managed is through the root programs. There are four major root programs of note: Microsoft Apple Mozilla Google ( the last two known as Googzilla – lol) Incidentally, you’ll notice those four are also behind the major browsers on both desktop and mobile. In order for a CA to have its certificates trusted by the root programs, and by extension the browsers and OSs that make use of them, it must adhere to that root program’s guidelines. The CA/B Forum is an industry forum that ideally helps to facilitate changes to the root programs (and the ecosystem itself).  But the root programs, which participate as browsers, can still act unilaterally and make changes as they see fit. When this happens, the need for interoperability basically dictates that whatever root program policy has the most stringent standards becomes the new de facto baseline requirement.  That’s how we got here. Now let’s talk about what this means for your website. What shorter SSL/TLS validity means for website owners First things first, this goes into effect September 1, 2020. So, if you’re using a two-year certificate that was issued before September 1, your certificate will stay valid until its original expiration date. You just won’t be able to renew for two years moving forward.  Or to put it another way, you have until the first of September to get two-year certs. After that they will be relegated to the desktop recycling bin of history.  From a bigger-picture standpoint, this might be a good time to start giving consideration to automating more of your certificate lifecycle management functions. Especially for larger organizations managing dozens of publicly-trusted website certificates, but also for organizations using publicly-trusted email certificates, as well as any organization leveraging a private CA or PKI-based electronic signatures. You might also consider moving some certificates from public to private trust, which also helps with management – you could even issue certs with longer validity using that method.  Otherwise, the way things are headed with the root programs continuing to push for shorter validity – organizations are pretty much going to be forced to automate a lot of these things at some point in the future.  Better to explore that now than when your feet are being pressed to the fire.  How GlobalSign will handle one-year certificates In the interest of simplicity – making the process as straightforward as possible – GlobalSign will provide SSL/TLS customers with the maximum validity of 397 days when they order one-year certificates starting on 31 August. This applies to new orders and renewals, to provide maximum validity for our customer’s benefit. You will still want to renew your certificate before it expires, but since we can no longer provide up to 90 additional days to your validity, we recommend you renew within 30 days of expiration.  What about reissuing my certificates? You may wonder what happens when you reissue one of your two-year certificates after this change goes into effect.  Well, we have good news for you!  If you reissue a certificate and lose validity (we’re required to limit validity to 397 days), you can reissue the certificate later – ideally less than 397 days prior to your original cert expire – and recover the lost validity from your first reissue! This works the same
Read more
Cart

No products in the cart.