High Level SysAdmin resigns...Mitigating Risk!! RRS feed

  • Question

  • I have spent some time on the internet and cannot find any baseline for mitigating risk when a high level SysAdmin resigns and moves on.

    Now this might sound like just another staff turnover, however the impact on security reaches far beyond. So the question came up?

    1. What needs changing?

    2. Who and when is change taking place?

    1. What needs changing?

    Ok, so the SA had access to all Admin passwords for the servers as well as all SQL server SA passwords. Over and above access to encryption keys for very sensitive data he also had access to admin rights on all desktops.

    2. Who and when is change taking place?

    Now the question is...who is changinging this and how do we do this as the current SA is still employed and the replacement only commences duties once the current SA moves on?

    Please give me your thoughts/links to an exceptable solution....if any?



    Tuesday, November 15, 2011 1:44 AM