A Capital Cyber practiceLeesburg, Virginia

Federal authorization

RMF and ATO for Federal Systems Explained

By Cybersecurity Consulting · Published · Updated

If you build or run a system for a federal customer, your team will likely carry much of the RMF and ATO work. Here is how it works and who decides.

Cybersecurity Consulting, a Capital Cyber practice in Leesburg, Virginia, provides CISO level leadership for CMMC, NIST SP 800-171 and federal authorization, with a program for ITAR technical data.

What do RMF and ATO mean?

The Risk Management Framework (RMF) is how federal agencies decide if a system is safe enough to run. The Authority to Operate (ATO) is the formal yes at the end.

NIST SP 800-37 Rev 2 sets out the process. The controls come from NIST SP 800-53. National security systems add CNSS Instruction 1253.

There are seven steps: Prepare, Categorize, Select, Implement, Assess, Authorize and Monitor. Each step feeds the next.

The framework is based on risk, not a checklist. Its goal is to give one accountable official enough facts to decide if the risk left over is fine for the mission.

Controls are the means. The decision is the end.

Who signs the ATO, and what does it mean?

A senior official, the authorizing official, signs it. The ATO says the risk of running the system is acceptable.

It is a risk acceptance, not a promise that the system is secure. It can carry conditions, and the official can revoke it if the risk changes.

The person who signs is accountable, so the evidence behind it matters.

How is a system sorted by impact?

Each system is rated by the harm a loss would cause. Confidentiality, integrity and availability each get a rating of low, moderate or high.

Most federal systems use FIPS 199, with the information types in NIST SP 800-60. The overall rating sets the starting set of controls.

National security systems follow CNSS Instruction 1253 for this step and for picking controls. It keeps the three ratings separate instead of merging them into one level. It also adds overlays for certain kinds of systems and data.

Get this right early, or you pick too many controls or too few.

Which controls apply?

Controls come from the NIST SP 800-53 catalog. NIST SP 800-53B defines the low, moderate and high baselines. You start from the one that fits your rating.

Then the baseline is tailored. Some controls are scoped out, with a written reason. Values are set, overlays are added and any stand-in controls are documented.

The system security plan records each control, how it is met and who owns it. Controls you get from an approved hosting platform, or a common control provider, are marked as inherited. That can cut the work a lot.

Who does what?

The authorizing official makes the risk call.

The system owner owns the system and the package.

Control assessors check that controls are in place and work as intended.

The security officer and engineers build the controls and keep the papers current.

Contractors often fill several roles below the official. A systems integrator may build the system, write the plan, put in the controls and prepare the package. A separate assessor then checks it.

Keep the roles apart, since an assessor who built the controls cannot give an independent view.

What goes into the package?

The package usually holds the system security plan and the security assessment report. It holds the plan of action and milestones. It adds a privacy plan where personal data is involved.

Supporting items include the impact rating, diagrams, inventories and policies. The official reads it to see the system, the leftover risk and the plan to reduce it.

Strong packages use specifics, not adjectives. Each control names the tool and the proof, and each finding has an owner and a date.

The risk summary says plainly what is not yet in place, and why that is or is not acceptable.

How long does it take, and what happens after?

It depends on size, rating, control maturity and how much is inherited. Any number given before the system is understood is a guess.

Three things slow it most: rating the system late, writing the papers after the build, and findings that force rework. The fastest path is to build RMF into the project. Rate early, pick controls during design, write as you build and collect evidence all along.

After the signature, the Monitor step begins and never really ends. Your team assesses controls, tracks changes, updates the action plan and reports.

Many agencies now use ongoing authorization. Live monitoring keeps the ATO standing, instead of a full redo on a fixed cycle. That only works if people review the data and act on it.

How does RMF and ATO work relate to CMMC?

They protect different systems. RMF covers federal systems and systems run for an agency. CMMC and NIST SP 800-171 cover contractor systems that hold CUI.

The NIST SP 800-171 rules come from the NIST SP 800-53 moderate baseline, so they share terms.

Some firms need both: a system run for an agency under an ATO, plus CUI on their own systems under DFARS 7012. Run each program on its own terms.

Next step: book a 30 minute call with Cybersecurity Consulting, a Capital Cyber practice, to map where your system stands in the seven steps.

Engagements

Which engagements cover this?

Questions

What else do readers ask?

What does RMF and ATO work mean for my company as a contractor?

It often means your team does much of the work. You may build the system, write the plan, put in the controls and prepare the package. The authorizing official still makes the final risk decision.

What are the seven steps of the RMF?

Prepare, Categorize, Select, Implement, Assess, Authorize and Monitor. NIST SP 800-37 Rev 2 defines them.

Does an ATO expire?

A traditional ATO has a term set by the authorizing official. Under ongoing authorization, live monitoring keeps it standing instead. Either kind can be revoked if the risk changes.

When does CNSSI 1253 apply instead of the standard baselines?

It applies to national security systems. Other federal systems use FIPS 199 and the NIST SP 800-53B baselines.

This article is general information about the regulations as written, not legal advice. Read your contract clauses and the regulation text, and take legal advice where the answer matters.

Book a call

Ready to talk it through?

Pick a time for a 30 minute call with the practice.