Hello everyone, I am new at the whole email game. I was wondering what file extensions you guys have blocked from sending and recieving ? So I am taking a pole..........
Posts: 3436
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline
I have used the list that Microsoft have blocked for Outlook 2002 and later. Basically it blocks any executable file or data file that can be executed Common ones to block are: EXE, COM, SCR, PIF, VBS, VB, VBA, VBER, LNK, BAT, CMD, SCT, SHS etc.
In my company, we block anything that can be executed on the desktop. This covers EXE, COM, BAT, CMD, VBS, PIF, WSF as well as media related files like WMV, MOV, MPG, MPEG, WAV, WMA, AVI, MP3, MP4.
All of these files are quarantined for a specified period of time before being deleted. That way if something truly critical were sent, it could be recovered easily enough.
Thats a good policy................they both are, sounds like anything that can be executable. So here is a question, do you guys block zip files? or no.
Yes and no. I block password protected ZIP files in the same fashion as the other files. I do let normal ZIP files go through, but I scan the contents of the ZIP files and will block them if they contain files that match the other criteria.
Posts: 420
Joined: 24.Feb.2003
From: India
Status: offline
Irrespective of what you use to scan the E-mail , these are the basic rules.
- Executables ( all that can execute) - Zipped Files ( Either way, password protected files are not probed completely) - Via-Media ( all Music, Image files, movie files of any format, Html or Shtml web attachments)
Remember : When you block the extension, you ensure that you are only "FILTERING" the known devils. The better way to fix this would be to ensure that you setup a good client side Anti-Virus software that will scan the mail, when it is being streamed from the Server to the Client.
I have a related question. Can you allow certain attachments within your domain? we currently have .aspx and the like blocked, but need to open them up for mail coming from within our network. How can this be done?
Posts: 3436
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline
I suggest you tell users to ZIP up such files to be distributed by Email, then you are not compromising email security. I just takes one bad mail to get through to infect a pc.
Posts: 6791
Joined: 9.Jun.2004
From: Philadelphia PA
Status: online
The most obvious thing here is to send a shortcut to the file rather than send the actual file.
I am never a fan of the Level1Remove feature on Outlook because there are too many rogue variables. Blocking at the gateway is far more sensible. If you did block at the gateway then any attachment could be sent internally.
Just about the last thing I would do would be to have the users zip the file and then email it.
Posts: 3436
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline
Why send shortcuts? If the file is located somewhere inaccessible to other users, a shortcut will just get a permission denied, it may be ok with web urls or paths to servers shares that the recipient has access to but useless otherwise.
Posts: 420
Joined: 24.Feb.2003
From: India
Status: offline
Hmmm
Question : Is it mandatory to send the Aspx attachment ?. From a security perspective, i'm sure that you'd like to limit the information that can reside on a messaging server or the client side. Simple enough, if you give me an attachment and i can misuse it.
We need to move away from the conventional thinking to something like,
a. You can send the Hyper link to the user, and they can access the same. b. There are enough "open source" pdf file burners, so you can automate to generate *.pdf files. c. Change the file extension of the same across to say .asp1. Educate your users to point to the IE to open and render the attachment (Crude but effective ;))