dogear

enter for all results · esc to close

GitHub Actions OIDC – Non-Human Identities and Secretless Authentication

eparon.mesite

A two-part guide on moving from static secrets to OIDC-based identities in GitHub Actions, including a practical lab for protecting APIs.

visit eparon.me ↗
0
sign in to dogear this
from
OpenID Connect
added
2026-10-10
likes
0

similar

  1. How We Discovered Vulnerabilities in CI/CD Pipelines of Popular Open-Source Projects cycode.com
    site category #cicd-attacks link ↗

    Extracting all repository and organization secrets in GitHub Actions.

  2. Manage Your GitHub Actions Secrets With A Simple CLI github.com
    tool category #actions link ↗
  3. Hacking GitHub AWS integrations again dagrz.com
    site category #cicd-attacks link ↗

    Attacking misconfigured pipelines that use OIDC.

  4. SecretHub github.com
    tool category #actions link ↗

    Have a single source of truth for your secrets and load them into GitHub Actions on demand.

  5. Keeping your GitHub Actions and workflows secure Part 2: Untrusted input securitylab.github.com
    site category #cicd-attacks link ↗

    GitHub Actions command injection.

  6. Vulnerable GitHub Actions Workflows Part 1: Privilege Escalation Inside Your CI/CD Pipeline legitsecurity.com
    site category #cicd-attacks link ↗

    GitHub Actions workflow_run PE.

OpenID Connect › Resources > Thematic Articles: “A two-part guide on moving from static secrets to OIDC-based identities in GitHub Actions, including a practical lab for protecting APIs.”