Quote:
Originally Posted by perdurabo
IIS (Microsoft's web server, which is reasonably secure by default these days)
|
Only if you keep it patched. Right out of the box, it's still vulnerable to a LOT of stuff. This brings us to our next lesson:
Don't take too long to patch stuff. Here's how a zero-day exploit works (for the non-techies):
1) MS releases a patch.
2) hacker downloads the patch
3) hacker reverse engineers the patch (takes it apart to see how it works, and what it does)
4) If he can find what the patch fixes, he knows the vulnerability.
5) Write an exploit to attack that vulnerability
If he can do this within a few days after patch release, he can own millions of boxes, since most users are lazy with patching. Corporate networks take a long time to patch for a different reason, which brings us to another lesson:
Test patches before you install them on a production server. I use virtual machines for patch testing. Install the patch on a machine that doesn't affect business. Make sure it works. DON'T TAKE TOO LONG TESTING PATCHES. While you're testing it, hackers are writing exploits, and if you take too long, they win.
(My response is a bit of a ramble, and for that, I apologize. I'm tired, and running on nothing but coffee. I'm trying to get information on the screen before I lose my train of thought. If anyone has questions, feel free to ask.)