I've setup three domain accounts for use by our ERP vendor, our PBX vendor and our MSP, so that they can do remote support on our servers. I'm paranoid about giving them access, as I don't feel vendors always take client security all that seriously, but they need remote access, especially when I'm on holiday, so what can I do. I initially created a Logmein account for them, so I can control access and log activity, but they hate that as they prefer to use their own Logmein/Teamviewer accounts, which I can understand. Unless I make it really simple for them, there's a high probability that I'll get called on holiday because they can't remember how to get access, so it's in my personal interest to let them use their own workflow to keep things simple and reliable for them.
Previously I'd disabled their domain accounts and only enabled them when I knew they wanted access. After they'd done what they needed to do, I'd disable the account. But this relied on me remembering to enable the accounts before I went on holiday. I could script this to make it easier. It wouldn't cover my sick-leave though, as I can't predict when I'm going to be sick. I could arrange for my colleague to run the script, but this adds a layer of complexity that increases the probability of failure. When the s**t hits the fan, the last thing you need is for the vendor to be unable to connect to solve the problem.
I was thinking of setting something up that e-mails me every time a vendor logs in to the domain. They're supposed to tell me whenever they connect, but they don't. Can anyone explain how I might achieve this?
Also, any general advice on managing vendor remote access to get the right balance between security and simplicity. Am I being too paranoid/controlling?