STIGhubSTIGhub
STIGsSearchCompare

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
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to VMware vSphere 7.0 vCenter Appliance STS Security Technical Implementation Guide

V-256755

CAT II (Medium)

The Security Token Service must be configured to limit access to internal packages.

Rule ID

SV-256755r889235_rule

STIG

VMware vSphere 7.0 vCenter Appliance STS Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000381

Discussion

The "package.access" entry in the "catalina.properties" file implements access control at the package level. When properly configured, a Security Exception will be reported if an errant or malicious webapp attempts to access the listed internal classes directly or if a new class is defined under the protected packages. The Security Token Service comes preconfigured with the appropriate packages defined in "package.access", and this configuration must be maintained.

Check Content

At the command prompt, run the following command: 
 
# grep "package.access" /usr/lib/vmware-sso/vmware-sts/conf/catalina.properties 
 
Expected result: 
 
package.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper. 
 
If the output of the command does not match the expected result, this is a finding.

Fix Text

Navigate to and open: 
 
/usr/lib/vmware-sso/vmware-sts/conf/catalina.properties 
 
Ensure the "package.access" line is configured as follows: 
 
package.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper. 
 
Restart the service with the following command: 
 
# vmon-cli --restart sts