STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM WebSphere Liberty Server Security Technical Implementation Guide

V-250341

CAT I (High)

Application security must be enabled on the WebSphere Liberty Server.

Rule ID

SV-250341r1015252_rule

STIG

IBM WebSphere Liberty Server Security Technical Implementation Guide

Version

V2R4

CCIs

CCI-000068CCI-002314

Discussion

Application security enables security for the applications in the environment. This type of security provides application isolation and requirements for authenticating application users. When a user enables security, both administrative and application security is enabled. Application security is in effect only when administrative security is enabled via the security feature. If the application server is to be used for only web applications, only the servlet-3.1 feature needs to be defined. If the application server is to be used for only ejb applications, only the ejbLite-3.1 feature needs to be defined. If both web and ejb applications are to be deployed on the application server, then both the servlet-3.1 and ejbLite-3.1 features need to be defined. The check and fix assumes that the application server will have both web and ejb applications deployed. Satisfies: SRG-APP-000315-AS-000094, SRG-APP-000014-AS-000009

Check Content

As a user with local file access to ${server.config.dir}/server.xml file, verify application security is enabled. 

If the appSecurity-2.0 feature is not defined within server.xml, this is a finding.

<featureManager>
<feature>appSecurity-2.0</feature>
</featureManager>

Fix Text

Configure the ${server.config.dir}/server.xml file and add the appSecurity-2.0 feature. 

<featureManager>
<feature>appSecurity-2.0</feature>
</featureManager>

Review ${server.config.dir}/logs/messages.log

Validate log entry that indicates "Security service is ready".