Search

Search bills, members, committees and pages...

S. 4564

U.S. SenateIn Senate Committee

Summary

S. 4564, the Maritime Cybersecurity Act, was introduced in the Senate on May 19, 2026 by Sen. Rick Scott (R) with 1 co-sponsor. It was referred to Commerce, Science, And Transportation, and last saw action on May 19, 2026: Read twice and referred to the Committee on Commerce, Science, and Transportation.


Record

Text

S. 4564 has 1 co-sponsor.

sb4564/introduced-in-senate.txt
119 S4564 IS: Maritime Cybersecurity Act
U.S. Senate
2026-05-19
text/xml
EN
Pursuant to Title 17 Section 105 of the United States Code, this file is not subject to copyright protection and is in the public domain.
II 119th CONGRESS 2d Session S. 4564 IN THE SENATE OF THE UNITED STATES May 19, 2026 Mr. Scott of Florida (for himself and Mr. Kim ) introduced the following bill; which was read twice and referred to the Committee on Commerce, Science, and Transportation A BILL
To amend title 46, United States Code, to require the Secretary of the department in which the Coast Guard is operating to assess cybersecurity risks of certain software and hardware used in certain maritime facilities, and for other purposes.
1.
Short title
This Act may be cited as the Maritime Cybersecurity Act .
2.
Cybersecurity vulnerability assessments of certain maritime facility software and hardware
Section 70102 of title 46, United States Code, is amended—
(1)
in subsection (b)—
(A)
in paragraph (1)(C), by inserting (including, with respect to covered facilities, cybersecurity risks of covered software or hardware as provided under subsection (d)(1)) after cybersecurity risks ;
(B)
in paragraph (3), by inserting before the period , except that, for covered facilities, the Secretary shall annually update each such vulnerability assessment with respect to the identification of weaknesses in security and cybersecurity risks of covered software or hardware in accordance with subsection (d)(1) ; and
(C)
in paragraph (4)—
(i)
by striking In lieu and inserting (A) Except as provided in subparagraph (B), in lieu ; and
(ii)
by adding at the end the following:
(B)
In the event that the Secretary accepts an alternative assessment described in subparagraph (A) for a covered facility, the Secretary shall still conduct an assessment under paragraph (1) of weaknesses in security and cybersecurity risks of covered software or hardware used at the facility in accordance with subsection (d)(1).
; and
(2)
by adding at the end the following:
(d)
Assessing cybersecurity risks of covered software or hardware
(1)
Assessments
(A)
In general
Not later than 1 year after the date of enactment of this subsection, and annually thereafter, the Secretary, in coordination with the Director of the Cybersecurity and Infrastructure Security Agency, shall conduct an assessment under subsection (b)(1) with respect to weaknesses in security and cybersecurity risks of covered software or hardware.
(B)
Reducing barriers
The Secretary may conduct an assessment under this paragraph—
(i)
notwithstanding any provision of an end user licensing agreement or other contract that would otherwise hinder such assessment; and
(ii)
without obtaining the consent of any owner or operator of a covered facility, or any other person, notwithstanding any other provision of law.
(2)
Covered facility reports and compliance
(A)
In general
Not later than 180 days after the date of enactment of this subsection, and annually thereafter, the owner or operator of a covered facility shall submit a report to the Secretary that—
(i)
identifies—
(I)
any covered software or hardware that—
(aa)
the owner or operator is using, plans to use, or during the previous year used at the facility; and
(bb)
was manufactured—
(AA)
by a foreign entity of concern or a foreign country of concern;
(BB)
by a company controlled or operated by a foreign entity of concern or a foreign country of concern; or
(CC)
in a foreign country of concern;
(II)
any instance with respect to the facility of a cybersecurity risk resulting in a transportation security incident involving the marine transportation system or any port security system; and
(III)
any other cybersecurity risk with respect to the facility, without regard to whether the risk resulted in a transportation security incident; and
(ii)
except as provided under subparagraph (B)(ii), certifies that any covered software or hardware that the owner or operator is using, plans to use, or during the previous year used has been assessed for consistency with standards of the National Institute of Standards and Technology or equivalent standards within the previous year and the owner or operator has mitigated against any inconsistencies with such standards.
(B)
Compliance
(i)
In general
Except as provided in clause (ii), the owner or operator of a covered facility may not use any covered software or hardware described in subparagraph (A)(ii) for which it cannot certify consistency with standards of the National Institute of Standards and Technology or equivalent standards.
(ii)
Waiver process
The Secretary may issue a waiver to allow an owner or operator of a covered facility to use covered software or hardware for which it cannot certify consistency with standards of the National Institute of Standards and Technology or equivalent standards if the Secretary determines that there is low risk to national security which is outweighed by the benefit to commerce.
(3)
Annual reports to Congress
Not later than 1 year after the date of enactment of this subsection, and annually thereafter, the Secretary, in coordination with the Director of the Cybersecurity and Infrastructure Security Agency, shall provide a report, to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives, on—
(A)
the findings of the most recent assessment under paragraph (1);
(B)
the findings of the most recent reports under paragraph (2);
(C)
any actions taken by the Secretary, or the Director of the Cybersecurity and Infrastructure Security Agency, to mitigate cybersecurity risks with respect to covered software or hardware; and
(D)
any recommendations to Congress on strengthening maritime transportation and port security with respect to cybersecurity risks of covered software or hardware.
(4)
Nondisclosure
Subject to paragraph (5), information in any assessment or report under this subsection shall not be disclosed to the public, pursuant to section 552(b)(3) of the United States Code.
(5)
Coordination
The Secretary shall coordinate, as appropriate, with Federal entities, and any other entities that have an agreement in effect with the Secretary for the sharing of information, to make information compiled by the Secretary under this subsection available to such entities for the purposes of maritime transportation security, cybersecurity risk mitigation, or compliance assistance related to covered facilities or covered software or hardware.
(e)
Definitions
In this section:
(1)
Covered facility
The term covered facility means a facility—
(A)
that is described in subsection (b)(1); and
(B)
to which part 105 or 106 of title 33, Code of Federal Regulations (or successor regulations), applies.
(2)
Covered software or hardware
The term covered software or hardware means any software or hardware that—
(A)
connects to the internet or otherwise poses a cybersecurity risk;
(B)
is used at a covered facility; and
(C)
is used in—
(i)
the marine transportation system, including in a crane manufactured—
(I)
by a foreign entity of concern or a foreign country of concern;
(II)
by a company controlled or operated by a foreign entity of concern or a foreign country of concern; or
(III)
in a foreign country of concern; or
(ii)
a business system that, if compromised or exploited, could result in a transportation security incident;
(iii)
a system whose ownership, operation, maintenance, or control is delegated wholly or in part to any other party; or
(iv)
any other maritime infrastructure determined by the Secretary to be a high cybersecurity risk to the security of any covered facility or to maritime transportation security.
(3)
Cybersecurity vulnerability
The term cybersecurity vulnerability means a characteristic or specific weakness that renders software or hardware or affiliated systems open to exploitation by a given threat or susceptible to a given hazard.
(4)
Foreign country of concern; foreign entity of concern
The terms foreign country of concern and foreign entity of concern have the meanings given such terms in section 10612(a) of the Research and Development, Competition, and Innovation Act ( 42 U.S.C. 19221(a) ).
.

Tracker

The tracker indicates the progress of this legislation as it moves through the legislative process.

  1. Introduced2026-05-19
  2. Passed Senate
  3. Passed House
  4. Conference
  5. To President
  6. Became Law

A bill to amend title 46, United States Code, to require the Secretary of the department in which the Coast Guard is operating to assess cybersecurity risks of certain software and hardware used in certain maritime facilities, and for other purposes.

Sponsors

Sen. Rick Scott (R) sponsors S. 4564, and 1 member has co-sponsored it from the day it was introduced.

Committees

S. 4564 went before 1 committee: Commerce, Science, and Transportation.

Commerce, Science, and Transportation
Commerce, Science, and Transportation
Referred To · May 19, 2026 · 458 Bills

Actions

S. 4564 has taken 2 actions since May 19, 2026.

ChamberAction
May 19, 2026
Senate
Read twice and referred to the Committee on Commerce, Science, and Transportation.Commerce, Science, and Transportation Committee
May 19, 2026
Introduced in Senate

Votes

S. 4564 has not gone to a roll call.

Titles

S. 4564 goes by 3 titles, 1 of them short titles.

  • Maritime Cybersecurity Act — Display Title
  • Maritime Cybersecurity Act — Short Title(s) as Introduced
  • A bill to amend title 46, United States Code, to require the Secretary of the department in which the Coast Guard is operating to assess cybersecurity risks of certain software and hardware used in certain maritime facilities, and for other purposes. — Official Title as Introduced

Classification

The Congressional Research Service files S. 4564 under Transportation and Public Works, one of its 31 policy areas.

CRS Subjects

CRS assigns every bill one policy area from its 31; S. 4564’s is Transportation and Public Works.

s4564/policy-areas.txt
Transportation and Public WorksAgriculture and FoodAnimalsArmed Forces and National SecurityArts, Culture, ReligionCivil Rights and Liberties, Minority IssuesCommerceCongressCrime and Law EnforcementEconomics and Public FinanceEducationEmergency ManagementEnergyEnvironmental ProtectionFamiliesFinance and Financial SectorForeign Trade and International FinanceGovernment Operations and PoliticsHealthHousing and Community DevelopmentImmigrationInternational AffairsLabor and EmploymentLawNative AmericansPublic Lands and Natural ResourcesScience, Technology, CommunicationsSocial WelfareSports and RecreationTaxationWater Resources Development

Source: congress.gov · legiscan.com