3 ms·
I have a lot of access to very confidential customer information at my job. But based on passwords I need to request that require someone else to approve. Based
by leokennis 4y ago
I have a lot of access to very confidential customer information at my job. But based on passwords I need to request that require someone else to approve. Based on a ticket/incident/change number that actually needs to exist. The password rotates as soon as it expires. All password requests and usage are logged and audited.
If you need to completely revoke someone's account overnight to prevent adverse impact, you designed your "access matrix" incorrectly.
- hn_throwaway_99 4y ago> If you need to completely revoke someone's account overnight to prevent adverse impact, you designed your "access matrix" incorrectly. This doesn't make any sense to me, and is in fact exactly how it should work. So you're telling me that every time, say, a CS rep needs to access some sensitive customer information (which is almost every single call), you think they should need to go through some password approval process? Security procedures that are so cumbersome to getting work done get bypassed. The whole point of SSO systems is that you can immediately revoke access to any and all systems at once by just changing one setting.
- leokennis 4y agoOf course it will depend on exactly how sensitive etc. the information is and there are always grey areas. But indeed, permanent access to sensitive info without ever needing approval from a second person (beyond being hired and gaining the access) seems like a bad idea.