Detections
Analytics

1.3 Ensure Apache Is Installed From the Appropriate Binaries

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

The CIS Apache Benchmark recommends using the Apache binary provided by your vendor for most situations in order to reduce the effort and increase the effectiveness of maintenance and security patches. However, to keep the benchmark as generic and applicable to all Unix/Linux platforms as possible, a default source build has been used for this benchmark.

**Important Note**: There is a major difference between source builds and most vendor packages that is very important to highlight. The default source build of Apache is fairly conservative and minimalist in the modules included, and therefore starts off in a fairly strong security state, while most vendor binaries are typically very well loaded with most of the functionality that one may be looking for. _**Therefore, it is important that you don't assume the default value shown in the benchmark will match default values in your installation.**_ You should always test any new installation in your environment before putting it into production. Also, keep in mind you can install and run a new version alongside the old one by using a different Apache prefix and a different IP address or port number in the 'Listen' directive.

Rationale:

The benefits of using vendor supplied binaries include:
- Easy installation; it should work straight out of the box.
- It is customized for your OS environment.
- It has been tested and gone through QA procedures.
- Everything you need is likely to be included, probably including some third-party modules. Many OS vendors ship Apache with 'mod_ssl', OpenSSL, PHP, 'mod_perl' and 'mod_security', for example.
- Your vendor will tell you about security issues, so you have to look for information in fewer places.
- Updates to fix security issues will be easy to apply. The vendor will have already verified the problem, checked the signature on the Apache download, worked out the impact, and so on.
- You may be able to get the updates automatically, reducing the window of risk.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

Installation depends on the operating system platform. For a source build, consult the Apache 2.2 documentation on compiling and installing [http://httpd.apache.org/docs/2.2/install.html](http://httpd.apache.org/docs/2.2/install.html). For Red Hat Enterprise Linux 5, the following 'yum' command could be used:

# yum install httpd

See Also

https://workbench.cisecurity.org/files/2020

Item Details

Category: SYSTEM AND INFORMATION INTEGRITY

References: 800-53|SI-2, CSCv6|2

Plugin: Unix

Control ID: c9f7a0ef096dd599136aa77b36cb312d29a4c814cd162d8ab9c0611856b901dc