Advice Archives - Enom BlogEnom Blog |

The Importance of Authentication in SSL

July 23, 2019

Advice, SSL

Like

Views: 315

Browsers have evolved to offer a better user experience and greater attention to security. Perhaps most importantly, they now display a security warning to users when they land on a website that lacks encryption:

This is a step forward to a safer Internet, but encryption is only part of the security equation.

Without a means to verify the owner of that website, the user can’t be sure who they are sending their information to.

When SSL certificates were first introduced, they served both these critical purposes:

1. Encrypting the data in transit

2. Authenticating the website to which the data is being sent

They were issued by a small handful of Certificate Authorities (CAs), accredited and compliant third parties able to provide both encryption and authentication of your website.

But as the Internet grew, so did the number of CAs in the market, and the variety of SSL options. And what was the main differentiating factor among these certificates? The level of authentication they provided.

Today, SSL products range from free “encryption-only” certificates, which can be registered in a matter of minutes, to Extended Validation (EV) SSL certificates, which, as their name suggests, involve a thorough validation (authentication) process as part of their registration.

When choosing an SSL certificate for your site, or helping a customer select one for theirs, your main question should be: what level of authentication do I need? After reading this blog, the answer will be clear.

Minimal Authentication: Domain-Validation (DV) Certificates

DV certificates are often described as “encryption-only” because they don’t provide confirmation of who the website owner really is. To register a DV certificate, the website owner simply needs to prove ownership of the domain name(s) they are trying to secure.

Think of a DV certificate like a library card: they are easy to obtain and aren’t considered a credible form of identification.

When to use a DV certificate

These certificates are sufficient if you’re securing a page just to maintain browser compliance (and avoid those warnings), or if you’re hosting a site that purely provides information and you want it done securely.

Basic Authentication: Organization-Validation (OV) Certificates

Before issuing an Organization-validated certificate, the Certificate Authority vets the organization and individual applying for the certificate. If a website visitor chooses to view the OV certificate, they’ll find this verified company information included in the details.

You can think of an OV certificate like a driver’s license: obtaining one involves a bit more hoop-jumping, but they are better trusted as a form of identification.

When to use an OV certificate

If you collect any basic personal information from your users, for example, login credentials, they’ll likely want to know who they are sending this information to. An OV certificate from a reputable CA may provide sufficient authentication and assurance in these cases.

However, Extended Validation certificates (see below) are often a better fit for e-commerce pages or business-critical sites where consumer trust is particularly important.

Advanced Authentication: Extended-Validation Certificates

Extended-validation (EV) certificates involve the most rigorous authentication process and, consequently, provide the highest level of assurance to website visitors.

What’s more, as mentioned above, they do this in a very obvious way: a green address bar that includes the name of the company. Finally, the CA Browser Forum, the SSL industry’s governing body, sets specific guidelines to govern the registration and authentication process for EV certificates.

These factors combine to make EV certificates the gold standard, and the assurance they provide becomes ever more essential as the average Internet user becomes savvier and security standards rise.

Continuing with our analogy, EV certificates can be thought of as passports: they are internationally recognized as the most trusted way to verify a website owner’s identity.

When to use an EV Certificate

We recommend using an EV if you’re looking to establish a high level of consumer trust or collecting sensitive information, which could range from login credentials to national identifiers, to credit card information. While not all browsers treat EV certificates the same way, for users, the additional visual cues can inspire trust and confidence to proceed with the transaction or activity.

Looking to better market your SSL lineup?

Our partners at DigiCert have some great resources to help you educate your customers and help them find the right fit. Through your partnership with us, you have access to an array of brands and certificate types to help make sure you properly meet the needs of your specific customer for their specific project. You can view our SSL offering here.

This post was sponsored by DigiCert, an Enom partner, and leading Certificate Authority.

Read More
Top questions from domain name buyers

May 6, 2019

Advice, New TLDs, Uncategorized

Like

Views: 3232
Guest Author: Alisha Shibli.

Alisha is a Content Marketing Specialist at Radix, the registry behind some of the most successful new domain extensions, including .STORE and .TECH.

Please note: The views expressed in this piece are the author’s own and do not necessarily represent those of Enom.

When it comes to registering a domain name, it’s easy to get overwhelmed. After all, when you’re building a business or starting an online venture, you want to ensure that all factors are working to your advantage. The process of choosing the right domain name is a lot less daunting when you know the basics. So today, we’re tackling some of the most common questions asked by domain name buyers. The information here will also be handy for resellers looking to educate their customers.

1. What is a domain name and how is it different from a website?

Websites and domain names are closely related, but they’re two different things. You can think of your website as your house and your domain name as its address. In order for someone to access your website, they need to know its domain name.

Every domain name has two basic parts: the “top-level domain” (TLD) and the “second-level domain.” For example, in the domain name [yourbrandname].tech, “.TECH” is the TLD and “yourbrandname” is your second-level domain. Together, these form a complete domain name.

Your domain name will usually include your brand name or the name of a particular sector or product that you’re promoting. When choosing a domain name, you’ll realize there are now numerous TLDs available such as .STORE, .PRESS, .SPACE, .ONLINE, .WEBSITE, .SITE, etc. So, make sure you choose whichever brands your business best.

2. What should I consider when buying a domain name?

What some businesses don’t realize is that choosing a domain name is one of the most important decisions they make when establishing their online presence. The domain name is more than just a glorified IP address. It is important for search engines and for customers. Moreover, it is an incredible branding tool, which is why it is crucial to choose a name that adds value to your business and will help you stay relevant even a decade later.

Here are a few factors to keep in mind when choosing a domain name for your business:
- Buy domain names that are easy to spell and remember. Avoid using misspelled words. A unique spelling may seem creative, but such domain names fail to be radio friendly—a very important factor in the voice search era.
- Keep your domain name as short as possible. Anything more than 18 characters is too long. For example, [healthysnack].store is a better domain name than [healthysnacks-store].com.
- Avoid using hyphens and numbers in your domain name. They are just extra characters for your customers to remember. A user might forget to add the hyphen or get confused between the numerical “6” and the word “six”.
- Make sure to do your homework and check global databases to ensure that your domain name isn’t trademarked or copyrighted. This will help if you plan to expand your business to other countries in the future.
- Consider leveraging new, descriptive TLDs to brand your business and act as a home for different marketing and sales endeavors. For example, Emirates has emirates.com as its commercial website and emirates.store as its online merchandise store.
3. If I have multiple domain names, how can I use them together?

You don’t just have to stick to one domain name! Using multiple TLDs in interesting ways can create memorable customer interactions with your brand, or, perhaps, promote your personal side-project alongside your primary business. Here are some of the many ways one can make use of new domain names:
- Primary Domain: Use a domain name to create an online identity for your business. For example, louder.online or stronger.tech
- Professional Email ID: Use a domain name to make a strong first impression with a unique email id. For example, [firstname]@[brand].online.
- Branded URL Shortener: Use a domain name to enhance brand visibility and build trust with every link that you share online. For example, [yourbrandname].tech/contest looks more official than “https://bit.ly/2taRHVV”.
- Domain Redirect: Use a domain name to make an important inner page easily accessible by creating a deep-link. For example, kindle.store redirects to Amazon’s Kindle store.
- Product Launches: Use a domain name to attract customers to your new product, store upgrades or seasonal promotions. For example, if you are introducing a new car and want to position it as a “fun” car, you can launch it on [carname].fun.
- Personal Brand: Use a domain name to build an attractive online persona for yourself. For example, terrene.space is the portfolio website of a freelance photographer, writer, graphic designer & illustrator, Ana Petre.
- Vanity: Use a new domain name to share your social media profile. For example, [yourname].tech could forward to one of your social media profiles.
- Blog / Press Page: Use a domain name to make your brand gain visibility online with a [brandname].press. For example, cars.mclaren.press is McLaren’s official media site.
4. How can I decide between a ccTLD, geoTLD, gTLD, or nTLD?

Let’s first clarify the difference between these terms.

Generic top-level domains (gTLD) are, as their name suggests, generic. They have a broad application based on the purpose of the website. For example, .COM (commercial), .ORG (organization), .NET (networks), .EDU (education), etc.

Country code top-level domains (ccTLD) are regulated by a specific country and are best used to target customers within that country. Some examples include. US, .CA (Canada).TR (Turkey) .IN (India), .CO.UK, .AE (UAE), .DE (Germany), .FR (France), etc.

GeoTLDs are similar, but they are tied to a specific region, rather than a country. City extension like .NYC or .LONDON as well as options like .AFRICA and .ASIA exist.

New generic top-level domains (nTLD), which are sometimes just referred to as “new TLDs” are recently launched generic domain extensions.

They tend to be more industry- or product-specific, so their adoption has the potential to make the Internet more organized and business-friendly. Some other examples of nTLDs include .STORE for eCommerce and retail, .TECH for technology, .FUN for leisure, .PRESS for media and news.

Plus, there are many with universal appeal, like .ONLINE, .SITE, etc. In fact, .ONLINE and .SITE have become so popular that over 1 million domain names have been registered on each of these extensions so far. And these nTLDs are still relatively new, you are likely to find that your perfect domain name is available on one of them!

In summary

When it comes to choosing the right domain extension for your domain name, you need to look at the nature and purpose of your business. For example, if you have a tech business, then a .TECH domain would be an ideal choice.

With the information above, you are well-equipped to make an informed choice. Get started with a search for your perfect domain name.
Read More
What Domain Resellers Should Know About ICANN’s Temporary Specification

September 18, 2018

Advice, Featured, GDPR, Industry Insight

Like

Views: 4017

On May 17, 2018, ICANN issued a “Temporary Specification for gTLD Registration Data,” the purpose of which is to provide ICANN’s contracted parties (registrars and registries) a path towards compliance with both ICANN contractual requirements and the GDPR. This involved the introduction of numerous registrar requirements, aimed at resolving points of conflict between ICANN’s Registrar Accreditation Agreement (RAA) and the GDPR. Here, we’ll highlight those requirements that are most relevant to our resellers, provide our stance on the Temporary Specification, and discuss some related upcoming features being added to the Enom platform.

What is a “Temporary Specification”?

To understand what makes the Temporary Specification unique, it’s important to understand how ICANN policy is typically developed. Normally, any policy that is binding on contracted parties (registrars and registries) is developed by a bottom-up, participatory process, taking input from all stakeholders and interested contributors, along a defined path called a “policy development process” (or “PDP”).

The output of a PDP is presented for public comment, refined, and then presented to ICANN’s Generic Names Supporting Organization (GNSO) Council for a vote. After a policy is approved by the GNSO Council, it is presented to the ICANN Board for final review and approval. Only after the ICANN Board approves the policy does it become binding on registrars and registries through a contractual provision in the above RAA.

The Temporary Specification was issued as an “emergency policy,” meaning it was adopted by a super-majority of the ICANN Board and bypassed the normal policy development process. Emergency policies must be re-approved by the ICANN Board every ninety (90) days and can exist for no more than one year. The idea is that one year provides sufficient time for the ICANN community to develop a permanent policy along the normal, bottom-up development path. The Temporary Specification was adopted on May 17, 2018 and will expire on May 16, 2019.

What does the Temporary Specification require of registrars?

The Temporary Specification includes a long list of items that registrars “must” or “shall” implement in order to be in compliance with their Registrar Accreditation Agreement, many of which are pulled directly from, or are heavily based on, the GDPR itself.

Here are some of the highlights, specifically those most relevant to resellers and registrants, with a note about any related changes we’re making within the Enom platform.

Registrars “must” or “shall”:

1. Redact personally identifying information from the public Whois output when (a) the registry or registrar is located in the EU; or (b) the registrant is located in the EU; or (c) the registry or registrar uses a data processor located in the EU for the registrant’s personal data. The redacted fields must say something like “REDACTED FOR PRIVACY.” (Temp. Spec. Appendix A Section 2)

Enom’s approach: As of May 25, 2018, Whois lookups results for all domains on our platform have returned “Data Protected” in place of any personally identifying information. However, we haven’t just limited this practice to the specific cases listed above; the redaction of personal data in the public Whois is our default for all domains on our platform.

2. Provide a method for third parties to contact the registrant through an anonymized email or web form. (Temp. Spec. Appendix A Section 2.5)

Enom’s approach: We plan to launch a Whois Contactability service that will allow the registrant to be contacted through a hosted web form. We’ll provide more details in the next few weeks.

3. Provide a means for the registrant to consent to have their contact details displayed in the public Whois, instead of the “Data Protected” notice mentioned above. (Temp. Spec. Section 7.2.1)

Enom’s approach: We’ll soon be launching a Whois Publicity service that allows registrants to opt into the display of their personal data in the public Whois, details of which will be released in the coming next weeks.

4. Implement Tiered Access to full Whois data, so that third-parties with a legitimate interest in access to a registrant’s personal data (such as law enforcement agencies) can review that data when necessary and appropriate. (Temp. Spec. Appendix A Section 4)

Enom’s approach: We’ve built a Tiered Access Directory — or “gated Whois” — that accomplishes this.

5. Provide mandatory disclosures to registrants detailing who has the registrant’s personal data, how it is processed, when and why a data transfer crosses international boundaries (if applicable), and the specific reasons that data is collected and transferred, among other subjects. (Temp. Spec. Section 7.1.)

Enom’s approach: This information is easily located on our Data Use Information Page

6. Comply with a new transfer policy, described in Appendix G to the Temporary Specification.

Enom’s approach: The domain transfer process changes we announced on April 30, 2018, anticipated the new transfer policy outlined in ICANN’s Temporary Specification. No further changes are needed.

7. Implement and observe Service Level Agreement (SLA) standards for Registration Data Access Protocol (RDAP), otherwise known as the successor to the WHOIS protocol. (Temp. Spec. Section 5.2)

Enom’s approach: These Service Level Agreement standards are not yet finalized, but Enom has played an active role in the RDAP pilot project. We’re in a position to easily implement any minor changes to our current system that the final agreement may call for, and to help shape the SLA to ensure it’s something that all registrars can meet in order to provide a reliable and fast RDAP service to users.

How and when are registrars expected to comply with the Temporary Specification?

ICANN has stated that it is “enforcing the requirements of the Temporary Specification as of 25 May 2018, as it does any other ICANN agreement or policy requirement.” However, aware that the requirements of the Temporary Specification came late, ICANN has provided registrars some leeway. While ICANN has already sent notices of non-compliance to many registrars, they appear to be withholding further action so long as the registrar demonstrates that they are working toward compliance. So we can expect that the various GDPR compliance processes in place now — which vary from registrar to registrar — may look quite different down the road. Virtually every registrar, including Tucows, is changing its implementation in important ways to comply with the Temporary Specification.

What changes is Enom implementing?

We have already implemented the majority of the mandatory requirements. As mentioned above, you can expect two new features in the coming months: Whois Contactability, which provides a means to contact the registrant through public Whois lookup results, and Whois Publicity, which allows registrants to opt into the public display of their contact data.

What is Enom’s stance on the Temporary Specification?

We believe industry-standard processes are important — they provide a level of consistency very much needed in this highly-connected registrant/registrar/registry network. Many of the Temporary Specification requirements will help move the industry forward towards a unified approach.

However, we view other aspects of the Temp. Spec. as problematic. The Temporary Specification aims to provide registries and registrars with a path to comply with both ICANN contractual requirements and the GDPR, but in a way that maintains “the existing Whois system to the greatest extent possible” and requires “robust collection of Registration Data.”

At Tucows, we believe that “maintaining the existing Whois system” and requiring “robust collection” of data violates the basic principles of GDPR. Put another way, we do not believe that the Temporary Specification is fully compliant with the GDPR. We have an ongoing disagreement with ICANN as to what the GDPR requires in three discrete areas, which is the subject of the ongoing ICANN v. EPAG litigation in Bonn, Germany.

Right now, we’re focused on implementing those Temporary Specification requirements that do not conflict with the GDPR (which is, of course, the vast majority). The GNSO has initiated an Expedited Policy Development Process (“EPDP”), which we are watching with great interest, as we work within the registrar community to advocate for the best outcome for registrars, resellers, and registrants. We’re advocating for policy which fully complies with the GDPR, keeps domain registration and management simple, and protects the interests of our resellers. As we’ve said before, in any instance where ICANN policy conflicts with the law, our priority is compliance with the latter.

Read More
Why Choose an EV SSL Certificate?

June 13, 2018

Advice, Featured, SSL

Like

Views: 3140

Identity theft and browser warnings are growing concerns among consumers. And while you may think enabling SSL on your website will allay these fears, failure to select the right TLS/SSL certificate can erode customer trust. To regain trust, site owners need an easy, reliable way to show customers that transactions are secure and that the site operator is who it says it is. But with the variety of TLS/SSL certs available – DV, OV, or EV – figuring out the best certificate for your business can be confusing. There are major differences in how domains are validated, and the following outline provides some key insights as to which certificate to select for your specific needs.

Domain Validation (DV) SSL Certificates

DV certificates prove ownership of the actual domain through a simple email validation process. DV certificates can be issued in minutes, show trust indicators in browsers (like the padlock icon), and enable HTTPS.

However, DV certificates do not vet the legitimacy of an organization and should not be used for e-commerce sites. Accordingly, DV certificates are best for internal sites, test servers, test domains, and for small to medium-sized businesses seeking cost-effective security.

Organization Validation (OV) SSL Certificates

OV certificates provide the same level of protection as DV certificates but go one step further. With an OV certificate, the Certificate Authority (CA) confirms the business is registered and legitimate, checking details such as business name, location, address, and incorporation or registration information, making these certificates more suitable for public-facing websites.

An OV certificate will also enhance a website’s reputation, providing customers greater assurance in conducting e-commerce transactions.

Extended Validation (EV) SSL Certificates

EV SSL certificates provide the highest level of trust, giving customers greater confidence that they are conducting business through trusted websites. EV SSL certificates are the industry standard for e-commerce websites. An EV SSL certificate triggers high-security web browsers to display an organization’s name in a green address bar and show the name of the Certificate Authority that issued it:

EV SSL certificates confirm site identity and validate the organization according to rigorous industry guidelines established by the CA/Browser Forum, including a strict vetting process using techniques that have been proven reliable in protecting the internet’s most valuable online businesses for more than ten years.

EV SSL certificates are a good choice for businesses, as these certificates can enhance credibility by showing suspecting consumers that sites are legitimately what they purport to be and that a business is serious about protecting the data of its customers.

Summed up, for the greatest level of website security, EV SSL certificates are the best choice.

Find Out More

This post was sponsored by Comodo CA, one of our trusted SSL providers. For more information about SSL, and a complete list of their products, visit www.ComodoCA.com.

Read More
A Guide to Choosing the Right SSL Certificate

May 24, 2018

Advice, Featured, SSL

Like

Views: 3284
A parent preparing a toddler for her first beach vacation and a seasoned kayaker preparing for Zambia’s Ghostrider rapid will not reach for the same life jacket. In the world of digital security, the purposes and specs of the various products are also highly relevant to the consumer, although the differences between them may not be so immediately clear. But in both cases, it’s important that the customer find the right fit. Whether you’re a business owner looking for the right SSL certificate for your own website or a domain provider looking to curate a solid SSL offering for your own customers, here’s what you should know about TLS/SSL certificates and what to look for when selecting a certificate provider.

What are TLS/SSL Certificates?

SSL is short for “Secure Sockets Layer,” and SSL certificates are used to secure communications between a website, host, or server and the end users that are connecting to it (or between two machines in a client-server relationship). An SSL certificate confirms the identity of the domain name (for example, ComodoCA.com) that is operating the website and enables encryption of all information between the server and the visitor to ensure the integrity of all the transmitted information.

Why are TLS/SSL Certificates So Important?

Identity theft and browser warnings are growing concerns among consumers. Failure to select the right TLS/SSL certificate for your website can erode customer trust and lower your rate of completed transactions, negatively impacting your bottom line.

How SSL Encryption Works

Encryption makes use of keys to lock and unlock your information, meaning you need the right key to “open,” or decode, the secured information.

Each SSL certificate comes with two keys:
- A public key, which is used to encrypt (scramble) the information.
- A private key, which is used to decrypt (unscramble) the information and restore it to its original format to make it readable.
Where Are SSL Certificates Used?

SSL certificates should be used in any instance where information needs to be transmitted securely. This includes:
- Communications between your website and your customers’ internet browsers.
- Internal communications on your corporate intranet.
- Email communications sent to and from your network (or private email address).
- Information between internal and external servers.
- Information sent and received from IoT and mobile devices.
Determining If a Site Has a Valid SSL Certificate

A website without an SSL certificate displays “http:// ” before the website address in the browser address bar. This moniker stands for “Hypertext Transfer Protocol,” the conventional way to transmit information over the Internet. Most internet users are aware that this indicates a website is not secure and historically have looked for https:// and a closed padlock symbol in their browser window to confirm that they are on the site of an authenticated organization:

However, it’s no longer sufficient for business websites to simply enable HTTPS and display the standard padlock symbol to their visitors. Online consumers are demanding assurance that the identity of the website they are visiting has been verified by authentication procedures that are proven to be highly trustworthy. And this assurance is provided in the form of an Extended Validation (EV) SSL certificate. EV certificates display a hard-to-miss green identifier in the URL bar and indicate to the visitor that the website was subjected to extensive scrutiny by the issuing Certificate Authority. The consumer can be confident that they are at a legitimate website, not a phishing website.

That’s not to say an EV certificate is necessary in every situation. But they can generate a higher level of consumer trust than other options, such Organization Validation (OV) certificates, or Domain Validation (DV) certificates, which undergo far less scrutiny.

Choosing between EV, OV, and DV Certificates

Domain Validation (DV) SSL Certificates

DVs are best for small- to medium-sized businesses seeking cost-effective security with no need to establish site visitor trust. Issuance of a DV certificate simply requires proof of ownership of the associated domain name, which is provided through a simple email validation process. These certificates can be issued in minutes, enable HTTPS, and display a clear indicator, such as the padlock symbol, in internet browsers.

However, DV certificates do not vet the legitimacy of the organization the website represents and should therefore not be used for e-commerce sites or sites that deal in sensitive information. They are, however, a great option for many internal sites, test servers, and test domains.

Organization Validation (OV) SSL Certificates

OV certificates provide the same level of protection as DV certificates but go one step further than simply requiring proof of domain ownership. With an OV certificate, the issuing Certificate Authority confirms the business associated with the domain name is registered and legitimate by checking details such as the business name, location, address, and incorporation or registration information. This makes the OV certificate a more suitable option for public-facing websites that represent companies or organizations.

Extended Validation (EV) SSL Certificates

EV certificates provide the highest level of trust by assuring consumers that they are conducting business through a trusted website. For this reason, these certificates have become the industry standard for e-commerce websites. EV SSL certificates trigger high-security web browsers to display a green address bar that includes the name of the company or organization that owns the domain. They also show the name of the issuing Certificate Authority:

Confirmation of the website’s identity and validation of the organization is carried out according to the rigorous industry guidelines established by the CA/Browser Forum and involves a strict vetting process that is shown to be effective over the course of more than ten years of real-world use.

EV SSL certificates are essential for large businesses or e-commerce sites as they can enhance credibility by showing discerning consumers that a prospective transaction is with a legitimate recipient and that the site is serious about protecting the data of its customers.

What to Look for When Choosing a Certificate Authority (CA)

As the world’s largest commercial Certificate Authority, Comodo CA is proactively monitoring for potential threats and attacks, working hand-in-hand with government agencies, browser providers, and our customers, to ensure it is keeping up with the ever-changing market.

When evaluating a CA, be sure that it:

1. Follows CA/B Forum Baseline Requirements.

This industry group consisting of Certificate Authorities and browser manufacturers developed standards that each CA must meet for its roots to remain trusted in browsers. These include:
- All information contained within the certificate must be validated to be true through a strict, clearly defined authentication process.
- Certificates must meet specific minimum levels of cryptographic strength to protect the integrity of the certificate and private key from evolving threats.
- Certificates must not exceed maximum specified durations.
- CAs must follow guidelines for CA security, certificate revocation mechanisms, audit requirements, liability, privacy and confidentiality, and delegation of authority.
2. Conducts Annual Audits – Both WebTrust and SOC 3

Annual audits are crucial to CA security, yet not every CA makes them a priority. At a minimum, your CA should meet these auditing standards.
- Maintain membership in the WebTrust program for CAs
  The WebTrust for Certification Authorities program was developed to increase consumer confidence in the Internet as a vehicle for conducting e-commerce and to increase consumer confidence in the application of PKI technology. Comodo CA, for example, undergoes an annual audit from Ernst & Young, which validates that:
- The Certification Authority (CA) discloses its SSL certificate practices and procedures and its commitment to provide SSL certificates in conformity with the applicable CA/Browser Forum Requirements.
- Subscriber information was properly collected, authenticated and verified.
- The integrity of keys and certificates is established and protected throughout their life cycles.
- Logical and physical access to CA systems and data is restricted to authorized individuals.
- The continuity of key and certificate management operations is maintained.
- CA systems development, maintenance and operations are properly authorized and performed to maintain CA systems integrity.
- The Certification Authority maintains effective controls to provide reasonable assurance that it meets the Network and Certificate System Security Requirements as set forth by the CA/Browser Forum.
- Submit to publish an annual Service Organization Control 3
  The SOC3 report is published to confirm that the security controls for this cloud service have been examined by an independent accountant. Again, as an example, Comodo CA undergoes an annual audit from Ernst and Young, to validate that Comodo CA has maintained effective controls over its system as it relates to four core principles: security availability, processing integrity and confidentiality.
To sum it up…

Trust is everything in the world of online business. Investment in technology to protect customers and earn their trust is a critical success factor for any company that does business online or hosts an e-commerce website. The effective implementation of TLS/SSL certificates is a proven tool to help establish customer trust. Check out Enom’s lineup of Comodo Certificates, or browse our full inventory of SSL products.

Looking to learn more?

This post was sponsored by Comodo CA, one of our trusted SSL providers. For more information about SSL, and a complete list of their products, visit www.ComodoCA.com.
Read More