STIGQter STIGQter: STIG Summary: Samsung Android OS 9 with Knox 3.x COPE Use Case KPE(Legacy) Deployment Security Technical Implementation Guide Version: 1 Release: 4 Benchmark Date: 24 Jul 2020:

Samsung Android must be configured to enforce that Strong Protection is enabled. This requirement is Not Applicable (NA) for devices older than Galaxy S10.

DISA Rule

SV-104033r1_rule

Vulnerability Number

V-93947

Group Title

PP-MDF-991000

Rule Version

KNOX-09-001485

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configure Samsung Android to enable Strong Protection.

This guidance is only applicable to Galaxy S10 (or newer) devices.

On the Samsung Android device, do the following:
1. Open Settings.
2. Tap "Biometrics and security".
3. Tap "Other security settings".
4. Tap "Strong Protection".
5. Tap to enable.
6. Enter the current password.

Check Contents

Review device configuration settings to confirm that Strong Protection is enabled.

This procedure is performed on the Samsung Android Galaxy S10 (or newer) devices only.

This setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement.

On the Samsung Android device, do the following:
1. Open Settings.
2. Tap "Biometric and security".
3. Tap "Other security settings".
4. Verify "Strong Protection" is enabled.

If on the Samsung Android device "Strong Protection” is disabled, this is a finding.

Vulnerability Number

V-93947

Documentable

False

Rule Version

KNOX-09-001485

Severity Override Guidance

Review device configuration settings to confirm that Strong Protection is enabled.

This procedure is performed on the Samsung Android Galaxy S10 (or newer) devices only.

This setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement.

On the Samsung Android device, do the following:
1. Open Settings.
2. Tap "Biometric and security".
3. Tap "Other security settings".
4. Verify "Strong Protection" is enabled.

If on the Samsung Android device "Strong Protection” is disabled, this is a finding.

Check Content Reference

M

Target Key

3509

Comments