
Policy as Code in Support of cATO
If you have spent any time developing or deploying software at a government agency, you have heard about Authority to Operate (ATO). Traditionally, an ATO was/is a point-in-time authorization. Systems would be subject to ‘rigorous’ testing & review, and once deemed secure by some group of humans by looking at written documentation and maybe some code reviews, were granted an ATO for a defined period. In the case of the traditional Risk Management Framework (RMF), that ATO is for three years. The challenge is…