SECAI Core · phase 15 of 15
Continuous integration/continuous deployment
A software development method combining app and platform updates (rapidly committed to production) with code updates (rapidly committed to a code repository or build server).
The Explain card
- Plain English
- CI/CD is a development practice where code changes are frequently merged, automatically tested and rapidly pushed to production, with both application and platform updates flowing through the same pipeline.
- Example
- A model retraining job commits new weights to the repository. The pipeline runs unit tests, safety evaluations and a model scan, then deploys the model to production automatically if everything passes.
- Why it matters
- The pipeline is the only gate between code and production. Security checks that live there run every time, and compromising the pipeline itself can poison everything that flows through it.
- Hook
- A conveyor belt to production: put the inspectors on the belt.
Where it sits in the deck
Phase 15: MLOps, Continuous Delivery, and Operational Resilience
Close the loop — operational practices, drift management, and delivery discipline that keep deployed AI systems healthy, current, and continuously improving.
