Be A Freedom Fighter · Bill Library
HR 10915 — Common-Sense Cloud Security Act
Freedom score: -3 (scale −10 to +10)
- Individual rights: 0
- Property rights: 0
- Economic freedom: -1
- Privacy & due process: -1
- Government power: -1
Sponsor: Rep. McCormick, Richard [R-GA-7] · Latest action: Referred to the Committee on Science, Space, and Technology, and in addition to the Committee on Oversight and Government Reform, for a period to be subsequently determined by the Speaker, in each case for consideration of such provisions as fall within the jurisdiction of the committee concerned. (2026-10-26)
Full text on GovInfo (introduced version) · Congress.gov · ← Bill Library index
Findings — 17 highlighted provisions
Each item below is one provision documented in the findings file. The same provision is highlighted in the full text underneath, with its section citation and criterion. Everything else on this page is plain, unreviewed bill text.
- Sec. 2(a)(1)–(2); Sec. 2(b)(2) · Individual Rights — A1 — Public comments. NIST solicits Federal Register comments on current/proposed security standards and a prototype. Affected: interested commenters and NIST. Enforcement: public solicitation requirement; no adjudicative hearing or private cause of action See in text ↓
- Sec. 2(e)(1)(A)–(B) · Economic Freedom — C1 — Voluntary certification. NIST and CISA coordinate Cloud Security Certification Program, with independent accredited private labs evaluating conformity. Affected: voluntary applicants, labs, and agencies. Enforcement: certification determinations; no general mandatory provider license See in text ↓
- Sec. 2(e)(1)(C)–(D), (2) · Economic Freedom — C2 — Certification tiers and decisions. Certification levels are tiered, certifications publicly listed; labs decide no later than 90 days from applicant submission. Enforcement: certification system, no express fine or fee See in text ↓
- Sec. 2(f)(1)–(3) · Economic Freedom — C3 — Federal contractor disclosures. OMB must update FedRAMP to align to standards, requiring federal-government cloud service providers to disclose specified cloud security information to OMB. Affected: federal cloud contractors and agencies. Enforcement: FedRAMP procurement/authorization framework; no independent fine stated See in text ↓
- Sec. 2(a)(2)(A) · Privacy and Due Process — D1 — Digital identity standards. Standards cover cloud digital credentials and connections between accounts (including potential agentic accounts) and devices; no standalone universal personal identification mandate See in text ↓
- Sec. 2(a)(2)(B)–(C)(i) · Privacy and Due Process — D2 — Security monitoring. Standards cover provider detection/response to suspicious activity, intracloud attacks, and unauthorized east-west traffic; no express government right to read private communications See in text ↓
- Sec. 2(a)(2)(C)(ii)–(iii) · Privacy and Due Process — D3 — Third-party and AI detection. Recommendations encompass vetting/continuous monitoring of integrations and AI anomaly detection. Affected: cloud providers and integrating apps through standards and applicable federal requirements See in text ↓
- Sec. 2(f)(1)–(3) · Privacy and Due Process — D4 — Contractor data disclosures. Required contractor disclosures include aggregate blast radius, traffic monitoring/inspection, policy-based filtering, and third-party access levels See in text ↓
- Sec. 2(e)(1)(C) · Privacy and Due Process — D5 — Public certification database. Certification database public; no separate redaction or appeal procedure created See in text ↓
- Sec. 2(a)(1)–(2)(D) · Government Power — E1 — Initial standards solicitation. Within 180 days NIST solicits comments on cloud identities, monitoring, third-party risks, AI, and blast radius See in text ↓
- Sec. 2(b)(1)–(2) · Government Power — E2 — Prototype and comment. Publish prototype within 50 days of solicitation and request comments See in text ↓
- Sec. 2(c) · Government Power — E3 — Final standards. Publish final standards/methodologies/recommendations within 135 days after prototype See in text ↓
- Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts See in text ↓
- Sec. 2(e)(1) · Government Power — E5 — Certification program deadline. Establish program coordinated with CISA within one year of standards publication See in text ↓
- Sec. 2(f) · Government Power — E6 — FedRAMP update. OMB in coordination with CISA/GSA updates FedRAMP within the same one-year period See in text ↓
- Sec. 2(g)(1)–(3) · Government Power — E7 — Congress report. Report within one year of final standards publication on implementation, private-sector gaps, and possible legislative/administrative remedies; no explicit reporting penalty See in text ↓
- Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity) See in text ↓
Full text (introduced version)
38 of 39 text blocks highlighted. Source: GovInfo, fetched cached.
SECTION 1. SHORT TITLE.
SEC. 2. NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY SPECIAL PUBLICATION ON THE CYBERSECURITY OF CLOUD-BASED INFRASTRUCTURE.
Sec. 2(a)(1)–(2); Sec. 2(b)(2) · Individual Rights — A1 — Public comments. NIST solicits Federal Register comments on current/proposed security standards and a prototype. Affected: interested commenters and NIST. Enforcement: public solicitation requirement; no adjudicative hearing or private cause of action
Sec. 2(a)(2)(A) · Privacy and Due Process — D1 — Digital identity standards. Standards cover cloud digital credentials and connections between accounts (including potential agentic accounts) and devices; no standalone universal personal identification mandate
Sec. 2(a)(2)(B)–(C)(i) · Privacy and Due Process — D2 — Security monitoring. Standards cover provider detection/response to suspicious activity, intracloud attacks, and unauthorized east-west traffic; no express government right to read private communications
Sec. 2(a)(2)(C)(ii)–(iii) · Privacy and Due Process — D3 — Third-party and AI detection. Recommendations encompass vetting/continuous monitoring of integrations and AI anomaly detection. Affected: cloud providers and integrating apps through standards and applicable federal requirements
Sec. 2(a)(1)–(2)(D) · Government Power — E1 — Initial standards solicitation. Within 180 days NIST solicits comments on cloud identities, monitoring, third-party risks, AI, and blast radius
Sec. 2(a)(1)–(2); Sec. 2(b)(2) · Individual Rights — A1 — Public comments. NIST solicits Federal Register comments on current/proposed security standards and a prototype. Affected: interested commenters and NIST. Enforcement: public solicitation requirement; no adjudicative hearing or private cause of action
Sec. 2(a)(1)–(2)(D) · Government Power — E1 — Initial standards solicitation. Within 180 days NIST solicits comments on cloud identities, monitoring, third-party risks, AI, and blast radius
Sec. 2(a)(1)–(2); Sec. 2(b)(2) · Individual Rights — A1 — Public comments. NIST solicits Federal Register comments on current/proposed security standards and a prototype. Affected: interested commenters and NIST. Enforcement: public solicitation requirement; no adjudicative hearing or private cause of action
Sec. 2(a)(2)(A) · Privacy and Due Process — D1 — Digital identity standards. Standards cover cloud digital credentials and connections between accounts (including potential agentic accounts) and devices; no standalone universal personal identification mandate
Sec. 2(a)(2)(B)–(C)(i) · Privacy and Due Process — D2 — Security monitoring. Standards cover provider detection/response to suspicious activity, intracloud attacks, and unauthorized east-west traffic; no express government right to read private communications
Sec. 2(a)(2)(C)(ii)–(iii) · Privacy and Due Process — D3 — Third-party and AI detection. Recommendations encompass vetting/continuous monitoring of integrations and AI anomaly detection. Affected: cloud providers and integrating apps through standards and applicable federal requirements
Sec. 2(a)(1)–(2)(D) · Government Power — E1 — Initial standards solicitation. Within 180 days NIST solicits comments on cloud identities, monitoring, third-party risks, AI, and blast radius
Sec. 2(b)(1)–(2) · Government Power — E2 — Prototype and comment. Publish prototype within 50 days of solicitation and request comments
Sec. 2(b)(1)–(2) · Government Power — E2 — Prototype and comment. Publish prototype within 50 days of solicitation and request comments
Sec. 2(b)(1)–(2) · Government Power — E2 — Prototype and comment. Publish prototype within 50 days of solicitation and request comments
Sec. 2(c) · Government Power — E3 — Final standards. Publish final standards/methodologies/recommendations within 135 days after prototype
Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts
Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts
Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts
Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts
Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts
Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts
Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts
Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts
Sec. 2(e)(1)(A)–(B) · Economic Freedom — C1 — Voluntary certification. NIST and CISA coordinate Cloud Security Certification Program, with independent accredited private labs evaluating conformity. Affected: voluntary applicants, labs, and agencies. Enforcement: certification determinations; no general mandatory provider license
Sec. 2(e)(1)(C)–(D), (2) · Economic Freedom — C2 — Certification tiers and decisions. Certification levels are tiered, certifications publicly listed; labs decide no later than 90 days from applicant submission. Enforcement: certification system, no express fine or fee
Sec. 2(e)(1)(C) · Privacy and Due Process — D5 — Public certification database. Certification database public; no separate redaction or appeal procedure created
Sec. 2(e)(1) · Government Power — E5 — Certification program deadline. Establish program coordinated with CISA within one year of standards publication
Sec. 2(e)(1)(A)–(B) · Economic Freedom — C1 — Voluntary certification. NIST and CISA coordinate Cloud Security Certification Program, with independent accredited private labs evaluating conformity. Affected: voluntary applicants, labs, and agencies. Enforcement: certification determinations; no general mandatory provider license
Sec. 2(e)(1)(C)–(D), (2) · Economic Freedom — C2 — Certification tiers and decisions. Certification levels are tiered, certifications publicly listed; labs decide no later than 90 days from applicant submission. Enforcement: certification system, no express fine or fee
Sec. 2(e)(1)(C) · Privacy and Due Process — D5 — Public certification database. Certification database public; no separate redaction or appeal procedure created
Sec. 2(e)(1) · Government Power — E5 — Certification program deadline. Establish program coordinated with CISA within one year of standards publication
Sec. 2(e)(1)(C)–(D), (2) · Economic Freedom — C2 — Certification tiers and decisions. Certification levels are tiered, certifications publicly listed; labs decide no later than 90 days from applicant submission. Enforcement: certification system, no express fine or fee
Sec. 2(f)(1)–(3) · Economic Freedom — C3 — Federal contractor disclosures. OMB must update FedRAMP to align to standards, requiring federal-government cloud service providers to disclose specified cloud security information to OMB. Affected: federal cloud contractors and agencies. Enforcement: FedRAMP procurement/authorization framework; no independent fine stated
Sec. 2(f)(1)–(3) · Privacy and Due Process — D4 — Contractor data disclosures. Required contractor disclosures include aggregate blast radius, traffic monitoring/inspection, policy-based filtering, and third-party access levels
Sec. 2(f) · Government Power — E6 — FedRAMP update. OMB in coordination with CISA/GSA updates FedRAMP within the same one-year period
Sec. 2(f)(1)–(3) · Economic Freedom — C3 — Federal contractor disclosures. OMB must update FedRAMP to align to standards, requiring federal-government cloud service providers to disclose specified cloud security information to OMB. Affected: federal cloud contractors and agencies. Enforcement: FedRAMP procurement/authorization framework; no independent fine stated
Sec. 2(f)(1)–(3) · Privacy and Due Process — D4 — Contractor data disclosures. Required contractor disclosures include aggregate blast radius, traffic monitoring/inspection, policy-based filtering, and third-party access levels
Sec. 2(f) · Government Power — E6 — FedRAMP update. OMB in coordination with CISA/GSA updates FedRAMP within the same one-year period
Sec. 2(f)(1)–(3) · Economic Freedom — C3 — Federal contractor disclosures. OMB must update FedRAMP to align to standards, requiring federal-government cloud service providers to disclose specified cloud security information to OMB. Affected: federal cloud contractors and agencies. Enforcement: FedRAMP procurement/authorization framework; no independent fine stated
Sec. 2(f)(1)–(3) · Privacy and Due Process — D4 — Contractor data disclosures. Required contractor disclosures include aggregate blast radius, traffic monitoring/inspection, policy-based filtering, and third-party access levels
Sec. 2(f) · Government Power — E6 — FedRAMP update. OMB in coordination with CISA/GSA updates FedRAMP within the same one-year period
Sec. 2(f)(1)–(3) · Economic Freedom — C3 — Federal contractor disclosures. OMB must update FedRAMP to align to standards, requiring federal-government cloud service providers to disclose specified cloud security information to OMB. Affected: federal cloud contractors and agencies. Enforcement: FedRAMP procurement/authorization framework; no independent fine stated
Sec. 2(f)(1)–(3) · Privacy and Due Process — D4 — Contractor data disclosures. Required contractor disclosures include aggregate blast radius, traffic monitoring/inspection, policy-based filtering, and third-party access levels
Sec. 2(f) · Government Power — E6 — FedRAMP update. OMB in coordination with CISA/GSA updates FedRAMP within the same one-year period
Sec. 2(g)(1)–(3) · Government Power — E7 — Congress report. Report within one year of final standards publication on implementation, private-sector gaps, and possible legislative/administrative remedies; no explicit reporting penalty
Sec. 2(g)(1)–(3) · Government Power — E7 — Congress report. Report within one year of final standards publication on implementation, private-sector gaps, and possible legislative/administrative remedies; no explicit reporting penalty
Sec. 2(g)(1)–(3) · Government Power — E7 — Congress report. Report within one year of final standards publication on implementation, private-sector gaps, and possible legislative/administrative remedies; no explicit reporting penalty
Sec. 2(g)(1)–(3) · Government Power — E7 — Congress report. Report within one year of final standards publication on implementation, private-sector gaps, and possible legislative/administrative remedies; no explicit reporting penalty
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Sec. 2(h)(1)–(11) · Government Power — Dates/definitions: Sequential 180-day, 50-day, 135-day, one-year deadlines; certification decisions within 90 days. No appropriation or sunset. External artificial-intelligence and critical-infrastructure definitions and internal terms (blast radius, cloud infrastructure, east-west traffic, intracloud attack, traffic inspection, filtering, third-party integration and workload identity)
Findings source: bill-scores-v2-batch29-findings-2026-11-14.md. Highlights come only from that file; no finding, score, or provision was invented for this page.
What you can do
Contact your U.S. Representative and Senators about this bill.
Find your Representative Contact your Senators
Spot an error on this page? Report it.