| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
3.5.3.2 Web Servers (Page 1 of 4) Web servers are often a companys primary interface with the outside world, since a companys web site is generally accessible to anyone, with no authorization required.
Web servers accept HTTP requests on port 80, and HTTPS requests on port 443. You can change these port numbers, if you wish, but understand that unless your site visitors know the alternate port number at which your site lives, they wont find it.
When looking at hardening your web server, you actually need to look at a variety of tasks (in addition to hardening the machine on which the server software is running). In the early 1990s, a web server consisted of just the server software itself and a bunch of static pages displayed upon request. Time marched on, and now web servers typically include some sort of application server to process pages whose content is dynamically created, such as JSP or ASP pages. So, hardening a web server includes:
Home - Table Of Contents - Contact Us CertiGuide for Security+ (http://www.CertiGuide.com/secplus/) on CertiGuide.com Version 1.0 - Version Date: November 15, 2004 Adapted with permission from a work created by Tcat Houser et al. CertiGuide.com Version © Copyright 2004 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||