3 ms·
Google so far hasn't shown much knowledge of endpoint security, uses many stacks with huge attack surface, and plays penetrate/patch. That's from their web serv
by nickpsecurity 11y ago
Google so far hasn't shown much knowledge of endpoint security, uses many stacks with huge attack surface, and plays penetrate/patch. That's from their web services all the way to mobile. Third parties, both companies and FOSS types, are doing better at protecting Android than Google. Although there's exceptions, Google seems mostly unqualified or uncaring in terms of strong INFOSEC.
So, I have little trust in the security of ARTOS or Vault for now. I tried to review the ARTOS kernel's design but they pulled it off their site. So, we have nothing to go on but their word. I can't wait to get some more objective information about its design and implementation for a real review.
- x5n1 11y agoFrom a political standpoint I don't know how many people would trust a Google product with security. Just the brand does not jive with the idea of security. Perhaps the product is good, I don't know. But FUD is in order considering the brand and its general past actions.
- nickpsecurity 11y agoI agree. The Snowden leaks showing they're tight with NSA can't help that, either. I'll go further, though, with my main privacy argument against companies such as Google: the incentives of an ad-driven company are 100% opposite of privacy-seeking users. Expecting Facebook, Google, Yahoo, etc to protect one's privacy is ludicrous as they get more money for each privacy violation if not convicted in court. The only kind of company that can be even semi-trusted is one that where you are the paying customer and their contract + host country's laws protect your privacy/security. Even more so if they have to contractually or legally pay huge fines for negligence. Align the incentives, then there's potential. If opposite incentives, turn 180 degrees and start running.
- deleted 11y ago[deleted]
- irascible 11y ago*jibe? Jive means BS.. jibe means "aligns with".. also fud can mean "fear uncertainty and doubt" or "fucked up disinformation".. Having said all that, I think it's a pretty neat idea to invert the Sim card firmware vulnerability into an asset. We'll have to see what comes of it..
- delroth 11y agoCare to show the huge attack surface in ChromeOS for example?
- nickpsecurity 11y agoI'd have to have its full details in front of me. Given how netbooks usually work, I'll hit you with a few questions and review it further if you have secure answers. Does it use regular firmware for its hardware or firmware hardened against attack? Are the drivers isolated in user-mode? Is the trusted software verified by eye, tool, or both to avoid all known code injections? Was that verified by third parties? Does it avoid software with huge TCB and many vulnerabilities such as Linux? Does it avoid Web apps and tech such as Flash? If yes to all of these, then it's a start on strong security and definitely worth reviewing if only to help close remaining holes. Otherwise, it's probably already received a number of patches and not worth a review. Which is it?
- kllrnohj 11y ago> Google so far hasn't shown much knowledge of endpoint security, uses many stacks with huge attack surface, and plays penetrate/patch. [citation needed] > Third parties, both companies and FOSS types, are doing better at protecting Android than Google. such as...? > Although there's exceptions, Google seems mostly unqualified or uncaring in terms of strong INFOSEC. Eh? What's your basis for this claim? They are pretty much always on the latest & greatest. ECHDE_RSA, certificate pinning, universal 2nd factor (FIDO), strong sandboxing & permissions (you may not remember, but those were things Google took mainstream with Chrome & Android). Google's also the company that took security vulnerability rewards and made that a thing. Plenty of things to dislike Google about (privacy is always an easy target, for example), but security really isn't one of them. They have one of the best trackrecords you can have here.
- dmix 11y ago> Third parties, both companies and FOSS types, are doing better at protecting Android than Google. I'm working on a 3rd-party OSS project securing Android https://copperhead.co/android https://copperhead.co/android (/shameless self plug) While Android is in pretty bad shape, I'd still give Google some credit, they have been slowly starting to improve their OS security in the last 2 years. But quite a few early design choices favouring performance over security, such as Zygote rendering ASLR ineffective, are lingering and holding back Android's security. They are also using Linux kernels from 2012 or earlier (3.4) on almost all devices, although from what I've heard that is mostly the fault of vendors such as Qualcomm moving slowly.
- kllrnohj 11y agoBad shape? How so? Zygote is more about memory than performance, and that's still a needed thing. SELinux is in enforcing mode and has an increasingly tighter and tighter net. Also Google is using 3.10 on the devices they sell, not 3.4. What Samsung, HTC, etc... ship is a different story, but that's not under Google's control.
- dmix 11y ago