It\nhappens all the time. Someone in the company tells you that you have to get an\nSSL\/TLS certificate for your website. Wait. What? Nooo, it doesn’t happen all\nthe time. But, it probably happened to you when working on a test or a special\npromotion site for your group, and that’s why you’re reading this blog post.\nThere are a few things to unpack so we’ve broken it down into a seven-part\nseries. Here’s part 1 \u2013 this section goes over some of the basics on SSL\/TLS\ncertificates and will prepare you for a polite conversation on transaction\nsecurity with your company’s security group.<\/p>\n\n
SSL\/TLS Puts the “S” in\nHTTPS<\/strong><\/p>\n\n In\nHTTPS, the “S” stands for “secure.” As consumers, we rely\non organizations to secure our online transactions, and on browsers to tell us\nwhen it’s safe to transact on a website. This quick tutorial shows how to spot\na secure website.<\/p>\n\n SSL\/TLS\ncertificates (they are both the same) serve two purposes \u2013 they encrypt\ninformation that is sent over the internet and they provide identity assurance,\nboth of which help online consumers to positively identify and trust websites\nthat are safe to transact with. An HTTP website\u2014 no “S”\u2014lacks both\nidentity and encryption, which means it’s not secure. Browsers now issue strong\nwarnings to visitors who try to enter websites that are not secured by HTTPS.\nThis usually makes the visitor queasy and they leave for another website where\nthey feel safe to make their transaction.<\/p>\n\n How Does an SSL\/TLS Certificate\nWork?<\/strong><\/p>\n\n Public\nKey Infrastructure (PKI) provides the framework that enables SSL\/TLS to be used\nfor cybersecurity. PKI uses encryption to protect information that passes\nbetween a server (your website) and a client (the device the person transacting\non your website is using). It uses two different types of matched cryptographic\nkeys to secure the transaction, the public key (which your server distributes\neverywhere) and the private key (which is locked away on your server).<\/p>\n\n When\ntransacting, the client and your server start with an encryption\n“handshake” that relies on your certificate, after which all\ncommunications between them are encrypted (so no one can intercept and read the\ncommunications in transit) and are authenticated between the client and server\n\u2013 that’s why encryption means security. From that point on, all the client’s\npersonal data — login credentials, credit card information, etc. \u2013 can be\ntransmitted securely to your server. A file that is created by a particular\npublic key can only be decrypted by the corresponding private key on your server\nand vice-versa, ensuring that the transaction is going to the intended\nrecipient and protecting the information from a cyberattack while in transit.<\/p>\n\n So, why do I need an SSL\/TLS\nCertificate?<\/strong><\/p>\n\n SSL\/TLS\ncertificates provide important advantages that can mean the difference between\ncreating a seamless and secure website experience versus an alarming one for\nwebsite visitors. Here are a few benefits that SSL\/TLS provide for you:<\/p>\n\n To\nsum it up, SSL\/TLS certificates are essential for web-based projects that can\nbe viewed by anyone surfing the internet \u2013 nearly 80% or all web page loads now\nare encrypted, and the number is rising rapidly. While there is no legal or\ntechnical requirement to use certificates, it does represent best practices and\nthe browsers make it much friendlier for visitors to engage with websites that\nhave HTTPS because of the security features they provide. Stay tuned for the\nnext post in our seven-part series, which will cover what you need to know\nabout the different certificate types.<\/p>","protected":false},"excerpt":{"rendered":" It happens all the time. Someone in the company tells you that you have to get an SSL\/TLS certificate for your website. Wait. What? Nooo, it doesn’t happen all the time. But, it probably happened to you when working on a test or a special promotion site for your group, and that’s why you’re reading […]<\/p>\n","protected":false},"author":1,"featured_media":821,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-22861","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/posts\/22861","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/comments?post=22861"}],"version-history":[{"count":0,"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/posts\/22861\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/media\/821"}],"wp:attachment":[{"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/media?parent=22861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/categories?post=22861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dinocolor.si\/en\/wp-json\/wp\/v2\/tags?post=22861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}