17 free courses — no signup wall
Architect-led enterprise cloud, security & AI
320+ downloadable toolkits — instant delivery
Skip to content
DevSecOps engineer

AI DevSecOps

Secure delivery for AI systems: pipelines, policy as code, secrets, and supply chain.

Who this is for

Engineers who own the pipeline that ships models and agents into production.

What you should be able to do

Ship through a pipeline that blocks on policy, scans dependencies, and never prints a secret.

Career ladder

The titles this track maps onto. Levels differ between companies — the useful part is the direction, and what each step adds to the one before it.

  1. DevOps Engineer
  2. DevSecOps Engineer
  3. Senior DevSecOps Engineer
  4. Staff Security Engineer
  5. Principal Security Architect

Tech stack

What the work is actually done with. Grouped by the job each tool does, so the list reads as a system rather than a pile of names.

CI/CD
GitHub ActionsAzure DevOpsArgo CD
Policy
OPAConftestSentinel
Supply chain
SBOMSigstoreDependency scanning
Secrets
VaultAWS Secrets ManagerAzure Key VaultOIDC federation

The delivery flow

The order the work actually happens in. Each step is where a decision gets made and written down, not a chapter heading.

  1. Threat model the pipeline
  2. Least-privilege CI identity
  3. Dependency + SBOM scan
  4. Policy as code gate
  5. Secret scanning
  6. Signed artifacts
  7. Deploy
  8. Audit trail

Reference repository structure

A starting layout for this track. The directories are the ones that get added late and hurt — decisions, evals, policy, lineage — promoted to the top level where they are visible.

delivery/
├── .github/workflows/     # least-privilege, OIDC not long-lived keys
├── policy/
│   ├── opa/               # deny-by-default, tested
│   └── tests/
├── supply-chain/
│   ├── sbom/
│   └── signing/
├── secrets/               # references only, never values
├── scanning/
│   ├── deps/
│   └── secrets-scan/
└── runbooks/

Primary sources

The standards, framework documents, and vendor references this track is built against. Go here when you need the authoritative wording rather than a summary — in a security review or an audit, the source is what counts.