cATO Evidence Automation for Agency Software Pipelines
What continuous authorization to operate expects, which pipeline evidence proves it, and how to automate the control map, SBOMs and policy gates in 90 days.
- PUBLISHED
- November 15, 2026
- READ TIME
- 6 MIN
- AUTHOR
- ONE FREQUENCY
- Topic
- devsecops, cato, government
- Published
- November 15, 2026
- Read time
- 6 min
- Word count
- 1,129
Short answer: Continuous authorization to operate (cATO) lets a system keep its authorization to operate by showing, continuously, that it manages risk, instead of re-authorizing at fixed intervals. The February 2022 memo from the Department of Defense CIO sets three expectations: continuous monitoring of risk management framework controls, an active cyber defense capability, and secure software supply chain practices. Evidence automation is how a delivery pipeline produces proof of those three things on every release, so an authorizing official can see risk in near real time.
This is a design guide for agency teams and contractors. It extends our guide to agile and DevSecOps transformation for government agencies. One Frequency Inc does not claim federal contracts, an authority to operate or a cATO; this describes an approach.
What is cATO, and who can grant it?
An ATO is a decision by an authorizing official that a system's risk is acceptable under the NIST Risk Management Framework (SP 800-37 Rev. 2). A cATO is an ATO that stays valid as long as the system continues to meet defined conditions, with the pipeline and monitoring supplying the evidence. DoD CIO guidance says a system seeking cATO must already hold an ATO, and its criteria are framed around software factories and DevSecOps platforms. In DoD, the authorizing official decides; outside DoD, agencies run their own authorization processes, and FedRAMP governs cloud services. Confirm which authority and policy apply to your system before you invest in automation.
What are the three competencies?
The cATO memo and the DoD Enterprise DevSecOps Fundamentals document describe three areas:
- Continuous monitoring. Real-time or near-real-time visibility into the state of the security controls, aligned with NIST SP 800-53 controls and the monitoring approach in NIST SP 800-137.
- Active cyber defense. The ability to detect, respond to and recover from attacks, and to test the defense itself.
- Secure software supply chain. Practices that protect the code, dependencies, build and release process, consistent with the NIST Secure Software Development Framework (SP 800-218).
The 2024 evaluation criteria add that practices are defined and documented, evidence of risk management and continuous monitoring exists, the workforce understands the practices, and the level of implementation is measured. Treat those as the audit questions your evidence must answer.
What evidence does a pipeline produce?
Automate the artifacts, and store them where the authorizing official can query them:
- Source and change evidence: signed commits, protected branches, review records and the link from each change to a ticket.
- Build evidence: build logs, reproducible build settings, signed artifacts and provenance records.
- Dependency evidence: a software bill of materials for each release, plus vulnerability scan results and the status of each finding. OMB memo M-26-05 lets agencies require an SBOM by contract.
- Test evidence: unit, integration, static analysis, dynamic analysis and secrets-scan results tied to the release.
- Configuration evidence: infrastructure-as-code state, drift reports and hardening baselines.
- Runtime evidence: logs, alerts, detections, response times and the results of recovery exercises.
- Control mapping: a table that maps each control to the automated check that supports it, the last result and the owner.
How do you design the evidence flow?
Think of three stages. First, collect machine-readable results from each pipeline stage in a common format. Second, evaluate them against policy as code, so a release that fails a gate cannot ship without a documented, approved exception. Third, publish a dashboard and an exportable package keyed by release and control, so a reviewer can answer "what changed and what is the risk" without a meeting.
Avoid two traps. Do not generate evidence that nobody reads; agree with the authorizing official on the views they need. And do not treat a dashboard as the authorization: the people and decision process still matter, and the criteria explicitly look at workforce knowledge.
What are the pitfalls?
- Starting before the baseline ATO exists. The guidance expects an ATO first.
- Metrics without thresholds. A scan result needs a rule that says what blocks a release.
- Tool sprawl. Every new scanner needs an owner, a data format and a place in the control map.
- Manual exceptions that never expire. Give every exception an owner and a date.
- Confusing cATO with FedRAMP. FedRAMP authorizes cloud services for federal use under its own program, and FedRAMP 20x is changing that process; check the FedRAMP site for the current phase.
How do you roll it out in 90 days?
- Days 1-30: inventory the systems, agree the control set and the evidence views with the authorizing official, and pick a data format.
- Days 31-60: instrument one pipeline end to end: SBOM, scans, signed artifacts, policy gates and a control-mapped dashboard.
- Days 61-90: run a recovery and an incident exercise, measure the results, fix the gaps and extend to the next system.
These are planning ranges, not a promise of authorization. Timelines depend on the system and the authorizing official.
How One Frequency approaches this
One Frequency builds production AI agents and automation, with orchestration, observability and guardrails, and does continuous compliance and security engineering. Our founder led engineering and the FedRAMP High effort for a zero-trust secure remote access platform at a previous company and led SOC 2 at a Series A cybersecurity company. We apply that to evidence pipelines, policy as code and control mapping. We are a service-disabled veteran-owned small business with an active SAM.gov registration. We do not claim a federal ATO or cATO. See our DevOps, government and cybersecurity and compliance pages, or contact us.
FAQ
Q: What is cATO in plain terms? A: It is a continuing authorization to operate that holds as long as a system keeps showing, with continuous evidence, that it manages risk. DoD CIO guidance centers it on continuous monitoring, active cyber defense and a secure software supply chain.
Q: Do you need an ATO before a cATO? A: Yes, according to DoD CIO implementation guidance, a system seeking cATO must already have achieved an ATO. The cATO then replaces periodic reauthorization with continuous evidence.
Q: Is cATO a DoD-only concept? A: The memo and criteria are DoD CIO documents. Civilian agencies have their own authorization processes under NIST RMF and, for cloud services, FedRAMP. The evidence automation ideas carry over, but the approving authority differs.
Q: What should a pipeline produce for cATO evidence? A: Signed builds, an SBOM per release, scan and test results, configuration state, runtime detections and a map from each control to the automated check that supports it.
Q: Does One Frequency have a cATO or ATO? A: No. One Frequency Inc claims no federal ATO or cATO. We provide engineering for evidence automation, policy as code and secure delivery pipelines.
Cited and consulted.
- 01DoD CIO: Continuous Authorization to Operate (cATO) memo, February 2022media.defense.gov · accessed Nov 15, 2026
- 02DoD CIO: DevSecOps Continuous Authorization to Operate (cATO) Evaluation Criteriadodcio.defense.gov · accessed Nov 15, 2026
- 03DoD CIO: DevSecOps Continuous Authorization Implementation Guidedodcio.defense.gov · accessed Nov 15, 2026
- 04DoD Enterprise DevSecOps Fundamentals v2.5dodcio.defense.gov · accessed Nov 15, 2026
- 05NIST SP 800-37 Rev. 2: Risk Management Frameworkcsrc.nist.gov · accessed Nov 15, 2026
- 06NIST SP 800-137: Information Security Continuous Monitoringcsrc.nist.gov · accessed Nov 15, 2026
- 07NIST SP 800-53 Rev. 5: Security and Privacy Controlscsrc.nist.gov · accessed Nov 15, 2026
- 08NIST SP 800-218: Secure Software Development Framework v1.1csrc.nist.gov · accessed Nov 15, 2026
- 09OMB M-26-05: Adopting a Risk-based Approach to Software and Hardware Security (Jan 23, 2026)whitehouse.gov · accessed Nov 15, 2026
- 10FedRAMP 20xfedramp.gov · accessed Nov 15, 2026
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.