What changed in Omnissa WS1 UEM Server STIG V1R2V1R2 changes

Omnissa WS1 UEM Server STIG V1R2 (2026-09-30) replaced V1R1 (2026-05-26): 1 check updated. It has 15 checks, against 15 in V1R1.

  • 0 added
  • 0 removed
  • 1 updated

Updated fields: Check text 1Fix text 1Title 1Discussion 1

Updated in V1R2 (1)

V-284354CAT IIThe Omnissa WS1 UEM server must enforce a 180-day maximum password lifetime restriction.Title, Check text, Fix text, Discussion

Title

The Omnissa WS1 UEM server must enforce a 6180-day maximum password lifetime restriction.

Check text

Authenticate to the Workspace ONE UEM console as an administrator. Navigate to Groups & Settings >> All Settings >> Admin >> Console Security >> Passwords. If "Password Expiration Period (days)" is not set to "60180" (or less), this is a finding. Note: If this procedure is not seen on the console, the Cloud Service Provider (CSP) is managing the setting. Contact the CSP to review the required setting.

Fix text

Authenticate to the Workspace ONE UEM console as an administrator. 1. Navigate to Groups & Settings >> All Settings >> Admin >> Console Security >> Passwords. 2. Configure "Password Expiration Period (days)" to "60180" or less. 3. Click "Save". Note: If this procedure is not seen on the console, the CSP is managing the setting. Contact the CSP to implement the required setting.

Discussion

Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals. One method of minimizing this risk is to use complex passwords and periodically change them. If the application does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the system and/or application passwords could be compromised. This requirement does not include emergency administration accounts, which are meant for access to the application in case of failure. These accounts are not required to have maximum password lifetime restrictions. Satisfies: FMT_SMF.1(2)b Reference: PP-MDM-431024

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.