- Issues
- ISSUE-403
ISSUE-403LowPipeline Composition
Outdated template
Control:CTRL-403Pipeline must use only up-to-date includes
📋 What is this?
An outdated template is used in the project CI/CD pipeline configuration.
⚠️ Impact
Outdated templates may have known vulnerabilities or fall behind current standards. For example, if your security scan template is outdated, it might miss detecting recent threats.
🔧 How to fix
Update the template in your project CI/CD configuration file to the latest version to stay secure and aligned with current standards.
✗ BeforeComponents are several versions behind the latest release.
# .gitlab-ci.yml - ❌ Uses outdated versioninclude: - component: gitlab.com/components/sast/sast@1.0.0 # Latest available: 1.5.2
- component: gitlab.com/components/secret-detection/secret-detection@2.1.0 # Latest available: 2.4.1✓ AfterComponents are up to date with the latest releases.
# .gitlab-ci.yml: ✅ Uses latest versionsinclude: - component: gitlab.com/components/sast/sast@1.5.2
- component: gitlab.com/components/secret-detection/secret-detection@2.4.1💡 Tips
- Use Plumber regularly to detect outdated includes before they become a security risk.
- Consider using Renovate or Dependabot to automate version updates in your CI configuration.
- Check the CI Catalog changelog for breaking changes before updating major versions.
⚙️ Configure this control
On the Plumber Platform: open the Policies page and set control CTRL-403 on the policy that governs the project.
With the CLI alone: set it in your configuration file. Every field and default is in the controls configuration reference, CTRL-403.