An Authority to Operate (ATO) is a formal decision by a senior US government official to accept the security risk of running a system and permit it to operate. It is granted through the NIST Risk Management Framework after the system’s controls are assessed, and maintained through continuous monitoring. A FedRAMP authorisation is an ATO for a cloud service, standardised so many agencies can reuse it.
The ATO is the moment a US federal system is allowed to run. Everything in the US risk management process, categorisation, controls, assessment, builds toward that single risk-acceptance decision.
What is an ATO and how is it granted?
An Authority to Operate is a formal decision by a senior official, the authorising official, to accept the security risk of operating an information system and to permit it to run. It is not a technical pass or fail; it is a risk-acceptance decision made by an accountable person on behalf of the government. Without an ATO, a federal system generally cannot go live.
An ATO is granted through the NIST Risk Management Framework, or RMF. The system is categorised by its impact level, appropriate controls from NIST SP 800-53 are selected and implemented, and those controls are independently assessed. The assessment results are packaged into an authorisation package for the authorising official, who weighs the residual risk, the risk that remains after the controls, and makes a risk-based decision to grant, grant with conditions, or withhold the ATO. Importantly, an ATO is not permanent: it reflects the risk accepted at a point in time and is maintained through continuous monitoring, and significant change or a lapse in monitoring can trigger reauthorisation. This is the same categorise, assess, authorise and monitor discipline that underpins FISMA.
ATOs and FedRAMP
For cloud services, the ATO is produced through FedRAMP. A cloud provider is assessed against the NIST SP 800-53 controls by an accredited third-party assessor, and an agency or the FedRAMP Board issues an authorisation. The defining feature of FedRAMP is reuse: one rigorous authorisation can be reused by many agencies, rather than each agency authorising the same cloud service from scratch. So a FedRAMP authorisation is, in effect, an ATO for a cloud service, standardised for reuse across government.
For Australian readers, the ATO concept parallels the authorisation decision an authorising officer makes after an IRAP assessment against the ISM, a security assessment informs an accountable risk-acceptance decision. The mechanics and frameworks differ, but the underlying idea, an official formally accepting residual risk before a system operates, is shared. For an organisation working across US and Australian authorisation regimes, Cybernion can help make sense of how they relate through advisory.
Frequently asked questions
What is an Authority to Operate?
An Authority to Operate, or ATO, is a formal decision by a senior US government official, the authorising official, to accept the security risk of operating an information system and to permit it to run. It is granted after the system’s security controls have been assessed, and it represents the government formally accepting the residual risk. Without an ATO, a federal system generally cannot go into operation.
How is an ATO granted?
An ATO is granted through the NIST Risk Management Framework. The system is categorised by impact, appropriate NIST SP 800-53 controls are selected and implemented, the controls are independently assessed, and the results are packaged for the authorising official, who weighs the residual risk and makes a risk-based decision to grant or withhold the ATO. After authorisation the system is continuously monitored to keep it valid.
How does an ATO relate to FedRAMP?
FedRAMP produces ATOs for cloud services used by the US government. A cloud provider goes through the FedRAMP process, assessment against NIST SP 800-53 by an accredited assessor, and an agency or the FedRAMP Board issues an authorisation that agencies can reuse. So a FedRAMP authorisation is an ATO for a cloud service, standardised so one authorisation can serve many agencies rather than each doing its own.
Is an ATO permanent?
No. An ATO reflects the risk accepted at a point in time and is maintained through continuous monitoring rather than being permanent. It can be time-bound and must be kept current as the system, its controls and the threat environment change; significant changes or lapses in monitoring can require reauthorisation. So an ATO is an ongoing state to maintain, not a one-time certificate.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Risk Management Framework, NIST Computer Security Resource Center, 2026
- FedRAMP, US General Services Administration, 2026
Last updated: 30 August, 2026
