Groundwork CloudRegulated Cloud ServicesStart a conversation ↗
THE METHOD IN DETAIL

The road is already researched.
Here is what it says, sector by sector.

Every eight-week engagement reads the organization against the same researched road. This page shows that road: how a reading works, and for each sector the gates in its own words, the cloud bar, how long authorization usually takes, and the sources, with the date they were read.

HOW A READING WORKS

One ladder, read from evidence.

51 positions in 12 service areas, each read on one ladder from 0 to 4, from evidence the organization already holds: 35 requests, existing material only. The engine proposes a level from the evidence; a consultant confirms or overrides it with a note; nothing is scored by a model.

LevelNameWhat it means
0ReactiveNothing defined; whatever happens, happens.
1InconsistentSomething exists or is done sometimes; no owner, no record that holds.
2DefinedA named owner attests that a written practice operates, tied to a tracked item. An attestation is evidence at this level only; commentary is recorded as feedback, never as evidence.
3ConsistentThe practice is performed at its own stated interval, through the service-management framework, and consecutive records show it with follow-through.
4AutomatedThe toolchain produces the evidence as often as the environment changes, humans in the loop, read on the PMO's cadence-driven executive dashboard. The target for a position depends on the change rate of the workloads it serves.

Where a position stands below its target, the road names the work: 53 workstreams placed on a road of the organization's chosen length, and 64 jumpstart packages that start that work.

RoadForHorizons (months from kickoff)
18 monthsa small estate, well funded, moving fast0–3 · 3–8 · 8–13 · 13–18
24 monthsa lighter estate with the means to move0–4 · 4–10 · 10–18 · 18–24
36 monthsa measured road0–6 · 6–15 · 15–27 · 27–36
48 monthsthe standard road0–6 · 6–18 · 18–36 · 36–48

An authorization lead time is a floor the road does not compress: if a sector's authorization usually takes longer than the road allows, the gate is held at that lead time and the page says so.

THE ROAD BY SECTOR

Same method. Each sector's own terms.

The five gates on the road are the same everywhere; what they are called, who decides, and how long they take are not. Each reading below is dated; requirements change, and the engagement reads the current text.

Federal civilian · State, local and education · Defense industrial base · Pharmaceutical · Legal and e-discovery · Electric and water utilities

FEDERAL CIVILIAN

Federal civilian

The cloud bar

FedRAMP Moderate for most agency systems; FedRAMP High where the system's FIPS 199 categorization is High.

The five gates, in this sector's words

  1. 1
    System categorized and bounded

    The federal information system is categorized under FIPS 199 and its authorization boundary drawn; for a cloud service, the offering inside its FedRAMP boundary and the agency's own components around it.

    Decidesthe system owner with the senior agency information security officer; the authorizing official approves the categorization
  2. 2
    Assessment under way

    The security assessment is scheduled against the package, or an interim authorization to test is granted where the agency uses one; for a cloud offering, its FedRAMP certification is in hand or in process.

    Decidesthe agency authorizing official, on the assessor's plan
  3. 3
    FedRAMP certification in hand

    The cloud offering holds a FedRAMP certification the agency can reuse, Rev. 5 agency path or 20x Class A, B or C, and the agency's remaining responsibilities are written into its own package.

    Decidesthe FedRAMP program certifies the offering; the agency decides its own use
  4. 4
    Authorization to operate

    The agency authorizing official grants the authorization decision on the package: system security plan, privacy plan, assessment report and plan of action and milestones, under A-130 and SP 800-37.

    Decidesthe agency authorizing official, with the CIO and the senior agency information security officer advising
  5. 5
    Ongoing authorization

    Continuous monitoring feeds an ongoing authorization; the plan of action is kept current; for the offering, FedRAMP's continuous reporting stands in for a re-authorization cycle.

    Decidesthe agency authorizing official on the continuous monitoring results

How long authorization usually takes

Federal civilian agency system authorization under the RMF (FISMA; NIST SP 800-37 Rev 2; agency A&A guides)every system operated by or for a civilian agency before it processes live data; the agency AO grants the authorization decision; agency guides (GSA, DHS, CMS) set the local process and validity period
6 months typical · 1 to 18
FedRAMP Rev5 agency (legacy) certification: agency authorization decision plus FedRAMP reviewa cloud service offering that a civilian agency sponsors; a 3PAO assesses, the sponsoring agency issues its authorization decision, then FedRAMP reviews and lists it; new Rev5 applications stop June 11, 2027 and Rev5 authorizations end December 31, 2028 under the Consolidated Rules for 2026
12 months typical · 8 to 15
FedRAMP 20x program certification (Class A, B, C) under the Consolidated Rules for 2026a cloud service offering seeking FedRAMP certification directly from FedRAMP without an agency sponsor; Class A (entry, from a SOC 2 Type II or a readiness report) opened August 3, 2026, Class B (formerly Low) and Class C (formerly Moderate) opened August 31, 2026, Class D (High) is planned for a 2027 pilot; mandatory adoption of the rules January 1, 2027
3 months typical · 1 to 6
09 months18 months

Jumpstart packages here

62 apply in full 2 in part · of 64

Sources, read 2026-10-13 · links checked 2026-10-15
STATE, LOCAL AND EDUCATION

State, local and education

The cloud bar

The state program's Moderate baseline (GovRAMP or TX-RAMP) at the floor, with FedRAMP packages reused through Fast Track; the data class sets anything stricter.

The five gates, in this sector's words

  1. 1
    Data classes and systems in scope

    Systems and data stores are tagged by data class rather than by one impact level: criminal justice information, federal tax information, health, education records; each class brings its rule and its reviewer.

    Decidesthe agency authorizing official; the CJIS Systems Agency for criminal justice information; the IRS Office of Safeguards for federal tax information
  2. 2
    Provider status identified

    For a cloud offering, the state program status required is identified and the provider's package requested: GovRAMP Ready, Core or Authorized, Fast Track from a FedRAMP package, or TX-RAMP certification.

    Decidesthe agency, under the state's program rules
  3. 3
    Provider authorized under the state program

    The offering holds GovRAMP Authorized or Provisionally Authorized status, or a TX-RAMP certification, and the agency's own responsibilities are listed against the provider's.

    Decidesthe sponsoring government authorizing official or the program's approvals committee; Texas DIR for TX-RAMP
  4. 4
    Agency authorization and data-class approvals

    The agency authorizing official accepts the system; for federal tax information the Safeguard Security Report stands with the IRS Office of Safeguards; for criminal justice information the CJIS agreements are signed; for an eligibility system, the CMS authority to connect.

    Decidesthe agency authorizing official; the IRS Office of Safeguards; the CJIS Systems Agency; CMS for the Hub
  5. 5
    Audits on their cycles

    The CJIS Systems Agency's triennial audit, the IRS safeguard review, the state's IT security audits and the provider's annual program renewal keep the standing current.

    Decidesthe auditors named; the agency responds

How long authorization usually takes

GovRAMP Authorized or Provisionally Authorized (sponsoring government AO or GovRAMP Approvals Committee)cloud providers selling to state, local, tribal, territorial governments and public higher education that accept GovRAMP (formerly StateRAMP; renamed 2025); Moderate is the common impact level
12 months typical · 6 to 18
GovRAMP Ready Verification (3PAO Readiness Assessment Report or Security Assessment Report, PMO-validated)providers that need a verified status without a sponsor, or as the step before Authorized; many participating governments accept Ready for procurement
6 months typical · 4 to 12
GovRAMP Core Verification (provider evidence validated by the PMO, no 3PAO)providers building toward Ready or Authorized, or whose government customers accept Core; closest to self-attestation because the evidence is the provider's own, checked by the program office rather than an independent assessor
5 months typical · 4 to 9
GovRAMP Fast Track from an existing FedRAMP package (reuse of the federal SAR/RAR and 90-day ConMon)providers holding a FedRAMP authorization or a federal 3PAO package who want GovRAMP Authorized without a second assessment
3 months typical · 1 to 6
TX-RAMP Level 1 or Level 2 certification by Texas DIR (DIR assessment or Fast Track on SOC 2 Type 2, ISO 27001 and similar reports)cloud services (IaaS, PaaS, SaaS) that process confidential or regulated data of Texas state agencies and public higher education under Texas Government Code 2054.0593; DIR itself assesses, no 3PAO and no fee
3 months typical · 1 to 18
TX-RAMP Provisional Certification (18-month bridge, or open-ended while enrolled in the GovRAMP Progressing Snapshot)providers in active Texas procurements that are not yet Level 1 or Level 2 certified
1 months typical · 1 to 2
FBI CJIS Security Policy conformance (no certification; contractor signs the CJIS Security Addendum; the CJIS Systems Agency audits at least triennially)any provider or contractor that stores, processes or transmits criminal justice information for a criminal justice or noncriminal justice agency
0 months typical · 0 to 0
State agency system authorization (a state CIO or agency executive accepts the risk; e.g., Washington SEC-02 with WaTech Security Design Review, California Cloud Smart documentation to CDT)a state agency adopting a cloud service, where the agency's own authorization process, not a vendor status, is the gate; the vendor supplies evidence (GovRAMP status, SOC 2, ISO 27001) into it
3 months typical · 1 to 12
09 months18 months

Jumpstart packages here

43 apply in full 21 in part · of 64

Sources, read 2026-10-13 · links checked 2026-10-15
DEFENSE INDUSTRIAL BASE

Defense industrial base

The cloud bar

The contract's requirement sets the CMMC level and the FedRAMP classification for any cloud offering that holds covered defense information (DFARS 252.204-7012): Moderate, or High where export-controlled technical data, specified CUI categories or the prime's flow-down require it.

The five gates, in this sector's words

  1. 1
    Assessment scope defined

    The CMMC Assessment Scope is drawn: CUI assets, security protection assets, contractor risk-managed assets, specialized assets, out-of-scope assets, with the enclave boundary and the cloud offerings that hold CUI named.

    Decidesthe contractor's security lead, owned by the Affirming Official
  2. 2
    Self-assessment posted

    A NIST SP 800-171 self-assessment against the scope is complete and the score is posted in SPRS with its plan of action; this is the contractor's own reading before any assessor.

    Decidesthe Affirming Official affirms; SPRS records
  3. 3
    Assessment scheduled or conditional status

    For Level 2, a C3PAO assessment is scheduled with the evidence ready, or a conditional status is held with the 180-day plan-of-action closeout running; for Level 1, the annual self-assessment stands in its place. Every cloud offering in scope is at FedRAMP Moderate or High with its customer responsibility matrix in the package.

    Decidesthe C3PAO (Level 2), DIBCAC (Level 3) or the contractor itself (Level 1 and Level 2 self)
  4. 4
    CMMC status held and affirmed

    The final (or conditional) CMMC status at the contract's level is recorded in SPRS and the Affirming Official's affirmation is current; the contracting officer checks it before award.

    Decidesthe Affirming Official; the contracting officer verifies
  5. 5
    Annual affirmation and reassessment rhythm

    The affirmation is renewed every year, the three-year reassessment is on the calendar, and a change that alters the scope triggers a new look; cloud offerings holding CUI stay at FedRAMP Moderate, or FedRAMP High where the data or the prime requires it.

    Decidesthe Affirming Official, with the assessor at the three-year mark

How long authorization usually takes

CMMC Level 1 (Self): annual self-assessment and affirmation in SPRScontractors and subcontractors holding only Federal Contract Information under FAR 52.204-21; required now under Phase 1 (DFARS 252.204-7021 in force since 10 Nov 2025)
1 months typical · 0 to 3
CMMC Level 2 (Self): triennial self-assessment against NIST SP 800-171 Rev 2, annual affirmation, SPRS postingcontractors handling CUI where the program office designates Level 2 (Self); during the Phase 2 suspension this is the only CUI designation a requiring activity may use
6 months typical · 1 to 18
CMMC Level 2 (C3PAO) certification assessment, three-year validitycontractors handling CUI where a solicitation designates Level 2 (C3PAO). Under 32 CFR 170.3(e) and DFARS 204.75 that designation was to become usual in Phase 2 from 10 Nov 2026; since 13 July 2026 the Department of War has suspended Phase 2 and program offices may not designate it. Certification remains available voluntarily and primes may still ask for it.
12 months typical · 4 to 24
CMMC Level 3 (DIBCAC) certification assessment by DCMA DIBCAC, three-year validitycontractors handling CUI tied to the highest-priority programs where DoD designates Level 3; the assessor is a DoD organization (DCMA DIBCAC) but the outcome is a CMMC Status, not an authorization decision. Cannot be newly designated during the Phase 2 suspension.
18 months typical · 9 to 30
DFARS 252.204-7012(b)(2)(ii)(D) cloud equivalency: external cloud providers must meet FedRAMP Moderate or equivalentany contractor that puts covered defense information in an external cloud service; the obligation sits on the cloud provider's authorization, not on the contractor, and remains in force throughout the CMMC suspension
0 months typical · 0 to 3
015 months30 months

Jumpstart packages here

23 apply in full 41 in part · of 64

Sources, read 2026-10-13 · links checked 2026-10-15
PHARMACEUTICAL

Pharmaceutical

The cloud bar

No authorization decision: the provider is a qualified supplier, and ISO/IEC 27001 or SOC 2 Type 2 is held where the company chooses it.

The five gates, in this sector's words

  1. 1
    GxP determination and intended use

    Each computerised system is determined GxP or not and its intended use is written; the GxP data risk assessment sets the controls the validation will prove.

    Decidesthe system owner and process owner; the quality unit approves
  2. 2
    Validation plan approved

    The validation plan, the user and functional requirements and the risk-based test strategy are approved before testing begins.

    Decidesthe quality unit
  3. 3
    Suppliers and infrastructure qualified

    Cloud and service providers are assessed as suppliers and the IT infrastructure is qualified; an ISO/IEC 27001 certificate or a SOC 2 Type 2 report answers the supplier assessment where the company chooses one.

    Decidesthe system owner with the quality unit; the supplier's certification body or auditor
  4. 4
    Validation report approved; system released

    The validation report is approved and the system released for GxP use; in the EU the Qualified Person certifies batches on its records; the inspector reads the validated state.

    Decidesthe quality unit; the Qualified Person (EU)
  5. 5
    Periodic review and change control

    The validated state is kept by change control and periodic review under the quality system; a change in intended use reopens the validation.

    Decidesthe system owner under the quality unit

How long authorization usually takes

Computerized system validation / computer software assurance (GAMP 5 Second Edition; FDA CSA guidance, February 3, 2026; 21 CFR 11.10(a); EU GMP Annex 11): the regulated company's own documented decision that a cloud system is fit for intended usepharmaceutical and device companies using cloud systems in GxP processes; there is no authorization decision and no regulator grants cloud approval. The company validates, keeps objective evidence, and shows it at inspection; the cloud provider is a supplier assessed by risk
4 months typical · 1 to 12
ISO/IEC 27001 certification by an accredited certification body (stage 1, stage 2, annual surveillance, recertification at three years)a certification the company or its cloud supplier chooses; pharma buyers ask suppliers for it, regulators do not require it
8 months typical · 3 to 12
SOC 2 Type 2 attestation by a CPA firm (Type 1 is a point-in-time design opinion; Type 2 covers an operating period)a report the cloud supplier chooses to obtain and the pharma company reads during supplier assessment; not required by FDA or EU GMP
9 months typical · 4 to 15
08 months15 months

Jumpstart packages here

32 apply in full 32 in part · of 64

Sources, read 2026-10-13 · links checked 2026-10-15
ELECTRIC AND WATER UTILITIES

Electric and water utilities

The cloud bar

Electric: under today's standards cloud reaches BES Cyber System Information, not BES Cyber Systems; water: no cloud bar in rule, EPA's guidance is advisory.

The five gates, in this sector's words

  1. 1
    BES Cyber Systems categorized; water assets assessed

    Electric: BES Cyber Systems identified and categorized by impact under CIP-002, and the BES Cyber System Information that may live in a third-party or cloud store identified under CIP-011; water: the risk and resilience assessment names the assets.

    Decideselectric: the CIP Senior Manager approves the identifications; water: utility management
  2. 2
    Policies approved; plan certified

    Electric: the cyber security policies approved by the CIP Senior Manager under CIP-003, with the information protection and access management programs documented; water: the emergency response plan certified to EPA within six months of the assessment.

    Decidesthe CIP Senior Manager; utility management certifying to EPA
  3. 3
    BES Cyber System Information in the cloud under the programs

    Electric: BES Cyber System Information is stored with a third party or in cloud only under the CIP-004 and CIP-011 programs, with encryption and key-management evidence the entity controls; the BES Cyber Systems themselves stay on premises under today's standards; water: the protection approach the assessment chose.

    Decidesthe CIP Senior Manager or delegate
  4. 4
    Compliance shown at audit; certification on file

    Electric: compliance with the CIP standards shown at the Regional Entity's compliance audit through the RSAWs and evidence, with self-reports and mitigation plans for what fell short; water: the certification to EPA on file.

    Decidesthe Regional Entity determines findings; the CIP Senior Manager owns the response; utility management certifies
  5. 5
    Audit cycle, self-logging and the five-year review

    Electric: the audit cycle, quarterly self-log reviews, the 15-month verification reviews and the implementation plans for new standards (the virtualization set enforceable 1 July 2028; CIP-015); water: the five-year review of the assessment and the plan.

    Decidesthe CIP Senior Manager; utility management

How long authorization usually takes

NERC CIP compliance shown at a Regional Entity Compliance Audit (risk-based cycle under the Rules of Procedure and Appendix 4C)registered entities with BES Cyber Systems (BA, RC, TOP, TO, GO, GOP, DP as applicable); there is no authorization decision, the entity must be compliant from each standard's effective date and the Regional Entity verifies it at audit
24 months typical · 12 to 36
NERC CMEP self-report, self-logging and Mitigation Plan path (the entity reports its own noncompliance and restores compliance)any registered entity that finds a CIP noncompliance between audits; self-logging only for entities the Regional Entity has admitted after an internal-controls review, and only for minimal-risk issues
4 months typical · 1 to 12
AWIA section 2013 (SDWA 1433) risk and resilience assessment and emergency response plan certification to EPAcommunity water systems serving more than 3,300 people; systems at or below 3,300, non-community systems and wastewater have no certification duty
6 months typical · 1 to 12
018 months36 months

Jumpstart packages here

27 apply in full 37 in part · of 64

Sources, read 2026-10-13 · links checked 2026-10-15
KEPT CURRENT

Read again every week.

Standards move, programs are renamed, guidance is withdrawn. Every source on this page, and the rest the studio relies on (686 in all), is checked by a weekly hygiene routine: links that moved are followed, and standards, programs and vendor methods are checked for new revisions, drafts, renames and withdrawals. A change that would alter what a gate means, a lead time or a requirement is reviewed and recorded before the road changes; nothing changes silently. Each sector shows when its sources were read and when its links were last checked; the last full check ran on 2026-10-15.

WHAT THIS IS NOT

Research, not a ruling.

These readings are the practice's research, dated and sourced. They are not legal advice and not a statement that any system is authorized, certified or compliant: the organization's own assessor, auditor, regulator or quality unit decides. Lead times are typical ranges from public sources and practice experience, not commitments.

Start a conversation →