~/talk

Azure DevOps security - Lessons learned

Talkat Øredev 2025 · 2025-11-05..11-07· [security, devops-and-delivery]
slides:none on file

Azure DevOps often exposes real attack surfaces: allow public projects makes org APIs discoverable, forks plus pull requests let readers inject YAML that runs on internal runners, and about 40% of older tasks have known security issues or bad dependencies. Fixes shown include separating pipeline YAML into its own repo, using containers with read‑only mounts, converting service connections to workload identity federation and managed identities, disabling grant access to all pipelines, and turning on audit logging.

AI-written summary · about

  1. 0:00Azure DevOps security intro
  2. 1:34Dev and Ops security gap
  3. 2:38Public project API risks
  4. 6:35Deprecated pipeline tasks
  5. 9:09Unsupported Node versions
  6. 11:13Pipeline template risks
  7. 11:54Branch policy vulnerabilities
  8. 17:20Code injection via YAML
  9. 21:33Container isolation for injection
  10. 24:55Privilege escalation pitfalls
  11. 27:05Entra ID privileged access
  12. 29:59Service credentials federation
  13. 32:07Managed DevOps pools
  14. 36:21Pipeline resource lateral movement
  15. 38:34Audit logging defense
  16. 40:46CI/CD security best practices
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.