V1R3 changes
Samsung Android OS 15 with Knox 3.x COBO STIG V1R3 (2026-04-01) replaced V1R2 (2025-10-01): 1 check added, 1 updated. It has 46 checks, against 45 in V1R2.
V1R3 checklistV1R2 checklist Compare V1R2 and V1R3 in STIG Compare
- 1 added
- 0 removed
- 1 updated
Updated fields: Check text 1Fix text 1
Added in V1R3 (1)
- V-282951All Samsung Android 15 installations must be removed.
Updated in V1R3 (1)
V-277011CAT IISamsung Android 15 must disable the ability of the user to wipe the device.Check text, Fix text
Check text
Review configuration settings to confirm that the user is unable to perform a factory reset and the admin has the ability to inject a recovery account on the device to unlock Factory Reset Protection (FRP).
This check procedure is performed on the device management tool and the Samsung Android 15 device.
On the MDM console:
Verify factory reset configuration:
COBO and COPE:
1. Open user restrictions.
2. Verify that "Disallow Factory Reset" is enabled.
Verify factory reset protection policy configuration:
1. From the Android Enterprise policy management, go to the Factory Reset Protection section.
2. Verify that "Factory Reset Protection" is set to "Allow/Enabled".
3. Verify that the correct Google Account ID(s) is/are listed as allowed to unlock the FRP.
On the managed Samsung Android 15 device, verify factory reset configuration.
COBO and COPE:
1. Open Settings >> General management >> Reset.
2. Tap the "Factory data reset" option.
3. Verify that the "Action not allowed" pop-up appears and the factory data reset does not proceed.
If the Android device user is able to perform a factory reset or the admin cannot unlock the Android phone after an FRP event, this is a finding.
Fix text
Configure the Samsung Android 15 device to disable the ability of the user to wipe the Android device. Enable the admin to inject a recovery account on the device soto they can unlock FRP.
On the MDM console:
Disallow factory reset:
COBO and COPE:
1. Open user restrictions.
2. Enable "Disallow Factory Reset".
Set factory reset protection policy:
COBO and COPE:
1. Select Device owner management >> Set factory reset protection.
2. From the "Accounts" section, go to Add Account >> Enter recovery account and press "Ok".
3. From the "Enabled" section, select "Enabled" to enable factory reset protection policy.
4. Press "Save" to confirm all changes.
API: addUserRestriction, DISALLOW_FACTORY_RESET and setFactoryResetProtectionPolicy
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V1R3 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.