Compose a pipeline
Pick the domains you are responsible for. Every control the graph holds for them is placed into the lifecycle phase where it belongs, with the frameworks it evidences and the attacks it stops.
Domains
- Static Code Analysis20
- Dependency Management24
- Container Security24
- Exposure & Vulnerability Management×
- Endpoint Protection6
- Secrets & Identity Security24
- Build Integrity & Cryptographic Trust19
- CI/CD Pipeline Security10
- Runtime Application Validation25
- Runtime & Kubernetes Protection24
- AI Model & Agent Security16
- Identity & Access Management16
- Cloud Security Posture14
- Package Registry & Provenance Security13
- API Security12
- Detection & Response12
- SBOM & Component Visibility12
- Vendor Governance12
- Infrastructure-as-Code Security11
- Developer Security & Secure Coding10
- Secure Design & Threat Modeling10
- Governance, Risk & Compliance8
- Source Control Security×
- Data Protection×
- Email & Collaboration Security1
Maturity ceiling
Controls carry the maturity level a program needs to run them. Raising the ceiling adds depth and volume; level 3 is a realistic target for most teams.
- GOV Governance and assurance
- The stream that decides what blocks, and proves it blocked.
- SUP Open source and third-party supply
- Everything you did not write, arriving faster than you can review it.
- DEV Design and development
- Where the cost of a fix is lowest and the attention is shortest.
- DEL Build and delivery
- The machine that makes the thing, and the largest single target in the chain.
- VER Testing and validation
- The stream that finds out whether any of the others worked.
- OPS Runtime and platform
- The last place to stop something, and the most expensive.
- OBS Detection and continuous observation
- The only stream whose answer changes while nothing else does.
The figure is how many controls the field places in that cell and the wash behind it is how much of the cell you have decided — 25 targeted, 0 ignored, 308 still open, of 333. A ring means the cell is closed. Your 21 controls account for 25 of those, because a control that belongs at build and again at deploy is two decisions about where it runs rather than one. Ignoring a control counts as decided and leaves the denominator, so coverage measures what you said you would do rather than everything that exists.
The dashed rules are the two boundaries every pipeline has, whatever its platform: intake at build and release at release. Both default open — nothing is refused unless something was configured to refuse it.
The columns are drawn as a row here and as a loop elsewhere, and the same eight phases are the eight color groups a player walks around the DevSecOpoly board, in these same colors. The shape is a convenience. What is real is that each phase is a set of activities, and an activity is only worth doing because it enables a capability.
21 capabilities appear 25 times, because a control can belong at more than one point in the lifecycle. Digest verification, for instance, is enforced at build and checked again at deploy — the same capability doing a different job.
- 01
Plan
1 capability
- 02
Code
6 capabilities
- Branch Protection & Ruleset EnforcementSCM · level 1 · table stakes · counters 2 · 7 controlsList only1 scored of 5
- Code Review EnforcementSCM · level 2 · counters 3 · 5 controlsList only1 scored of 4
- Commit Signing & VerificationSCM · level 3 · counters 2 · 3 controlsList only3 products
- Developer & Maintainer MFA EnforcementSCM · level 1 · table stakes · counters 3 · 4 controlsList only2 products
- Repository Access GovernanceSCM · level 2 · counters 2 · 5 controlsList only3 products
- Contextual Remediation GuidanceEVM · level 3 · 2 controlsCompare3 scored of 5
- 04
Test
1 capability
- 05
Release
1 capability
- 07
Operate
7 capabilities
- Repository Access GovernanceSCM · level 2 · counters 2 · 5 controlsList only3 products
- Repository Security Posture AssessmentSCM · level 2 · 4 controlsList only5 products
- Source Control Audit LoggingSCM · level 2 · counters 2 · 5 controlsList only2 products
- Data Discovery & ClassificationDATA · level 2 · 3 controlsList only2 products
- Data Loss PreventionDATA · level 3 · counters 2 · 4 controlsOne product1 product
- Sensitivity Labeling & EncryptionDATA · level 2 · 4 controlsOne product1 product
- Asset Discovery & InventoryEVM · level 1 · table stakes · 5 controlsList only1 scored of 7
- 08
Monitor
9 capabilities
- Source Control Audit LoggingSCM · level 2 · counters 2 · 5 controlsList only2 products
- Application Security Posture ManagementEVM · level 3 · 5 controlsCompare2 scored of 8
- Automated Ticketing & Remediation WorkflowEVM · level 2 · 3 controlsCompare2 scored of 8
- Contextual Remediation GuidanceEVM · level 3 · 2 controlsCompare3 scored of 5
- Finding Ownership RoutingEVM · level 3 · 2 controlsCompare2 scored of 5
- Fix ValidationEVM · level 3 · 3 controlsList only1 scored of 5
- Risk-Based Vulnerability PrioritizationEVM · level 3 · counters 1 · 6 controlsCompare3 scored of 11
- Vulnerability Aggregation & DeduplicationEVM · level 2 · 3 controlsCompare3 scored of 11
- Vulnerability SLA TrackingEVM · level 2 · 4 controlsList only1 scored of 6
Framework coverage
What this selection alone would let you evidence.
ASVS 5.0
2 of 17
OWASP Application Security Verification Standard (ASVS) 5.0.0
V11 · V14
CI/CD Top 10
6 of 10
OWASP Top 10 CI/CD Security Risks
CICD-SEC-1 · CICD-SEC-10 · CICD-SEC-2 · CICD-SEC-7 · CICD-SEC-8 · CICD-SEC-9
S2C2F
1 of 25
OpenSSF Secure Supply Chain Consumption Framework (S2C2F)
UPD-3
SLSA 1.2
4 of 16
Supply-chain Levels for Software Artifacts (SLSA) 1.2
Source L2 — Continuous immutable history · Source L2 — Source provenance attestations · Source L3 — Enforced technical controls · Source L4 — Two-party review
SSDF 1.1
6 of 42
NIST Secure Software Development Framework 1.1 (SP 800-218)
PO.4.1 · PS.1.1 · PW.7.1 · RV.2.1 · PO.4.2 · RV.2.2
Scorecard
4 of 20
OpenSSF Scorecard Checks
Branch-Protection · Code-Review · Security-Policy · Webhooks
Coverage by phase
Plan
Not modeledNo attack techniques are modeled against this phase yet. That is a gap in our model, not evidence the phase is safe.
Code
1 countered · 3 open of 4
Test
Not modeledNo attack techniques are modeled against this phase yet. That is a gap in our model, not evidence the phase is safe.
Release
1 countered · 3 open of 4
Operate
3 countered · 10 open of 13
Monitor
Not modeledNo attack techniques are modeled against this phase yet. That is a gap in our model, not evidence the phase is safe.
What this selection leaves open
Trusted Supplier Compromise
Open12 real incidentsCommon · Operate
Nothing in this pipeline counters it. The graph knows 5 capabilities that would: Commercial Software Binary Composition Analysis, Continuous Vendor Risk Monitoring, Nth-Party Dependency Mapping, SaaS & CI/CD Integration Governance, and others.
Maintainer Account Takeover
Countered10 real incidentsCommon · Release
Countered by Developer & Maintainer MFA Enforcement.
Stolen Publishing Token
Open9 real incidentsCommon · Release
Nothing in this pipeline counters it. The graph knows 7 capabilities that would: Access Token Scoping & Least Privilege, Deployment Environment Protection, Engineering Platform Audit Log Monitoring, Leaked Credential Validation & Revocation, and others.
Artifact Tampering After Build
Open7 real incidentsCommon · Release
Nothing in this pipeline counters it. The graph knows 7 capabilities that would: Artifact Digest Integrity Verification, Artifact Signing, Build Provenance Attestation, Dependency Pinning & Lockfile Integrity Verification, and others.
Exploitation of Known Vulnerable Component
Countered5 real incidentsVery Common · Operate
Countered by Risk-Based Vulnerability Prioritization.
Leaked Secret Abuse
Open5 real incidentsVery Common · Operate
Nothing in this pipeline counters it. The graph knows 5 capabilities that would: Dynamic Short-Lived Credentials, Leaked Credential Validation & Revocation, Secret Push Protection, Secrets Detection in Source Code, and others.
Abandoned Package or Domain Takeover
Open2 real incidentsCommon · Release
Nothing in this pipeline counters it. The graph knows 2 capabilities that would: Maintainer & Publisher Risk Analysis, Open Source Project Health Scoring.
Adversary-in-the-Middle MFA Phishing
Countered2 real incidentsVery Common · Operate
Countered by Developer & Maintainer MFA Enforcement.
Unauthorized Commit Injection
Countered2 real incidentsCommon · Code
Countered by Branch Protection & Ruleset Enforcement, Code Review Enforcement, Commit Signing & Verification.
AI Agent Privilege Abuse
Open1 real incidentEmerging · Operate
Nothing in this pipeline counters it. The graph knows 3 capabilities that would: AI Agent & MCP Server Governance, AI Coding Assistant Security Guardrails, Non-Human Identity Discovery & Governance.
Cloud Misconfiguration Exploitation
Open1 real incidentVery Common · Operate
Nothing in this pipeline counters it. The graph knows 3 capabilities that would: Cloud Security Posture Management, IaC Misconfiguration Scanning, IaC Plan-Time Policy Evaluation.
Exposed Kubernetes Control Interface
Open1 real incidentCommon · Operate
Nothing in this pipeline counters it. The graph knows 2 capabilities that would: Kubernetes Manifest & Helm Chart Scanning, Kubernetes Security Posture Management.
9 further techniques with no documented incidents
Not in this comparison
- Does not apply to this kind of pipeline
- stages A composed pipeline has no authored stages; its capabilities are grouped by lifecycle phase.
- gaps Gap analysis compares a stage's capabilities against the products that stage uses, and only a client pipeline records products in use. A composed pipeline models the design, not an estate.
How this was produced
Every figure above was read from the Gantry knowledge graph, version 7.1.0, and computed when you opened this page — in 300 ms on 2026-10-27. Nothing here is a cached verdict or a dataset assembled for marketing: it is the same model our engagements run on.