We have all heard alot about trojan horse programs and the threat that they pose to your network's security. This Trojan FAQ sheds some light on what these programs are, what they do, how they can infect your network and suggests measures that could be taken to prevent such infections. You can make sure that you have a good grasp on these malicious programs by browsing through this regularly updated Trojan FAQ which provides the answers to these questions and many others. With thanks to Dancho Danchev for his contributions to this FAQ.
Here's a summary of the whole FAQ. You'll learn how to behave in a secure manner while reading these tips, and don't forget that they could be a lifesaver as far as Windows Trojan threats are concerned.
Security Policy
First of all you should establish an Anti-Malware Policy, guiding the staff members on the process of protecting critical company data from destruction or exposure. It needs to clearly state their responsibilities while using any of the company's Information Resources, thus making sure that it will be easily understood and properly implemented later. You should define what is allowable and what is not, what they should and what they shouldn't do in order to keep their workstations, as well as the company's network free of malware. Keep it short, precise and easy to understand, know your audience before your start building it, measure their computer/security level skills for maximal effectiveness. A sample Anti-Virus Policy can be found here.
Gateway Protection
You might consider using Gateway Protection, detecting and blocking malware at the Server level before reaching the workstations. A few reasonable products for this activity are:
Content Blocking
Another valuable strategy that might be implemented, in the company's effort to protect its critical data from malware, is to filter known to be dangerous and potentially destructive file extensions at the Server level. These include: .exe, .com, .vbs, .scr, .asd, .asf, .asx, .bas, .bat, .chm, cmd, .com, .dll, .exe, .hlp, .hta, .hto, .js, .jse, .link, .lnk, .pif, .reg, .scr, .vb, .vbe, .vbs, .wsf, .wsh, and .wsc. A list of dangerous extensions may be found here.
Whenever someone from the company needs to receive a specific attachment having one of these extensions, the receiver might ask the sender to change the file's extension, and in this way confirms that indeed, a known person has sent the attachment.
In your Anti-Malware Policy, you need to state whether the use of Free E-mail providers is allowed or it is strictly prohibited. Educate them on the problem of potentially destructive attachments, downloaded from their external e-mail and run on the company's network. On the other hand, if the use of these services is prohibited due to security policy, then block access to these and let your staff members know that the proper use of the E-mail system is being strictly monitored.
Discuss your security issues with thousands of other network security experts. Click here to join!