Why is malicious SSL traffic not generating alerts after you have edited the httpd.conf file?
If the system administrator changes the User and/or Group name of the Apache owner to a non-default value in the httpd.conf file, the agent will not be able to scan the SSL traffic.
The agent uses the /tmp/.issx_key object which is owned by the previous Apache user/group. Because the owner user/group has changed, the SSL monitoring component will lose access control rights over this object and monitoring for this traffic will fail.
Important: When performing administration tasks via ssh or local console, configuration changes made to your IBM appliance by any user other than admin could degrade appliance performance. Installing or activating other services or applications may also impact appliance performance or security. IBM Infrastructure Security Support will not support configuration changes made using the root user account unless specifically directed by a support engineer or IBM documentation. The following DCF Technote content is supported. Any further changes made that are not included in this document will place your product into an unsupported state and IBM product support may require you to reimage your appliance to restore it to a supported state.
To avoid this issue, the system administrator needs to ensure that the ownership of /tmp/.issx_key and the Apache processes are the same. This can be done using the following steps:
- Access the command line on the server on which the agent is installed.
- Enter the following to stop the agent service:
- Change the owner and/or group for the file with the following command:
GroupNamematch the name and group that you set for the Apache owner.
- Enter the following to start the agent service:
- Restart the Apache service. The command for this will vary depending on what version of Apache you are using.
If the above information does not resolve your issue, contact IBM Security Systems Customer Support.