Parcours métiersEn préparation
CI/CD Security Engineer
CI/CD security engineers secure the pipelines that build and ship software. This path works through the OWASP Top 10 CI/CD security risks hands-on: poison a pipeline, abuse a dependency chain, bypass a flow-control gate, and recover the secrets a careless pipeline leaks.
Compétences requises
Les compétences clés de ce métier. Chacune regroupe les prérequis dont elle dépend.
Pipeline fundamentals1 compétences
- Recover secrets from Git history0%
Comprend
- Use a Git forge (clone, branch, fork, pull request)
Poisoned pipeline execution3 compétences
- Execute a Public (fork-based) Poisoned Pipeline Execution0%
Comprend
- Use a Git forge (clone, branch, fork, pull request)
- Read and understand a CI/CD pipeline
- Execute a Direct Poisoned Pipeline Execution
- Execute an Indirect Poisoned Pipeline Execution0%
Comprend
- Use a Git forge (clone, branch, fork, pull request)
- Read and understand a CI/CD pipeline
- Execute a Direct Poisoned Pipeline Execution
- Abuse weak pipeline access controls to reach the controller0%
Comprend
- Use a Git forge (clone, branch, fork, pull request)
- Read and understand a CI/CD pipeline
- Execute a Direct Poisoned Pipeline Execution
Dependency chain abuse1 compétences
- Abuse a dependency chain to poison a pipeline0%
Comprend
- Use a Git forge (clone, branch, fork, pull request)
Flow control and gates1 compétences
- Bypass a CI/CD flow-control or scan gate0%
Comprend
- Read and understand a CI/CD pipeline
Identity and artifacts2 compétences
- Compromise and abuse a CI/CD identity0%
Comprend
- Use a Git forge (clone, branch, fork, pull request)
- Hijack a 3rd-party artifact used in a pipeline0%
Comprend
- Read and understand a CI/CD pipeline
En préparation
Ce parcours est en cours de construction. Suivez les cours en attendant.
Tous les coursEn quoi consiste le métier
- Map a pipeline's trigger, permissions and trust boundaries.
- Exploit poisoned pipeline execution, dependency-chain and flow-control flaws.
- Recover leaked credentials and prove artifact-integrity gaps.
- Recommend fixes a platform team can apply.