Be A Freedom Fighter · Bill Library

HR 10915 — Common-Sense Cloud Security Act

Freedom score: -3 (scale −10 to +10)

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.

  1. 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 ↓
  2. 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 ↓
  3. 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 ↓
  4. 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 ↓
  5. 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 ↓
  6. 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 ↓
  7. 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 ↓
  8. 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 ↓
  9. 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 ↓
  10. 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 ↓
  11. Sec. 2(b)(1)–(2) · Government Power — E2 — Prototype and comment. Publish prototype within 50 days of solicitation and request comments See in text ↓
  12. Sec. 2(c) · Government Power — E3 — Final standards. Publish final standards/methodologies/recommendations within 135 days after prototype See in text ↓
  13. 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 ↓
  14. Sec. 2(e)(1) · Government Power — E5 — Certification program deadline. Establish program coordinated with CISA within one year of standards publication See in text ↓
  15. 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 ↓
  16. 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 ↓
  17. 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.

[Congressional Bills 119th Congress] [From the U.S. Government Publishing Office] [H.R. 10915 Introduced in House (IH)] <DOC> 119th CONGRESS 2d Session H. R. 10915 To require the Director of the National Institute of Standards and Technology to develop new standards, methodologies, and recommendations with respect to the cybersecurity of cloud-based infrastructure, and for other purposes. _______________________________________________________________________ IN THE HOUSE OF REPRESENTATIVES October 26, 2026 Mr. McCormick introduced the following bill; which was 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 _______________________________________________________________________ A BILL To require the Director of the National Institute of Standards and Technology to develop new standards, methodologies, and recommendations with respect to the cybersecurity of cloud-based infrastructure, and for other purposes. Be it enacted by the Senate and House of Representatives of the United States of America in Congress assembled,

SECTION 1. SHORT TITLE.

This Act may be cited as the ``Common-Sense Cloud Security Act''.

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

(a) In General.--Not later than 180 days after the date of the enactment of this Act, the Director of the National Institute of Standards and Technology (in this section referred to as the ``Director'') shall solicit through the Federal Register public comment on the following:

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

(1) The existing standards, methodologies, and recommendations of the Institute with respect to 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

(2) Developing new standards, methodologies, and recommendations of the Institute with respect to such cybersecurity, that include the following: (A) Standards for managing and securing the digital identities utilized with respect to such infrastructure, including standards to link logins and other access credentials for an account, which may be an agentic account, to a device. (B) Standards for a system through which cloud service providers are able to monitor and address security alerts and unauthorized or malicious activity. (C) Recommendations regarding the following: (i) Addressing the prevention, detection, and mitigation of intracloud attacks and unauthorized east-west traffic. (ii) Vetting, authorizing, and continuously monitoring third-party application integrations and software-as-a-service applications, to ensure that such integrations and applications have appropriate access to the cloud environments of such providers. (iii) Adopting artificial intelligence tools for the detection of unusual or suspicious activity in such environments, in a manner that resembles such adoption by the Federal Government and other public sector entities. (D) A methodology by which such a provider is able to determine the blast radius of such provider.

Sec. 2(b)(1)–(2) · Government Power — E2 — Prototype and comment. Publish prototype within 50 days of solicitation and request comments

(b) Prototype.--Not later than 50 days after the date of the solicitation under subsection (a), the Director shall carry out the following:

Sec. 2(b)(1)–(2) · Government Power — E2 — Prototype and comment. Publish prototype within 50 days of solicitation and request comments

(1) Publish in the Federal Register a prototype of the standards, methodologies, and recommendations referred to in paragraph (2) of such subsection.

Sec. 2(b)(1)–(2) · Government Power — E2 — Prototype and comment. Publish prototype within 50 days of solicitation and request comments

(2) Solicit through the Federal Register public comment on such prototype.

Sec. 2(c) · Government Power — E3 — Final standards. Publish final standards/methodologies/recommendations within 135 days after prototype

(c) Final Version.--Not later than 135 days after the publication of the prototype of the standards, methodologies, and recommendations under subsection (b), the Director shall publish in the Federal Register a final version of such standards, methodologies, and recommendations.

Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts

(d) Consultation.--In developing the standards, methodologies, and recommendations referred to in paragraph (2) of subsection (a), the Director shall consult with the following:

Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts

(1) The Secretary of Defense.

Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts

(2) The National Cyber Director.

Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts

(3) The Director of the Cybersecurity and Infrastructure Security Agency.

Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts

(4) Cloud service providers.

Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts

(5) Owners and operators of critical infrastructure.

Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts

(6) Associations of entities in critical infrastructure sectors, such as banking and finance and public health and health care.

Sec. 2(d)(1)–(7) · Government Power — E4 — Consultation. Consult Defense Secretary, National Cyber Director, CISA Director, cloud providers, critical infrastructure, trade associations, experts

(7) Entities that satisfy the following requirements (as determined by the Director): (A) Are academic or not-for-profit. (B) Have expertise in cloud security and artificial intelligence governance.

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

(e) Certification.--

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

(1) In general.--Not later than one year after the publication of the final version of the standards, methodologies, and recommendations under subsection (c), the Director, in coordination with Director of the Cybersecurity and Infrastructure Security Agency, shall establish a program, to be known as the ``Cloud Security Certification Program'' (in this section referred to as the ``Program''), that satisfies the following requirements: (A) Is voluntary. (B) Is modeled to the extent practicable on the IT Security Validation Programs of the National Institute of Standards and Technology, such that third-party, independent, private-sector, accredited testing laboratories conduct evaluations and make determinations on whether to certify an entity's conformance with such standards, methodologies, and recommendations, including with respect to the following: (i) Blast radius. (ii) Intracloud attack. (iii) Third-party application integration. (iv) Workload identity. (C) Includes a public database of each such certification. (D) Includes tiered certification levels.

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

(2) Deadline.--Not later than 90 days after the date on which an entity submits to a laboratory under the Program an application for a certification described in subparagraph (B) of paragraph (1), such laboratory shall make for such entity a determination under such subparagraph.

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

(f) Federal Risk and Authorization Management Program.--Not later than one year after the publication of the final version of the standards, methodologies, and recommendations under subsection (c), the Director of the Office of Management and Budget, in coordination with the Director of the Cybersecurity and Infrastructure Security Agency and the Administrator of General Services, shall update the Federal Risk and Authorization Management Program to conform with such standards, methodologies, and recommendations, including by requiring each private sector entity that provides cloud services to the Federal Government to disclose to the Director of the Office information relating to the following:

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

(1) The aggregate blast radius of such entity.

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

(2) East-west traffic monitoring, network traffic inspection, and policy-based filtering conducted by such entity.

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

(3) The scope and access levels of any third-party application integrations in the cloud environments of such entity.

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

(g) Report.--Not later than one year after the publication of the final version of the standards, methodologies, and recommendations under subsection (c), the Director shall submit to the Committee on Science, Space, and Technology of the House of Representatives and the Committee on Commerce, Science, and Transportation of the Senate a report that includes information relating to the following:

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

(1) Implementation by Federal departments and agencies of such standards, methodologies, and recommendations.

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

(2) The gaps and challenges, if any, with respect to the adoption of such standards, methodologies, and recommendations by private sector entities.

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

(3) Recommendations of the Director for legislative or administrative action with respect to the cybersecurity of cloud-based infrastructure.

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)

(h) Definitions.--In this section:

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)

(1) Artificial intelligence.--The term ``artificial intelligence'' has the meaning given such term in section 5002 of the National Artificial Intelligence Initiative Act of 2020 (15 U.S.C. 9401).

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)

(2) Blast radius.--The term ``blast radius'' means the maximum potential scope of unauthorized data access or system compromise from a compromised workload, data asset, or credential in a cloud environment.

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)

(3) Cloud-based infrastructure.--The term ``cloud-based infrastructure'' means computing, storage, and networking services, including infrastructure-as-a-service, platform-as-a- service, and software-as-a-service, provided through a public, private, or hybrid cloud environment.

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)

(4) Critical infrastructure.--The term ``critical infrastructure'' has the meaning given such term in section 1016 of the USA PATRIOT Act (42 U.S.C. 5195c).

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)

(5) Critical infrastructure sectors.--The term ``critical infrastructure sectors'' has the meaning given such term in section 2001 of the Homeland Security Act of 2002 (6 U.S.C. 601).

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)

(6) East-west traffic.--The term ``east-west traffic'' means network traffic between virtual machines, containers, or services in a cloud data center or cloud environment.

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)

(7) Intracloud attack.--The term ``intracloud attack'' means an action by a threat actor to exploit a vulnerability or misconfiguration of a cloud environment and conduct unauthorized lateral movement, privilege escalation, or data exfiltration with respect to such environment.

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)

(8) Network traffic inspection.--The term ``network traffic inspection'' means the monitoring, examination, and analysis of network communications to identify, assess, log, or respond to malicious, unauthorized, or anomalous activity or support the enforcement of a cybersecurity policy.

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)

(9) Policy-based filtering.--The term ``policy-based filtering'' means the application of a predefined security policy to permit, deny, restrict, log, or otherwise control network communications based on the source, destination, or content of such communications or an indicator of malicious or unauthorized activity.

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)

(10) Third-party application integration.--The term ``third-party application integration'' means the ability of a third party or external software service to interact with a cloud environment through a standardized authorization protocol or application programming interface.

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)

(11) Workload identity.--The term ``workload identity'' means the digital credentials and tokens utilized by a nonhuman entity to authenticate or access a cloud resource. <all>

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.