I have a database on my website containing semi-private information. It's not totally mission critical, but still I would like to take some measure of precaution that it doesn't accidentally or otherwise get downloaded or hacked.
I've noticed that if I go to:
I, or any user for that matter can download my db and see the data in it. So I have funny names for my direcories, but that seems to me to use the "run & hide" approach as opposed to a secure approach. I think some combination of the two will suit my security needs.
Q: how do I prevent that from happening in IIS - I have been browsing around in IIS, but apparently, I've missed somthing.
I am a nobody, and nobody is perfect; therefore, I am perfect.
I've noticed that if I go to:
I, or any user for that matter can download my db and see the data in it. So I have funny names for my direcories, but that seems to me to use the "run & hide" approach as opposed to a secure approach. I think some combination of the two will suit my security needs.
Q: how do I prevent that from happening in IIS - I have been browsing around in IIS, but apparently, I've missed somthing.
I am a nobody, and nobody is perfect; therefore, I am perfect.