Skip to content

If the HYCU virtual appliance uses role-based access control, it must enforce organization-defined role-based access control policies over defined subjects and objects.

An XCCDF Rule

Description

Organizations can create specific roles based on job functions and the authorizations (i.e., privileges) to perform needed operations on organizational information systems associated with the organization-defined roles. When administrators are assigned to the organizational roles, they inherit the authorizations or privileges defined for those roles. Role-Based Access Control (RBAC) simplifies privilege administration for organizations because privileges are not assigned directly to every administrator (which can be a significant number of individuals for mid- to large-size organizations) but are instead acquired through role assignments. RBAC can be implemented either as a mandatory or discretionary form of access control. The RBAC policies and the subjects and objects are defined uniquely for each network device, so they cannot be specified in the requirement.

ID
SV-268223r1038369_rule
Version
HYCU-ND-000050
Severity
Medium
References
Updated

Remediation Templates

A Manual Procedure

Ensure the correct RBAC controls and access are applied properly within the HYCU Web UI's Self-Service menu. Avoid granting too much access to any particular user or group. 

For the HYCU VM console, administrators should only allow access to anyone else deemed to be qualified as a server administrator for the system. 

To check for any unauthorized users, run the following command within the HYCU Web console: 
cat /etc/passwd