RMF and the Authority to Operate

Prerequisites: distinguish generated output from source evidence; review the AI workflow reference. Public self-study is not official agency training, accreditation or a credential.

What you will be able to do

This lesson develops the ability to contribute accurate system evidence to an RMF decision process. The setting is ORION Service Navigator, a fictional public-benefits information service using public guidance and wholly synthetic constituent questions; it never determines eligibility or takes an action on a person. Every person, organization, system record, metric, and outcome in the case is fictional. Do not replace the case with operational, classified, CUI, export-controlled, proprietary, employer-confidential, or third-party personal information.

By the end of the lesson, you will be able to:

• Demonstrate how to contribute accurate system evidence to an RMF decision process.
• Apply that model to the synthetic ORION Service Navigator environment.
• Produce a reviewable artifact that separates evidence, assumption, uncertainty, and authority.
• Recognize the critical failure and select a safe remediation path.

The performance standard is not confident language. It is a traceable decision, an artifact another qualified reviewer can inspect, a clear boundary around the learner’s authority, and a safe response to uncertainty. Knowledge checks are formative and do not award a certification or endorsement.

This curriculum runs self-study on VetsLearn. Where the text calls for an instructor, peer or formal review, use the stated acceptance criteria for self-review. Reflection questions support reflection; they do not replace independent assessment. A peer review is optional unless your actual organization requires it.

Part 1 RMF implementation and assessment

NIST RMF sequences Prepare, Categorize, Select, Implement, Assess, Authorize and Monitor. Preparation establishes context; categorization examines consequences; selection tailors controls; implementation documents what exists; assessment tests effectiveness; authorization is the responsible senior official’s risk decision; monitoring updates evidence. A course cannot issue an ATO. Control narratives identify component, role, identity/object rules, retained evidence and exceptions. AI behavior questions do not replace conventional access, logging, recovery and change controls.

Write and test one control narrative

Synthetic implementation: “ORION policy revision P2 binds user group R-A to collection A. The application uses the authenticated identity to filter retrieval before snippets enter the model. The data owner maintains the mapping; engineering deploys it; the test lead records results.” This states an enforcement mechanism rather than a slogan.

Test packet: fixture A-01 belongs to A; B-01 belongs to B. Reader-A requests A-01 and should receive it. Reader-A requests B-01 and should receive no snippet and a denial. A direct identifier lookup and a paraphrased semantic query must both fail to reveal B-01. Logs should record a denial without copying protected contents.

Observed fictional result: direct lookup is denied, but semantic retrieval returns B-01. Mark the control ineffective for that path, retain the query/configuration/output and route the gap. Fixing the direct lookup alone is insufficient; repeat both tests after repair.

Starter package definitions: an implementation narrative explains what exists; an assessment result reports what was observed; an open-risk record describes unresolved consequence, owner and action. These artifacts support the authorizing official; none is itself an authorization.

Part 2 Synthetic worked example

ORION claims secure access because hosting is assessed. Its retrieval index returns the same documents to every user. Reader-A requests a document reserved for Reader-B and receives it. This is an application authorization finding. Provider evidence and a prompt saying “be careful” do not resolve enforcement.

Guided practice: identify the unsupported conclusion, name missing evidence and rewrite with its scope intact. Change one assumption and identify which decision reopens.

Part 3 Feedback and repair

Pass when enforcement is tested, planned controls are not called implemented and authorization is routed to the legitimate official. A checklist without results does not pass.

Keep failed evidence beside the repair. Explain the criterion, correct the artifact and test a different invented case.

Next step: carry your versioned artifact and failures into the next federal lesson; the capstone returns to these records. Check live policy and authorization with current official sources and responsible owners.

Source: NIST RMF overview, consulted 2026-10-02.