On March 21st, the IETF voted unanimously to approve the latest draft for TLS 1.3. Four years and 28 drafts in the making, TLS 1.3 boasts new standards to improve both security and speed of the TLS protocol.
In 2016, there has been an influx of satirical stories and hoax videos surrounding cybersecurity, due to the widespread news coverage on the FBI vs. Apple case. Given how many people have fallen for these deceptive stories—and continue to be tricked by scam phishing emails—the necessity of cybersecurity education is more crucial now than ever. Here are a few useful tips on how to avoid misleading websites and fake information.
With big hacks making headlines seemingly every week, users and businesses alike understand the need to protect their financial data from digital compromises. Here are three online tools that can help safeguard sensitive financial information.
There are two categories of web traffic, and only one is safe for financial data. The first and most common type is information traveling over HTTP (HyperText Transfer Protocol), which is the backbone of the web. Data sent via HTTP is not encrypted—it can be read by anyone who intercepts it, such as the staff at a user's ISP. The other type of web traffic is information moving over HTTPS, which stands for HTTP Secure. Unlike information transmitted via HTTP, this data is encrypted, which makes it safer to send financial details. When users sign into their bank accounts, for example, browsers default to HTTPS and display a padlock to indicate an encrypted connection.
When users browse online, they often forget to clear the data from their web browser cache. However, this means that browsers can locally save sensitive website information such as bank account numbers and email passwords. If there is no company practice in place for staff to perform basic security measures like clearing their cache, malware can enter their systems, find private data, and send it to hackers, leading to dire consequences for companies.
How Browser Caches Store Web Data
A cache is a repository of stored data that is used to speed up the process of retrieving data. If a user accessing a resource already has some of its data stored in a cache, then the user does not need to retrieve that data from the resource—he or she can simply use it from the cache. But if the cache is empty, he or she must obtain all of it from the resource, which can be time-consuming.