STIGQter STIGQter: STIG Summary: Samsung Android OS 9 with Knox 3.x COPE Use Case KPE(AE) Deployment Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 25 Oct 2019: Samsung Android must be configured to enable Knox Common Criteria (CC) Mode.

DISA Rule

SV-103883r1_rule

Vulnerability Number

V-93797

Group Title

PP-MDF-991000

Rule Version

KNOX-09-000710

Severity

CAT I

CCI(s)

Weight

10

Fix Recommendation

Configure Samsung Android to enable Knox CC Mode.

On the MDM console, for the device, in the "Knox restrictions" group, select "enable CC mode".

The following configuration must also be implemented for the Samsung Android device to be operating in the NIAP-certified compliant CC mode of operation:
- KNOX-09-001440: Minimum password quality
- KNOX-09-000500: Disable face
- KNOX-09-000430/(KNOX-09-000440): Max password failures for local wipe
- KNOX-09-001370/(KNOX-09-001360): Password recovery
- KNOX-09-001390/(KNOX-09-001400): Password history length
- KNOX-09-001050/(KNOX-09-001040): Revocation check
- KNOX-09-001340/(KNOX-09-001330): OCSP check
- KNOX-09-001420: Secure Startup (for devices prior to Galaxy S10)
- KNOX-09-001480: Strong Protection (for Galaxy S10 (or newer) devices)
- KNOX-09-000980: Enable external storage encryption or disallow mount physical media

Note: STIGIDs listed above not in parentheses are personal space requirements. STIGIDs in parentheses are workspace requirements.

Check Contents

Review device configuration settings to confirm that Knox CC Mode is enabled.

This procedure is performed on both the MDM Administration console and the Samsung Android device.

On the MDM console, for the device, in the "Knox restrictions" group, verify that "enable CC mode" is selected.

On the Samsung Android device, to verify that CC Mode has not failed, do the following:
1. Open Settings.
2. Tap "About phone".
3. Tap "Software information".
4. Verify that the Security software version for MDF does not display "Disabled".

For Samsung Android devices prior to Galaxy S10, to verify that CC Mode is enabled, do the following:
1. Open Settings.
2. Tap "Biometric and security".
3. Tap "Secure startup".
4. Verify that "Do not require" is disabled.

For Galaxy S10 (or newer devices), to verify that CC Mode is enabled, do the following:
1. Open Settings.
2. Tap "Biometric and security".
3. Verify that "Strong Protection" is enabled and cannot be disabled.

If on the MDM console "enable CC mode" is not selected, or on the Samsung Android device the software version for "MDF" displays "Disabled", or on a Galaxy S10 (or newer device) "Strong Protection" can be disabled, or on a device older than a Galaxy S10 "Do not require" is not disabled, this is a finding.

Vulnerability Number

V-93797

Documentable

False

Rule Version

KNOX-09-000710

Severity Override Guidance

Review device configuration settings to confirm that Knox CC Mode is enabled.

This procedure is performed on both the MDM Administration console and the Samsung Android device.

On the MDM console, for the device, in the "Knox restrictions" group, verify that "enable CC mode" is selected.

On the Samsung Android device, to verify that CC Mode has not failed, do the following:
1. Open Settings.
2. Tap "About phone".
3. Tap "Software information".
4. Verify that the Security software version for MDF does not display "Disabled".

For Samsung Android devices prior to Galaxy S10, to verify that CC Mode is enabled, do the following:
1. Open Settings.
2. Tap "Biometric and security".
3. Tap "Secure startup".
4. Verify that "Do not require" is disabled.

For Galaxy S10 (or newer devices), to verify that CC Mode is enabled, do the following:
1. Open Settings.
2. Tap "Biometric and security".
3. Verify that "Strong Protection" is enabled and cannot be disabled.

If on the MDM console "enable CC mode" is not selected, or on the Samsung Android device the software version for "MDF" displays "Disabled", or on a Galaxy S10 (or newer device) "Strong Protection" can be disabled, or on a device older than a Galaxy S10 "Do not require" is not disabled, this is a finding.

Check Content Reference

M

Target Key

3507

Comments