The Three Speeds
Updated
BeginnerWhat you'll learn
~15 min- Distinguish the three authorization speeds and what each actually requires
- Explain 'ATO in a day' as an inheritance claim, not a process miracle
- Use assessor-capacity arithmetic to predict which way any authorization policy will move
Same framework, three gears
Lesson 1.1 gave you the honest range: six months to three years for a traditional authorization, weeks for delivery onto the right platform, and a stated industry direction where the question answers itself continuously. Those aren’t three frameworks - they’re three gears of the same RMF. The first two vary one axis (how much of the package was already authorized before you arrived); the third varies another (how often the acceptance itself happens). Programs mix them - the gears are a planning shorthand, not a taxonomy - and the shorthand’s structure has one variable: how much answering is left for you to do.
GEAR 1: TRADITIONAL you answer for EVERYTHING - every control, (6mo - 3yr) every statement, a full assessment, a full package to one AO. Most of the time is waiting for assessment and review, not engineering.
GEAR 2: INHERITANCE a PLATFORM answered for most controls (days - weeks) already; you answer for your delta. The package shrinks; the assessment shrinks; the SCOPE of the AO decision shrinks (the responsibility does not). Module 4 tours the platforms.
GEAR 3: CONTINUOUS the package updates itself from pipeline (aspiration w/ evidence and the authorization is an real exemplars) ongoing state, not an event. Module 6 takes this seriously - including how far it actually is from most shops' reality.“ATO in a day” decoded
You will hear the phrase constantly, usually from a vendor deck — and commercial readers already know the mechanism under its cloud name, the shared-responsibility model: the provider answers for the layers it runs, you answer for what you build on top — with one federal difference: a provider’s controls count as inherited only once they have been assessed and authorized, so the model is the same shape but the paperwork is not optional. Here is the decode, and it never fails: “ATO in a day” means inheritance in a day. The day-long part is authorizing your delta on a platform whose own authorization took someone else years. The exemplar claims worth knowing, because they show the model working at both scales: cloud-platform programs report workload authorization in minutes on a certified pipeline, and weeks to stand up a compliant landing zone, against the year-plus baseline the same programs quote for doing it from scratch (these are a DoD platform program’s own public claims, not an audited benchmark; treat them as illustrative of the ratio, not as quotas). Reusable-authorization schemes (Certificates to Field — a DoD construct that lets a once-approved component carry its approval to other environments on the same platform — and similar constructs elsewhere) are the same move formalized: authorize the pipeline and platform once, then let conforming workloads inherit.
Nothing about the risk disappeared — it moved into the platform’s package, where it’s answered once instead of hundreds of times. That’s the whole trick — and for leadership it is the entire business case: every control the platform already answers for is assessor time you do not wait on and statements you do not write, which is why a delta-only delivery ships in weeks against a from-scratch package’s year or more. Lesson 4.3 examines what the platforms actually demand of your software in exchange.
The arithmetic that explains federal policy
Why does the slow gear exist at all? Here’s the number that reframes it: the FedRAMP program — the authorization machinery for the entire federal cloud marketplace — operates with on the order of fifty recognized assessment organizations listed to serve it (the count and its source sit in Lesson 4.1’s status callout). Set that against hundreds of cloud services seeking authorization and every agency needing its packages reviewed, and you get the load-bearing fact of this entire domain:
Assessor throughput is the binding constraint. Every major authorization reform of the last five years — inheritance platforms, reusable certificates, machine-readable packages, risk-based tailoring — is, at bottom, an attempt to spend scarce assessor-hours on deltas instead of repetition.
This gives you a predictive tool, not just an explanation. When you read any new authorization policy, ask: does this reduce assessor-hours per authorized system? If yes, expect it to advance. If it adds review burden — however virtuous — expect it to stall. Module 4’s landscape (a certification program suspended over its compliance cost and burden, an entire rewrite built around assessment-scope minimization) will keep proving the rule. And it’s why Module 6’s rollout lesson plans your program around assessor capacity as a first-class constraint, the way you’d plan around any scarce dependency.
Prompt first: gear selection
Switch your workspace agent to Plan mode with your architecture and target agency notes, and ask it to plan a gear-selection brief (if you do not have live exports or files handy, ask it to generate a small Meridian practice sample from the lesson’s scenario first):
We are delivering our grid-analytics software into a federal energy-coordination system. Plan a gear-selection brief comparing traditional ATO against inheritance platforms, estimate our control delta, and ask about any unknown constraints.Check that the plan or draft covers:
- Candidate inheritance platforms available in your context (agency platform offerings, DoD software factories, and authorized cloud landing zones) and what each answers for
- Your remaining control delta on each platform (application-layer, data handling, and delivery pipeline) expressed as a fraction of a Moderate baseline
- Which gear to recommend and which platform intake requirements you must build before approaching them
- An honest timeline range for leadership that explicitly includes the assessor-capacity caveat rather than a single-day promise
If the draft quotes a single point date instead of a range, follow up with: Replace the point timeline with a calendar range and attach the assessor-throughput constraint.
The third requirement is your defense against the meeting where someone quotes a vendor’s “day one authorization” line as a schedule commitment.
Traditional / inheritance / continuous; delta; assessor throughput as the binding constraint; certification distinct from risk acceptance (Lesson 1.1); cite-the-release (Lesson 1.2). That’s the whole map. Every remaining lesson is one region of it in working detail: Modules 2-3 build the package as data, Module 4 walks the delivery paths, Module 5 crosses the boundary, Module 6 closes the loop toward continuous.
A program office announces a new policy: every software delivery must add a second independent assessment before authorization, to raise assurance. Applying this lesson's predictive tool, what is the most likely real-world outcome?
Practice status — among mature regulated delivery programs, commercial and federal
(a few rows carry a more specific status - principle, canon, suspended - where one of the five would mislead)
| Practice | Status | Also called |
|---|---|---|
| inheritance / shared responsibility | common baseline federal delta: provider controls must be assessed and authorized | — |
| reusable authorizations (CtF - Certificate to Field; RAISE - the Navy’s pipeline-reciprocity construct) | federal (RMF-wide reciprocity; both examples are DoD-family) | reciprocity constructs |
| continuous authorization | emerging the direction (Module 6); point-in-time is the norm | — |
| assessor-capacity arithmetic | this training’s heuristic a planning tool, not a published metric | — |
Scale: required | common baseline | strong optional | reference-shop (seen only at organizations that publish their own practice) | emerging
Key takeaway
Three gears, one framework: traditional (you answer for everything), inheritance (a platform answered first; you answer for the delta), continuous (the answering never stops — Module 6’s honest subject). “ATO in a day” is always an inheritance claim. And behind every policy in this domain sits one number — assessor throughput — that predicts which reforms advance and which stall. You now hold the map; next module, we turn controls into data.
- LEADERSHIP DECISION
- pick the gear deliberately and fund toward the platform's intake requirements - never accept 'ATO in a day' as a schedule
- PRACTITIONER ACTION
- produce the gear-selection brief: candidate platforms, the delta you would still own, a timeline RANGE with the assessor-capacity caveat
- SUCCESS MEASURE
- authorization timeline committed as a calendar range with the delta enumerated; zero schedule commitments built on an 'ATO in a day' claim