Branch Protection Enforcement Patterns

When to Use This Skill

graph TD
    T[Terraform Module] -->|Applies| BP[Branch Protection Rules]
    GA[GitHub App] -->|Monitors| BP
    GA -->|Detects| DRIFT[Configuration Drift]
    DRIFT -->|Triggers| REM[Automated Remediation]
    REM -->|Restores| BP
    BP -->|Enforces| PR[Pull Requests]
    PR -->|Generates| AUDIT[Audit Evidence]

    %% Ghostty Hardcore Theme
    style T fill:#a7e22e,color:#1b1d1e
    style GA fill:#65d9ef,color:#1b1d1e
    style DRIFT fill:#f92572,color:#1b1d1e
    style BP fill:#fd971e,color:#1b1d1e

Key Components:

• Terraform modules - Declare protection rules as code
• GitHub Apps - Monitor and enforce compliance organization-wide
• Drift detection - Identify unauthorized changes
• Automated remediation - Restore protection without manual intervention
• Audit collection - Capture evidence for compliance reporting

Prerequisites

• GitHub organization with admin access
• Terraform or OpenTofu (for IaC deployment)
• GitHub App with appropriate permissions (for automated enforcement)
• Basic understanding of Git workflow and branch protection concepts

Implementation

Step 1: Choose Your Security Tier

Start with Security Tiers to select the appropriate protection level for your repositories.

Step 2: Apply Protection

Manual (single repository):

gh api --method PUT \
  repos/org/repo/branches/main/protection \
  --input protection-config.json

Automated (organization-wide):

Step 3: Monitor Compliance

Deploy GitHub App Enforcement to detect drift and maintain compliance.

Step 4: Collect Evidence

Implement Audit Evidence patterns for compliance reporting.

Key Principles

1. Defense in Depth

Multiple enforcement layers: local configuration, drift detection, audit verification.

2. Automation Over Documentation

Don't document the policy. Enforce it automatically.

3. Tier-Based Configuration

Standard, Enhanced, Maximum tiers prevent both under-protection and over-restriction.

4. Immutable Audit Trail

GitHub API provides tamper-proof evidence of all enforcement actions.

5. Formalized Exceptions

Bypass controls with approval workflows, time-boxing, and automatic re-enablement.

Techniques

The Enforcement Gap

Most organizations have branch protection policies. Few enforce them consistently.

The Problem:

• New repositories inherit no protection
• Developers disable protection during incidents, forget to re-enable
• Configuration drift across 100+ repositories
• No automated detection when protection is weakened
• Exceptions bypass controls without audit trails

The Solution:

Automated enforcement with multiple defense layers:

1. Security tier templates - Standardized configurations for different risk levels
2. Infrastructure as Code - Terraform/OpenTofu modules for consistent deployment
3. GitHub App enforcement - Automated drift detection and remediation
4. Audit reporting - Compliance evidence collection
5. Formalized bypass controls - Time-boxed exceptions with approval workflows

Security Tiers

Different repositories require different protection levels.

Right-Sized Security

Not all repositories need maximum protection. Documentation repos can use Standard tier. Production infrastructure requires Maximum tier. Choose based on blast radius.

See Security Tiers for detailed configuration templates.

Architecture Overview

graph TD
    T[Terraform Module] -->|Applies| BP[Branch Protection Rules]
    GA[GitHub App] -->|Monitors| BP
    GA -->|Detects| DRIFT[Configuration Drift]
    DRIFT -->|Triggers| REM[Automated Remediation]
    REM -->|Restores| BP
    BP -->|Enforces| PR[Pull Requests]
    PR -->|Generates| AUDIT[Audit Evidence]

    %% Ghostty Hardcore Theme
    style T fill:#a7e22e,color:#1b1d1e
    style GA fill:#65d9ef,color:#1b1d1e
    style DRIFT fill:#f92572,color:#1b1d1e
    style BP fill:#fd971e,color:#1b1d1e

Key Components:

• Terraform modules - Declare protection rules as code
• GitHub Apps - Monitor and enforce compliance organization-wide
• Drift detection - Identify unauthorized changes
• Automated remediation - Restore protection without manual intervention
• Audit collection - Capture evidence for compliance reporting

What You'll Learn

This section covers comprehensive branch protection enforcement:

Configuration & Standards

• Security Tiers - Tiered protection templates for different risk levels
• Branch Protection Rules - Detailed configuration reference

Infrastructure as Code

• OpenTofu Modules - OpenTofu-specific patterns and considerations
• Multi-Repo Management - Patterns for 100+ repository enforcement

GitHub App Enforcement

• GitHub App Enforcement - Centralized enforcement with GitHub Apps
• Enforcement Workflows - Automated workflows for organization-wide compliance
• Drift Detection - Detecting and remediating configuration drift

Audit & Compliance

• Audit Evidence - Collecting and storing compliance evidence
• Compliance Reporting - Automated reporting for SOC 2, ISO 27001, PCI-DSS
• Verification Scripts - Audit preparation and continuous monitoring

Bypass Controls

• Bypass Controls - Formalized bypass procedures with approval workflows
• Emergency Access - Break-glass procedures for production incidents
• Exception Management - Managing permanent and temporary exceptions

Operations

• Troubleshooting - Common issues and solutions

Quick Start

Step 1: Choose Your Security Tier

Start with Security Tiers to select the appropriate protection level for your repositories.

Step 2: Apply Protection

Manual (single repository):

gh api --method PUT \
  repos/org/repo/branches/main/protection \
  --input protection-config.json

Automated (organization-wide):

Step 3: Monitor Compliance

Deploy GitHub App Enforcement to detect drift and maintain compliance.

Step 4: Collect Evidence

Implement Audit Evidence patterns for compliance reporting.

See reference.md for additional techniques and detailed examples.

Examples

See examples.md for code examples.

Full Reference

See reference.md for complete documentation.

Related Patterns

• Required Status Checks
• Commit Signing
• Audit & Compliance
• GitHub Apps

References

• Source Documentation
• AEL Enforce