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.

Quick Actions

We are continuing to improve Stigviewer and we are planning on rolling out new services in the near future. Would you like to be part of the conversation on what those features should be? If so, click here.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-268223	HYCU-ND-000050	SV-268223r1038369_rule		Medium

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.

STIG	Date
HYCU Protege Security Technical Implementation Guide	2024-10-29

Details

Check Text (C-72244r1038367_chk)

HYCU offers the capability to leverage RBAC controls within the Web UI's Self-Service menu. The organization would need to generate and document its own specific requirements around using RBAC in HYCU.

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

Review the groups and accounts within Web UI's Self-Service menu.

If any RBAC setting does not meet the organization's guidelines, this is a finding.

Fix Text (F-72147r1038368_fix)

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

Use the "userdel" command to remove any unauthorized users.

STIG VIEWER