SAMMY UI is optimized for resolutions with a width 1024px and higher.
Cloud Controls Matrix
Browse Cloud Controls...
UEM-05: Endpoint Management
Endpoint Management
UEM-05: Are processes, procedures, and technical measures defined, implemented and evaluated, to enforce policies and controls for all endpoints permitted to access systems and/or store, transmit, or process organizational data?
For managed endpoints, universal policy enforcement through one or more centralized configuration management tools is essential. Note: "Universal" enforcement is not necessarily "unified." Some vendors claim to offer "unified endpoint management" systems, but none are truly capable of managing all security features of all endpoint types.

For unmanaged endpoints, guidance should be provided but will not be enforced (by definition).

Based on risk assessment, different configurations may be acceptable for systems access and/or information storage—resulting in various degrees of end-points management with different access requirements. These may include using container technology for sensitive data isolation. For example, an organization that prohibits using electronic mail for sensitive information may determine that access to company electronic mail using a personally-owned device requires only limited controls (such as an acceptable passcode, a lock screen, reasonably up-to-date software, and no circumvention of vendor security controls [such as jailbreaking or rooting]).
Control implemented
Not applicable - A “N/A” answer indicates that the portion of the control in question is out of scope of the assessment. The “SSRM control ownership” column is to be left blank (e.g., greyed out), and optionally the CSP may explain why it is the case (“CSP Implementation Description”).
No - A “No” answer indicates that the portion of the control in question is not implemented, while in scope of the assessment. The CSP has to assign the implementation responsibility of the control to the relevant party under column “SSRM control ownership”, and optionally elaborate on the “why” (has not been implemented), and “what” has to be done for its implementation by that party.
Yes - A “Yes” answer indicates that the portion of the control in question is implemented. The CSP indicates the responsible and accountable parties (SSRM control ownership), and optionally elaborates on the implementation “how-to” per relevant party CSP and/or CSC.
Control ownership
CSP-owned - The CSP is entirely responsible and accountable for the CCM control implementation.
CSC-owned - The Cloud Service Customer (CSC) is entirely responsible and accountable for the CCM control implementation.
Third-party - The third-party CSP in the supply chain (e.g., an IaaS provider) is responsible for CCM control implementation, while the CSP is fully accountable.
Shared CSP and CSC - Both the CSP and CSC share CCM control implementation responsibility and accountability.
Shared CSP and third party - Any CCM control implementation responsibility is shared between CSP and the third party, but the CSP remains fully accountable.
Description

Define, implement and evaluate processes, procedures and technical measures to enforce policies and controls for all endpoints permitted to access systems and/or store, transmit, or process organizational data.