STIGUI
V-250327CAT II — Medium severitySV-250327r1265256_rule

The WebSphere Liberty Server must be configured to offload logs to a centralized system.

Rule version IBMW-LS-000230 · STIG v2 · 2026-09-10

Discussion

Log processing failures include, but are not limited to, failures in the application server log capturing mechanisms or log storage capacity being reached or exceeded. In some instances, it is preferred to send alarms to individuals rather than to an entire group. Application servers must be able to trigger an alarm and send an alert to, at a minimum, the SA and ISSO in the event there is an application server log processing failure.

Satisfies: SRG-APP-000109-AS-000070, SRG-APP-000358-AS-000064

Check

As a privileged user with local file access to ${server.config.dir}/server.xml, verify the logstashCollector-1.0 feature is enabled.

grep -i -A5 logstashcollector server.xml

EXAMPLE: <featureManager> <feature>logstashCollector-1.0</feature> </featureManager>

<logstashCollector source="message,accessLog,audit" hostName="<ip address of logstash server>" port="<port of logstash server>" sslRef="DefaultTLSSettings" </logstashCollector>

If "logstashCollector" is not a configured feature and the logstashCollector "source" setting does not contain "message,accessLog,audit", this is a finding.

Fix

To send Liberty logs to a centralized syslog system, the Elastic environment must be set up as per the ELK stack/Elasticsearch directions. Once that is completed, configure the server.xml. The following is a sample configuration. Individual keystore, truststore, and authentication settings will vary. The SME must substitute their own values as needed.

The message, audit, and accessLog sources must be included at a minimum.

For additional information refer to the IBM website: https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.WebSphere.wlp.doc/ae/twlp_analytics_logstash.html

EXAMPLE:

<featureManager> <feature>logstashCollector-1.0</feature> </featureManager>

<keyStore id="defaultKeyStore" password="xxxxxxx" /> <keyStore id="defaultTrustStore" location="trust.jks" password="xxxxxxx" /> <ssl id="myTLSConfig" trustStoreRef="defaultTrustStore" keyStoreRef="defaultKeyStore" />

<logstashCollector source="message,accessLog,audit" hostName="your ELK stack server" port="Your ELK stack port" sslRef="myTLSConfig"> </logstashCollector>

Identifiers

Group ID
V-250327
Group title
SRG-APP-000109-AS-000070
Rule ID
SV-250327r1265256_rule
Check ID
C-53762r795032_chk
Fix ID
F-53716r795033_fix