OpenControls Logo

STIG Viewer

STIGViewer Support

The Omnissa WS1 UEM API must be configured to use approved authorizations for access control.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-284174OMW1-API-000200SV-284174r1223915_ruleCCI-000213medium
Description
To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoW-approved Public Key Infrastructures (PKIs), all DoW systems (e.g., networks, web servers, and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. This requirement is applicable to access control enforcement applications (e.g., authentication servers) and other applications that perform information and system access control functions. Methods include: - Basic Authentication (not recommended). - API Key Authentication. - TLS Encryption. - OAuth 2.0. - JWT-Based Authentication. - OpenID Connect (OIDC). Satisfies: SRG-APP-000033-API-000070, SRG-APP-000095-API-001740, SRG-APP-000141-API-000240, SRG-APP-000247-API-000870, SRG-APP-000461-API-001075
STIGDate
Omnissa WS1 UEM API Security Technical Implementation Guide2026-06-15

Related Frameworks

5 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (27) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CFG-01Configuration Management Program
1.00
CFG-02Secure Baseline Configurations
1.00
CFG-03Least Functionality
1.00
CRY-01Use of Cryptographic Controls
1.00
DCH-01Data Protection
1.00
HRS-02Position Categorization
1.00
HRS-11Separation of Duties (SoD)
1.00
IAC-01Identity & Access Management (IAM)
1.00
IAC-01.2Authenticate, Authorize and Audit (AAA)
1.00
IAC-02Identification & Authentication for Organizational Users
1.00

+17 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-18(1)Authentication and Encryption
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.1
1.00
3.1.2
1.00
3.3.1
1.00
3.3.2
1.00
3.4.6
1.00
CCI5 mappings
CCI-000130
1.00
CCI-000213
1.00
CCI-000381
1.00
CCI-001095
1.00
CCI-003747
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (7) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

PR.AA-05
1.00
PR.DS-10
1.00
PR.IR-01
1.00
PR.PS-01
1.00
PR.PS-04
1.00
PR.PS-05
1.00
PR.IR-04
0.50

Who does this work

17 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-284174r1223915_chk)

Verify WS1 UEM REST API access control has been configured to require "Directory" authentication. 1. Log in to the WS1 UEM console. 2. Navigate to Groups & Settings >> All Settings >> System >> Advanced >> API >> REST API >> Authentication tab. 3. Verify the authentication configuration is set correctly: Basic - "Disabled", Certificates - "Disabled", and Directory - "Enabled". 4. Verify the Child Permission is set to "Inherit only". If the WS1 UEM REST API authentication is not set correctly, this is a finding.

Fix Text (F-88643r1211949_fix)

Implement WS1 UEM REST API access control has been configured to require "Directory" authentication using the following procedures: 1. Log in to the WS1 UEM console. 2. Navigate to Groups & Settings >> All Settings >> System >> Advanced >> API >> REST API >> Authentication tab. 3. If the configuration is already set as listed in step 4 below, select "Inherent". If the configuration is not already set as listed in step 4 below, select "Override". 4. Select the following settings: Basic - "Disabled", Certificates - "Disabled", and Directory - "Enabled". 5. For Child Permission, select "Inherit only".