Most answers to "how long does an ATO take" are a range with nothing behind it: six months, a year, sometimes two. The range is real, but it doesn't help a program manager build a schedule. An Authority to Operate (ATO) is the authorizing official's signed acceptance of a system's risk, and the time it takes is set mostly by the steps where the work waits on someone else. The government's own published figures, and the way the Risk Management Framework (RMF) distributes those waits, make a better starting point.
How long does an ATO take?
There is no standard duration. No statute, OMB circular or NIST publication sets one, and the published numbers come from individual agencies describing their own experience. Treat them as planning assumptions.
Two government sources give figures. The Centers for Medicare and Medicaid Services (CMS) says on its ATO planning site that "using the old waterfall process, getting and maintaining an Authority to Operate (ATO) can take 3-9 months." In a 2018 blog post quoted by FedScoop, Aidan Feldman, a developer at 18F, the General Services Administration's digital services team, wrote that "ATOs across government have traditionally taken 6-18 months," and described how the team cut its own from more than six months to about 30 days.
The conditions behind that 30-day figure matter more than the number. The systems were small, almost all ran on cloud.gov, a platform-as-a-service with a FedRAMP authorization, and the team used a System Security Plan template that left out controls the platform already covered. Assessors and the project team worked one ATO at a time in focused sprints.
Where does the time go in the RMF?
The RMF in NIST Special Publication (SP) 800-37 Rev. 2 has seven steps and 47 tasks. Writing documents is only part of it. The schedule risk sits in the tasks whose primary responsibility belongs to someone outside the delivery team.
| RMF step | Tasks | Who holds primary responsibility for the key task | What the schedule waits on |
|---|---|---|---|
| Prepare | P-1 to P-18 | Authorizing official (P-11, the authorization boundary) | Agreeing the boundary, and a published list of common controls (P-5) |
| Categorize | C-1 to C-3 | Authorizing official or designated representative, with the senior agency official for privacy (C-3) | Approval of the FIPS 199 categorization |
| Select | S-1 to S-6 | Authorizing official or designated representative (S-6) | Review and approval of the security and privacy plans |
| Implement | I-1 to I-2 | System owner | Engineering work, plus documenting the as-built state |
| Assess | A-1 to A-6 | Authorizing official or designated representative (A-1, and A-2 with the control assessor); control assessor (A-3) | Assessor availability, an approved assessment plan, then remediation and retest |
| Authorize | R-1 to R-5 | Authorizing official or designated representative (R-2, R-3); authorizing official (R-4) | Risk analysis, the response to open findings and the decision |
| Monitor | M-1 to M-7 | Authorizing official (M-6, ongoing authorization) | Continuous monitoring results; this is what keeps the ATO current |
Counted that way, the authorizing official (P-11) or the official's designated representative (C-3, S-6, A-1 and A-2) is on five tasks before the risk determination and decision in R-2 through R-4. Each is a meeting to book and a document to turn around. A team that plans for one signature at the end finds out about the other five late.
Where ATO schedules slip
Delays tend to cluster in a few places, and most of them are visible early.
The boundary moves. P-11 sets the authorization boundary, NIST gives the authorizing official primary responsibility for it, and everything after it depends on that line. A new interface or a hosting change late in the build means re-scoping controls and, often, rewriting parts of the plan.
Inheritance isn't documented. P-5 asks the organization to publish the common controls available for inheritance. When that list doesn't exist, or the hosting provider's package isn't in hand, the team ends up writing and assessing controls it should have inherited. This is the condition 18F removed by building on cloud.gov.
The assessor is booked late. A-1 selects the assessor and A-2 approves the assessment plan. If the assessment team is a shared agency resource or a separately procured contract, its calendar can set the date more than the system's readiness does.
Findings arrive with no remediation time. A-5 covers initial remediation and reassessment, and A-6 produces the plan of action and milestones (POA&M). Schedules that put the assessment report and the decision back to back leave no room for either.
Privacy review starts late. The senior agency official for privacy shares primary responsibility for the categorization review (C-3), so a system that handles personally identifiable information needs that office's time booked alongside the security reviews.
The authorizing official changes. If a new official arrives before the decision, plan to brief that person on the package from the beginning.
How long is an ATO valid?
As long as the authorizing official says. NIST SP 800-37 Rev. 2 has the authorizing official set an authorization termination date as a condition of the ATO and adjust it at any time. It also says organizations may eliminate the termination date once the system operates under ongoing authorization, with a review frequency in its place.
The familiar three-year cycle isn't in either NIST SP 800-37 or OMB Circular A-130, which since its 2016 revision tells agencies to reauthorize "on a time- or event-driven basis in accordance with agency risk tolerance." NIST notes that termination dates are guided by federal and organizational policies, so your agency or department may set its own maximum.
For shared and cloud services, NIST SP 800-37 calls the customer's decision an authorization to use (ATU) and says it does not require a termination date while the customer continues to accept the risk and the provider's ATO meets federal and organizational requirements. Under FedRAMP, agencies still record that decision as their own ATO. The FedRAMP 20x explainer covers how a cloud provider's FedRAMP status feeds the agency's authorization.
Do ongoing and continuous ATO make it faster?
They make the second authorization faster, not the first. A-130 sets two conditions for ongoing authorization: the system must already hold an initial ATO, and continuous monitoring programs must cover all implemented security and privacy controls at the right rigor and frequency. The authorizing official then formally approves the transition.
For DoD systems, the Department of Defense's February 2022 continuous ATO (cATO) memo adds its own bar, three competencies the authorizing official must see: ongoing visibility of key cybersecurity activities inside the boundary, the ability to conduct active cyber defense in real time, and use of an approved DevSecOps reference design. Building toward those from the start is what lets a team avoid assembling a new package every time the termination date comes up. Our earlier post on accelerating federal ATO with DevSecOps goes through the engineering side.
How to plan an ATO schedule
Start the plan at the Prepare step, not at the assessment. A workable schedule names a date and an owner for each task that waits on someone else:
- Confirm who the authorizing official and designated representative are, and book the P-11, C-3, S-6 and A-2 decisions before the work they approve is finished.
- Freeze the authorization boundary (P-11) early, and treat later changes as schedule changes.
- Get the agency's common control list and the hosting provider's authorization package before writing the security plan, so inherited controls are marked as inherited from the first draft.
- Select the assessor (A-1) as soon as the plan is drafted, and confirm the assessment window in writing.
- Leave time between the assessment report and the decision for remediation, retest and the POA&M (A-5 and A-6).
- Write the continuous monitoring strategy (S-5) as if you will ask for ongoing authorization, because that is what shortens every authorization after the first.
Our DevSecOps team helps agencies build the evidence for these steps into the delivery pipeline, so the package is current when the authorizing official asks for it. The total duration stays an assumption; the date for each dependency is something you can set.
The Bottom Line
Ask how long an ATO takes and the honest answer is "as long as the slowest dependency." Map the RMF tasks that wait on other people, book the authorizing official's and assessor's time early, and inherit every control you can. That is where schedules are won or lost, well before the final signature.
FAQ
How long is an ATO valid?
NIST SP 800-37 Rev. 2 says the authorizing official establishes the authorization termination date as a condition of the ATO and can shorten it at any time. Under ongoing authorization the termination date can be removed and replaced by a review frequency. Agency or department policy may set a maximum period, so check your agency's own security policy.
What is the difference between an ATO and an ATU?
In NIST SP 800-37 terms, an authorization to operate is issued for an information system, and an authorization to use is what a customer organization issues when it accepts the risk of using a shared or cloud system another organization has authorized. NIST says an ATU does not require a termination date while the customer keeps accepting the risk and the provider's ATO meets federal and organizational requirements. Under FedRAMP, agencies still record their acceptance of a cloud service as their own ATO.
Can a system go into production before the ATO is signed?
OMB Circular A-130 requires agencies to complete an initial authorization to operate prior to operational status. NIST also describes the authorizing official issuing an ATO for a short, restricted period when a system has to be tested in the operational environment before all controls are in place, which NIST notes was formerly called an interim authority to test. Whether that fits your situation is the authorizing official's decision.
Who signs an ATO?
The authorizing official, a senior federal official designated by the agency. A-130 says only federal government personnel may serve in that role, and NIST says the explicit acceptance of risk cannot be delegated to the designated representative. If the authorizing official changes after an authorization, A-130 has the new official sign a new decision document, set new terms and conditions without extending the termination date, or start a reauthorization.
Does continuous ATO mean no ATO package?
No. Continuous ATO (cATO) is the Department of Defense's term; A-130 calls the civilian equivalent ongoing authorization. Either way the system still needs an initial authorization. Under A-130, moving to ongoing authorization requires that initial ATO plus continuous monitoring programs covering all implemented controls, and the authorizing official's formal approval. The package is then kept current instead of rebuilt for each reauthorization.
Sources
- NIST, SP 800-37 Rev. 2, Risk Management Framework for Information Systems and Organizations (December 2018)
- OMB, Circular A-130, Managing Information as a Strategic Resource (July 2016), Appendix I
- CMS, Planning for ATO at CMS
- DoD CIO, Continuous Authorization to Operate (cATO) memo (February 2022)
- FedScoop, 18F slices ATO times from 6 months to 30 days (August 13, 2018)
How we researched this. Every number, date and requirement here is checked against the sources listed above, primary documents first, and the post is fact-checked again before publication. When a rule, date or status changes, we update the post and log the change below. Read our editorial standards or send a correction.





