Lesson 6 of 14 · about 60 minutes · Updated November 15, 2026
Certifications and Government Authorizations: ISO 27001, HITRUST, PCI DSS, FedRAMP, GovRAMP and CMMC
You'll be able to
- Distinguish certification, attestation, validation, verification and authorization, and say who is accountable for each.
- Describe the ISO/IEC 27001 certification cycle, the accreditation chain and the 2025 and 2026 transitions, and check a vendor's certificate.
- Explain how HITRUST certifications and PCI DSS validation work, including merchant and service provider levels and the documents each produces.
- Explain the difference between a FedRAMP certification and an agency authorization to operate, and how FedRAMP 20x changes the path.
- Describe CMMC scoring, conditional status, affirmations and the status of the program after the July 2026 suspension.
- Choose and sequence certifications by buyer and govern them with a register, an owner and board reporting.
Start here: the short version
- Five different things get called "certified." An ISO/IEC 27001 certificate comes from an accredited certification body; a HITRUST certification comes from HITRUST after an external assessor tests the controls; a PCI DSS Report on Compliance is signed by a Qualified Security Assessor for the card brands; a FedRAMP certification is a federal program decision that each agency still has to turn into its own authorization to operate; and a CMMC status is a Defense Department contract eligibility record kept in a federal database. Know which one you hold or are being shown, because each proves something different.
- ISO/IEC 27001 runs on a three-year cycle. A two-stage initial audit, surveillance audits in years two and three, then recertification. Every accredited certificate to the 2013 edition stopped being valid after Oct. 31, 2025.1 The privacy extension, ISO/IEC 27701, was reissued as a standalone management system standard on Oct. 14, 2025.2
- HITRUST and PCI DSS are contract-driven. Health plans and health systems ask for HITRUST (CSF v11.8.0 was released May 2026), and the card brands set PCI validation by volume: a Visa Level 1 merchant (more than 6 million transactions a year) needs an annual Report on Compliance by a Qualified Security Assessor.34
- FedRAMP is changing its machinery. FedRAMP 20x is now the main path, the program will stop accepting new sponsored Rev5 agency certifications on June 11, 2027, and on Nov. 15, 2026 its marketplace counted 559 certified services, 39 of them through 20x.56 GovRAMP (StateRAMP until a February 2025 rebrand) does a similar job for state and local buyers.7
- CMMC is in force but its third-party phase is paused. The program rule took effect Dec. 16, 2024, and the contract rule Nov. 10, 2025; on July 13, 2026 the Department of War suspended Phase 2, and as of Nov. 15, 2026 no restart date had been announced.891011 The duty to meet NIST SP 800-171 and to report honest scores did not pause, and the False Claims Act still applies.
- Choose certifications by buyer, not by fashion. Build one control set, map it once, and then buy the assessments your customers, regulators and contracts actually require, in the order that opens the most revenue or removes the most legal exposure first.
Rules and standards described: ISO/IEC 27001:2022 with Amendment 1:2024, ISO/IEC 27701:2025, ISO/IEC 27006-1:2024 and ISO/IEC 17021-1:2015 (paid standards, described and not reproduced), under accreditation transition rules IAF MD 26 and IAF MD 29 and the Global Accreditation Cooperation arrangement in effect from Jan. 1, 2026; HITRUST CSF v11.8.0 (May 8, 2026); PCI DSS v4.0.1 (June 2024) with Visa's validation levels and Mastercard's Security Rules and Procedures, Merchant Edition (Aug. 4, 2026); the FedRAMP Authorization Act (Pub. L. 117-263, sec. 5921, Dec. 23, 2022, 44 U.S.C. 3607 to 3616), OMB Memorandum M-24-15 (July 25, 2024) and the FedRAMP Consolidated Rules for 2026; GovRAMP verification levels as posted Nov. 15, 2026; the CMMC program rule, 32 CFR Part 170 (effective Dec. 16, 2024, eCFR text current to Nov. 1, 2026), the DFARS CMMC rule (effective Nov. 10, 2025) and DFARS Class Deviation 2026-O0025, Revision 3 (Sept. 3, 2026); Idaho Technology Authority Policy P1090 (approved April 16, 2024). All read Nov. 15, 2026. Certification schemes, card brand rules and federal programs change often, and two of them (FedRAMP and CMMC) were in the middle of major changes when this lesson was written; check the scheme owner's current text before relying on any point.
Before you change anything. Plan changes to production systems, test them first, keep a way back, and follow your change management process. For clinical, plant-floor or other safety systems, involve the vendor, your safety lead and qualified engineers (see modules 109 and 111).
A cloud software company in Boise sells a scheduling and records product. In one month its sales team brings back four requests. A regional health system will not sign a renewal without a HITRUST certification. A national retailer wants proof the product is outside its card data environment, or else a PCI DSS Attestation of Compliance. A federal agency likes the product but cannot use it without FedRAMP. And a defense subcontractor that wants to use the product to store engineering drawings marked as Controlled Unclassified Information asks whether it meets the FedRAMP Moderate baseline, because the subcontractor's own CMMC assessment depends on it. The company already holds an ISO/IEC 27001 certificate and a SOC 2 Type 2 report. Its chief information security officer has a budget for perhaps two more assessments next year, and the chief financial officer wants to know which ones will pay for themselves.
That is the everyday problem this lesson addresses. Large organizations both buy and sell assurance. They ask their vendors for certificates and reports, and their customers and regulators ask the same of them. Each scheme has its own owner, its own assessors, its own cycle, its own costs and its own failure modes, and the differences matter when a contract, a federal award or a court case turns on what a certificate actually proved.
This lesson does not repeat the overview of standards in module 108, lesson 3, The Standards Map, which explains what ISO/IEC 27001's clauses and Annex A contain, the PCI DSS requirements, the CMMC levels and how frameworks relate. It goes one level down, into how each certification or authorization is actually obtained, kept, read and governed in a large organization. SOC reports and attestations, the other big family of assurance documents, are in lesson 5; how one control set is mapped to many rules is in lesson 4; budgeting for assessments is in lesson 2; AI management system certification under ISO/IEC 42001 is in lesson 13; and sector rules for manufacturers and defense suppliers are in module 111, lesson 6. Small-business versions of the same choices are in module 73, lesson 4 and module 73, lesson 5.
What the words mean: certification, attestation, authorization, verification
People use "certified" loosely. Procurement officers, auditors and contract drafters should not, because the word decides who is accountable if the claim turns out to be wrong.
| Kind of assurance | Example | Who decides | What it says | What it does not say |
|---|---|---|---|---|
| Management system certification | ISO/IEC 27001, 27701, 42001, 22301 | A certification body, itself accredited by a national accreditation body | The organization runs a management system that conforms to the standard, within a stated scope, as sampled at audit | That every control is strong, or that anything outside the scope is covered |
| Framework certification by a scheme owner | HITRUST e1, i1, r2 | HITRUST, after an authorized external assessor tests and HITRUST quality-reviews the work | The tested controls met the scheme's scoring threshold for a defined scope and period | That the environment was secure after the test, or for systems not in scope |
| Contractual compliance validation | PCI DSS Report on Compliance, Attestation of Compliance, Self-Assessment Questionnaire | A Qualified Security Assessor, an Internal Security Assessor, or the entity itself, as the card brands and acquiring banks allow | The entity met PCI DSS on the date of assessment | That it stayed compliant; the card brands treat compliance as continuous and validation as a snapshot |
| Attestation report | SOC 1, SOC 2, SOC 3 (lesson 5) | A licensed CPA firm under AICPA standards | An opinion on management's description and the controls, for a point in time (Type 1) or a period (Type 2) | A pass or fail grade; readers must read the exceptions |
| Government authorization | Agency authorization to operate (ATO) using a FedRAMP certified service | The agency's authorizing official | The agency accepts the residual risk of using the system for a stated purpose | That any other agency or any private buyer accepts the same risk |
| Program certification or verification | FedRAMP certification; GovRAMP verification; CMMC status | A government or nonprofit program office, often after an accredited third-party assessor's work | The service or contractor met the program's requirements at the stated level | That the buyer's own use, configuration and data are safe |
| Self-assessment with affirmation | CMMC Level 1 and Level 2 (Self); PCI SAQ | The organization, signed by a named senior official | The official affirms the requirements are met | Anything independently checked; but the signature carries legal weight under the False Claims Act or contract |
Two practical rules follow. First, a certificate is evidence, not a guarantee; it moves the burden of proof, and it gives the buyer a document to rely on and a party to point to. Second, the person who signs matters. A self-affirmation by a senior official in the Supplier Performance Risk System, or a PCI Attestation of Compliance signed by an executive officer, is a statement the government or the card brands can hold that official's organization to, and it is the statement that most often appears in False Claims Act cases, discussed in the CMMC section below.
ISO/IEC 27001 certification, step by step
ISO/IEC 27001:2022 sets requirements for an information security management system (ISMS): the leadership, risk assessment, risk treatment, policies, internal audit, management review and corrective action that keep a security program running and improving. What its clauses and the 93 Annex A controls contain is covered in module 108, lesson 3. The standard is sold by ISO and national standards bodies such as ANSI in the United States; this lesson describes it and does not reproduce it. Here the question is how an organization gets and keeps an accredited certificate.
The accreditation chain: who certifies the certifiers
ISO itself does not certify anyone. ISO's help pages say plainly that it does not issue certificates or accredit certification bodies, and they direct anyone checking a certificate to an accredited-certification database or to the relevant accreditation body.12 The chain has three links:
- The certification body (sometimes called a registrar) audits the organization and issues the certificate. Large international ones include BSI, DNV, SGS, Bureau Veritas, TUV companies and many smaller firms. A certification body that wants its certificates to carry weight must meet ISO/IEC 17021-1:2015, the general standard for bodies that audit and certify management systems, and ISO/IEC 27006-1:2024, the information security supplement to it.1314
- The accreditation body audits the certification body. In the United States the main one for ISMS certification is the ANSI National Accreditation Board (ANAB); the United Kingdom has UKAS, Ireland INAB, Germany DAkkS, and so on. One country, one accreditation body is the usual pattern.13
- The international arrangement makes a certificate accredited in one country count in another. For decades this was the International Accreditation Forum (IAF) Multilateral Recognition Arrangement. On Jan. 1, 2026 the IAF and the laboratory accreditation group ILAC became non-operational and were replaced by a single body, Global Accreditation Cooperation Incorporated (Global ACI); existing recognition carries over without interruption, and the old IAF mark may be used during a transition expected to run to Jan. 1, 2029.15 The IAF's General Assembly agreed in principle to transfer its database of accredited certificates, IAF CertSearch, to Global ACI by Dec. 31, 2025.16
The chain matters because unaccredited certificates exist and are sold cheaply. A certificate from a body that no accreditation body has audited may be printed on good paper and carry an ISO-like logo, but it has no international recognition, and a careful buyer will not accept it. The first check on any certificate is whether the issuing body is accredited for ISO/IEC 27001 by a recognized accreditation body, and whether the certificate itself appears in the accreditation body's list or in IAF CertSearch.1217
Scoping and the Statement of Applicability
Before any auditor arrives, the organization decides the scope of its ISMS: which business units, locations, products, systems and processes are inside it. Clause 4.3 of the standard requires the scope to be documented, and the certificate will print a summary of it. In a large organization the scoping decision is the most consequential choice in the whole effort, for three reasons:
- Cost and effort scale with scope. Audit time under ISO/IEC 27006-1:2024 is calculated from the number of people working within the scope (the standard now uses an "effective number of personnel" concept), adjusted for complexity, number of sites and similar factors; the 2024 edition moved that method to a new Annex C and added rules for scope extensions and multi-site audits.13
- Customers read the scope. A certificate for "the corporate IT department at the Denver headquarters" says nothing about the hosted product a hospital is buying. Sales teams sometimes show the certificate without the scope; procurement teams should always ask for both.
- Scope creep is slow. Adding a business unit later is an extension audit, with its own audit time. Organizations that start narrow (one product line, one data center) and widen yearly often find the certificate never catches up with the business.
The Statement of Applicability (SoA) is the second key document. It lists each of the 93 Annex A controls, says whether it is applicable, whether it is implemented, and why any is excluded. An SoA that excludes, say, secure development controls for a software company is a red flag a customer can see in five minutes. Sophisticated buyers ask for the SoA, or at least a summary of it, under a nondisclosure agreement.
Stage 1 and Stage 2 audits
The initial certification audit is done in two stages, under ISO/IEC 17021-1 and 27006-1:14
- Stage 1 (readiness and documentation). The auditor reviews the ISMS documentation: scope, policy, risk assessment method, risk assessment results, risk treatment plan, SoA, internal audit and management review records. The auditor confirms the organization is ready for Stage 2 and identifies "areas of concern" that could become nonconformities. Stage 1 is often partly remote. If the organization is not ready, the certification body may stop here.
- Stage 2 (implementation). Usually weeks to a few months after Stage 1, the auditor tests whether the ISMS actually operates: interviews with managers and staff, samples of records (access reviews, change tickets, incident logs, supplier reviews, training records), and observation. The 2024 edition of ISO/IEC 27006-1 adds requirements for reporting how much of the audit was done remotely, and certificates for organizations with few or no physical sites must say that their activities are carried out remotely.13
- Findings. The auditor reports major nonconformities (a requirement is not met, or a systemic failure casts doubt on the system's ability to achieve its results), minor nonconformities (an isolated lapse that does not undermine the system) and opportunities for improvement. Major nonconformities must be corrected, with evidence the certification body accepts, before certification can be granted; minor ones need an accepted corrective action plan.
- Certification decision. A person at the certification body who did not do the audit reviews the report and makes the decision. The certificate is then issued, normally valid for three years.
Typical elapsed time from a decision to pursue certification to a certificate in hand is several months to a year or more for a large organization, because the ISMS needs time to produce records (at least one internal audit and one management review) before Stage 2. This lesson could not find an authoritative public survey of time or cost; consultancies publish ranges, and those figures are marketing estimates rather than data.
Surveillance, recertification and the three-year cycle
Certification is not a one-time event. Under ISO/IEC 17021-1, surveillance audits must be held at least once each calendar year, and the first one must come no more than 12 months after the certification decision. A recertification audit, closer to a full audit, is held before the certificate expires at the end of the third year.14 Surveillance audits sample the system: the management review, internal audits, corrective actions, changes since last time, use of the certification marks, and a rotating set of controls.
A certificate can be suspended or withdrawn if a major nonconformity is not corrected, if surveillance is not allowed to take place, or if the certified organization misuses the certificate. Customers who rely on certificates should therefore check status at least yearly, not only at onboarding.
The 2022 edition transition and the auditor rules that changed with it
The current edition of ISO/IEC 27001 was published in October 2022. Under the accreditation community's transition document, IAF MD 26, every organization certified to the 2013 edition had to be transitioned to the 2022 edition by Oct. 31, 2025; after that, accredited 2013 certificates were no longer valid.1 A vendor showing a 2013-edition certificate in 2026 is showing an expired document, whatever date is printed on it, and a procurement file that still relies on one needs updating.
A second, less visible change affected the auditors. ISO/IEC 27006-1:2024, published in March 2024, replaced the earlier rules for ISMS certification bodies. Accredited certification bodies had 24 months from the end of the publication month to transition, with the transition document IAF MD 29:2024; ANAB described the deadline for applying the new edition to all clients as March 31, 2026, though one passage of its notice also mentions an earlier date.13 The new edition dropped a fixed requirement for auditor work experience and training hours, removed the old rule requiring accreditation body approval when remote work exceeded 30 percent of planned on-site time, rewrote the audit-time method and updated the controls guidance to match the 2022 Annex A.13 For buyers the practical effect is small. For certified organizations, audit-day quotes in 2026 and later may differ from earlier ones because the calculation changed.
Amendment 1 of February 2024 added climate change as an issue the organization must consider in its context analysis. It is not a new edition, did not require a separate transition, and adds no security control.18
How many certificates exist
ISO publishes an annual survey of certificates reported by certification bodies. A summary of the ISO Survey 2024 published by a certification consultancy reported 96,709 ISO/IEC 27001 certificates covering 179,877 sites worldwide, up from 47,291 certificates in the 2023 survey, with 4,260 certificates in the United States.17 Treat the year-to-year jump with care: the survey depends on certification bodies choosing to report, and ISO says that starting in 2025 the survey is compiled from IAF CertSearch data, so changes in method can move totals as much as changes in adoption.19 The direction, however, is clear: ISO/IEC 27001 has become the default security certificate outside the United States, and an increasingly common one inside it.
Reading someone else's ISO certificate
Vendor management teams (see module 108, lesson 8) can check an ISO/IEC 27001 certificate in about 20 minutes:
- Confirm the edition is 2022 and the expiry date is in the future.
- Read the scope statement. Does it cover the product, service, location and data you are buying?
- Identify the certification body and its accreditation body. Look for the accreditation mark and number; check the accreditation body's directory.
- Look the certificate up in IAF CertSearch or the certification body's own register.12
- Ask for the Statement of Applicability (or a summary), the date of the last surveillance audit, and whether any major nonconformities were raised and closed.
- Ask how the vendor's subcontractors and cloud providers are covered: usually through supplier controls in Annex A, not through the certificate itself.
- Record what you checked and when, and set a reminder to recheck in a year.
ISO/IEC 27701 and the other ISO certifications that ride along
ISO/IEC 27701:2025: privacy becomes its own management system
ISO/IEC 27701 adds privacy to the security management system. Its first edition, in 2019, was written as an extension of ISO/IEC 27001: an organization could only be certified to it together with 27001. The second edition, ISO/IEC 27701:2025, was published Oct. 14, 2025 and replaces the 2019 version. Certification bodies describe the central change the same way: it "now becomes a stand-alone standard," a privacy information management system (PIMS) standard with its own management system clauses rather than a set of additions to 27001.2
Two practical consequences follow. First, an organization whose privacy program is run by a privacy office separate from security (see lesson 10) can, in principle, be certified for privacy without first holding 27001, though most large organizations will keep the two together because the controls overlap. Second, there is a transition. The accreditation community's information and data security working group agreed on a plan that the United Kingdom's accreditation body published in March 2026 and revised in August 2026: certification bodies submit gap analyses by December 2026, accreditation bodies aim to transition the certification bodies by Oct. 31, 2027, and certification bodies are to have transitioned all certified clients by Oct. 31, 2028. The same plan covers a new companion standard for certification bodies, ISO/IEC 27706:2025.20 Other national accreditation bodies follow the same working group consensus, but check the accreditation body for your certification body; dates can differ slightly.
For buyers, a 27701 certificate is the closest thing to an international privacy certification in common use. It is not a legal safe harbor under any U.S. state privacy law or under the EU General Data Protection Regulation, and it does not replace the risk assessments those laws require. It is evidence that a privacy management system exists and is audited.
Other ISO certifications that large organizations add
| Standard | What it covers | How it is certified | Where this course covers it |
|---|---|---|---|
| ISO/IEC 27017 and 27018 | Cloud security controls (27017) and protection of personal data in public clouds acting as processors (27018) | Usually as additional controls inside a 27001 audit, listed on the certificate | 108, lesson 3 |
| ISO/IEC 27701:2025 | Privacy information management system | Standalone or with 27001 (transition through Oct. 31, 2028 under the UKAS plan) | Above, and lesson 10 |
| ISO/IEC 42001:2023 | Artificial intelligence management system | Separate accredited certification; often audited alongside 27001 | Lesson 13 |
| ISO 22301:2019 | Business continuity management system | Separate accredited certification | Lesson 12 |
| ISO/IEC 20000-1 | IT service management | Separate accredited certification | Not covered in detail |
| ISO 9001 | Quality management; required by many manufacturing and aerospace buyers | Separate accredited certification; common audit structure lets organizations combine audits | 111, lesson 6 |
Because all ISO management system standards share a common clause structure (context, leadership, planning, support, operation, performance evaluation, improvement), a large organization can run an "integrated management system" and have one certification body audit several standards in the same visit. Integrated audits save days. They also concentrate risk: if the internal audit or management review process fails, several certificates are exposed at once.

HITRUST: the health care sector's certification
HITRUST is a private organization that publishes the HITRUST CSF (not to be confused with the NIST Cybersecurity Framework), a control framework that maps requirements from HIPAA, NIST, ISO, PCI DSS, state laws and dozens of other sources into one set of requirement statements. Its certifications are bought mostly by vendors that sell to health plans, health systems and other health care organizations, which often write a HITRUST requirement into their business associate and vendor contracts. How health care organizations use it with business associates is covered in module 109, lesson 6; this section covers how the certification works.
The three main assessments
| Assessment | Size | Validity | Who it suits |
|---|---|---|---|
| e1 (essentials, one year) | 43 core controls | 1 year | Lower-risk vendors and startups; a first step that can be built on |
| i1 (implemented, one year) | 182 control requirements, described by HITRUST as leading practices | 1 year | Moderate-risk vendors; the common middle ground in health plan contracts |
| r2 (risk-based, two years) | Tailored by risk factors; the largest of the three (HITRUST's page gives no single count) | 2 years, with an interim check in the middle | Organizations handling large volumes of sensitive health data or required by customers or regulators to show the most assurance |
HITRUST also lists an AI security assessment that can stand alone or pair with e1, i1 or r2, an AI risk management assessment of 51 controls aligned to ISO and NIST AI risk work, "Insights Reports" that translate results into other frameworks such as HIPAA, NIST SP 800-171 and GovRAMP, and a NIST CSF 2.0 add-on to the r2.21
How a HITRUST certification is earned
- Scope and license. The organization licenses HITRUST's assessment platform (MyCSF), defines the scope (systems, facilities, data) and, for r2, answers risk-factor questions that decide which requirement statements apply.
- Readiness. Many organizations run a self-assessment first to find gaps. Gaps found here are cheaper than gaps found by the validator.
- Validated assessment. A HITRUST-authorized external assessor firm tests each requirement and scores it. For r2, scoring uses HITRUST's maturity model, which looks not only at whether a control is implemented but also at whether it is written as policy, documented as procedure, measured and managed.
- HITRUST quality assurance. HITRUST reviews the assessor's work before it issues a certification. This central review is the main difference from SOC 2, where the CPA firm issues its own opinion and no central body checks it.
- Corrective action plans. Requirements that fall short of the threshold can lead to required corrective action plans that must be tracked to closure.
- Inheritance. An organization that runs on a HITRUST-certified cloud or service provider can "inherit" scores for controls the provider performs, reducing its own testing.
HITRUST updates its framework often. Version 11.8.0 was announced in advisory HAA 2026-002 on May 7, 2026 and made available on May 8, 2026; it continued consolidating overlapping requirement statements, added mappings to sources including NIST SP 800-137 (continuous monitoring) and the OWASP Top 10 for LLM Applications 2025, refreshed mappings to PCI DSS v4.0.1 and the AICPA SOC 2 criteria, and narrowed two requirements in the e1 and i1 baselines.3 Assessments started on an older version must be created by HITRUST's published deadlines, which HITRUST announces in separate advisories.
HITRUST markets its certification with breach statistics. Its assessments page says fewer than 1 percent of HITRUST-certified environments reported a security breach over recent years and elsewhere cites a 99.62 percent breach-free rate.21 Those are the scheme owner's own figures, based on what certified organizations reported to it, without a published method on that page. They may be true, and they may reflect that organizations able to pass an r2 already run strong programs. A buyer should not read them as a promise about any one vendor.
PCI DSS validation: Reports on Compliance, questionnaires and attestations
PCI DSS v4.0.1, published June 11, 2024, is the only active version of the card industry's security standard; v4.0 was retired at the end of 2024 and the requirements that were "best practice" until March 31, 2025 are now mandatory.22 The PCI Security Standards Council's standards page, last modified April 8, 2026 and checked Nov. 15, 2026, names no newer version.23 What the requirements say is covered in module 108, lesson 3, and merchant basics and scope reduction in module 73, lesson 5. Here the subject is validation: how a large merchant or service provider proves compliance, and to whom.
Who sets the rules: the council writes, the brands enforce
The PCI Security Standards Council writes the standard and trains and qualifies assessors. It does not decide who must validate or how. Each card brand runs its own compliance program, and the acquiring bank (the merchant's card processor bank) is responsible to the brand for its merchants. Visa's Account Information Security program puts it directly: the council "owns and maintains" the standard and Visa "manages compliance enforcement and validation"; issuers and acquirers are responsible for their merchants' and service providers' compliance; and when a merchant is noncompliant Visa may assess the acquirer, which passes the cost on through its merchant agreement.24 That is why a merchant's PCI obligations appear in its merchant agreement, not in a statute, and why the acquiring bank, not the council, is the party that asks for the paperwork.
Merchant and service provider levels
Validation requirements depend on annual transaction volume, counted per brand. Visa's published levels are:4
| Visa level | Who | Validation |
|---|---|---|
| Merchant Level 1 | More than 6 million Visa transactions a year across all channels, or any merchant a Visa region has identified as Level 1 | Annual Report on Compliance (ROC) by a Qualified Security Assessor (QSA); quarterly network scan by an Approved Scanning Vendor (ASV); Attestation of Compliance (AOC) |
| Merchant Level 2 | 1 million to 6 million transactions a year, all channels | Annual Self-Assessment Questionnaire (SAQ); quarterly ASV scan; AOC |
| Merchant Level 3 | 20,000 to 1 million e-commerce transactions a year | Annual SAQ; quarterly ASV scan; AOC |
| Merchant Level 4 | Fewer than 20,000 e-commerce transactions, and other merchants up to 1 million transactions | Annual SAQ recommended; scans if applicable; requirements set by the acquirer |
| Service Provider Level 1 | VisaNet processors, or any service provider storing, processing or transmitting more than 300,000 transactions a year | Annual ROC by a QSA; quarterly ASV scan; AOC; listed on Visa's public list of compliant service providers |
| Service Provider Level 2 | Fewer than 300,000 transactions a year | Annual SAQ; quarterly ASV scan; AOC; may choose to validate as Level 1 to be listed |
Mastercard's rules, in its Security Rules and Procedures, Merchant Edition dated Aug. 4, 2026, use the same 6 million and 1 million thresholds for merchants but differ in detail. A Mastercard Level 1 merchant's annual assessment can be signed by a QSA, by a PCI-certified Internal Security Assessor (ISA), or, "unless prohibited by law," by an executive officer of the merchant. A Level 2 merchant that completes SAQ A, SAQ A-EP or SAQ D must also engage a QSA or ISA. Mastercard makes many categories of service providers (such as third-party processors and payment gateways) Level 1 regardless of volume, requiring an annual ROC by a QSA, and says the ISA option is not available to Level 2 service providers.25 A large merchant that accepts several brands must meet the strictest applicable rule.
Visa also runs a Technology Innovation Program that relieves eligible merchants of the annual validation if at least 75 percent of their yearly transactions come through EMV chip terminals, a validated point-to-point encryption solution, or EMVCo tokenization.24 Relief from validation is not relief from compliance; the merchant still must comply.
The documents: ROC, SAQ, AOC, and who may sign
- Report on Compliance (ROC). A long, detailed report, in the council's required template, recording how each requirement was tested and the result. It contains sensitive architecture detail. It is shared with the acquirer or brand on request but almost never with customers.
- Self-Assessment Questionnaire (SAQ). A shorter self-assessment. There are several types, matched to how the merchant takes cards: for example SAQ A for fully outsourced e-commerce, SAQ A-EP for e-commerce sites that affect the payment page, SAQ B-IP and C for certain terminals and payment applications, SAQ P2PE for validated point-to-point encryption, and SAQ D, the full set, for everyone else and for service providers.
- Attestation of Compliance (AOC). A short form, signed by the entity and, where applicable, the assessor, declaring the result. The AOC is the document a merchant or service provider shares with business partners. Payment processors' own guidance tells merchants to send the AOC and never the full ROC.
- Qualified Security Assessor (QSA). An individual employed by a QSA company, both qualified by the council, who performs ROC assessments. The council lists qualified companies publicly.
- Internal Security Assessor (ISA). An employee of the assessed company trained and certified by the council, allowed by some brand rules (as with Mastercard above) to perform or support the company's own assessment.
- Approved Scanning Vendor (ASV). A council-approved company that runs the quarterly external vulnerability scans required by PCI DSS Requirement 11.
Large organizations meet three PCI problems smaller ones rarely face. One is scope: a hospital, university or county takes cards in dozens of places (gift shops, parking, tuition, utilities, court fines), and each channel may need its own SAQ unless the organization centralizes and segments. A second is the customized approach in v4.x, which lets a mature organization meet a requirement's objective in its own way, but only with a documented targeted risk analysis that the QSA must test; it is more work, not less. The third is service provider evidence: under PCI DSS Requirement 12.8 the organization must keep a list of service providers that touch card data, know which requirements each one handles, and monitor their compliance status at least yearly, which in practice means collecting and reading AOCs and responsibility matrices.
FedRAMP: selling cloud services to federal agencies
The Federal Risk and Authorization Management Program, run by the General Services Administration (GSA), decides which cloud services federal agencies may use and supplies the security evidence agencies rely on. It began in 2011 under an Office of Management and Budget policy memo. Congress put it in statute in the FedRAMP Authorization Act, section 5921 of the National Defense Authorization Act for fiscal 2023 (Pub. L. 117-263), signed Dec. 23, 2022 and codified in part at 44 U.S.C. 3607 to 3616. OMB Memorandum M-24-15, issued July 25, 2024, "formally rescinded and replaced" the 2011 policy and set a new vision, scope and governance structure, including a FedRAMP Board that advises the GSA Administrator.26
Certification versus authorization: the distinction that matters
FedRAMP's 2026 rules use the word "certification" for what the program grants to a cloud service, and keep "authorization to operate" (ATO) for what an agency grants to its own use of that service. The rules describe a FedRAMP certification as something that "gives agencies reusable security evidence about a cloud service"; the agency still decides whether and how to use it. Before using a certified service, the agency must define what the service will be used for and what data it will hold, categorize its own system under FIPS 199 and FIPS 200, configure and test the controls the agency is responsible for, document them in its own System Security Plan, and then have its authorizing official issue an ATO and notify FedRAMP.27
Two rules in the 2026 consolidated rules carry out the statute's goal of reuse. Agencies should treat a certification package as presumptively adequate evidence of the provider's work (the "presumption of adequacy"), and an agency must not require information from a certified provider beyond what FedRAMP requires, or insist on a particular certification type or path, unless the agency head or a delegate finds a "demonstrable need" and notifies FedRAMP. Agencies may still ask clarifying questions.2728 For a provider, this is what makes FedRAMP worth its cost: one package, reused by many agencies, instead of a separate security review by every customer.
The traditional Rev5 path
Until 2025, almost every certification came through the "Rev5" process, named for the NIST SP 800-53 Revision 5 controls its Low, Moderate and High baselines are built from. FedRAMP now calls Rev5 a legacy certification type. Its legacy playbook describes the sponsored agency path in three phases:29
- Preparation. Optionally, a FedRAMP-recognized third-party assessment organization (3PAO) performs a readiness assessment, producing a Readiness Assessment Report that can earn a "FedRAMP Ready" designation. The provider then needs an agency partner willing to sponsor it, submits an information form to get a FedRAMP ID, dedicates staff (at minimum a technical writer, a technical subject matter expert and a project manager), selects a 3PAO, and holds a kickoff meeting with the agency and FedRAMP to agree the system boundary and known gaps.
- Authorization. The provider writes a System Security Plan. The 3PAO writes a Security Assessment Plan, tests the system with the environment frozen, and writes a Security Assessment Report recommending whether to certify. The provider turns the findings into a Plan of Action and Milestones (POA&M). The sponsoring agency reviews the package and, if it accepts the risk, its authorizing official signs an ATO. FedRAMP's program office then reviews the package for quality and risk, and the marketplace listing changes to certified.
- Continuous monitoring. Every month the provider sends agencies an updated POA&M, vulnerability scan results and requests for deviations or significant changes, and reports incidents. Providers with several agency customers use a shared "collaborative" monitoring process. A 3PAO performs an annual assessment. The playbook warns that a provider that cannot show a mature monitoring process may not be certified at all.
The Rev5 path was slow and expensive, and the hardest part was often finding an agency willing to sponsor a provider. GAO's January 2024 review found that FedRAMP use at the 24 CFO Act agencies had grown about 60 percent from July 2019 to April 2023, but that providers' estimated costs "varied widely and ranged anywhere from tens of thousands to millions of dollars," that actual cost data was thin because OMB had not said which costs to track, and that agencies and providers named six main problems: slow responses, unprepared providers, thin agency resources, technical and process requirements, difficulty finding an agency sponsor, and inconsistency among 3PAOs. GAO also found that nine agencies reported using cloud services that lacked FedRAMP authorization.30 GAO's three recommendations are now listed as implemented, through M-24-15 and GSA guidance of Jan. 16, 2025.30
FedRAMP 20x: the new path
FedRAMP 20x, announced in March 2025, replaces control-by-control document review with automated validation of a smaller set of outcomes, called Key Security Indicators, and with continuous evidence rather than point-in-time audits. Its own summary of the phases:5
| Phase | Dates | What happened or is planned |
|---|---|---|
| Phase 1 | April to September 2025 | Low-impact pilot; 26 submissions; first pilot authorizations in late July 2025, including program authorization without an agency sponsor |
| Phase 2 | Nov. 18, 2025 to March 2026 | Moderate-impact pilot; 14 qualifying submissions; first pilot authorizations March 6, 2026 |
| Phase 3 | Fiscal 2026, third and fourth quarters | Formal 20x requirements; Consolidated Rules for 2026 published in June 2026; submissions opened |
| Phase 4 (estimated) | Fiscal 2027, first half | Class D (High impact) pilot |
| Phase 5 (estimated) | Fiscal 2027, second half | No new Rev5 certifications after June 11, 2027; transition paths for existing Rev5 providers |
20x certifications come in classes. Class A is a pilot class for providers with mature programs, needing little information up front; Class B is a low-impact class for common, lightly used services; Class C is a moderate-impact class for enterprise services used across an agency; and Class D, for high-impact systems, is still being designed.5 Agencies should not authorize use of a Class A service for more than 12 months unless the provider is working toward Class B, C or D.28 FedRAMP granted the first full 20x Class C certification on Nov. 2, 2026.31 FedRAMP's rules for assessors say it "will stop accepting applications for sponsored Agency Certifications on June 11, 2027" and that agencies should generally steer providers to 20x program certification rather than start new sponsored Rev5 efforts.32
On Nov. 15, 2026, FedRAMP's home page counted 559 certified services, 39 of them certified through 20x, and listed a Nov. 10, 2026 notice (NTC-0017) on migration progress reporting for its new vulnerability detection and response rules.6 Two days earlier, module 108 recorded 557 and 38; the count moves weekly.
Why FedRAMP matters beyond federal agencies
FedRAMP reaches well beyond federal buyers. The CMMC program rule lets a defense contractor keep Controlled Unclassified Information in a cloud service only if the offering is FedRAMP Moderate (or higher) or "meets security requirements equivalent to" that baseline, and it pulls the contractor's own connections to that cloud into its assessment scope.33 DFARS 252.204-7012 already required the same FedRAMP Moderate equivalence for cloud services holding covered defense information, and a defense contractor's failure to meet it was one of the admitted facts in the MORSECORP settlement discussed below.34 Many states, universities and large companies also accept a FedRAMP package as strong evidence in their own vendor reviews.

GovRAMP (formerly StateRAMP) and state programs
State and local governments buy as much cloud software as federal agencies, but FedRAMP does not cover them. StateRAMP, a nonprofit, was created to fill that gap with a verification program based on NIST SP 800-53 controls. On Feb. 14, 2025 it announced it would do business as GovRAMP, keeping StateRAMP as its legal name; its president, J.R. Sloan, said "our name is evolving to better reflect the community we serve," and the announcement said the change "is not about changing the mission or strategic direction."7 Route Fifty reported at the time that the program was used in 27 states and that local governments, K-12 schools and universities had found the old name limiting; because some states name "StateRAMP" in laws and policies, the two names are used interchangeably.35
| GovRAMP level | What it involves (as posted Nov. 15, 2026) |
|---|---|
| Security Snapshot | A 12-month assessment of the top 40 NIST controls; a Progressing Security Snapshot tracks the same 40 controls over time |
| Core Verification | A 12-month status after a program-office-validated assessment of 60 NIST controls, with quarterly continuous monitoring |
| Ready Verification | A 12-month status based on an independent 3PAO assessment of 80 NIST controls, validated by the program office, with monthly monitoring and an annual assessment |
| Authorized or Provisional Verification | A 12-month status based on an independent 3PAO assessment of more than 300 NIST controls, validated by the program office, with monthly monitoring and an annual assessment |
GovRAMP's home page reported more than 1,200 member organizations, more than 70 government organizations engaged and more than 330 products in the program on Nov. 15, 2026, and on Nov. 2, 2026 it opened public comment on a proposed "20x Delta Assessment" to align with FedRAMP 20x.36 Many providers with a FedRAMP certification use it to reach GovRAMP status with less additional work.
Idaho and GovRAMP
Idaho's executive branch does not require GovRAMP. The Idaho Technology Authority's cloud services policy, P1090 (authority Idaho Code 67-833, approved April 16, 2024), sets minimum rules for agencies using cloud services: classify data first under ITA Policy P4130; encrypt all non-public state data at rest and in transit with validated cryptography; keep the most sensitive classification level (Level 4) out of any cloud service; require terms of service under which state data does not become the vendor's property and can be retrieved when the contract ends; manage cloud accounts centrally; audit periodically for misconfiguration and misuse; and dispose of data securely at the end. It states that "accountability for security and privacy in public cloud deployments cannot be delegated to a cloud provider." It cites NIST SP 800-144, 800-145 and 800-53A as references but does not name FedRAMP, StateRAMP or GovRAMP.37
GovRAMP's own list of participating government organizations, checked Nov. 15, 2026, includes one Idaho entry: the Idaho Administrative Office of the Courts, a state-level participant listed for 2026.38 GovRAMP notes that participation "can reflect exploration, planning, or active implementation," so the listing shows interest, not a statewide requirement. Idaho agencies, counties and school districts that buy cloud services can still ask vendors for a FedRAMP or GovRAMP status as evidence; it simply is not mandated by ITA policy. Legislators and county commissioners can reasonably ask whether that should change, a question taken up in Hard questions.
CMMC assessments in practice
The Cybersecurity Maturity Model Certification program checks whether defense contractors protect Federal Contract Information and Controlled Unclassified Information (CUI). Its levels and history are in module 108, lesson 3, and what it means for manufacturers is in module 111, lesson 6. In short: Level 1 is an annual self-assessment against 15 basic safeguarding requirements; Level 2 is the 110 requirements of NIST SP 800-171 Revision 2, assessed either by the contractor or by a Certified Third-Party Assessment Organization (C3PAO) every three years; and Level 3 adds 24 requirements from NIST SP 800-172, assessed by the Defense Contract Management Agency's Defense Industrial Base Cybersecurity Assessment Center (DIBCAC). The program rule, 32 CFR Part 170, was published Oct. 15, 2024 and took effect Dec. 16, 2024; the DFARS rule that puts CMMC into contracts took effect Nov. 10, 2025, starting Phase 1.89 This section covers the mechanics a program leader has to manage.
Scoring
Each Level 2 requirement is scored MET, NOT MET or not applicable. The rule says evidence must be "in final form and not draft"; working papers, drafts and unapproved policies do not count. The maximum score equals the number of Level 2 requirements (110). For each requirement NOT MET, its value (1, 3 or 5 points, depending on how much harm its absence could cause) is subtracted, "which may result in a negative score." Requirements whose absence could lead to significant exploitation of the network or exfiltration of CUI are worth 5 points, and partial credit is allowed only in narrow cases such as multifactor authentication.39 The Defense Department's assessment methodology runs from 110 down to -203.34
Conditional status and plans of action
A contractor that does not meet every requirement may still reach "Conditional" status at Level 2 if all of these are true: its score divided by the number of requirements is at least 0.8 (88 of 110); no requirement on its plan of action and milestones is worth more than 1 point, except encryption that is in place but not FIPS-validated; and none of six named requirements is on the plan, among them the System Security Plan itself and controls over external connections, public information and physical access. Level 1 allows no plan of action at all.40 Open items must be closed and confirmed in a "POA&M closeout assessment" within 180 days of the conditional status date; for a C3PAO assessment, the C3PAO does the closeout. If the deadline passes, conditional status expires, standard contractual remedies apply, and the contractor is ineligible for new awards at that level for that system until it earns a new status.4033
What happens in a C3PAO assessment
- Scope. The contractor defines its CMMC Assessment Scope: the systems, people and facilities that process, store or transmit CUI, plus security protection assets and connected systems, under the scoping rules in 32 CFR 170.19. Enclaves (a separated environment just for CUI) shrink scope and cost.
- Assessment against NIST SP 800-171A. The C3PAO tests each requirement's assessment objectives using the June 2018 assessment procedures, scores them under the CMMC methodology and enters results in the CMMC instance of the Defense Department's eMASS system, which sends them to the Supplier Performance Risk System (SPRS). The contractor receives a CMMC Assessment Findings Report.33
- Re-evaluation window. A requirement scored NOT MET may be re-evaluated during the assessment and for 10 business days after the active assessment period if more evidence exists, the change does not weaken other requirements, and the findings report has not been delivered.33
- Evidence integrity. The contractor must hash the evidence files with a NIST-approved hashing algorithm, give the C3PAO the list of file names and hash values for upload, and keep the hashed artifacts for six years from the status date.33
- Outside providers. Cloud services holding CUI must be FedRAMP Moderate or equivalent; other external service providers (a managed security provider, for example) must be documented in the System Security Plan and assessed within the contractor's scope.33
- Affirmation. A senior "Affirming Official" must affirm continuing compliance in SPRS after every assessment, after any closeout, and every year after a final status. Contracts requiring Level 2 (C3PAO) cannot be awarded until both the status and the affirmation are in SPRS.4133
- Government override. DIBCAC may assess any contractor, and if its results show the requirements were not achieved or maintained, its results "take precedence over any pre-existing CMMC Status."33
The affirmation is the step boards and general counsel's offices should watch most closely. It is a signed statement by a named senior official to the federal government, repeated every year, that every applicable requirement is implemented and will stay implemented. The Justice Department's False Claims Act cases against contractors have turned on statements of this kind.
Where CMMC stands in November 2026
On July 13, 2026 the Department of War (the secondary name the Defense Department has used since a September 2025 executive order) suspended Phase 2, which would have made Level 2 C3PAO assessments the default in new contracts from Nov. 10, 2026, and created a review and reform task force with 60 days to report. Its chief information officer, Kirsten Davies, called cybersecurity a "critical, nonnegotiable priority" but said the program was creating "prohibitive compliance costs and unacceptable bureaucratic burdens."10 DFARS Class Deviation 2026-O0025, Revision 3, signed Sept. 3, 2026, lets contracting officers use Level 1 (Self) or Level 2 (Self), requires baseline compliance with NIST SP 800-171 Revision 2 under DFARS 252.204-7012, "Suspends the November 2026 CMMC Phase 2 transition," and directs contracting officers to remove third-party CMMC requirements from existing contracts at the next option or modification.42
Nov. 10, 2026 passed without Phase 2. As of Nov. 12, 2026, independent trackers reported that no new rollout date had been announced and the task force report had not been released.43 Federal News Network reported on Oct. 27, 2026, from an internal summary of responses to the Department's request for information, that the options under discussion included restarting Phase 2 within about 90 days for a narrower group of contractors, expanding plans of action to 270 days (which would need rulemaking), finalizing a move to SP 800-171 Revision 3, and relying on a coming FAR rule on CUI to narrow who must meet 800-171; the Department declined to comment, and these were options, not decisions.11 The 32 CFR Part 170 rule itself was not rescinded or amended; this lesson found no official CMMC announcement between Oct. 28 and Nov. 15, 2026.
The assessment machinery kept running. The CMMC Accreditation Body (the Cyber AB, which authorizes C3PAOs and certifies assessors) reported at a Sept. 29, 2026 town hall that 117 C3PAOs were authorized and 2,362 final and 71 conditional Level 2 certificates had been issued; certifications already issued stay valid for their three-year terms.44 Those are the accreditation body's own counts, not a government census. GAO's March 12, 2026 report found the Department's rollout plans addressed six of seven elements of a sound strategy but had not documented how it would handle outside factors, especially whether there would be enough private assessors, and warned that relying on waivers "would not address underlying challenges"; the Department agreed and promised a corrective plan by Dec. 31, 2026.45
What did not pause: DFARS 252.204-7012 and SP 800-171 Revision 2 for covered defense information; 72-hour incident reports to the Department; SPRS scores and annual affirmations; and False Claims Act exposure for misstatements. On Sept. 1, 2026, the Justice Department announced that Honeywell Aerospace agreed to pay $2,042,518 to resolve allegations that one of its business units did not meet SP 800-171 on one network from April 2020 through December 2023; the case began as a whistleblower suit by a former employee, who received $375,823, and the claims were allegations only, with no determination of liability.46 A suspension of third-party assessments is not a suspension of the duty.
What a large defense contractor should do now
- Keep the SP 800-171 Revision 2 program running and the SPRS score accurate. Update the score when it changes, not at the next assessment.
- Treat every affirmation as a legal statement. Have the Affirming Official sign only after a documented internal review, and keep that review with the hashed evidence.
- If a C3PAO assessment is already scheduled, consider keeping it: existing certificates remain valid for three years and many prime contractors still ask for them.
- Reduce scope with a CUI enclave and FedRAMP Moderate cloud services, so that whatever form the program takes next costs less.
- Track the subcontractor base. Primes flow requirements down, and a supplier's false affirmation can become the prime's problem.
- Watch for the task force report, a Federal Register notice on the Revision 3 rulemaking and the FAR CUI rule. Any of them can change the plan quickly.

Choosing and sequencing certifications
A large organization can easily end up holding a dozen assessments, each bought for one customer or one deal, each with its own calendar, evidence requests and consultants. The better approach starts from a single control framework and treats each certification as a view of it.
Start from who is asking, and why
| If the demand comes from | The usual answer | Watch for |
|---|---|---|
| U.S. enterprise software customers | SOC 2 Type 2 (lesson 5) | Customers who also accept ISO; ask before buying both |
| Customers in Europe, Asia, or global procurement teams | ISO/IEC 27001, often with 27701 for privacy | Scope that matches the product they buy |
| Health plans and health systems | HITRUST i1 or r2 | Contracts that name a specific assessment; e1 may not satisfy them |
| Taking or processing payment cards | PCI DSS validation at the brand-required level | Scope reduction through tokenization and outsourcing before validating |
| Federal agencies | FedRAMP (20x for new entrants) | Rev5 sponsorships ending June 11, 2027 |
| State, local and education buyers | GovRAMP, where required; FedRAMP often accepted | State-by-state rules; Idaho's executive branch does not require it |
| Defense Department contracts with CUI | SP 800-171 compliance, SPRS score, CMMC status | Program changes after the 2026 suspension |
| Regulators (banks, insurers, health care) | Usually none of these by name; regulators examine the program itself | Treating a certificate as a substitute for the risk assessment the rule requires |
Sequencing principles
- Build the control set first. Pick a backbone (NIST SP 800-53, the NIST CSF 2.0 with a control catalog, or a commercial unified framework), map it to every scheme you need, and assign each control an owner and evidence. Lesson 4 covers the mapping and the evidence calendar.
- Do the broadest management system early. ISO/IEC 27001 forces the risk assessment, internal audit and management review that every other scheme quietly assumes.
- Buy the revenue-gating assessment next. If a health plan contract worth millions requires HITRUST, that comes before a certification nobody has asked for.
- Use inheritance. Run regulated workloads on cloud services that already hold FedRAMP, HITRUST and PCI service provider status, and inherit their controls where the scheme allows.
- Align audit windows. A SOC 2 review period, the ISO surveillance audit and the HITRUST testing window can share evidence if they overlap. Keep a single evidence repository with each artifact tagged to every control it supports.
- Retire what nobody uses. Each year ask sales and procurement which certifications customers actually requested. Drop the ones nobody asked for.
Costs and timelines: what is actually known
Reliable public cost data is scarce, and most figures in circulation are vendor marketing. The best government numbers:
- CMMC. The Defense Department's own regulatory estimates for a Level 2 C3PAO assessment, which exclude the cost of implementing the controls, ran from about $104,670 (small entities) to $117,768 (other than small) per three-year cycle; it estimated $41,050 for the government-assessment portion of Level 3 for larger entities.8 CSIS summarized the Department's figure for a small company's initial Level 2 assessment as about $102,000, including roughly $31,000 paid to the assessment organization, and reported a Small Business Administration estimate that total costs including remediation can reach about $594,000.47 Federal News Network's October 2026 report put the average assessment cost reported in RFI responses near $47,000.11 The spread shows how much depends on the starting point.
- FedRAMP. GAO found provider estimates "from tens of thousands to millions of dollars" and no consistent tracking.30 FedRAMP 20x is designed to reduce both the cost and the time; its early data is too new to give a reliable average.
- ISO/IEC 27001, HITRUST and PCI. No government or scheme owner publishes average prices. Costs depend on audit days (driven by headcount and complexity under ISO/IEC 27006-1), assessor rates, the number of locations and the work needed to close gaps. Treat any published range as an estimate and get several quotes.
Internal cost usually exceeds the assessor's fee: staff time to collect evidence, remediation, tooling and the opportunity cost of engineers pulled into audits. Budget planning for assessments, including the people side, is in lesson 2.
Governing a portfolio of certifications
Certifications are organizational commitments, and they need an owner, a calendar and oversight just like policies do.
- Keep a certification register. For each certificate, attestation or authorization: scheme and version, scope, issuer, assessor, dates (issued, next surveillance, expiry), open findings and plans of action, the executive who signs or affirms, and which contracts depend on it.
- Name a single owner. Usually the governance, risk and compliance team in the CISO's organization (see lesson 1), with internal audit providing independent checks (see lesson 8).
- Report to the board. A short quarterly line in the security report: status of each certification, any major nonconformity, conditional status or lapse, and upcoming audits. Lesson 3 shows the report format.
- Control the marketing. Sales materials, websites and questionnaire answers must match the scope and status exactly. Saying "FedRAMP compliant" for a service that is not certified, "ISO certified" for a product outside the scope, or "PCI certified" for an organization that only completed an SAQ invites contract claims, regulator interest and, in federal contracting, False Claims Act exposure.
- Remember what it does not prove. A certificate shows a process was audited against a standard on certain dates. It does not show that the next incident will be handled well. Organizations with current certificates are breached every year; see lesson 5 on clean reports at breached companies.
- Plan production changes carefully. Remediation to pass an assessment (new network segmentation, encryption, identity changes) is a change to production systems: plan it, test it and have a way back.
Pictures, Numbers and Infographics
The numbers a program leader, buyer or reporter most often needs, with their sources:
| Item | Number or date | Source |
|---|---|---|
| Deadline to move ISO/IEC 27001 certificates from the 2013 to the 2022 edition | Oct. 31, 2025 | INAB applying IAF MD 261 |
| ISO/IEC 27001 certificates worldwide, ISO Survey 2024 (as summarized) | 96,709 certificates; 179,877 sites; 4,260 in the U.S. | ISO Survey 2024 summary17 |
| ISO/IEC 27701:2025 published | Oct. 14, 2025; client transition by Oct. 31, 2028 under the UKAS plan | DNV; UKAS220 |
| IAF and ILAC replaced by Global Accreditation Cooperation | Jan. 1, 2026 | NATA notice15 |
| HITRUST CSF v11.8.0 available | May 8, 2026 | HITRUST HAA 2026-0023 |
| HITRUST e1 / i1 size and validity | 43 controls, 1 year / 182 requirements, 1 year; r2 valid 2 years | HITRUST21 |
| Visa Level 1 merchant threshold | More than 6 million transactions a year | Visa4 |
| Visa Level 1 service provider threshold | More than 300,000 transactions a year | Visa4 |
| Visa Technology Innovation Program threshold | At least 75 percent of transactions through chip, validated P2PE or EMVCo tokens | Visa24 |
| FedRAMP Authorization Act signed | Dec. 23, 2022 (Pub. L. 117-263, sec. 5921) | FedRAMP / OMB M-24-1526 |
| Growth in FedRAMP authorizations at CFO Act agencies | About 60 percent, July 2019 to April 2023 | GAO-24-10659130 |
| FedRAMP certified services | 559 total; 39 through 20x (Nov. 15, 2026) | FedRAMP6 |
| Last day for new sponsored Rev5 agency certifications | June 11, 2027 | FedRAMP32 |
| Maximum agency ATO for a 20x Class A service | 12 months, unless the provider pursues a higher class | FedRAMP28 |
| StateRAMP rebrand to GovRAMP announced | Feb. 14, 2025 | GovRAMP7 |
| GovRAMP program size | 1,200+ members; 70+ government organizations; 330+ products | GovRAMP36 |
| CMMC program rule effective / DFARS rule effective | Dec. 16, 2024 / Nov. 10, 2025 | Federal Register89 |
| CMMC Phase 2 suspended | July 13, 2026; no restart date as of Nov. 15, 2026 | Department of War10 |
| Minimum for CMMC Level 2 Conditional status | Score at least 0.8 of requirements (88 of 110); close within 180 days | 32 CFR 170.2140 |
| CMMC evidence retention | 6 years, hashed | 32 CFR 170.1733 |
| Authorized C3PAOs; Level 2 certificates issued | 117; 2,362 final and 71 conditional (Sept. 29, 2026) | Cyber AB, as reported44 |
| DoD estimate for a Level 2 C3PAO assessment, three-year cycle | About $104,670 to $117,768, before remediation | 89 FR 830928 |
| Honeywell Aerospace False Claims Act settlement | $2,042,518 (Sept. 1, 2026) | DOJ, as reported46 |
Common mistakes
Reporting a score that no longer matched reality
MORSECORP, a Massachusetts defense contractor, agreed on March 26, 2025 to pay $4.6 million to settle False Claims Act allegations. In facts it admitted, it had posted an SP 800-171 score of 104 in January 2021; a consultant told it in July 2022 that its actual score was -142; and it did not update the government's system until June 2023. It also admitted that from January 2018 to September 2022 it used a third-party email host without making sure the host met security requirements equivalent to FedRAMP Moderate.34 The lesson for every affirmation and self-assessment: when the facts change, the filing must change.
Assuming one noncompliant network does not count
The Honeywell Aerospace settlement of Sept. 1, 2026 involved allegations that one business unit's single network did not meet SP 800-171 for more than three years.46 Large organizations with many enclaves and acquired networks should map exactly which systems handle covered information, because the government's theory reaches every one of them.
Claiming compliance in proposals that the program does not support
Aerojet Rocketdyne agreed in July 2022 to pay $9 million to resolve allegations, brought by its former senior director of cybersecurity, that it misrepresented its compliance with federal cybersecurity requirements in contracts.48 Georgia Tech Research Corporation agreed on Sept. 30, 2025 to pay $875,000 to resolve a cyber-fraud suit that included allegations about a lab that lacked a required system security plan and a self-assessment score submitted for a system that did not exist as described.49 Proposal teams need a process that checks every security claim against the certification register before submission; lesson 4 covers the Civil Cyber-Fraud Initiative in detail.
Using cloud services without the required authorization
GAO found in January 2024 that nine federal agencies reported using cloud services that lacked FedRAMP authorization, despite OMB's requirement.30 Private organizations make the same mistake when a team adopts a software-as-a-service tool for regulated data without asking whether it carries the certification a contract requires. Procurement, single sign-on and expense controls are the places to catch it.
Relying on self-attestation without checking
CSIS recalled that a 2022 Defense Department inspector general review found all 10 research contractors it examined out of compliance with the NIST requirements they had agreed to meet, one of the reasons the Department moved toward third-party assessment in the first place.47 Whatever the assurance model, a buyer that never samples the evidence behind a self-attestation is relying on hope.
Accepting expired, unaccredited or out-of-scope certificates
After Oct. 31, 2025, an accredited ISO/IEC 27001:2013 certificate was no longer valid.1 Vendor files across many organizations still contain them, along with certificates from unaccredited bodies and certificates whose scope covers a headquarters office rather than the service being bought. The fix is mechanical: verify in IAF CertSearch or the accreditation body's directory, read the scope, and recheck yearly.12
Questions people ask
Is ISO/IEC 27001 better than SOC 2?
Neither is better; they answer different questions. ISO/IEC 27001 certifies that a management system exists and is audited every year against an international standard; SOC 2 gives a CPA firm's opinion on specific controls over a period, with exceptions listed. U.S. buyers usually ask for SOC 2, international buyers for ISO. Many large providers hold both and use the same evidence. Lesson 5 compares them in detail.
Can our organization be "PCI certified"?
Not in the sense people usually mean. The PCI Security Standards Council does not certify merchants. A merchant or service provider validates its compliance through a Report on Compliance or a Self-Assessment Questionnaire and signs an Attestation of Compliance, as its acquiring bank and the card brands require.24 Level 1 service providers that validate with a QSA can appear on Visa's public list of compliant service providers.4 Avoid the word "certified" in sales material.
Once we are FedRAMP certified, can any agency use our service?
Any agency may, but each must still issue its own authorization to operate for its own use, after configuring its own controls. The 2026 rules tell agencies to treat the package as presumptively adequate and not to demand extra information without a documented "demonstrable need," which shortens their work considerably.2728
Should a new provider start a Rev5 sponsorship now?
For most providers, no. FedRAMP's own rules tell agencies to steer providers to 20x program certification, and new sponsored Rev5 applications end June 11, 2027.32 Providers that need High-impact certification may have to wait for the Class D pilot planned for fiscal 2027.5
CMMC Phase 2 is suspended. Can a defense contractor stop working on it?
No. The suspension changed which contracts require a third-party assessment. It did not change DFARS 252.204-7012, the NIST SP 800-171 requirements, SPRS scores, annual affirmations or False Claims Act exposure.4246 A contractor that lets its program slide will face a harder assessment when the program restarts and a larger legal risk in the meantime.
We already comply with HIPAA. What does HITRUST add?
HIPAA's Security Rule is a federal regulation with no certification; HHS does not certify anyone as HIPAA compliant. HITRUST is a private framework and certification that maps HIPAA and many other sources into tested requirements, with HITRUST reviewing the assessor's work before certifying.21 Customers ask for it because it gives them a common, checked answer instead of a long questionnaire. It does not replace the HIPAA risk analysis; see module 109, lesson 4.
How do we check a vendor's claim quickly?
For ISO, search IAF CertSearch and read the scope.12 For FedRAMP, search the FedRAMP Marketplace for the exact service and certification class.6 For GovRAMP, check its program participants list.36 For PCI, ask for the AOC and check Visa's service provider list.4 For HITRUST, ask for the letter of certification and the scope. For CMMC, ask the supplier for its status, the status date and the affirmation date; primes can see suppliers' status in SPRS where the system allows.
Will a certificate lower our cyber insurance premium?
Sometimes indirectly. Underwriters ask about specific controls (multifactor authentication, endpoint detection, backups, privileged access), and a certificate can make the answers easier to support. This lesson found no public data showing a standard premium discount for any certification. Lesson 9 covers what underwriters ask.
Hard questions
Should government require third-party assessment, or trust contractors to self-assess?
For third-party assessment: self-attestation had years to work in defense contracting and the evidence says it did not; a 2022 inspector general review found all 10 research contractors it examined out of compliance, and the government's own cases show scores that bore no relation to reality.4734 Small suppliers are entry points into larger networks, and primes cannot audit every supplier themselves. For self-assessment with enforcement: third-party assessments cost about $100,000 or more per cycle before any remediation by the Department's own numbers, the pool of assessors is limited (GAO's March 2026 report flagged this), and the Department itself cited "prohibitive compliance costs" when it paused Phase 2; small firms may leave the defense market, reducing competition.81045 What the evidence shows: self-attestation without checking produced inaccurate scores; third-party assessment costs real money and depends on assessor capacity. The options reported in October 2026 (a narrower third-party requirement, longer plans of action, narrower CUI designations) are attempts to find a middle. Whatever is chosen, False Claims Act enforcement continues to backstop honesty.11
Do certifications make organizations safer, or only better documented?
Yes, safer: certifications force the basics (risk assessment, asset inventory, access review, incident response testing) that many breaches show were missing, and HITRUST reports that fewer than 1 percent of its certified environments reported a breach.21 Only better documented: audits sample, are scheduled in advance and focus on whether a process exists; certified organizations are breached regularly, and scheme owners' breach statistics rely on self-reporting by organizations that chose to certify. What the evidence shows: there is no independent, controlled study that isolates the effect of any one certification on breach rates. The honest answer is that certifications raise the floor and improve evidence, and that the quality of the program behind the certificate matters more than the certificate. Boards should ask for both: the certificate, and the metrics in lesson 3.
Should states such as Idaho require GovRAMP or FedRAMP for cloud services that hold public data?
For a requirement: state and local agencies hold tax, health, court and law enforcement data but rarely have staff to review every vendor; a common verification program gives them checked evidence and lets one review serve many agencies, which is why GovRAMP reports use in many states.35 Against a requirement: verification costs money that vendors pass on in prices, can shut out small local vendors, and duplicates FedRAMP; Idaho's policy already sets clear minimum rules (data classification, encryption, ownership of data, no Level 4 data in the cloud) and keeps accountability with the agency.37 What the evidence shows: this lesson found no study comparing breach rates in states that require GovRAMP with those that do not. A middle path some buyers use is to require GovRAMP or FedRAMP only for high-sensitivity systems and accept other evidence, such as SOC 2 or ISO, for the rest.
Is FedRAMP 20x moving too fast, or not fast enough?
Too fast: automated indicators and lighter documentation could miss risks that a human reviewer reading a full security plan would catch, and Class A services carry little upfront information. Not fast enough: GAO documented years of delays and costs in the millions under the old process, and agencies used uncertified cloud services anyway.30 What the evidence shows: FedRAMP limited Class A ATOs to 12 months unless the provider moves up, kept agency ATOs in place, and is piloting High impact separately, which are hedges against moving too quickly.528 It is too early for outcome data; watch FedRAMP's own reports and future GAO reviews.
For reporters and advocates
What public records exist.
- FedRAMP Marketplace. Free and public. It lists every certified service, its certification type or class, the agencies using it and, since Nov. 10, 2026, a description and availability date for each service in a package.6 Compare an agency's announced cloud contracts with the marketplace.
- GovRAMP participant lists. Its program participants list and participating government organizations list are public.3638
- IAF CertSearch. Free searches confirm whether an ISO certificate is accredited and current.12
- Visa's list of PCI DSS compliant service providers. Public; useful when a payment company claims compliance.4
- Federal rules and contract documents. 32 CFR Part 170 on eCFR; DFARS class deviations on the Defense Pricing, Contracting and Acquisition Policy site; solicitations on SAM.gov, which show which CMMC level a contract requires.4239
- Enforcement. Justice Department press releases and settlement agreements in Civil Cyber-Fraud Initiative cases; qui tam complaints become public on PACER (and often on CourtListener) once unsealed.4634
- Audits. GAO reports on FedRAMP and CMMC, and Defense Department inspector general reports, are free.3045
- SEC filings. Many public companies mention ISO, SOC 2, FedRAMP or CMMC status in 10-K Item 1C risk management descriptions; EDGAR full-text search finds them. Compare those claims with the marketplaces and registers above.
Questions to ask.
- Of a company: which certifications do you hold, for which products and locations, from which issuer, and when do they expire? Who signs your CMMC affirmations or PCI attestations?
- Of a government agency: which cloud services hold your residents' data, what certification or verification does each have, and who issued the authorization to operate? How many services are in use without one?
- Of a defense contractor: what SPRS score is posted, when was it last updated, and was it checked by anyone outside the company?
- Of a vendor that claims a certification in a public contract: can you produce the certificate, the scope and the verification record?
The Idaho angle. The Idaho Technology Authority's cloud policy, P1090, is public, and it does not require FedRAMP or GovRAMP; the only Idaho entry on GovRAMP's participating government list, as of Nov. 15, 2026, is the Administrative Office of the Courts.3738 Under the Idaho Public Records Act (Idaho Code Title 74, Chapter 1), reporters and residents can ask state agencies, counties, cities and school districts for their list of cloud services holding non-public data, the data classification for each, the contract terms on data ownership and return required by P1090, and any vendor security evidence (certificates, SOC reports, FedRAMP or GovRAMP status) on file. Expect technical details to be withheld under security exemptions; contracts, policies and the names of certifications usually are not. Idaho companies that sell to the Defense Department, including suppliers around the state's aerospace, manufacturing and research employers, are subject to the same CMMC and SP 800-171 rules as anywhere else, and their status appears in federal contract records rather than state ones.
Where to go next
- FedRAMP Marketplace and Consolidated Rules for 2026: Free. The official list of certified cloud services and the current program rules; agencies, vendors and reporters use it to check a service's status and class.
- IAF CertSearch: Free basic search. Confirms whether an ISO management system certificate is accredited and current; procurement and vendor risk teams should use it before accepting a certificate.
- DoD CIO CMMC resources: Free. The Defense Department's CMMC program pages, guidance documents and announcements; check here first for any restart after the 2026 suspension.
- 32 CFR Part 170 on eCFR: Free. The current text of the CMMC rule, including scoring (170.24), plans of action (170.21) and affirmations (170.22).
- PCI Security Standards Council document library: Free with license acceptance. PCI DSS v4.0.1, SAQs, ROC templates and AOC forms; for merchants, service providers and assessors.
- GovRAMP program participants and government organizations: Free. Shows which governments participate and which products hold GovRAMP status; useful for state and local buyers and reporters.
- HITRUST assessments and certifications: Free to read; assessments are paid. Describes e1, i1, r2 and AI assessments for health care vendors and buyers.
- GAO-26-107955 on CMMC: Free. GAO's March 2026 review of CMMC implementation risks, especially assessor capacity; useful for boards, legislators and reporters.
Still being checked (7 items)
These points could not be fully confirmed against a primary source when this lesson was written and fact checked in November 2026. The text above states each one as uncertain.
- ISO's own catalogue pages (ISO/IEC 27001, 27701, 17021-1) refused automated access on Nov. 15, 2026; the 17021-1 surveillance and recertification rules are stated from the standard's published requirements, and 27701:2025 facts come from DNV and UKAS.
- ISO Survey 2024 certificate counts (96,709 worldwide; 4,260 U.S.) come from a consultancy's summary of the survey, not ISO's dataset, which requires a login; the large jump from 2023 may partly reflect reporting changes.
- The Justice Department's Honeywell Aerospace release (Sept. 1, 2026) and the Federal News Network CMMC article (Oct. 27, 2026) could not be opened; their figures are taken from Nixon Peabody and Secureframe summaries.
- Cyber AB certificate and C3PAO counts are issuer-reported figures relayed by a private tracker, not an official government census.
- No official CMMC announcement between Oct. 28 and Nov. 15, 2026 could be found; the web search budget for this build ran out before a final news check on Nov. 15, 2026.
- HITRUST's breach-rate claims are the scheme owner's own figures without a published method on its page.
- No authoritative public data on typical ISO/IEC 27001, HITRUST or PCI assessment prices or timelines was found; the lesson gives no dollar figures for them.
Last verified November 15, 2026. General education, not legal, compliance, audit or other professional advice; rule versions and dates are stated in the text, and the sources used are listed in the Notes and Sources below. Check the regulator's current text before relying on any point.
Notes
- Irish National Accreditation Board (INAB), "Transition requirements for ISO/IEC 27001:2022," applying IAF MD 26 (certified clients to be transitioned by Oct. 31, 2025; 2013-edition certificates not valid after that date) (read Nov. 15, 2026). Read it online. ↩
- DNV, "Revision of ISO/IEC 27701" (ISO/IEC 27701:2025 published Oct. 14, 2025, replacing the 2019 edition; "now becomes a stand-alone standard"; transition rules to be set by accreditation bodies) (read Nov. 15, 2026). Read it online. ↩
- HITRUST Alliance, Advisory HAA 2026-002, "CSF Version 11.8.0 Release," May 7, 2026 (available in MyCSF May 8, 2026; new and refreshed authoritative sources; two e1 and i1 requirement changes) (read Nov. 15, 2026). Read it online. ↩
- Visa, "Validation of Compliance" (merchant Levels 1 to 4 and service provider Levels 1 and 2, thresholds and validation requirements; Level 1 service providers listed on Visa's list of PCI DSS compliant service providers) (read Nov. 15, 2026). Read it online. ↩
- FedRAMP, "FedRAMP 20x" program page (Phases 1 to 5 with dates; 26 Phase 1 submissions; 14 qualifying Phase 2 submissions; first Moderate pilot authorizations March 6, 2026; Classes A to D; no new Rev5 certifications after June 11, 2027) (read Nov. 15, 2026). Read it online. ↩
- FedRAMP home page and marketplace counts (559 total certified services, 39 through FedRAMP 20x; notice NTC-0017 and marketplace changes dated Nov. 10, 2026) (read Nov. 15, 2026). Read it online. ↩
- GovRAMP, "StateRAMP Announces Rebrand to GovRAMP, Reflecting Mission to Unite Public and Private Sectors in Advancing Cybersecurity," Indianapolis, Feb. 14, 2025 (legal name remains StateRAMP, doing business as GovRAMP) (read Nov. 15, 2026). Read it online. ↩
- Department of Defense, "Cybersecurity Maturity Model Certification (CMMC) Program," final rule, 89 FR 83092, Oct. 15, 2024 (32 CFR Part 170, effective Dec. 16, 2024), including levels, phased plan and regulatory cost estimates (Level 2 C3PAO assessment about $104,670 small entity and $117,768 other than small per three-year cycle; Level 3 government assessment portion $41,050), figures as recorded in module 108 lesson 3 and rechecked against the Federal Register page (read Nov. 15, 2026). Read it online. ↩
- Department of Defense, "Defense Federal Acquisition Regulation Supplement: Assessing Contractor Implementation of Cybersecurity Requirements," final rule, 90 FR 43560, Sept. 10, 2025 (effective Nov. 10, 2025) (read Nov. 15, 2026). Read it online. ↩
- U.S. Department of War, "War Department Changes Cybersecurity Maturity Model Certification Requirements," July 13, 2026 (Phase 2 suspended; 60-day review and reform task force; quotations from CIO Kirsten Davies) (read Nov. 15, 2026). Read it online. ↩
- Secureframe, "CMMC News 2026: Every Program Update, Rule Change and Enforcement Action" (latest entry Oct. 27, 2026, summarizing a Federal News Network report on an internal summary of RFI responses: restart options, 270-day POA&M idea, about $47,000 average assessment cost, 2,433 Level 2 certifications by September; the Defense Department declined comment). Secondary summary; the Federal News Network article could not be opened (read Nov. 15, 2026). Read it online. ↩
- ISO Help Center, "How to verify an accredited certification" (ISO does not issue certificates or accredit certification bodies; use IAF CertSearch or contact the accreditation or certification body) (read Nov. 15, 2026). Read it online. ↩
- ANSI Blog (ANAB), "ISO/IEC 27006-1:2024 Transition" (published March 2024; IAF MD 29:2024; 24-month transition; changes to audit time (new Annex C), auditor competence, remote auditing and controls guidance) (read Nov. 15, 2026). Read it online. ↩
- ISO/IEC 17021-1:2015, Conformity assessment: Requirements for bodies providing audit and certification of management systems, Part 1: Requirements, ISO catalogue entry (two-stage initial audit, annual surveillance with the first within 12 months of the certification decision, three-year recertification cycle). Paid standard, described from its published requirements; the ISO catalogue page refused automated access on Nov. 15, 2026 (read Nov. 15, 2026). Read it online. ↩
- National Association of Testing Authorities, Australia (NATA), "Communication to Regulators about Global Accreditation Cooperation Incorporated," Version 1.0, April 2026 (Global ACI fully operational Jan. 1, 2026; IAF and ILAC non-operational; IAF MLA folded into the Global ACI MRA; mark use expected to end Jan. 1, 2029) (read Nov. 15, 2026). Read it online. ↩
- International Accreditation Forum, Resolution 2025-11, "Transfer of IAF CertSearch Database to Global Accreditation Cooperation Incorporated" (transfer agreed in principle by Dec. 31, 2025; IAF ceased operations Jan. 1, 2026) (read Nov. 15, 2026). Read it online. ↩
- Global Standards (consultancy), "ISO Survey 2024" infographic, October 2025, summarizing ISO's survey (ISO/IEC 27001: 96,709 certificates and 179,877 sites in 2024, against 47,291 certificates and 79,213 sites in 2023; 4,260 certificates in the United States). Secondary summary; ISO's dataset requires an IAF CertSearch login (read Nov. 15, 2026). Read it online. ↩
- ISO/IEC 27001:2022/Amd 1:2024, "Climate action changes," catalogue summary (published February 2024), via iTeh Standards (read Nov. 15, 2026). Read it online. ↩
- ISO Committee on conformity assessment, "The ISO Survey" (from 2025 compiled from IAF CertSearch data; results available as a free dataset after login) (read Nov. 15, 2026). Read it online. ↩
- United Kingdom Accreditation Service (UKAS), Technical Bulletin, "Transition Arrangements for Privacy Information Management Systems," March 18, 2026, Revision 1 dated Aug. 18, 2026 (ISO/IEC 27701:2025 and ISO/IEC 27706:2025; gap analyses by December 2026; accredited bodies transitioned by Oct. 31, 2027; certified clients by Oct. 31, 2028) (read Nov. 15, 2026). Read it online. ↩
- HITRUST Alliance, "Assessments and Certifications" (e1: 43 controls, 1 year; i1: 182 requirements, 1 year; r2: 2 years; AI Security and AI Risk Management (51 controls) assessments; Insights Reports; NIST CSF 2.0 add-on; claims that fewer than 1 percent of certified environments reported a breach and a 99.62 percent breach-free rate) (read Nov. 15, 2026). Read it online. ↩
- PCI Security Standards Council, "Just Published: PCI DSS v4.0.1," June 11, 2024 (read Nov. 15, 2026). Read it online. ↩
- PCI Security Standards Council, "PCI Data Security Standard (PCI DSS)" standards page, last modified April 8, 2026 (v4.x resources; no newer version announced) (read Nov. 15, 2026). Read it online. ↩
- Visa, "Account Information Security (AIS) Program and PCI" (roles of the PCI SSC and Visa; acquirer and issuer responsibility; assessments for noncompliance; Technology Innovation Program at 75 percent of transactions), page last modified September 2024 (read Nov. 15, 2026). Read it online. ↩
- Mastercard, Security Rules and Procedures: Merchant Edition, Aug. 4, 2026, sections 2.2.2 (merchant levels and validation, including ISA and executive officer signature options) and 2.2.3 (service provider levels) (read Nov. 15, 2026). Read it online. ↩
- FedRAMP Consolidated Rules for 2026, "M-24-15" (OMB Memorandum M-24-15, "Modernizing the Federal Risk and Authorization Management Program," July 25, 2024; FedRAMP Authorization Act, Pub. L. No. 117-263, sec. 5921 (2022), codified in part at 44 U.S.C. 3607 to 3616; FedRAMP Board) (read Nov. 15, 2026). Read it online. ↩
- FedRAMP Consolidated Rules for 2026, "Initial Agency Authorization" (certification "gives agencies reusable security evidence about a cloud service"; agency categorization, SSP and ATO; notify FedRAMP; presumption of adequacy; Class A limit) (read Nov. 15, 2026). Read it online. ↩
- FedRAMP Consolidated Rules for 2026, "Agency Use of FedRAMP Certified Cloud Services" (no additional requirements without a demonstrable need and notice to FedRAMP; ATO before use; notify FedRAMP; Class A ATOs not beyond 12 months) (read Nov. 15, 2026). Read it online. ↩
- FedRAMP Legacy Documentation, "The FedRAMP Rev5 Agency Authorization Path" (preparation, authorization and continuous monitoring phases; readiness assessment; SSP, SAP, SAR, POA&M; PMO review) (read Nov. 15, 2026). Read it online. ↩
- U.S. Government Accountability Office, Cloud Security: Federal Authorization Program Usage Increasing, but Challenges Need to Be Fully Addressed, GAO-24-106591, Jan. 18, 2024 (about 60 percent growth in authorizations, July 2019 to April 2023; provider costs from tens of thousands to millions of dollars; six challenges; nine agencies using unauthorized services; recommendations later closed as implemented) (read Nov. 15, 2026). Read it online. ↩
- FedRAMP blog index, including "Propelling Change: FedRAMP Launches Consolidated Rules for 2026" (June 25, 2026) and "Memo to Milestone: FedRAMP Grants the First Full FedRAMP 20x Class C Certification" (Nov. 2, 2026) (read Nov. 15, 2026). Read it online. ↩
- FedRAMP Consolidated Rules for 2026, "Rev5 Assessments" ("FedRAMP will stop accepting applications for sponsored Agency Certifications on June 11, 2027"; agencies to steer providers to 20x program certification) (read Nov. 15, 2026). Read it online. ↩
- 32 CFR 170.17, CMMC Level 2 certification assessment and affirmation requirements (eCFR, text current to Nov. 1, 2026), including paragraphs (a)(1)(iv), (c)(2) re-evaluation, (c)(4) artifact retention and (c)(5) cloud service providers (read Nov. 15, 2026). Read it online. ↩
- U.S. Department of Justice, "Defense Contractor MORSECORP Inc. Agrees to Pay $4.6 Million to Settle Cybersecurity Fraud Allegations," March 26, 2025 (admitted facts; SPRS scale -203 to 110), as recorded in module 108 lesson 3 (read Nov. 15, 2026). Read it online. ↩
- Route Fifty, "Exclusive: StateRAMP to rebrand later this year," Feb. 14, 2025 (used in 27 states; reasons for the name change; names used interchangeably) (read Nov. 15, 2026). Read it online. ↩
- GovRAMP home page (verification levels: Security Snapshot of 40 controls, Core of 60, Ready of 80, Authorized or Provisional of 300+; 1,200+ members; 70+ government organizations engaged; 330+ products; Nov. 2, 2026 comment period on a proposed 20x Delta Assessment) (read Nov. 15, 2026). Read it online. ↩
- Idaho Technology Authority, Enterprise Policy P1090, "Cloud Services" (authority Idaho Code 67-833; approved by ITLC April 16, 2024). Copy saved in the lesson's work folder (read Nov. 15, 2026). Read it online. ↩
- GovRAMP, "Participating Government Organizations" table (Idaho entry: Idaho Administrative Office of the Courts, State, 2026; participation "can reflect exploration, planning, or active implementation"). Copy saved in the lesson's work folder (read Nov. 15, 2026). Read it online. ↩
- 32 CFR 170.24, CMMC Scoring Methodology (eCFR, text current to Nov. 1, 2026) (read Nov. 15, 2026). Read it online. ↩
- 32 CFR 170.21, Plan of Action and Milestones requirements (eCFR, text current to Nov. 1, 2026) (read Nov. 15, 2026). Read it online. ↩
- 32 CFR 170.22, Affirmation (eCFR, text current to Nov. 1, 2026) (read Nov. 15, 2026). Read it online. ↩
- Office of the Assistant Secretary of War for Acquisition and Sustainment, DFARS Class Deviation 2026-O0025, Revision 3, signed Sept. 3, 2026, paragraph (b), as quoted in module 108 lesson 3 (read Nov. 13, 2026) and confirmed unchanged in secondary trackers (read Nov. 15, 2026). Read it online. ↩
- Cyber Sierra, "CMMC Phase 2 Suspended. November 10 Start Date Did Not Happen But Evidence Work Does Not Stop," updated Nov. 12, 2026 (no new rollout date announced; task force report not public). Secondary source (read Nov. 15, 2026). Read it online. ↩
- The Defense Compliance Report, "CMMC Deadlines 2026: Phase 2 Status Tracker," reporting Cyber AB Town Hall figures of Sept. 29, 2026 (117 authorized C3PAOs; 2,362 final and 71 conditional Level 2 certificates). Issuer-reported, not a government census (read Nov. 15, 2026). Read it online. ↩
- U.S. Government Accountability Office, Defense Contractor Cybersecurity: DOD Should Address External Factors That Could Impede Program Implementation, GAO-26-107955, March 12, 2026 (recommendation status updated after July 2026) (read Nov. 15, 2026). Read it online. ↩
- Nixon Peabody, "Honeywell settlement shows FCA risk for NIST 800-171 gaps," Sept. 9, 2026, summarizing the Justice Department's Sept. 1, 2026 announcement ($2,042,518; one network, April 2020 to December 2023; relator share $375,823; allegations only). The Justice Department release refused automated access (read Nov. 15, 2026). Read it online. ↩
- Jerry McGinn and Oliver Buntin, "What the CMMC Pause Means for the Defense Industrial Base," Center for Strategic and International Studies, July 29, 2026 (cost figures, SBA estimate, 2022 inspector general finding, arguments on both sides) (read Nov. 15, 2026). Read it online. ↩
- U.S. Attorney's Office, Eastern District of California, "Aerojet Rocketdyne Agrees to Pay $9 Million to Resolve False Claims Act Allegations of Cybersecurity Violations in Federal Government Contracts," July 8, 2022 (read Nov. 15, 2026). Read it online. ↩
- U.S. Department of Justice, "Georgia Tech Research Corporation Agrees to Pay $875,000 to Resolve Civil Cyber-Fraud Litigation," Sept. 30, 2025 (read Nov. 15, 2026). Read it online. ↩
Check yourself
1. After what date was an accredited ISO/IEC 27001:2013 certificate no longer valid?
Under IAF MD 26, as applied by accreditation bodies such as INAB, certified clients had to transition to the 2022 edition by Oct. 31, 2025.
2. Who issues an accredited ISO/IEC 27001 certificate?
ISO says it does not issue certificates or accredit certification bodies; accredited certification bodies audit and certify, overseen by accreditation bodies.
3. Under ISO/IEC 17021-1, how often must surveillance audits occur during a three-year certification cycle?
ISO/IEC 17021-1:2015 requires surveillance at least once per calendar year, the first no more than 12 months after the certification decision.
4. What is the main structural change in ISO/IEC 27701:2025?
DNV and UKAS describe the 2025 edition, published Oct. 14, 2025, as a standalone standard rather than an extension of ISO/IEC 27001.
5. Which validation does Visa require of a Level 1 merchant (more than 6 million Visa transactions a year)?
Visa's validation table requires an annual ROC by a QSA, quarterly ASV scans and an AOC for Level 1 merchants.
6. Under FedRAMP's 2026 rules, what does a FedRAMP certification do by itself?
The Consolidated Rules for 2026 say a certification "gives agencies reusable security evidence about a cloud service"; each agency must still categorize its system, complete its own ATO and notify FedRAMP.
7. When will FedRAMP stop accepting applications for sponsored Rev5 agency certifications?
FedRAMP's Rev5 assessment rules and 20x page state it will stop accepting sponsored agency certifications on June 11, 2027.
8. To reach Conditional Level 2 (C3PAO) status under 32 CFR 170.21, a contractor's score must be at least what share of the Level 2 requirements?
32 CFR 170.21(a)(2)(i) requires the score divided by the number of Level 2 requirements to be at least 0.8, with further limits on what may be on the POA&M.
9. What did the Department of War's July 13, 2026 action do?
The July 13, 2026 announcement suspended Phase 2 and created a task force; Class Deviation 2026-O0025 Rev. 3 keeps baseline SP 800-171 Rev. 2 compliance under DFARS 252.204-7012.
10. Which statement about Idaho is accurate as of Nov. 15, 2026?
ITA Policy P1090 (approved April 16, 2024) lists those minimum requirements and cites NIST publications without naming FedRAMP, StateRAMP or GovRAMP.
Terms in this lesson
- Certification body
- An organization that audits management systems and issues certificates, such as for ISO/IEC 27001; its certificates carry weight only if a recognized accreditation body has accredited it.
- Accreditation body
- A national body, such as ANAB in the United States or UKAS in the United Kingdom, that assesses certification bodies against ISO/IEC 17021-1 and sector rules such as ISO/IEC 27006-1.
- Global Accreditation Cooperation (Global ACI)
- The single international accreditation organization that replaced the IAF and ILAC on Jan. 1, 2026 and carries forward their mutual recognition arrangements.
- Statement of Applicability (SoA)
- The ISO/IEC 27001 document listing each Annex A control, whether it applies, whether it is implemented, and the reason for any exclusion.
- Major and minor nonconformity
- Audit findings under ISO certification: a major one means a requirement is not met or the system cannot achieve its results and must be fixed before certification; a minor one is an isolated lapse needing a corrective action plan.
- Surveillance audit
- A partial audit by the certification body at least once each calendar year between initial certification and recertification.
- HITRUST r2
- HITRUST's risk-based, two-year validated assessment, tailored by risk factors and quality-reviewed by HITRUST before certification.
- Report on Compliance (ROC)
- The detailed PCI DSS assessment report, usually prepared by a Qualified Security Assessor, recording how each requirement was tested.
- Attestation of Compliance (AOC)
- The short signed PCI DSS form declaring the result of a ROC or SAQ; the document shared with business partners.
- Internal Security Assessor (ISA)
- An employee trained and certified by the PCI Security Standards Council who may perform or support the company's own PCI assessment where card brand rules allow.
- An agency authorizing official's formal acceptance of the risk of using a system for a stated purpose; required for each agency's use of a FedRAMP certified service.
- Presumption of adequacy
- The FedRAMP principle that agencies treat a certification package as adequate evidence and do not demand more without a documented demonstrable need.
- FedRAMP 20x
- FedRAMP's newer certification path, using automated validation of Key Security Indicators and continuous evidence, with Classes A to D and no agency sponsor required.
- C3PAO
- Certified Third-Party Assessment Organization: a company authorized by the Cyber AB to perform CMMC Level 2 certification assessments.
- Affirming Official
- The senior official who must affirm in SPRS, after each CMMC assessment and every year, that the organization has implemented and will maintain the required security requirements.
- Conditional CMMC status
- A temporary status for a contractor that scores at least 0.8 of the requirements with only allowed items on its plan of action; it expires unless closed out within 180 days.
Sources
- 32 CFR Part 170, CMMC Program (eCFR) (2026-11-01) checked 2026-11
- CMMC Program final rule, 89 FR 83092 (2024-10-15) checked 2026-11
- DFARS CMMC final rule, 90 FR 43560 (2025-09-10) checked 2026-11
- Department of War, CMMC Phase 2 suspension announcement (2026-07-13) checked 2026-11
- FedRAMP Consolidated Rules for 2026: Initial Agency Authorization (2026-06-25) checked 2026-11
- FedRAMP 20x (2026-11-15) checked 2026-11
- OMB M-24-15 on the FedRAMP site (2024-07-25) checked 2026-11
- GAO-24-106591, Cloud Security: Federal Authorization Program Usage Increasing (2024-01-18) checked 2026-11
- GAO-26-107955, Defense Contractor Cybersecurity (2026-03-12) checked 2026-11
- Mastercard Security Rules and Procedures: Merchant Edition (2026-08-04) checked 2026-11
- Visa, Validation of Compliance (2026-11-15) checked 2026-11
- HITRUST Advisory HAA 2026-002, CSF v11.8.0 (2026-05-07) checked 2026-11
- UKAS Technical Bulletin on ISO/IEC 27701:2025 transition (2026-03-18) checked 2026-11
- Idaho Technology Authority Policy P1090, Cloud Services (2024-04-16) checked 2026-11