managing application access with higher staff turnover ?

[scott_e]

Afternoon.

Anyone else got the headache of your organisation spawning the introduction of multiple online tools for project management , development , billing , CRM , whatever etc .... and if so how to you manage it.

Organisation is growing , we have offices in multiple locations = more staff joining = more staff leaving = resulting in potential security holes.

Planning a full audit of all systems and who has access to what seems a good starting place.
Develop some sort of policy around adding access , removing access , introduction of new tools.
One person = 1 user would help.

Much of its is security 101 common sense. Want to get this right in the short term so its not a problem in the long as we grow.

Interested to know how other organisations cope with these issues.

Cheers
Scott

[Ferg]

Try to balance the size of the systems audit you do by scoping it down to business functions. Taking on the whole thing from a blank sheet of paper is likely not to balance as far as time/accuracy and the business need and time frames you'll have. This has certainly worked for me and IME allows a more objective review within a smaller set of stakeholders and budget areas.

[scott_e]

Thanks for the PM Ferg , you have reply.

[Sanjøy]

SMS the new passwords out every morning, if you dont get a password....

[scott_e]

SMS the new passwords out every morning, if you dont get a password....

Thanks for the reply Sanjoy. Talking 50 if not 100 different systems, some with APIs , some without. Would be impossible to automate.

[Ferg]

Hey Sanjoy, you're getting slowly polluted by exposure to corp banking.