MDS2 (Medical Device)
Data handling, access and accountability capabilities (2.3.3 to 2.3.6, 2.3.10, 2.3.15) – MDS2 (Medical Device)

MDS2 (Medical Device) AUTH: AUTH Authorization: disclose how the device blocks unauthorised users and manages privileges

Discloses the device's ability to determine that a user is authorised: whether it can prevent access by unauthorised users through login requirements or other mechanisms, with the physical or technical safeguards (password, biometrics, key card) noted (AUTH-1); whether authorisation can use federated user management such as LDAP or OAuth (1.1); whether the customer can push group policies to the device, for example through Active Directory (1.2); whether particular groups, organisational units or group policies are required (1.3); whether users can be given different privilege levels by role such as user, administrator or service (AUTH-2); whether the owner or operator can obtain unrestricted administrative privileges to the operating system or application through a local root or administrator account, and whether multiple privileged accounts and limits on administrator-account use are supported (AUTH-3); whether all API access requests are authenticated or controlled (AUTH-4); and whether the device runs by default in a restricted-access or kiosk mode (AUTH-5).

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

Other controls in Data handling, access and accountability capabilities (2.3.3 to 2.3.6, 2.3.10, 2.3.15) – MDS2 (Medical Device)

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.