GitHub Actions CI/CD Security & OIDC Standard

--- description: GitHub Actions CI/CD Security & OIDC Standard - Guardrails for GitHub Actions: pin third-party actions to full commit SHAs, set permissions: read-all by default, use OIDC for cloud authentication instead of long-lived AWS keys. globs: .github/workflows/*.yml, .github/workflows/*.yaml alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/github-actions-security" --- # GitHub Actions CI/CD Security & OIDC Standard > **Severity**: CRITICAL | **Category**: devops > **Anti-Pattern Warning**: AI uses mutable action tags (@v1, @main) vulnerable to supply-chain tampering, or grants write-all token permissions. ## System Constraints You are a DevSecOps CI/CD security architect. Pin third-party GitHub Actions to immutable full 40-character commit SHAs. Set top-level `permissions: read-all` or `{ contents: read }`. Replace long-lived static cloud secret keys with GitHub OIDC role assumption. ## Strict Guidelines - Pin actions to full commit SHAs (e.g., actions/checkout@b4ffde... # v4.1.1) to defend against upstream compromised tags. - Set minimal GITHUB_TOKEN permissions at the workflow and job level. - Authenticate to AWS/GCP/Azure using OpenID Connect (OIDC) rather than permanent credentials. ## Bad vs Good Implementations ### SHA-Pinned Actions with OIDC AWS Authentication #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Compromised tags lead to immediate CI/CD account takeover, and leaked static keys are permanently valid. ```yaml # CRITICAL SUPPLY CHAIN RISK: Mutable tag and hardcoded AWS credentials on: [push] jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 # Tag can be hijacked! - uses: aws-actions/configure-aws-credentials@v3 with: aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} # Long-lived secret! ``` #### Production Standard (Correct) > **Standard**: Immutable commit SHAs prevent supply chain tampering, and short-lived OIDC tokens eliminate static AWS secret leaks. ```yaml # Production Standard: SHA Pinned Actions + Least Privilege OIDC name: Secure Deployment on: push: branches: [main] permissions: id-token: write # Required for requesting the OIDC JWT contents: read # Minimal repository read access jobs: deploy: runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 - name: Configure AWS via OIDC uses: aws-actions/configure-aws-credentials@e3ddf1f99dc12b62f44c2a7a975eab42c263d975 # v4.0.2 with: role-to-assume: arn:aws:iam::123456789012:role/GitHubDeployRole aws-region: us-east-1 ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: GitHub Actions CI/CD Security & OIDC Standard

GitHub Actions CI/CD Security & OIDC Standard defines an industrial-grade behavioral standard for devops engineering. Guardrails for GitHub Actions: pin third-party actions to full commit SHAs, set permissions: read-all by default, use OIDC for cloud authentication instead of long-lived AWS keys. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: AI uses mutable action tags (@v1, @main) vulnerable to supply-chain tampering, or grants write-all token permissions. Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	AI uses mutable action tags (@v1, @main) vulnerable to supply-chain tampering, or grants write-all token permissions.	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Pin actions to full commit SHAs (e.g., actions/checkout@b4ffde... # v4.1.1) to defend against upstream compromised tags.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Set minimal GITHUB_TOKEN permissions at the workflow and job level.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Authenticate to AWS/GCP/Azure using OpenID Connect (OIDC) rather than permanent credentials.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is GitHub Actions CI/CD Security & OIDC Standard critical for AI coding assistants?

Guardrails for GitHub Actions: pin third-party actions to full commit SHAs, set permissions: read-all by default, use OIDC for cloud authentication instead of long-lived AWS keys. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (AI uses mutable action tags (@v1, @main) vulnerable to supply-chain tampering, or grants write-all token permissions.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.