OpenControls Logo

STIG Viewer

STIGViewer Support

The MobileIron Core v10 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.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-91817MICR-10-000590SV-101919r1_ruleCCI-000366medium
Description
Having several administrative roles for the MobileIron Core v10 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 configurations they may not understand or approve of, which can weaken overall security and increase the risk of compromise. - Server primary administrator: Responsible for server installation, initial configuration, and maintenance functions. Responsible for the setup and maintenance of security configuration administrator and auditor accounts. Responsible for the maintenance of applications in the MAS. - Security configuration administrator: Responsible for security configuration of the server, defining device user groups, setup and maintenance of device user group administrator accounts, and defining privileges of device user group administrators. - Device user group administrator: Responsible for maintenance of mobile device accounts, including setup, change of account configurations, and account deletion. Responsible for defining which apps user groups or individual users have access to in the MAS. Can only perform administrative functions assigned by the security configuration administrator. - Auditor: Responsible for reviewing and maintaining server and mobile device audit logs. SFR ID: FMT_SMR.1.1(1)
STIGDate
MobileIron Core v10.x MDM Security Technical Implementation Guide2019-02-19

Related Frameworks

3 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (9) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CFG-01Configuration Management Program
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
IAC-21.3Management Approval For Privileged Accounts
1.00
MON-01Continuous Monitoring
1.00
MON-01.7File Integrity Monitoring (FIM)
1.00
CFG-02Secure Baseline Configurations
0.50
CFG-02.7Approved Configuration Deviations
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-12Session Termination
1.00
AC-16(1)Dynamic Attribute Association
1.00
AC-17(1)Monitoring and Control
1.00
AC-2Account Management
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-24(1)Transmit Access Authorization Information
1.00
AC-25Reference Monitor
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.5
1.00
3.4.1
1.00
3.4.2
1.00
CCI3 mappings
CCI-000366
1.00
CCI-002226
1.00
CCI-002227
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.CM-09
1.00
PR.PS-01
1.00
PR.DS-10
0.50
PR.PSPlatform Security
0.50
PR.PS-05
0.50

Who does this work

10 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-101919r1_chk)

Review the MDM server configuration settings and verify the server is configured with the Administrator roles: - Server primary administrator - Security configuration administrator - Device user group administrator - Auditor On the MDM console, do the following: 1. Verify a user is in the "Server primary administrator" role. a. Logon to the MobileIron Core Server system manager portal as a user with the "server primary administrator" role using a web browser. b. Select Security >> Identity Source >> Local Users. If a user in the "server primary administrator" role is not listed, this is a finding. 2. Verify a user is in the "Security configuration administrator" role. a. Logon to the MobileIron Core Server administrator portal as a user with the "server primary administrator" role using a web browser. b. Select Admin >> Admins. c. Select user with the "Security configuration administrator" role. d. Click Actions >> Edit Roles. e. Verify that the following roles are selected: "Manage label", "View user", "Manage app", "Manage configuration", "Manage policy", "Manage settings and services", and "Manage administrators and device" spaces. If the "Security configuration administrator" user is not found or any of the required roles are not selected, this is a finding. 3. Verify a user is in the "Device user group administrator" role. a. Logon to the MobileIron Core Server administrator portal as a user with the "server primary administrator" role using a web browser. b. Select Admin >> Admins. c. Select user with the "Device user group administrator" role. d. Click Actions >> Edit Roles. e. Verify that the following roles are selected: "wipe devices", "add device", "manage ActiveSync device", and "delegate retired device" roles. If the "Device user group administrator" user is not found or any of the required roles are not selected, this is a finding. 4. Verify a user is in the "Auditor" role. a. Logon to the MobileIron Core Server administrator portal as a user with the "server primary administrator" role using a web browser. b. Select Admin >> Admins. c. Select user with the "Device user group administrator" role. d. Click Actions >> Edit Roles. e. Check that the following roles are selected: "Manage logs and events". If the user is not found or any of the required roles are not selected, this is a finding.

Fix Text (F-98019r1_fix)

Configure the MDM server with the Administrator roles: - Server primary administrator - Security configuration administrator - Device user group administrator - Auditor On the MDM console, do the following: 1. Follow the instructions in the "MobileIron Core and Android Client Mobile Device Management Protection Profile Guide" in section "Configuring administrators to have roles defined by federal requirements": a. Follow the instructions for "Configuring administrators to be a server primary administrator". b. Follow the instructions for "Configuring administrators to be a security configuration administrator". c. Follow the instructions for "Configuring administrators to be a device user group administrator". d. Follow the instructions for "Configuring administrators to be an auditor". 2. In each case instructions are provided to create a new user with the identified role.