It's all a matter of what you mean by "safe." A server machine is just a
computer, like any other. It is connected to the Internet, which means that
it can send and receive network traffic. What is accessible to whom via what
methods and/or network protocols and ports is all a matter of permissions.
These can be handled by a firewall, local or domain file and directory
permissions, or by an individual process, such as the IIS web services. IIS
is the listener for HTTP requests, and maintains its own set of permissions
regarding what resources it will serve via HTTP.
This means that if the IIS permissions are set right, nobody except the
authors and administrators of a web site should be able to download files in
protected folders, such as the _Private folder. HOWEVER, this does not mean
that such resources are *absolutely* protected. They are on the same machine
as the rest of the server software. This means that they may or may not be
accessible remotely via some other protocol, or even locally from the same
machine.
So, the bottom line is, how safe is safe enough? How can you ensure that
your data is secure? Short answer - you can't. At some point an element of
trust enters the equation. Do you trust your hosting service to know what
they are doing? Long answer - If you're running a web site, web server
permissions are probably all you need to know about. However, if that site
is accessible via FTP, those permissions should be checked as well. Beyond
that, you would have to ask all the right questions of your hosting
service - or trust them.
--
HTH,
Kevin Spencer
Microsoft MVP
Professional Chicken Salad Alchemist
Big thicks are made up of lots of little thins.
P@tty Ayers said:
Tom, my host company tells me that a folder above the web root is no safer
from hackers than one within the web root. Both are still accessible.