![]() Before you make these kinds of adjustments/decisions, you have to be sure that you have the written backing of management.There are several issues at work here that need to be resolved. Despite all the preventative measures we put into place and training we did, somehow, this one user managed to get the virus.twice. For example, we have had ONE user bring down the entire company TWICE with ransomeware. In my little IT world at the company I work for I'm lucky if someone from higher management says anything to a user about their computer usage. It is fantasy, right? I agree that it is a people problem, but are solutions like this really enforceable?I agree that this is fantasy. NO software is worth losing your job over!I love the fantasy element of a solution like this. After firing one or two people (high ranking people are best here!), the word will quickly get out that doing this is NOT a good thing and you will find it stops pretty quickly. As soon as you find something that should not be there, just fire the user, citing their contract of employment. Then use a discovery tool to find out what software is being installed. You should first ensure that the employee's have a contract of employment that forbids them from installing software on company hardware. To me, the issue is more how to get the users to do the right things in the first place. It is fantasy, right? I agree that it is a people problem, but are solutions like this really enforceable? But some software does not need to write to more restricted places, thus can be installed without needing admin privileges. You can avoid some issues by ensuring the users do not have admin rights. This is more of a people problem rather than a technical one.
0 Comments
Leave a Reply. |