V1R2 changes
BlackBerry CylancePROTECT Mobile for UEM STIG V1R2 (2024-01-24) replaced V1R1 (2023-07-04): 1 check updated. It has 14 checks, against 14 in V1R1.
V1R2 checklistV1R1 checklist Compare V1R1 and V1R2 in STIG Compare
- 0 added
- 0 removed
- 1 updated
Updated fields: Check text 1Fix text 1
Updated in V1R2 (1)
V-257267CAT IICylancePROTECT Mobile must be configured with the following Android security patch compliance and hardware certificate attestation controls: -"Android hardware attestation frequency" = 6 hours -"Device grace period" = 0 hours -"Challenge frequency for noncompliant devices" = 6 hours.Check text, Fix text
Check text
Verify the following Android security patch compliance and hardware certificate attestation controls are enabled for CylancePROTECT Mobile:
-"Android hardware attestation frequency" = 6 hours.
-"Device grace period" = 03 days (72 hours).
-"Challenge frequency for noncompliant devices = 61 day (24 hours).
1. Log on to the BlackBerry UEM console.
2. In the management console, click Settings >> General Settings >> Attestation.
3. In the "Android hardware attestation frequency" section, select verify "Enable hardware patch level attestation challenges for Android devices" is selected.
4. In the "Challenge frequency" drop-down list, verify the device attestation response is set to "61 hoursday" (24 hours).
5. In the "Device grace period drop-down" list, verify the grace period is set to "03 hoursdays" (no72 grace periodhours).
6. In the "Challenge frequency for noncompliant devices" field, verify the frequency UEM tests the integrity of devices that are not currently in compliance is set to "6 hours".
If required Android security patch compliance and hardware certificate attestation controls are not enabled, this is a finding.
Fix text
Configure the following Android security patch compliance and hardware certificate attestation controls:
-"Android hardware attestation frequency" = 6 hours.
-"Device grace period" = 03 days (72 hours).
-"Challenge frequency for noncompliant devices" = 61 day (24 hours).
1. Log on to the BlackBerry UEM console.
2. In the management console, click Settings >> General Settings >> Attestation.
3. In the "Android hardware attestation frequency" section, select "Enable hardware patch level attestation challenges for Android devices" checkbox.
4. in the "Challenge frequency" drop-down list, set the device must return an attestation response to "61 hoursday" (24 hours).
5. In the Device grace period drop-down list, set the grace period to "03 hoursdays" (no72 grace periodhours).
6. In the Challenge frequency for noncompliant devices field, set how often UEM tests the integrity of devices that are not currently in compliance to "6 hours".
7. Click "Save".
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 V1R2 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.