Does your application require customizing System.Net.WebPermission, SocketPermission or DnsPermission settings?
.Net frameworks comes with deefault security settings where components running under Intranet, Internet Zone can only have WebPermission to connect back to the server, from where they are downloaded. Also the component from Intranet zone and Internet zone don't have any SocketPermission and DnsPermission by default.
I am trying to find out some real world usage scenarios, where people are customizing these security settings for there application or components in either intranet or internet zone deployment. Special interest is WebPermission, SocketPermission, DnsPermission or NetworkInformationPermission (NetowrkInformationPermission is only in .net frameworks 2.0).
If you are one of them, please drop your comment about scenario and your experience with it.