Title

The UEM server must require end-point devices to reauthenticate when organization-defined circumstances or situations requiring reauthentication. (Cat II impact)

Discussion

An example of an organization-defined circumstance or situation requiring reauthentication is reauthentication after a period of inactivity. Without reauthenticating devices, unidentified or unknown devices may be introduced; thereby facilitating malicious activity. In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of devices, including (but not limited to), the following other situations. (i) When authenticators change; (ii) When roles change; (iii) When security categories of information systems change; (iv) After a fixed period of time; or (v) Periodically. For distributed architectures (e.g., service-oriented architectures), the decisions regarding the validation of identification claims may be made by services separate from the services acting on those decisions. In such situations, it is necessary to provide the identification decisions (as opposed to the actual identifiers) to the services that need to act on those decisions. Gateways and SOA applications are examples of where this requirement would apply.

Check Content

Verify the UEM server requires end-point devices to reauthenticate when organization-defined circumstances or situations requiring reauthentication. If the UEM server does not require end-point devices to reauthenticate when organization-defined circumstances or situations requiring reauthentication, this is a finding.

Fix Text

Configure the UEM server to require end-point devices to reauthenticate when organization-defined circumstances or situations requiring reauthentication.

Additional Identifiers

Rule ID: SRG-APP-000390-UEM-000261_rule

Vulnerability ID: SRG-APP-000390-UEM-000261

Group Title: SRG-APP-000390-UEM-000261

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.