TMA-GITHUB-1.2.2

Ensure repository creation is limited to specific members

SedangLevel 1Otomatisgithub

Deskripsi

Limit the ability to create repositories to trusted users and teams. Restricting repository creation to trusted users and teams is recommended in order to keep the organization properly structured, track fewer items, prevent impersonation, and to not overload the version-control system. The organization must not let members create public, private or internal repositories. Uses the GitHub REST/GraphQL API through gh api (read-only). The repository comes from GH_REPO or the current git checkout (gh's {owner}/{repo} resolution, GH_HOST for GitHub Enterprise Server); the organization comes from GH_ORG (default: the repository owner). Fails when gh is missing or unauthenticated (gh auth login or GH_TOKEN); organization settings and branch protection need an owner/admin token.

Cara pemeriksaan

Metode audit: Perintah shell

shell

command -v gh >/dev/null 2>&1 || exit 1
gh auth status >/dev/null 2>&1 || exit 1
O=${GH_ORG:-$(gh api 'repos/{owner}/{repo}' --jq .owner.login 2>/dev/null)}
[ -n "$O" ] || exit 1
v=$(gh api "orgs/$O" --jq '.members_can_create_public_repositories == false and .members_can_create_private_repositories == false and (.members_can_create_internal_repositories // false) == false' 2>/dev/null) || exit 1
[ "$v" = true ] && echo compliant

Output yang diharapkan: compliant

Cara perbaikan

Metode perbaikan: Panduan atau patch infrastruktur

Organization Settings > Member privileges > Repository creation: uncheck Public, Private (and Internal) so only owners can create repositories.

Properti

Sistem operasi: Apa saja
Tag: githubsource-code
Referensi: CIS GitHub Benchmark v1.2.0 - 1.2.2 Ensure repository creation is limited to specific members

Periksa host ini

Jalankan ini pada mesin yang diizinkan untuk Anda audit. Pemindaian bersifat hanya baca.

shell

tmaegis scan --target github