Deep Dive · Federal AI Authorization

The Evidence Map for the Federal AI Authorization Boundary

The action layer behind the core verdict: how to plan a federal AI service around authorization without overstating the evidence.

Source Storm Research Verification 9 citation clusters checked Prepared for Leader discussion

How to use this

Use this as the authorization-route map for federal AI conversations. It helps a sponsor fund uses that can reuse existing evidence now while refusing production dates that treat authorization as a review after the pilot.

First moves before hiring anyone

Classify the data and mission use before choosing the service.

Record the FIPS 199 category, the DoD impact level where relevant, data flows, identity path, and prohibited data. This decides whether a usable AI service is usable for this workload.

Pick the authorization route out loud: reuse, temporary pilot, or net-new.

Do not call all three a pilot. State the evidence already reusable, the agency work left, the temporary-use expiration rule, and who pays for the gaps.

Make the authorization boundary a product artifact.

Keep the architecture, data flows, inherited-control matrix, secure configuration, model-update process, logging, incident path, and evidence owner in one maintained packet.

Budget the agency side, not just the provider package.

Assign owners for configuration, agency-responsible controls, contract language, package review, logs, vulnerability management, and continuous-monitoring review.

Treat model, data, and integration changes as monitored operational changes.

Machine-readable, continuously produced evidence is the design direction. It cuts friction only if the delivery process produces it as the service ships.

Owner, briefing, proof

Owner

Named authorizing official plus owners for agency-responsible controls, configuration, and continuous-monitoring review.

Briefing

Authorization-route decision brief: reuse, temporary pilot, or net-new, with the FIPS 199 category or DoD impact level named.

Proof

An evidence packet a risk owner can accept: boundary, data flows, controls, configuration, model updates, logs, and incident path.

Where to start

Start with one AI use, one data classification, and one authorization route. If the route is unclear, map the intended use against existing packages and impact levels first, and build the evidence packet inside delivery, not as a review after the demo works.

Claim ledger

Checked

citation clusters traced to primary or strongest reachable sources

Fabricated

invented or unsupported source clusters found in the public claim set

Corrected

wording narrowed after source review

Demoted

useful signals kept out of the headline

ConfirmedNIST SP 800-37 Rev. 2: The Risk Management Framework runs authorization and continuous monitoring as one system life cycle.nist.gov

ConfirmedOMB M-24-15: Presumption of adequacy at or below the FIPS 199 level; agency FISMA responsibility preserved.whitehouse.gov

CorrectedFedRAMP Rev. 5 agency authorization: A fully built service is readiness guidance, not an absolute eligibility gate.fedramp.gov

ConfirmedDoD Instruction 8520.03: Cloud services and authentication must match impact levels IL2 through IL6.esd.whs.mil

ConfirmedGAO-23-105482: Agency-side control allocation, package review, and monitoring duties persist after authorization.gao.gov

CorrectedGAO-24-106591: Provider estimates of $300,000 to $3.7 million use inconsistent methods; not a typical FedRAMP price.gao.gov

ConfirmedGAO-26-107530: 11 of 15 reporting agencies cited products delayed or unprocurable over authorization barriers.gao.gov

DemotedFedRAMP 20x program update: The under-five-week figure measures agency review, not end-to-end deployment.fedramp.gov

DemotedFedRAMP 20x roadmap: Phase 1 Low pilots confirmed; future dates are estimates and 80% automation is a goal.fedramp.gov

Where the evidence stops

"FedRAMP authorization means the agency can deploy the service" is not supported; the agency's own risk decision and monitoring duties remain.
"FedRAMP takes X months" has no public end-to-end evidence base; plan from the specific service, data class, impact level, and route.
"Authorization is already mostly automated" overstates FedRAMP 20x; 80% automation is a goal and the higher-impact path remains prospective.

What would change our mind

FedRAMP publishes audited elapsed-time, cost, rework, or reuse data by impact level for 20x or agency authorizations.
Final Consolidated Rules or a revised 20x schedule materially changes the Low, Moderate, or High certification paths.
Agency GRC tools produce and ingest machine-readable OSCAL authorization and monitoring artifacts in routine use.
Temporary AI pilot authorizations disclose whether they convert to full authorization or terminate at the 12-month limit.
A published oversight report shows reuse materially reducing, or failing to reduce, agency authorization effort and deployment delay.

Deep Dive staged from verified Storm Research · nothing here asserts above the registry calibration