Our offices are scattered across five universities, several technical colleges and some off-campus locations, so things like virtual private networks (VPN) are not feasible -- too many network fiefdoms are involved.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
FTP, (Internet Information Server) IIS and WebDav could be used, but are subject to a lot of hacking. (Secure Shell) SSH and Rsync are attractive but involved. Your recommendations would be appreciated.
From the solutions you mention, I'm assuming the latter. Without knowing more about your situation, I'd look at (Secure Sockets Layer) SSL/IIS combination. Of course you have to secure IIS, and you must obtain a certificate for SSL, but you can secure the operation including authentication. Turn on auditing to log file access and authentication. IIS logs will include info on transfer, security log on logon and file access. The reason for using SSL is that to get user names in audit. You need NTFS and Windows authentication on IIS, and you don't want user credentials crossing networks in clear. With SSL, the connection is made, and then even the password and user name will be encrypted.
Dig Deeper on Windows mobile device management
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.