I am trying to ensure that customers on a shared IIS 5 server do not have the ability to access other directories except for their own through the FileSystemObject in ASP, or any other means for that matter.
I have managed to get this set up correctly (where only their website directory is visible to them) by restricting the NTFS permissions for the IUSR account, but am confused as to why it works in the first place. All the sites are currently running in pooled out-of-process mode, which from doing extensive reading causes ASP execution to be run in the security context of the IWAM account, not the IUSR or SYSTEM accounts. This being said, shouldn't the security context used in the execution of the FileSystemObject be that of the IWAM account, causing directory listing to fail because the IWAM account has no permissions over it?
How, exactly, does the IWAM account affect the security context of scripts run in pooled protection mode? Is the IWAM account only used to load dllhost.exe into process? Once it is in process and being used to process the FileSystemObject commands, does that object then use the IUSR permissions to physically browse the drive?
Thanks in advance.