Sixteen years in, DevSecOps has stopped being a startup buzzword and started being infrastructure. The idea — putting security checks inside the delivery pipeline and the team, so every change is verified and traceable before it ships — now shows up in defense procurement, EU law, and the questionnaires your enterprise clients send before they book a charter platform integration. Yet 2026 finds the discipline in a strange position: more official attention than ever, still no single definition, and still no certification anyone can hang on a wall. This piece takes stock. Where the practice came from, what actually changed in the past year, what stubbornly hasn’t, and what operators in aviation-adjacent businesses should do about it. The reference document behind this summary is the DevSecOps briefing at xOps School, and its timeline is worth keeping bookmarked.
How the discipline got here
The arc is longer than most people assume. The milestones that shaped it:
- 2010. The Rugged Software manifesto makes the case that software should be built to survive attack, planting the seed that security belongs in development.
- 2012. Gartner publishes a report under the name “DevOpsSec” — proof that analysts were already struggling with the word order.
- February 2022. NIST ships version 1.1 of its Secure Software Development Framework, tied to the requirements of US executive order 14028 — the moment secure development became a federal expectation.
- March 2022. SP 800-204C applies the paradigm to microservices CI/CD, calling DevSecOps “a facilitating paradigm” rather than pretending to define it.
- April 2023. SLSA reaches version 1.0, giving supply-chain integrity its first stable grading ladder.
- February 2024. SP 800-204D follows, covering security of the CI/CD pipeline itself.
- October 2024. The US Department of Defense’s Enterprise DevSecOps Fundamentals hits version 2.5 — the discipline’s name literally inside a defense instruction.
- December 2024. The EU Cyber Resilience Act enters into force, with its main obligations due December 2027 — the only legally binding item anywhere in this list.
Read in sequence, the pattern is clear: a grassroots idea hardened into government expectations in about a decade. Just as telling is what sits between the milestones — incident after incident where a build tool, an action, or a library was compromised through the supply chain rather than the code itself, each one pushing another organization from “interesting idea” to “procurement requirement.” The discipline grew less from theory than from expensive lessons, which is why its guidance reads like a list of other people’s scars.
What changed for DevSecOps in the past year
Four developments from late 2025 into mid-2026 redraw the map for practitioners. First, OMB rescinded memorandum M-22-18 in January 2026, loosening the federal zero-trust and software-security memory requirements that had driven much enterprise demand — a reminder that policy tailwinds can reverse. Second, the 2025 edition of OWASP’s Top 10 turned category A03 into a catch-all for supply-chain failures rather than a single dependency-scanning technique, acknowledging where incidents actually happen now. Third, SLSA issued version 1.2, adding a Source track that grades trust in the repository side — history, review process — alongside the familiar build levels. Fourth, in July 2026 CISA, joined by seventeen partner organizations, refreshed the minimum elements for software bills of materials, tightening what a usable inventory must contain.
The year also delivered its object lesson. In March 2026, tags on two widely used scanner-related GitHub Actions were force-pushed to distribute a malicious build; responders contained it the same evening, but the “Immutable” badge those packages carried had not prevented the tampering. The lesson lands on the same point as the standard updates: trust the artifact you verified, not the label attached to it.
What hasn’t changed about DevSecOps
Three things look identical to five years ago. There is still no official, normative definition of DevSecOps — NIST, the DoD, and OWASP each use the term in their own sense, “SecDevOps” and “DevOpsSec” still circulate as loose synonyms, and no body certifies the discipline or standardizes the job title. The core mechanics are also unchanged: controls have positions, confidence levels, costs, and actions; gates stop merges only for severe, fixable, confidently detected, new findings; exceptions carry owners and expiry dates with a ninety-day ceiling; and SBOMs, signing, and provenance are produced per build and checked at deploy. And the adoption research still points the same direction — culture predicts uptake better than tooling, and teams that skip the gate policy and buy scanners anyway remain the discipline’s best-documented failure story. The metrics have also settled into a standard set worth knowing by name: how often humans overrule the gate each month, how fast new findings get fixed at median and worst-case, how many defects escaped that an existing check should have caught, what share of deployments carry verifiable provenance, and how many exceptions are past their expiry. Any operator can ask a software vendor for those five numbers; the ones who can produce them without a week’s notice are the ones whose security programme actually runs.
What this means for charter and aviation operators
If you run a platform in the charter, booking, or aviation-services space, three practical consequences follow. One: if you sell software or connected services into the EU, the Cyber Resilience Act’s December 2027 obligations are a real deadline with real teeth, and the evidence practices above — inventory, provenance, verified releases — are the same work the regulation expects. Two: US government-adjacent work increasingly flows through SSDF attestations, so being able to map your controls to the framework’s practices is bid-table currency. Three: enterprise charter clients now ask pipeline questions in procurement — who signs your releases, can you produce an inventory, what blocks a deploy. A small operator that can answer those three in writing looks materially safer than a larger one that cannot.
The purchasing advice is equally plain. Evaluate security tooling the way our guide to comparing and reviewing software tools suggests evaluating anything: against your own requirements and evidence, not a logo. And remember that no tool certifies DevSecOps — a vendor claiming a certification for the discipline is either confused or selling.
The numbers an operator should know
Between the standards and the watchlist sits a handful of working figures that make vendor and internal conversations concrete:
- 45 minutes — the working budget for threat modeling one significant change.
- 10 to 20 percent — the protected time that makes an embedded security champion real instead of nominal.
- Under 5 percent a month — the override rate a credible gate stays below.
- 90 days — the maximum life of an exception before it must be renewed with reasons.
- SLSA Build levels 0 to 3, with GitHub artifact attestations landing at level 2, or 3 under pinned reusable workflows.
- December 2027 — the date the Cyber Resilience Act’s main obligations bite.
Six figures, and you can hold your own in any pipeline security conversation this year.
The twelve-month watchlist
Three markers are worth tracking. The EU Cyber Resilience Act’s implementation guidance will harden as December 2027 approaches, and early adopters will shape the templates everyone else copies. NIST’s Secure Software Development Framework is working through a version 1.2 draft that has been circulating since December 2025 — when it finalizes, attestation templates will shift. And SBOM expectations will keep tightening after the July 2026 minimum-elements refresh, so teams still generating inventories only when a customer asks should expect that excuse to stop working. None of these requires new architecture from a small team; they require the habits already described, kept current.
The honest summary of 2026: the discipline’s center of gravity has moved from “should we do this?” to “can you show your work?” Aviation has always run on demonstrated compliance — crew certifications, maintenance logs, dispatch releases. DevSecOps is the software side of that same culture, and the teams building it now, with structured DevOps and tech-skills training or on their own, will find the regulatory wave arriving as a formality rather than a crisis. For individuals, the skills gap is a genuine opportunity: the structured learning paths for building a tech career apply here as much as anywhere, because a discipline without a certification is one where demonstrable practice is the only credential that counts.

