HackTheCore
ResearchDevSecOps, Supply Chain and CI/CDPipeline and Runner Compromise

DevSecOps, Supply Chain and CI/CD // Field Brief

Pipeline and Runner Compromise

This DevSecOps and Supply Chain field brief frames Pipeline and Runner Compromise around the trust boundaries an authorized assessor needs to verify. Use it to plan safe validation, capture reproducible evidence and distinguish a meaningful control failure from an isolated technical symptom.

field noteassessment referencepublic sources

Why it matters in practice

Within DevSecOps and Supply Chain, Pipeline and Runner Compromise changes how scope, prerequisites and evidence should be handled. Focus on the concrete asset or data flow under test, record the assumptions that make the condition exploitable and connect verified behavior to an operational consequence and remediation decision.

Primary coverage

  • Map which jobs can access which secrets, environments and artifact stores.
  • Check token permissions, pull-request trust, reusable workflows and third-party action imports.
  • Identify whether runners are shared, ephemeral or long-lived and what residue they keep.
  • Follow the runner outward: what can it sign, publish, deploy or reconfigure?

Assessment focus

For Pipeline and Runner Compromise, document the starting condition, tested action, observable result and any constraint that limited validation. Separate what was proven from what remains inferred, then tie each recommendation to the control boundary described in the evidence.

Selected public references

Related research

Compare the adjacent DevSecOps and Supply Chain briefs below to test whether the same assumption, evidence pattern or mitigation boundary appears elsewhere in the domain.