Difference between revisions of "Redhat: Apache security"
Jump to navigation
Jump to search
(Created page with "== Apache Security == Apache can be made secure through several layers of security. * IPTables can limit access to the system * Apache Configuration ptions can limit access ...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 17: | Line 17: | ||
== Apache and SELinux == | == Apache and SELinux == | ||
| + | |||
| + | * [[Redhat: Apache_webserver_SELinux_Booleans | Apache Webserver SELiniux Booleans]] | ||
| + | * [[Redhat: Apache_webserver_SELinux_Types | Apache Webserver SELiniux Types]] | ||
| + | |||
| + | |||
| + | == Security within Apache == | ||
Latest revision as of 14:25, 18 August 2013
Apache Security
Apache can be made secure through several layers of security.
- IPTables can limit access to the system
- Apache Configuration ptions can limit access to users, groups and hosts
- Secure Apache Websites Encrypt Communication
- SELinux can limit can Limit Damage should there be a problem
Ports and Firewalls
The webserver uses ports 70 and 443 by default. These must be open in the firewall to allow communication. These can be configured as trusted services.
Of course if you use non-standard ports these must be manually opened in IPtables.
Apache and SELinux