What changed in Samsung Android OS 14 with Knox 3.x COPE STIG V2R4V2R4 changes

Samsung Android OS 14 with Knox 3.x COPE STIG V2R4 (2026-04-01) replaced V2R3 (2025-10-01): 1 check added, 1 updated. It has 48 checks, against 47 in V2R3.

V2R4 checklistV2R3 checklist Compare V2R3 and V2R4 in STIG Compare

  • 1 added
  • 0 removed
  • 1 updated

Updated fields: Check text 1Fix text 1

Added in V2R4 (1)

  • V-282945All Samsung Android 14 installations must be removed. Exception: Tactical Edition (TE) devices with Android 14 can be used until April 2027.

Updated in V2R4 (1)

V-277005CAT IISamsung Android 14 must disable the ability of the user to wipe the device.Check text, Fix text

Check text

ReviewVerify, configurationthe settingsSamsung todevice confirm that the user ishas unablebeen trained to not perform a factory resetwipe andwithout the adminapproval hasof the abilityauthorizing toofficial inject a recovery account on the device to unlock Factory Reset Protection (FRPAO). This checkConform procedureby isreviewing performedsite onmobile the device managementtraining toolrecords andor the SamsungUser Android 14 deviceAgreement. On theThis MDM console: Verify factory reset configuration: COBO and COPE: 1. Open user restrictions. 2. Verify that "Disallow Factory Reset" is enabled. Verifya factoryUser-Based resetEnforcement 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(sUBE) is/are listed as allowed to unlock the FRPcontrol. OnIf the managed Samsung Android 14 device, verifyuser factoryhas 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"been pop-uptrained appearsto and the factory data reset does not proceed. If the Android device user is able to perform a factory resetwipe orwithout the adminapproval cannotof unlock the Android phone after an FRP eventAO, this is a finding.

Fix text

ConfigureTrain theusers Samsung Android 14 device to disablenot theperform abilitya offactory thereset useron to wipe the AndroidSamsung device. Enablewithout theAO adminapproval. toDocument injecttraining avia recoverythe accountsite's onmobile the device sotraining theyrecords canor unlock FRP. On the MDMUser console: Disallow factory reset: COBO and COPE: 1Agreement. OpenThis useris restrictions. 2.a EnableUBE "Disallow Factory Reset"control. Set factory reset protection policyNote: COBO andIt COPE: is 1.not Selectpossible Devicefor owner management >> Set factory reset protection. 2. From the "Accounts"MDM section, go to Addenforce Accountthis >>control Enterwhen recovery account and press "Ok". 3. From the "Enabled"Samsung section,device selectis "Enabled"deployed toin enableCOPE factory reset protection policymode. 4. Press "Save" to confirm all changes. API: addUserRestriction, DISALLOW_FACTORY_RESET and setFactoryResetProtectionPolicy

V-277005 in V2R4

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 V2R4 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.