Google Chrome

Chrome will mark HTTP pages as “not secure”

Starting with Chrome 68, which is scheduled to be released in July 2018, Google will explicitly mark all HTTP sites as “not secure”: According to Google’s numbers, 68% …

https

Google to enforce HTTPS on TLDs it controls

In its sustained quest to bring encryption to all existing Web sites, Google has announced that it will start enforcing HTTPS for the 45 Top-Level Domains it operates. How …

locks

TLS security: Past, present and future

The Transport Layer Security (TLS) protocol as it stands today has evolved from the Secure Sockets Layer (SSL) protocol from Netscape Communications and the Private …

https

Making HTTPS phishing sites easier to spot

For years, we taught users that a website’s URL that includes https at its very beginning is a relatively good indicator of whether they can safely input sensitive …

locks

Breaking TLS: Good or bad for security?

As the use of TLS by malware and phishing increases, some security practitioners are seeking solutions to break TLS so they can monitor all traffic in and out of their …

building

The HTTPS interception dilemma: Pros and cons

HTTPS is the bread-and-butter of online security. Strong cryptography that works on all devices without complicating things for users. Thanks to innovative projects like …

magnify

Inline SSL solution eliminates network blind spots

At RSA Conference 2017, Gigamon announced an expansion to its GigaSECURE SSL/TLS Decryption solution, with new inline capabilities, bringing enhanced visibility into encrypted …