Benchmark: 4.2 Access to Artifacts

Overview

This section consists of security recommendations for access management of artifacts.

Artifacts are often stored in registries, some external and some internal. Those registries have user entities that control access and permissions. Artifacts are considered sensitive, because they are being delivered to the customer, and are prone to many attacks: data theft, dependency confusion, malicious packages, and more. That is why their access management should be restrictive and careful.

Usage

Install the mod:

mkdir dashboards
cd dashboards
powerpipe mod init
powerpipe mod install github.com/turbot/steampipe-mod-github-compliance

Start the Powerpipe server:

steampipe service start
powerpipe server

Open http://localhost:9033 in your browser and select 4.2 Access to Artifacts.

Run this benchmark in your terminal:

powerpipe benchmark run github_compliance.benchmark.cis_supply_chain_v100_4_2

Snapshot and share results via Turbot Pipes:

powerpipe benchmark run github_compliance.benchmark.cis_supply_chain_v100_4_2 --share

Controls

4.2.3 Ensure user access to the package registry utilizes Multi-Factor Authentication (MFA)

Benchmark: 4.2 Access to Artifacts

Overview

Usage

Controls

Tags