Groups | Blog | Home
all groups > iis security > july 2004 >

iis security : Trimming down App. Mappings in IIS 6.0


PaulT
7/27/2004 2:56:56 PM
I'm trying to find explanation for the application mappings
which get installed with IIS 6.0 and .net framework.

Which ones do we really need to keep if we are primarily using asp and aspx
(.Net)?

I would like to hear from the IIS admins if it's a good practice to trim
down the application mappings or leave them whatever IIS 6.0 sets up since
it is supposed to be secured to start with?

Appreciate your time.

..htw, .ida, .idq, .asp, .cer, .cdx, .asa, .idc, .shtm, .shtml, .stm,

..net:
=====
..asax
..ascx
..ashx
..asmx
..aspx
..axd
..vsdisco
..rem
..soap
..config
..cs
..csproj
..vb
..vbproj
..webinfo
..licx
..resx
..resources

Thanks,
Paul

Paul Lynch
7/28/2004 9:05:29 AM
[quoted text, click to view]

< SNIP >

Paul,

Have a look at this list, it might help you decide what to do :

http://www.iisfaq.com/Default.aspx?tabid=2552


Regards,

Paul Lynch
Bernard
7/28/2004 10:27:48 AM
Yes,it is always good practice to remove unused application mapping.
For asp, you only need asp and asa
For .net list, if you are sure you won't be using .asmx, you can remove it
as well.
so based on your application design, you should disabled those unneeded
extension.

Part of Urlscan installation, is to remove application mapping and map
unused extension to 404.dll

--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



[quoted text, click to view]

AddThis Social Bookmark Button