| Finding ID |
Severity |
Title |
Description |
|
V-241818
|
High |
The Jamf Pro EMM server must connect to [Authentication Gateway Service (AGS)] with an authenticated and secure (encrypted) connection to protect the confidentiality and integrity of transmitted information. |
Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered.
This requirement applies only to those applications that are either distributed or can allow access to data non-locally. Use of this requirement will be limited to situations... |
|
V-241798
|
High |
Jamf Pro EMM must be maintained at a supported version. |
The MDM/EMM vendor maintains specific product versions for a specific period of time. MDM/EMM server versions no longer supported by the vendor will not receive security updates for new vulnerabilities which leaves them subject to exploitation.
SFR ID: FPT_TUD_EXT.1.1, FPT_TUD_EXT.1.2 |
|
V-241817
|
Medium |
All Jamf Pro EMM server local accounts created during application installation and configuration must be disabled. |
A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently and promptly addressed. If an attacker compromises an account, the entire Jamf Pro EMM server infrastructure is at risk. Providing automated support functions for the management of accounts will ensure only... |
|
V-241816
|
Medium |
The firewall protecting the Jamf Pro EMM server platform must be configured so that only DoD-approved ports, protocols, and services are enabled. (See the DoD Ports, Protocols, Services Management [PPSM] Category Assurance Levels [CAL] list for DoD-approved ports, protocols, and services). |
All ports, protocols, and services used on DoD networks must be approved and registered via the DoD PPSM process. This is to ensure that a risk assessment has been completed before a new port, protocol, or service is configured on a DoD network and has been approved by proper DoD... |
|
V-241815
|
Medium |
The firewall protecting the Jamf Pro EMM server platform must be configured to restrict all network traffic to and from all addresses with the exception of ports, protocols, and IP address ranges required to support Jamf Pro EMM server and platform functions. |
Most information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations. Since MDM server is a critical component of the mobility architecture and must be configured to enable only... |
|
V-241814
|
Medium |
The Jamf Pro EMM server platform must be protected by a DoD-approved firewall. |
Most information systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Unneeded services and processes provide additional threat vectors and avenues of attack to the information system. The MDM... |
|
V-241813
|
Medium |
The Jamf Pro EMM must enforce the limit of three consecutive invalid logon attempts by a user. |
By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account.
SFR ID: FMT_SMF.1(2)b. / IA-7-a
Satisfies: SRG-APP-000065 |
|
V-241812
|
Medium |
The Jamf Pro EMM must automatically disable accounts after a 35 day period of account inactivity (local accounts). |
Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Applications need to track periods of user inactivity and disable accounts after 35 days... |
|
V-241811
|
Medium |
The Jamf Pro EMM local accounts must prohibit password reuse for a minimum of five generations. |
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
To meet password policy requirements, passwords need to be changed at specific policy-based intervals.
If the information system or application allows the user to consecutively reuse their password when... |
|
V-241810
|
Medium |
The Jamf Pro EMM local accounts must be configured with password maximum lifetime of 3 months. |
Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals.
One method of minimizing this risk is to use complex passwords and periodically change them. If the application does not limit the lifetime of passwords and force users to change their... |
|
V-241809
|
Medium |
The Jamf Pro EMM local accounts must be configured with password minimum lifetime of 24 hours. |
Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement.
Restricting this setting limits the user's ability to change their password. Passwords need to be changed at specific policy based intervals; however, if the application allows the user to immediately and... |
|
V-241808
|
Medium |
The Jamf Pro EMM local accounts must be configured with at least one special character. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor in determining how long it takes to... |
|
V-241807
|
Medium |
The Jamf Pro EMM local accounts must be configured with at least one number. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-241806
|
Medium |
The Jamf Pro EMM local accounts must be configured with at least one uppercase character. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-241805
|
Medium |
The Jamf Pro EMM local accounts must be configured with at least one lowercase character. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-241804
|
Medium |
The Jamf Pro EMM local accounts password must be configured with length of 15 characters. |
The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that... |
|
V-241803
|
Medium |
The MySQL DatabasePassword key must be removed or set to a blank value in the database configuration file in Jamf Pro EMM. |
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 |
|
V-241802
|
Medium |
MySQL database backups must be scheduled in Jamf Pro EMM. |
Database backups are a recognized best practice to protect against key data loss and possible adverse impacts to the mission of the organization.
SFR ID: FMT_SMF.1(2)b. / CM-6 b
Satisfies: SRG-APP-000516 |
|
V-241801
|
Medium |
Separate MySQL user accounts with limited privileges must be created within Jamf Pro EMM. |
If separate MySQL accounts with limited privileges are not created an adversary could gain unauthorized access to the application or gain access unauthorized features which could lead to the compromise of sensitive DoD data.
SFR ID: FMT_SMF.1(2)b. / CM-6 b
Satisfies: SRG-APP-000516 |
|
V-241800
|
Medium |
A unique database name and a unique MySQL user with a secure password must be created for use in Jamf Pro EMM. |
If the default MySQL database name and password are not changed an adversary could gain unauthorized access to the application which could lead to the compromise of sensitive DOD data.
SFR ID: FMT_SMF.1(2)b. / IA-5(1)(c)
Satisfies: SRG-APP-000171 |
|
V-241799
|
Medium |
The default mysql_secure_installation must be installed. |
The mysql_secure_installation configuration of MySQL adds several important configuration settings that block several attack vectors. The My SQL application could be exploited by an adversary without mysql_secure_installation.
SFR ID: FMT_SMF.1(2)b. / CM-7(1)(b)
Satisfies: SRG-APP-000383 |
|
V-241797
|
Medium |
Authentication of Jamf Pro EMM server accounts must be configured so they are implemented either via an Authentication Gateway Service (AGS) which connects to the site DoD Identity Access Management (IdAM) environment that utilizes CAC authentication or via strong password controls for the administrator local accounts. |
A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently and promptly addressed. If an attacker compromises an account, the entire Jamf Pro EMM server infrastructure is at risk. Providing automated support functions for the management of accounts will ensure only... |
|
V-241796
|
Medium |
The Jamf Pro EMM server must be configured to leverage the MDM platform user accounts and groups for Jamf Pro EMM server user identification and CAC authentication. |
A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently and promptly addressed. If an attacker compromises an account, the entire Jamf Pro EMM server infrastructure is at risk. Providing automated support functions for the management of accounts will ensure only... |
|
V-241795
|
Medium |
The Jamf Pro EMM server must be configured to have at least one user in the following Administrator roles: Server primary administrator, security configuration administrator, device user group administrator, auditor. |
Having several administrative roles for the Jamf Pro EMM server supports separation of duties. This allows administrator-level privileges to be granted granularly, such as giving application management privileges to one group and security policy privileges to another group. This helps prevent administrators from intentionally or inadvertently altering other settings and... |
|
V-241793
|
Medium |
The Jamf Pro EMM server must be configured to transfer Jamf Pro EMM server logs to another server for storage, analysis, and reporting.
Note: Jamf Pro EMM server logs include logs of MDM events and logs transferred to the Jamf Pro EMM server by MDM agents of managed devices. |
Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. Since the Jamf Pro EMM server has limited capability to store mobile device log files and perform analysis and reporting of mobile device log files, the Jamf Pro EMM server must have the capability to transfer log... |
|
V-241792
|
Medium |
The Jamf Pro EMM server must be configured with an enterprise certificate for signing policies (if function is not automatically implemented during Jamf Pro EMM server install). |
It is critical that only authorized certificates are used for key activities such as code signing for system software updates, code signing for integrity verification, and policy signing. Otherwise, there is no assurance that a malicious actor has not inserted itself in the process of packaging the code or policy.... |
|
V-241791
|
Medium |
The Jamf Pro EMM server or platform must be configured to initiate a session lock after a 15-minute period of inactivity. |
A session time-out lock is a temporary action taken when a user (MDM system administrator) stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually... |
|
V-241790
|
Medium |
When the Jamf Pro EMM server cannot establish a connection to determine the validity of a certificate, the server must not have the option to accept the certificate. |
When a Jamf Pro EMM server accepts an unverified certificate, it may be trusting a malicious actor. For example, messages signed with an invalid certificate may contain links to malware, which could lead to the installation or distribution of that malware on DoD information systems, leading to compromise of DoD... |
|
V-241794
|
Low |
The Jamf Pro EMM server must be configured to display the required DoD warning banner upon administrator logon.
Note: This requirement is not applicable if the TOE platform is selected in FTA_TAB.1.1 in the Security Target (ST). |
Note: The advisory notice and consent warning message is not required if the general purpose OS or network device displays an advisory notice and consent warning message when the administrator logs on to the general purpose OS or network device prior to accessing the Jamf Pro EMM server or Jamf... |
