The Samsung Knox for Android platform must be configured to enable the access control policy that prevents [groups of application processes] from accessing [all] data stored by other [groups of application processes].

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-61221	KNOX-35-024800	SV-75701r1_rule		Medium

Description
The access control policy restricts processes and applications in one processing environment (container) from accessing data in another. Exceptions should only be allowed under the administrator control to protect sensitive DoD data from exposure. SFR ID: FMT_SMF_EXT.1.1 #45, FDP_ACF_EXT.1.2

STIG	Date
Samsung Android OS 5 with Knox 2.0 Security Technical Implementation Guide	2016-02-24

Details

Check Text ( C-62177r1_chk )
Note: This validation procedure is identical to the one for KNOX-39-015400. It only needs to be performed once. If it is found compliant on the first check, it is also compliant here. If it is determined to be a finding on first check, it is also a finding here. Redundant checks are necessary to maintain requirements traceability and provide complete risk management information to AOs. This validation procedure is performed on both the MDM Administration Console and the Samsung Knox for Android device. Check whether the appropriate setting is configured on the MDM Administration Console: 1. Ask the MDM administrator to display the "Android Knox Container" rule. 2. Verify the existence of this rule. 3. Pushing this rule to the device that does not have a container installed will result in creation of the container. On the Samsung Knox for Android device: 1. From the device home screen, pull down the notification bar. 2. Verify the existence of the KNOX icon. 3. If available on the MDM agent, verify the container rule in the list of rules received by the MDM agent. If the MDM Administrator cannot configure the "Android Knox Container" rule, or if the KNOX icon is not present in the notification bar, or if the container rule is not found in the MDM agent rule list (MDM vendor-specific check), this is a finding.

Check Text ( C-62177r1_chk )

Note: This validation procedure is identical to the one for KNOX-39-015400. It only needs to be performed once. If it is found compliant on the first check, it is also compliant here. If it is determined to be a finding on first check, it is also a finding here. Redundant checks are necessary to maintain requirements traceability and provide complete risk management information to AOs.

This validation procedure is performed on both the MDM Administration Console and the Samsung Knox for Android device.

Check whether the appropriate setting is configured on the MDM Administration Console:
1. Ask the MDM administrator to display the "Android Knox Container" rule.
2. Verify the existence of this rule.
3. Pushing this rule to the device that does not have a container installed will result in creation of the container.

On the Samsung Knox for Android device:
1. From the device home screen, pull down the notification bar.
2. Verify the existence of the KNOX icon.
3. If available on the MDM agent, verify the container rule in the list of rules received by the MDM agent.

If the MDM Administrator cannot configure the "Android Knox Container" rule, or if the KNOX icon is not present in the notification bar, or if the container rule is not found in the MDM agent rule list (MDM vendor-specific check), this is a finding.

Fix Text (F-67081r1_fix)
On the MDM Administration Console, create the "Android Knox Container" rule and push this rule to the device.