Hi,
I'm trying to set up an FTP account for an untrusted third party using IIS 7.5. For security reasons, I created a new website and ftp under IIS (i.e. running under "thirdparty.example.com" instead of the main "www.example.com" and in its own folder).
What worries me is that all the guides suggest that the FTP logins are granted via Windows user accounts, so (e.g.) if I want to grant this person access via the "thirdparty_ftp_user" FTP login, I need a Windows user account with that name and password?
Does it *have* to be done this way?! I'd rather set up an FTP login that *wasn't* the name of a user account so there wasn't the risk to begin with of them being able to do anything beyond FTP.
Currently, I have:-
- Set up a "thirdparty_ftp_user" Windows account as a normal (non-Administrator) user
- Removed the "Users" group from the account
- Disabled remote login (this displays a message to that effect if this is attempted) (*)
Is there any way I can restrict the account's permissions and activity *only* to the specified FTP folder so they can't go anywhere else on the system? Although in theory the user shouldn't be able to log in, I can "runas" this user and still navigate around the Windows directories etc.
I appreciate that user isolation exists, but this appears to be to isolate FTP users *from each other*, i.e. giving them separate subfolders. I'm not actually that bothered about them having control over the entire "third party" subfolder, it's the rest of the system I'm worried about!
Would appreciate any feedback if there's something I've missed out! Much appreciated,
- MM