STIGQter: STIG Summary: Jamf Pro v10.x EMM Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 03 Feb 2020:

A unique database name and a unique MySQL user with a secure password must be created for use in Jamf Pro EMM.

DISA Rule

SV-108705r1_rule

Vulnerability Number

V-99601

Group Title

PP-MDM-991000

Rule Version

JAMF-10-100080

Severity

CAT II

CCI(s)

• CCI-000196 - The information system, for password-based authentication, stores only cryptographically-protected passwords.

Weight

10

Fix Recommendation

Create a unique database name and a unique MySQL user with a secure password. The procedure is found in the following Jamf Knowledge Base article:

https://www.jamf.com/jamf-nation/articles/542/title

Check Contents

Verify a unique database name and a unique MySQL user with a secure password have been created for use in Jamf Pro EMM.

1. Execute the show databases command.
- Ensure at least one database name other than the default databases exits. The default databases are:
infomation_schema
mysql
performance_schema
sys

2. Verify there is a unique MySQL user.
- In MySQL, run select * mysql.user;
- Look for a user that is not Root or one of the other MySQL service accounts.

Both of these steps must be correct.

If a unique database name and a unique MySQL user with a secure password have not been created, this is a finding.

Vulnerability Number

V-99601

Documentable

False

Rule Version

JAMF-10-100080

Severity Override Guidance

Verify a unique database name and a unique MySQL user with a secure password have been created for use in Jamf Pro EMM.

1. Execute the show databases command.
- Ensure at least one database name other than the default databases exits. The default databases are:
infomation_schema
mysql
performance_schema
sys

2. Verify there is a unique MySQL user.
- In MySQL, run select * mysql.user;
- Look for a user that is not Root or one of the other MySQL service accounts.

Both of these steps must be correct.

If a unique database name and a unique MySQL user with a secure password have not been created, this is a finding.

Check Content Reference

M

Target Key

3593

Comments