STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to IBM WebSphere Traditional V9.x Security Technical Implementation Guide

V-255834

CAT I (High)

The WebSphere Application Server Java 2 security must not be bypassed.

Rule ID

SV-255834r1137578_rule

STIG

IBM WebSphere Traditional V9.x Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-000213

Discussion

WebSphere provides a passive filter mechanism that will allow administrators to set Java 2 security in the admin console as enabled while still allowing applications to access host resources. This setting bypasses the enforcement of Java2 security. Application access is allowed and activity is logged to the system.out file. This feature is to aid in the identification of application access requirements to the underlying host so security policies can be created. This feature is executed via a custom property that is set for each application server instance operating on the WebSphere server. This setting should only be enabled in a development or testing environment in order to identify what applications access requirements are so security policies can then be created.

Check Content

If the system is a development or test system, this requirement is NA.

From the admin console, select Servers >> Server Types >> WebSphere application servers.

For each application server, select Server Infrastructure >> Administration >> Custom properties.

If the "com.ibm.websphere.java2secman.norethrow" resource value exists and is set to "true", this is a finding.

Fix Text

From the admin console, select Servers >> Server Types >> WebSphere application servers.

For each application server, select Server Infrastructure >> Administration >> Custom properties.

Delete the "com.ibm.websphere.java2secman.norethrow" resource value from production systems.