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 Jamf Pro v10.x EMM Security Technical Implementation Guide

V-241803

CAT II (Medium)

The MySQL DatabasePassword key must be removed or set to a blank value in the database configuration file in Jamf Pro EMM.

Rule ID

SV-241803r971326_rule

STIG

Jamf Pro v10.x EMM Security Technical Implementation Guide

Version

V3R1

CCIs

CCI-001813

Discussion

If the database password is not removed or set to a blank value in the configuration file, the user is not forced to enter the password, which would allow an adversary to access to access the database. SFR ID: FMT_SMF.1(2)b. / CM-5(10) Satisfies: SRG-APP-000380

Check Content

Verify the MySQL <DatabasePassword> key has been removed or set to a blank value in Jamf Pro EMM.

1. On the Jamf Pro server, navigate to the JSS/Tomcat/webapps/ROOT/WEB-INF/xml.
2. Find the "Database.xml" file and open it in a text editor.
3. Find the <DatabasePassword>.
4. Verify that there is no password.

If the MySQL <DatabasePassword> key has not been removed or not set to a blank value, this is a finding.

Fix Text

Remove the MySQL <DatabasePassword> key or set to a blank value in Jamf Pro EMM.

If the database password is removed from the configuration file, the database password must be entered manually for the Jamf Pro EMM server web app during startup. In a clustered environment, the database password must be entered manually for each individual node.

Note: Default values are included below for reference only. Use unique values in production environments.

<Database>
...
<DatabaseName>jamfsoftware</DatabaseName>
<DatabaseUser>jamfsoftware</DatabaseUser>
<DatabasePassword></DatabasePassword>
...
</Database>