STIGViewer Support

The MaaS360 MDM Agent must be configured to implement the management setting: periodicity of reachability events equals six hours or less.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-82193M360-10-301700SV-96907r1_ruleCCI-000169medium
Description
Key security-related status attributes must be queried frequently so the MaaS360 MDM Agent can report status of devices under management to the Administrator and management. The periodicity of these queries must be configured to an acceptable timeframe. Six hours or less is considered acceptable for normal operations. SFR ID: FAU_ALT_EXT.2.1
STIGDate
IBM MaaS360 with Watson v10.x MDM Security Technical Implementation Guide2019-08-06

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (15) 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.

END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
MON-01Continuous Monitoring
1.00
MON-01.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00
MON-01.3Inbound & Outbound Communications Traffic
1.00
MON-01.4System Generated Alerts
1.00
MON-01.7File Integrity Monitoring (FIM)
1.00
MON-01.8Security Event Monitoring
1.00
MON-03Content of Event Logs
1.00

+5 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (57) 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-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
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-3Access Enforcement
1.00
AC-3(3)Mandatory Access Control
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AC-7Unsuccessful Logon Attempts
1.00

+47 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) 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.3.1
1.00
3.3.2
1.00
CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (4) 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.

Who does this work

12 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-96907r1_chk)

Verify the periodicity for agent checking to the server has been set to six hours or less. For Apple iOS devices, confirm with IBM that the periodicity for agent checking to the server has been set to 6 hours or less. For Samsung Android devices: 1. In the portal, navigate to "Security". 2. Select "Policy". 3. Select the policy for Samsung Android devices. 4. Open the policy. 5. Select "Device Settings" and then "Device Management". 6. Verify "Data Heartbeat Frequency" is set to 360 minutes or less. If the periodicity for agent checking to the server has not been set to 6 hours or less, this is a finding.

Fix Text (F-89053r1_fix)

The procedure for configuring the periodicity depends on the MOS type. For Apple iOS devices, the site System Administrator should ask IBM to configure the SaaS to set the periodicity for agent checking to the server to six hours or less. For Samsung Android devices: 1. In the portal, navigate to "Security". 2. Select "Policy". 3. Select the policy for Samsung Android devices. 4. Open the policy. 5. Select "Device Settings" and then "Device Management". 6. Set the "Data Heartbeat Frequency" to 360 minutes or less.