Skip to main content

💼 4.3 Ensure “Block Project-Wide SSH Keys” Is Enabled for VM Instances - Level 1 (Automated)

  • Contextual name: 💼 4.3 Ensure “Block Project-Wide SSH Keys” Is Enabled for VM Instances - Level 1 (Automated)
  • ID: /frameworks/cis-gcp-v2.0.0/04/03
  • Located in: 💼 4 Virtual Machines

Description​

It is recommended to use Instance specific SSH key(s) instead of using common/shared project-wide SSH key(s) to access Instances.

Similar​

  • Sections
    • /frameworks/cis-gcp-v3.0.0/04/03
    • /frameworks/cis-gcp-v1.3.0/04/03
  • Internal
    • ID: dec-c-94dcef4b

Similar Sections (Take Policies From)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS GCP v1.3.0 → 💼 4.3 Ensure “Block Project-Wide SSH Keys” Is Enabled for VM Instances - Level 1 (Automated)1
💼 CIS GCP v3.0.0 → 💼 4.3 Ensure “Block Project-Wide SSH Keys” Is Enabled for VM Instances - Level 1 (Automated)1

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS GCP v1.3.0 → 💼 4.3 Ensure “Block Project-Wide SSH Keys” Is Enabled for VM Instances - Level 1 (Automated)1
💼 CIS GCP v3.0.0 → 💼 4.3 Ensure “Block Project-Wide SSH Keys” Is Enabled for VM Instances - Level 1 (Automated)1

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlags

Policies (1)​

PolicyLogic CountFlags
📝 Google GCE Instance Block Project-Wide SSH Keys is not enabled 🟢1🟢 x6