How does GitHub support compliance requirements for enterprises?

Question

Options

• AGitHub provides configurable controls such as an audit log, SAML authentication, and enterprise
• BGitHub disables all external collaboration features.
• CGitHub only allows those with repository owner (admin) permissions to write changes to
• DGitHub automatically encrypts user passwords in plaintext for quick access.

• A
  89% (56)
• B
  2% (1)
• C
  6% (4)
• D
  3% (2)

Explanation

Option A is correct because GitHub Enterprise provides a suite of compliance-ready tools: audit logs track who did what and when, SAML/SSO authentication integrates with corporate identity providers, and enterprise managed users give organizations strict control over account lifecycle and access - all of which are core requirements in frameworks like SOC 2, HIPAA, and ISO 27001.

Why the distractors are wrong:

• B is wrong - GitHub actively supports external collaboration (pull requests, outside contributors, forks); disabling it would defeat much of GitHub's purpose.
• C is wrong - GitHub has a full permission hierarchy (read, triage, write, maintain, admin); restricting writes to only admins is not a compliance feature and would make normal development impossible.
• D is wrong - storing passwords in plaintext is a critical security vulnerability, not a feature. GitHub uses hashed credentials; "plaintext for quick access" is a red flag phrase that always signals a wrong answer on security topics.

Memory tip: Think "ACE" compliance - Audit logs, Corporate SSO (SAML), and Enterprise user management. If a choice describes GitHub restricting or weakening its collaboration model, it's almost certainly wrong.

No community discussion yet for this question.