Ensure user management of the package registry is not local

MediumLevel 1Manual reviewgitlab

Description

Manage users and their access to the package registry with an external authentication server and not with the package registry itself. Some package registries offer a tool for user management, aside from the main Lightweight Directory Access Protocol (LDAP) or Active Directory (AD) server of the organization. That tool usually offers simple authentication and role-based permissions, which might not be granular enough. Having multiple user management tools in the organization could result in confusion and privilege escalation, as there will be more to manage. To avoid a situation where users escalate their privileges because someone missed them, manage user access to the package registry via the main authentication server and not locally on the package registry.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

For each package registry, verify that its user access is not managed locally, but instead with the main authentication server of the organization.

How it is fixed

Fix method: Guidance or infrastructure patch

For each package registry, use the main authentication server of the organization for user management and do not manage locally.

Properties

Operating systems: Any
Tags: devsecopsgitlab
Reference: CIS GitLab Benchmark v1.0.1 - 4.2.4 Ensure user management of the package registry is not local