5 ms·
It's kind amazing that Google keeps reiterating how their incredible security protects your data, and that even employees are extremely carefully monitored. Yet
by ocdtrekkie 10y ago
It's kind amazing that Google keeps reiterating how their incredible security protects your data, and that even employees are extremely carefully monitored. Yet their confidential trade secrets were taken by a dude who seemingly didn't have access to them as part of his job (since he had to go install the software) and a portable hard drive.
The post also says he talked about replicating their technology at a competitor with colleagues months before he actually stole the data too. Generally if you work on something confidential, and you start talking about taking it elsewhere, someone reports it or something.
Sidebar question if there are any armchair lawyers around: While I expect Uber to lose this lawsuit based on the type of evidence being claimed here, is it also possible for Uber to sue the supplier for leaking their confidential data back to Google? Because that seems like an incredible lapse of confidentiality in itself. Or will the notion that it wasn't legitimately their confidential data in the end, make Uber's own claim void?
- smilekzs 10y ago> is it also possible for Uber to sue the supplier for leaking their confidential data back to Google? My first reaction to the waymo announcement is also on this. "apparently inadvertently" sounds like a blatant lie.
- bobdole1234 10y agoChances are Google shares patent royalties with companies that help them build the technology they use, so the supplier was likely ensuring their continued royalties by informing on the infringement.
- deleted 10y ago[deleted]
- JoshTriplett 10y agoThere's a huge difference between security of user data and security of company secrets. Having access to the latter is not unreasonable; access to the former should be heavily restricted and closely monitored.
- aiiane 10y agoAnd it is.
- polishTar 10y agoThere's a number of tradeoffs to be made between internal secrecy/silos and trust/openness in any company, and google tends to lean heavily towards trusting their employees when it comes to corp data + resources, designs, strategy etc. User data is an entirely different matter, and is appropriately treated as such.
- ocdtrekkie 10y agoIt doesn't need to be about "secrecy", it's about "security". Even when you ignore the employee trust issue, and assume everyone at your company would never betray you, "least privilege" is still not just best practice for security, it's common sense. People should not be able to access data they don't need. If they need it, you can grant it. But the assumption should be that someone who doesn't use the design server shouldn't have access to the design server. I don't want to know about or see information I don't need to have at work. It's not that I'm not trustworthy. It's not that I would abuse it. I just don't need the liability that it gets out through me. Because your account credentials could get stolen. Your laptop could get stolen. Your laptop could get hacked into. Your laptop could get malware. Reducing the list of people who have access to a resource insulates against all of these things... automatically. And sure, all of those risks have other ways to mitigate them as well. But layers of security is key. And hey, it also stops employees from sneaking off with your data too.
- danielweber 10y agoTheir model was "trust the employee, and use the courts to enforce punishment if that trust was misplaced." We are in phase two of that right now.
- Harimwakairi 10y agoHaving access to code and data you don't technically "need" is often how people learn new skills and advance their careers without leaving the company. It's an important part of the culture.
- ocdtrekkie 10y ago
- bitmapbrother 10y agoI'd like to see you enter a Google data center and try to steal data.
- klodolph 10y agoI'd like to add to what other people are saying here. I've worked at a company where people were given, basically, the minimum level of trust. All the horizontal projects were dead, teams competed with each other for the same clients, and we chose meeting rooms to avoid being overheard by other teams when we were discussing things. It sucked. I left.
- ocdtrekkie 10y agoThis is entirely not related to what we're talking about here. It's not about trust, it's about good practice. If someone needs access to something, they request it, you grant it. Simple. But there should be common sense controls on data access, for everyone's benefit. You're talking about a hostile work environment. I'm talking about a secure one.
- klodolph 10y agoThat's more than just an oversimplification. Security is inherently hostile, I don't see any other way of putting things. We tolerate a certain amount of hostility in order to reap the benefits that security gives us, and we tolerate a certain amount of vulnerability in order to reap the benefits that laxness gives us. > If someone needs access to something, they request it, you grant it. Simple. The saying goes that for every complex problem, like security, there is a simple solution, like that one, and that solution is wrong. The cost of such a process is just too high for most companies. You have to request access, explain why you need access, someone has to review it, then grant it. That's how it worked at the company I was complaining about. Processes that should take minutes took hours, those that should take hours took days. Security, like so many things, is subject to cost-benefit analysis. Better security systems use the full triad: prevention, detection, and response. From the article, it sounds like these are working as intended. The security team detected the exfiltration and responded with a lawsuit. Trying to rely only on prevention will just lead to paralysis. I might also be jaded, because when I hear phrases like "good practice" my instinct is that it means "omitting the cost-benefit analysis."
- 10y ago
- cromwellian 10y agoThere's a huge difference between employees being able to see our source repository, and employees being able to see user data or secrets. Generally, Google values its openness internally, and most employees can see the source code of most projects. In fact, that's how large scale refactorings and bug fixes work: I find a bug, I might have to fix the library in question, but also find all callers in the entire code base and fix them as well. In general, when I develop, I virtually have all of Google's code base 'checked out' and can edit any of millions of files in my snapshot of the world. I don't need to check out multiple silo'ed repositories or beg for access, diving into any code in the universe has almost zero transactional overhead, it's all mapped into one giant filesystem. (https://plus.google.com/+MattUebel/posts/4dQBDF5CmdX https://plus.google.com/+MattUebel/posts/4dQBDF5CmdX) On the other hand, production systems are heavily walled off from the corporate network. For all intents and purposes, the corp network your desktop is plugged into is "untrusted" Nice try though.