|
|
|
|
|
by livueta
2386 days ago
|
|
I feel like if any one person can seriously subvert something, you've already lost. Maybe that's just my perspective from working at international enormous tech corp X, but we've already basically got that problem in the form of employees hailing from repressive states (yeah, Australia, that's you now too) where everything needs cross-signing anyway. All in all, I'd probably be more concerned about foreign nationals open to various forms of coercion than I would felons - in the general case, anyway. Of course, there are certain environments where more assurance is needed and not employing from either category is reasonable, and the type of criminal background also matters. For instance, someone from a bad neighborhood who got swept up in gang activity like the guy in the article is probably a lot less likely to try to fuck you over than a serious convicted blackhat/fraudster. It's also possible to, as in the article, explicitly limit their roles to those that don't touch customer data or sensitive product code, where it'd be significantly more sufficient to parlay access into a quick payout. One ironic thing is that's frequently the exact opposite of how it works in practice: think of all the crooked telco CS reps who've been doing SIM swaps recently. Those roles aren't exactly exclusive positions, and I'd argue they're a good example of why paying people crap combined with poor vetting and lots of access is a bad idea. |
|
I think a baseline level of trust is an absolute requirement, regardless of how well implemented your organizational access security is.
I would say that any company source code, by definition, is a company secret, and there will always exist an easy means for an employee to leak or compromise that secret.