United States (federal) · other
ATO: what it requires, and the records to keep
An ATO is the official decision by a senior federal official to authorize operation of an information system and explicitly accept its risk, made after security and privacy controls are assessed under the NIST RMF. Any AI system or AI service an agency runs or connects to its data needs to sit inside an authorized boundary, which makes the ATO the gate for federal AI deployments.
01 / What it requires
What ATO requires
Federal agencies, which must authorize each information system before use; vendors and contractors whose systems process agency data go through the agency's process.
- 01Designate senior officials (authorizing officials) to formally authorize systems and common controls.
- 02Complete an initial authorization for each system, based on explicit risk acceptance, before it becomes operational.
- 03Categorize the system, select and implement NIST SP 800-53 controls, and assess them before authorization.
- 04Continuously monitor controls and move to ongoing authorization when eligible.
- 05Reauthorize systems on a time-driven or event-driven basis as risk changes.
02 / AI work
Where it touches AI work
Applies to AI systems as to any system: an AI model, AI-enabled application or AI cloud service used by an agency needs an authorization decision covering its data flows, and changes such as new models or data sources can trigger reassessment.
03 / Dates
The dates that matter
Revised OMB Circular A-130 sets agency authorization duties
NIST SP 800-37 Rev. 2 published, adding a Prepare step
FedRAMP Authorization Act enacted; FedRAMP packages presumed adequate for agency ATOs
NIST SP 800-53 Release 5.2.0 issued
04 / Enforcement
Who enforces it
OMB oversight, inspector general audits and annual FISMA reporting to Congress; no civil penalties. Systems without an ATO should not operate.
05 / Records
Records an organisation keeps
What an auditor or an inquiry usually asks to see. Your obligations depend on your role and your facts.
- 01Signed authorization decision document
- 02System security and privacy plans
- 03Security assessment report
- 04Plan of action and milestones and continuous monitoring reports
Optional evidence · where Planisphere fits
Keep a record anyone can check
When your team meets a duty, Planisphere can seal the event it reports as a receipt.
A disclosure shown, a review signed, a model change approved: the event your system reports.
The event becomes a sealed receipt, dated and attributed to whoever is signed in.
Paste the receipt into Verify. No account or key.
A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.
QUESTIONS
The questions that come next
How do I get an ATO for a generative AI capability under the AI RCC pilots?+
A generative AI capability piloted through DoD's AI Rapid Capabilities Cell still needs an authorization decision under DoD's Risk Management Framework; no separate ATO standard for those pilots could be confirmed. The authorizing official needs a defined system boundary covering the model and its hosting (for commercial cloud, a DISA Provisional Authorization at the right Impact Level), assessed SP 800-53 controls, a plan of action and milestones, and a continuous monitoring plan. For generative AI, add test results on model behaviour and a plan to re-test when the model, prompts or data sources change. Read the full answer
SOURCES
Go back to the source
Office of Management and Budget
Legal Information Institute (Cornell)
CHANGE LOG
What changed, and when
Rebuilt from primary sources; facts checked on this date.
Related: ATO vs CMMC · ATO vs DoW IL2 / IL4 · ATO vs NIST SP 800-53 Rev. 5 · ATO for defense AI workflows · NIST AI RMF · OMB M-25-21/22 · DoW RAI S&IP · EO 14179 · FIPS 140-3 · SHA-256 / FIPS 180-4