Skip to main content
FIELD REPORT · DEVOPS

Agile and DevSecOps Transformation for Government Agencies

How agencies and contractors combine agile contracting, DevSecOps pipelines and continuous authorization, with the 2025-2026 DoD and OMB policy changes explained.

PUBLISHED
November 15, 2026
READ TIME
7 MIN
AUTHOR
ONE FREQUENCY
KEY FACTS
Topic
devops, devsecops, government
Published
November 15, 2026
Read time
7 min
Word count
1,280

Short answer: Agile and DevSecOps in government work when the contract, the security authorization and the pipeline are designed together. The policy direction in 2025 and 2026 points that way: the Department of Defense calls the Software Acquisition Pathway the preferred route for software, DoD guidance allows continuous authorization to operate (cATO) for mature software factories, and OMB replaced its secure software attestation memos in January 2026 with a risk-based approach. The practical task is to automate security evidence inside the pipeline so authorization follows delivery instead of blocking it.

This guide is for agency program leaders and contractors planning an agile transformation. One Frequency does not claim federal contracts or authorizations to operate; this is an approach description.

What is DevSecOps in a government context?

DevSecOps builds security testing, compliance checks and evidence collection into the same automated pipeline that builds and deploys software. In government, the extra constraint is the authorization process: a system normally needs an authority to operate (ATO) under the NIST Risk Management Framework (SP 800-37 Rev. 2), using controls from SP 800-53 Rev. 5 and the baselines in SP 800-53B. The DoD's own Software Modernization Strategy identifies the ATO as a long step in delivery and proposes continuous authorization to shorten it.

What changed in federal policy in 2025 and 2026?

  • Software Acquisition Pathway. DoD Instruction 5000.87 (October 2, 2020) created the pathway for software-intensive systems. Reporting from March 2025 describes a Secretary of Defense memo directing components to adopt it as the preferred path for software.
  • Software Fast Track. A DoD CIO memo, "Accelerating Secure Software" (April 2025), set up the Software Fast Track initiative, covering cyber and supply chain risk management, software security verification and faster authorizations.
  • Continuous ATO. The DoD CIO's cATO memo (February 2022) and its implementation guide describe how an organization with a mature software factory can operate with continuous authorization while maintaining required real-time risk posture.
  • Secure software attestation. OMB memo M-26-05, dated January 23, 2026, rescinds M-22-18 and M-23-16. Agencies must keep software and hardware inventories and set risk-based assurance policies, may still choose to use the CISA attestation form, and may contractually require a software bill of materials on request.
  • Secure development guidance. NIST SP 800-218 (SSDF) version 1.1 is final; a revision 1 initial public draft appeared on December 17, 2025, and Executive Order 14306 (June 2025) directed NIST to update the framework.
  • FedRAMP 20x. FedRAMP is piloting a new authorization approach for cloud services, with Low and Moderate pilots completed and wider adoption phases planned. Check the FedRAMP site for the current phase.

Policy is moving fast. Confirm the current status of each item against its primary source before you cite it in a proposal.

How do you contract for agile delivery?

The Digital Services Playbook has 13 plays; play 4 is to build the service using agile and iterative practices and play 5 is to structure budgets and contracts to support delivery. The GSA-hosted TechFAR Hub explains how the FAR supports agile work, including that using a contractor for agile development is not inherently governmental and that a high-level product vision with outcome-based objectives can be consistent with FAR requirements. Modular contracting under FAR Part 39 breaks large IT acquisitions into smaller increments. Note that the FAR is being rewritten under the 2025 overhaul, so part and section numbers may differ from older guidance.

Practical contract features that support agile delivery:

  • Outcome-based objectives and a prioritized backlog instead of a fixed requirements list.
  • Short, fixed-length increments with working software demonstrated to the government each time.
  • Government product owner with authority to reprioritize.
  • Acceptance criteria that include security and test evidence from the pipeline.
  • Options and modular task orders so the agency can stop, redirect or continue.

What should a government DevSecOps pipeline automate?

  1. Source control and review: protected branches, required reviews and signed commits.
  2. Build integrity: reproducible builds, dependency scanning and a software bill of materials generated on every build.
  3. Testing: unit, integration and security tests (static and dynamic analysis, secret scanning, container scanning) as blocking gates.
  4. Infrastructure as code: policy-as-code checks against the control baseline before deployment.
  5. Deployment: progressive delivery with rollback, and approvals logged.
  6. Evidence: every gate writes results to a store that maps back to control IDs, so an assessor can query current compliance rather than review a stale binder.
  7. Monitoring: runtime telemetry and alerts feed the continuous monitoring the authorization depends on.

Our guides on CI/CD pipeline best practices, deployment frequency and security for AI-assisted development cover the engineering detail.

What are the common failure modes of a government agile transformation?

  • Agile delivery, waterfall authorization. Teams ship every two weeks but the system waits months for an ATO decision. Fix it by involving the authorizing official's staff in sprint reviews and by generating control evidence from the pipeline.
  • A product owner without authority. If priorities need committee approval, increments stall. Name one empowered owner.
  • Tooling before process. Buying a pipeline product does not create a software factory; teams still need branching, testing and release discipline.
  • Security as a final gate. Finding vulnerabilities at the end is expensive. Shift scanning and threat modeling into the first sprint.
  • Measuring activity. Counting story points or commits rewards the wrong behavior.

How should agencies and contractors measure progress?

Use delivery metrics (deployment frequency, lead time, change failure rate, recovery time) alongside security measures such as time to remediate findings and the share of controls with automated evidence. Report trends, not single numbers. See our engineering productivity metrics guide.

Where does AI fit?

AI agents can draft control narratives from pipeline evidence, triage scanner findings, and summarize change risk for reviewers. Keep them inside approval gates and audit logs; our guide to agent governance at scale explains how, and the NIST AI RMF gives the risk structure.

How One Frequency approaches this

One Frequency is an SBA-certified SDVOSB (UEI QWJ3CV1TB8C9, CAGE 13SR2). Our founder has 25+ years of software engineering experience, led SOC 2 at a Series A cybersecurity company, and led engineering and the FedRAMP High effort for a secure remote access platform at a previous company. We apply that to pipeline design, evidence automation and agile delivery structure. We have no authorizations to operate of our own and make no claim of federal past performance. See DevOps, government or contact us.

FAQ

Q: What is a continuous ATO? A: A continuous authorization to operate lets an organization with a mature software factory maintain authorization through real-time risk monitoring instead of periodic reauthorization. The DoD CIO issued cATO guidance in February 2022 and an implementation guide.

Q: Did OMB's secure software attestation requirement go away? A: OMB memo M-26-05 (January 23, 2026) rescinded M-22-18 and M-23-16. Agencies may still choose to use the CISA attestation form and may contractually require a software bill of materials.

Q: Can the government buy agile development services under the FAR? A: Yes. The TechFAR Hub explains that agile development by a contractor is not inherently governmental and that outcome-based objectives are consistent with FAR requirements. Modular contracting under FAR Part 39 supports incremental delivery.

Q: What is the NIST SSDF? A: The Secure Software Development Framework, NIST SP 800-218, sets practices for secure software development. Version 1.1 is final, and a revision 1 draft was released in December 2025.

Q: Does One Frequency hold an ATO or FedRAMP authorization? A: No. One Frequency does not claim an ATO, FedRAMP authorization or CMMC certification. It offers pipeline and evidence engineering to help clients pursue theirs.

SOURCES

Cited and consulted.

  1. 01OMB M-26-05: Adopting a Risk-based Approach to Software and Hardware Security (Jan 23, 2026)whitehouse.gov · accessed Nov 15, 2026
  2. 02CISA: Secure Software Development Attestation Formcisa.gov · accessed Nov 15, 2026
  3. 03NIST SP 800-218: Secure Software Development Framework v1.1csrc.nist.gov · accessed Nov 15, 2026
  4. 04NIST SP 800-218 Rev. 1 (SSDF v1.2) initial public draftcsrc.nist.gov · accessed Nov 15, 2026
  5. 05Executive Order 14306: Sustaining Select Efforts to Strengthen the Nation's Cybersecurityfederalregister.gov · accessed Nov 15, 2026
  6. 06DoD Instruction 5000.87: Operation of the Software Acquisition Pathwayesd.whs.mil · accessed Nov 15, 2026
  7. 07DoD CIO memo: Accelerating Secure Software (Software Fast Track)dodcio.defense.gov · accessed Nov 15, 2026
  8. 08DoD CIO: Continuous Authorization to Operate (cATO) memo, February 2022media.defense.gov · accessed Nov 15, 2026
  9. 09DoD Software Modernization Strategydodcio.defense.gov · accessed Nov 15, 2026
  10. 10NIST SP 800-37 Rev. 2: Risk Management Frameworkcsrc.nist.gov · accessed Nov 15, 2026
  11. 11NIST SP 800-53 Rev. 5: Security and Privacy Controlscsrc.nist.gov · accessed Nov 15, 2026
  12. 12U.S. Digital Service: Digital Services Playbook (13 plays)playbook.usds.gov · accessed Nov 15, 2026
  13. 13TechFAR Hub: General considerations for agile contractingtechfarhub.cio.gov · accessed Nov 15, 2026
  14. 14FedRAMP 20xfedramp.gov · accessed Nov 15, 2026
  15. 15acquisition.gov: FAR overhaul, Part 39 (modular contracting)acquisition.gov · accessed Nov 15, 2026
View All Insights
NEXT STEP

Ready to ship the next outcome?

One Frequency Consulting brings 25+ years of technology leadership and military discipline to every engagement. First call is operator-grade scoping — sixty minutes, no charge.