Create an Apache Web Server record in order to authenticate to an Apache web server running on a Unix host, and scan it for compliance. Unix authentication is required so you'll also need a Unix record for the host running the web server.
This record type is only available in accounts with PC or SCA and is only supported for compliance scans.
Did you know? You can allow the system to create Apache Web Server authentication records for auto discovered instances and scan them.
- Apache HTTP Server 2.2 and 2.4
- IBM HTTP Server 7.x, 8.x and 9.x
- VMware vFabric Web Server 5.x
- Pivotal Web Server 6.x
- Go to Scans > Authentication.
- Check that you have a Unix record already defined for the host running the web server.
- Create an Apache Web Server record for the same host. Go to New > Application Records > Apache Web Server.
Managers can add authentication records.
Unit Managers must be granted these permissions:
- Manage PC module / Manage SCA module
- Create/edit authentication records/vaults
We'll authenticate to each target host using the credentials provided in the Unix record. If the host is running IBM HTTP Server, VMware vFabric Web Server or Pivotal Web Server, then we'll check to see if an Apache Web Server record exists. If yes, we'll use credentials from the Unix record to authenticate to the Unix system, access the web server configuration, and scan it for compliance.
Yes, you can use the same record if Apache is installed in the same location on the hosts. The path to the Apache configuration file and to the Apache control command has to be the same for each target host specified in the IPs section of the record. If it's different then you need to create a separate record.
You can create multiple Apache Web Server authentication records with the same IP address defined - as long as the path to the configuration file is unique. Simply create one record for each host instance on the host.
Your PC reports identify compliance evaluation findings for Apache instances. Each instance string identifies the configuration file path.
Avoid duplicate instances reported - The way we report the instance changed in version 7.13 to include the configuration file path. We recommend you purge your hosts running Apache before you scan them with this version to avoid having duplicate instances reported - the old instance format and the new instance format.