Google Opens Up Chrome and Chrome OS To Enterprise Security, Control Integrations (theverge.com) 10
Google is highlighting how Chromebooks can work in "zero trust" corporate environments with its new Chrome Enterprise Connectors Framework. From a report: The new integration system is designed to make the Chrome browser and Chrome OS devices easier for IT departments to implement with existing security, endpoint, and authentication solutions as well as bother management solutions. Google Chrome OS exec John Solomon describes the new tools as a "plug and play" solution that lets other companies helm Chrome OS management functions like remote-wiping a Chromebook using BlackBerry Unified Endpoint Management or flagging malware downloads with Splunk. These types of management functions previously worked through the Google Admin console. Managing and enrolling Chrome OS devices in the enterprise will still rely on Google tools like Google Admin and Chrome Browser Cloud Management. But new tools like Chrome OS Data Controls give enterprises more options to allow or lock down actions like printing, screen capture, copy / paste, and other potential data loss situations. It might even give IT a better handle on buggy Chrome OS updates and is currently available through the Trusted Tester program.
Chromebooks / Chrome OS hardware is limited and (Score:2)
Chromebooks / Chrome OS hardware is limited and software for it small (it can do Linux but in an VM with out direct GPU)
also blocking screen capture, copy / paste can brake apps.
Re: (Score:2)
Also, zero trust doesn't mean Google won't know the IP address used to connect to the Internet and that they can't collect data.
Re:Chromebooks / Chrome OS hardware is limited and (Score:5, Interesting)
Ransomware and this other bullshit would stop literally overnight if we went back to dumb terminals.
Ransomware infections are not exclusively initiated by end-user activities. Even in the days of dumb terminals, attacks could occur due to exposed software vulnerabilities. I'm old enough to remember attacks like the Morris Worm [wikipedia.org] and Code Red [wikipedia.org], for example.
There have been many serious vulnerabilities since, such as the recent Log4j [theconversation.com] debacle, which have been used for ransomware attacks, and would not have been been mitigated by using dumb terminals.
oh bother (Score:3)
> bother management solutions
I think this is Google's real position here.
Zero Trust? (Score:1)
It does something, and you can argue that it might be easier or more useful if you really squint, but really it's just a gimmick.
Give it 5 years and maybe.
Re: (Score:3)
Actually the concept of zero trust is good, and not even new. Without all the hype, zero trust is this:
Don't trust users based on their IP address, user agent string, or other non-authenticated information.
So if you work in a place where you have services like MariaDB, SSH, remote desktop, or whatever web app allowing connections based on the IP address of the client, without authenticating the user, then your services are vulnerable to an attacker that managed to get past one layer of security. You don't
Ah yes, their old embrace extend cancel (Score:1)
Chromebooks & "zero trust" corporate environme (Score:3)