In part 1 and part 2 of this three part series, I covered how to implement security procedures easily (especially if said churches don’t have resources to have IT people on staff) for both the infrastructure and for individual use.
In this final part, I am going to cover a few other best practices to help with your IT security.
Ready? Let’s go…
1. Take it Home!
If you use notebook computers, take them home at night.
It astounds me how many times I see people leaving their portable computers in the office. Churches get burglarized. It happens. An average of 4500 churches per year are burglarized. One in every four church fires is arson related. Don’t let sensitive data and information get into the hands of thieves. Take your notebook computer home.
2. Update Your Computer Software
This includes your operating system as well as programs, particularly security programs. Yes, Windows seems to have new updates every day and it’s tedious to have to continually install these updates, but they are necessary. Make sure your anti-virus and anti-spyware programs are set to automatically update.
These patches and updates are important.
3. Do Not Share Your Passwords
I know that if you work in a church, the issue of trust should be strong, but it still doesn’t mean just handing your password off to anybody (though you should have somebody that will make sure to keep you accountable and you should allow them full access to your computer).
They may be trustworthy, but they may also be dangerous when logged into a computer.
4. Chain Emails, Hoaxes, and More
By forwarding chain mails, virus hoaxes, and more, the only thing you’re assured of is getting even more of them in the future and possibly infecting your computer (and others) with malware or a virus.
5. Log Off and Lock Your Computer
Even if it is only for a moment.
If you are in a church where offices are cut off from the rest of the church, maybe it seems like a waste of time, but there are many churches where offices are in the same area as a lot of foot traffic. It doesn’t take long for somebody to get on your computer and get it messed up even if the harm caused was unintentional.
IT security for a small church or a church with a small staff and no IT staff doesn’t have to be an issue. Follow the practical steps laid out in this series of posts (and the comments!) and you’ll be on your way.
Any other suggestions?
[Images via dheuer, Florian, lunchtimemama]
Stuart says
In line with your fifth point – don’t log others onto your or any other computer.
If they need access, then let them submit an appropriate request.