3 ms·
Ok, but your private key, session tokens and CLI access tokens (kube configs, gcloud etc;) are your password in those situations. They tie to your identity, th
by dijit 3y ago
Ok, but your private key, session tokens and CLI access tokens (kube configs, gcloud etc;) are your password in those situations.
They tie to your identity, thus you must not treat them the same as company secrets, they are professional personal secrets which should not be disclosed or allowed to fall into anyone elses hands (less they be revoked and cycled).
It's not just good security posture it could affect your career quite badly or lead to legal issues.
- JohnFen 3y agoI agree. I don't think I've said anything counter to that (or perhaps I wasn't being clear?) > thus you must not treat them the same as company secrets, they are professional personal secrets They are company secrets that are tied to my identity. The company owns those secrets, not me. Just like my keycard to get into the building.
- dijit 3y ago> I agree. I don't think I've said anything counter to that (or perhaps I wasn't being clear?) I think given the context of the thread (don't touch my secrets), saying that you don't have anything you would consider confidential towards your employer or colleagues is a direct contradiction to what I stated. That's why I'm "arguing" because my employer/colleagues should not have access to my private key, ever.
- JohnFen 3y agoAh, OK. Then we do disagree to an extent. There are several very legitimate times when my employer needs to have access to my keys. If I'm leaving the company, for an obvious instance. But my core point is that such keys/passwords aren't really mine, they're the company's and in the end, the company gets to decide what I'm to do with them. I think the building access keycard is a perfect analogy. I'd never let anyone borrow mine on my own volition, but if the company wants to retrieve it from me, that's their prerogative. It's theirs, after all.
- brazzledazzle 3y agoIf an employer needs someone’s particular keys something probably went wrong or there’s bad processes in place. But that aside I think the default course of action should be to aggressively guard your secrets and tokens since they represent you. Not as personal or private property but to keep someone (be it a fellow employee or a 3rd party attacker) from impersonating you without authorization. There are exceptions but the circumstances where an employer would need to retrieve my keys without my assistance are extremely rare and in those instances it’s unlikely I’d still be an employee anyway.
- dijit 3y agoWe disagree. The handing of the keycard is necessary to ensure it's destroyed and can't be used as a "proof" you work somewhere (most access cards these days have your name, face and the company logo printed on the front). The keycard will be removed from the access list to the building even when it's destroyed, they're not considered reusable by most companies. Your private key is not reusable, it should be destroyed and revoked from all system when you leave a company.
- lmm 3y agoWe could destroy the keycard with both parties present, that seems safest. I don't mind turning in a private key permanently and getting a receipt at the time, but it needs to be very clear that it's no longer my responsibility.
- brazzledazzle 3y agoI’m not clear how we’re in disagreement here since I agree with this. When I say your keys/creds should be guarded I mean while they’re still valid.
- dijit 3y agoi replied to you and not the parent by accident. sorry.