TMA-GITHUB-1.3.11
Ensure an organization provides SSH certificates
Description
As an organization, become an SSH Certificate Authority and provide SSH keys for accessing repositories. There are two ways for remotely working with Source Code Management: via HTTPS, which requires authentication by user/password, or via SSH, which requires the use of SSH keys. Reported as a manual review item: no reliable read-only gh api check exists for this control.
Méthode de vérification
Méthode d'audit: Revue manuelle
Cette recommandation ne peut pas être vérifiée automatiquement. Une analyse la liste avec ces instructions lorsque vous passez --include-manual.
Only if you have an enterprise account, verify that the enterprise organization has an SSH Certificate Authority server and provides an SSH certificate with which to sign keys by performing the following: 1. In the top right corner of GitHub.com, click your profile photo, then click Your organizations. 2. Next to the organization, click Settings. 3. In the "Security" section of the sidebar, click Authentication security. 4. Verify that there's an SSH certificate authority listed there.
Méthode de correction
Méthode de correction: Recommandation ou correctif d'infrastructure
Only if you have an enterprise account, deploy an SSH Certificate Authority server and configure it to provide an SSH certificate with which to sign keys by performing the following: 1. In the top right corner of GitHub.com, click your profile photo, then click Your organizations. 2. Next to the organization, click Settings. 3. In the "Security" section of the sidebar, click Authentication security. 4. To the right of "SSH Certificate Authorities", click New CA. 5. Under "Key," paste your public SSH key. 6. Click Add CA. 7. Click Save.
Propriétés
- Systèmes d'exploitation
- Tous
- Étiquettes
- githubsource-code
- Référence
- CIS GitHub Benchmark v1.2.0 - 1.3.11 Ensure an organization provides SSH certificates