HTTPS or bust: Chrome’s plan to label sites as “Not Secure”

Google just announced that beginning in July 2018, with the release of Chrome 68, web pages loaded without HTTPS will be marked as “not secure”.
More than half of web visitors will soon see this warning when browsing unencrypted HTTP sites, according to data from Cloudflare’s edge that shows 56.62% of desktop requests originate from Chrome. Users presented with this warning will be less likely to interact with these sites or trust their content, so it’s imperative that site operators not yet using HTTPS have a plan to do so by July.

How did we get here (and why)?
To those who have followed the Chrome team’s public statements, this announcement comes as no surprise. Google has been gearing up for this change since 2014, as Chrome boss Parisa Tabriz tweeted and Chris Palmer memorialized in a widely distributed email. While this step is an important and potentially jarring one for users, it’s by no means the last step that Google will take to influence website administrator behavior for the better.
But why are they making this change (now)? Google’s primary motivation for driving HTTPS adoption is simple: a safe browsing experience is good for business. Users that feel Continue reading
The carrier deployed more than 300 microservices last year.
Enterprises continue to be the biggest server buyers — for now.
Verizon is planning to offer blockchain services for enterprises.
The company's approach is to diffuse an attack before it explodes.
The modem supports two concurrent LTE connections from two different operators.
The converged infrastructure offers pooled resources and greater scalability.
A new solution brief from Dell EMC and VMware discusses an innovative turnkey solution—Dell EMC NFV Ready Bundle for VMware—that is optimized to simplify and accelerate production deployments.