Apache Web Server

This pack includes Cortex XSIAM content.

What does this pack contain?

• XDRC (XDR Collector) and Broker VM syslog integration.
• Modeling Rules for the following events:
  • Access Logs
  • Reverse Proxy Logs
  • Error Log

Configuration on Server Side

Apache httpd configuration:

You need to configure Apache Web Server to forward Syslog messages.

Open your Apache Web Server instance, and follow these instructions Documentation:

1. Log in to your Apache Web Server instance as a root user.
2. Edit the Apache configuration file httpd.conf.
   • Ensure to keep a backup copy of the file.
   • Edit one configuration file at a time. Save the file after each change and monitor its effect.
   • For further information on Apache Log Files - Documentation
3. Add the following information in the Apache configuration file to specify a custom path for the syslog events:

   CustomLog "|/usr/bin/logger -t httpd -p <facility>.<priority>" combined 

Where:

• facility is a syslog facility, for example- local0.
• priority is a syslog priority, for example- info OR notice.

1. Disable hostname lookup:

   HostnameLookups off

5. Save the configuration file.
6. Edit the syslog configuration file:

   /etc/syslog.conf

7. Add the following information to your syslog configuration file:

   <facility>.<priority> <TAB><TAB>@<host>:<port>

Where:

• facility - This value must match the value that you typed in the step 3.
• priority - This value must match the value that you typed in step 3.
• TAB - Indicates you must press the Tab key.
• host - The syslog destination IP address.
• port - The syslog destination Port.

1. Save the syslog configuration file.
2. Restart the syslog service:

   /etc/init.d/syslog restart

10. Restart Apache to complete the syslog configuration.

Apache Reverse Proxy configuration:

To configure Apache Reverse Proxy logging, see the following guide here.
Supported log format for Reverse Proxy logs is:

%V:%{local}p %A %h %l %u %t \"%r\" %>s %B \"%{Referer}i\" \"%{User-Agent}i\" %P %D %{HTTPS}e %{SSL_PROTOCOL}x %{SSL_CIPHER}x %{UNIQUE_ID}e %{remote}p %I %O \"%{Host}i\" main %{CF_RAY_ID}e %{CF_EDGE_COLO}e

Custom Log Format string description list can be found here.

• Pay attention: Timestamp Parsing is only available for the default %t format: [%d/%b/%Y{Key}%H:%M:%S %z]

Collect Events from Vendor

In order to use the collector, use the Broker VM option.

Broker VM

To create or configure the Broker VM, use the information described here.

You can configure the specific vendor and product for this instance.

1. Navigate to Settings > Configuration > Data Broker > Broker VMs.
2. Right-click, and select Syslog Collector > Configure.
3. When configuring the Syslog Collector, set the following values:
   • vendor as vendor - apache
   • product as product - httpd

XDRC (XDR Collector)

You will need to use the information described here.

You can configure the vendor and product by replacing [vendor]_[product]_raw with apache_httpd_raw.

When configuring the instance, you should use a YAML file that configures the vendor and product, as seen in the configuration below for the Apache Web Server

Copy and paste the contents of the following YAML in the Configure the module section (inside the relevant profile under the XDR Collectors Profiles).

Configure the module:

The following example shows how to set paths in the modules.d/apache.yml file to override the default paths for Apache HTTP Server access and error logs:

- module: apache
  access:
    enabled: true
    var.paths: ["/path/to/log/apache/access.log*"]
  error:
    enabled: true
    var.paths: ["/path/to/log/apache/error.log*"]