Omnissa WS1 UEM API Security Technical Implementation Guide

acceptedOmnissa WS1 UEM API Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of War (DoW) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

DISASTIG.DOD.MIL

Release: 1 Benchmark Date: 26 May 2026

3.5.2

1.10.0

1I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-APP-000033-API-000070<GroupDescription></GroupDescription>OMW1-API-000200The Omnissa WS1 UEM API must be configured to use approved authorizations for access control.<VulnDiscussion>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</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Omnissa WS1 UEM APIDISADPMS TargetOmnissa WS1 UEM API5749CCI-000213CCI-000130CCI-000381CCI-001095CCI-003747Implement 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".

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.

SRG-APP-000247-API-000520<GroupDescription></GroupDescription>OMW1-API-002700The Omnissa WS1 UEM API must employ throttling.<VulnDiscussion>The API must employ throttling to limit the effects of information flooding types of denial-of-service (DoS) attacks. DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. In the case of application DoS attacks, care must be taken when designing the application to ensure the application makes the best use of system resources. SQL queries have the potential to consume large amounts of CPU cycles if they are not tuned for optimal performance. Web services containing complex calculations requiring large amounts of time to complete can bog down if too many requests for the service are encountered within a short period of time. The methods employed to meet this requirement will vary depending upon the technology the application uses. However, a variety of technologies exist to limit or, in some cases, eliminate the effects of application-related DoS attacks. Employing increased capacity and bandwidth combined with specialized application layer protection devices and service redundancy may reduce the susceptibility to some DoS attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Omnissa WS1 UEM APIDISADPMS TargetOmnissa WS1 UEM API5749CCI-001095Implement WS1 UEM REST API server bandwidth throttling using the following procedures: 1. Log in to the WS1 UEM console. 2. Navigate to Groups & Settings >> All Settings >> System >> Advanced >> API >> REST API >> User tab. 3. Set the server throttling based on the site operational environment. Note: The User tab may not be viewable if the WS1 UEM organizational group instance does not have permission to access configuration settings available on the User tab. In this case, have the SA of the top organizational group configure the throttling setting.

Verify WS1 UEM REST API server bandwidth throttling has been configured. Specific configuration settings should be based on the site operational environment. 1. Log in to the WS1 UEM console. 2. Navigate to Groups & Settings >> All Settings >> System >> Advanced >> API >> REST API >> User tab. 3. Verify the server throttling has been set based on the site operational environment. Note: The User tab may not be viewable if the WS1 UEM organizational group instance does not have permission to access configuration settings available on the User tab. In this case, have the system administrator (SA) of the top organizational group confirm throttling has been set. If WS1 UEM REST API server bandwidth throttling has not been configured, this is a finding.