H.R. 328House116th Congress (2019-2021)Passed House

Hack Your State Department Act

Sponsored by Ted LieuRep. Ted Lieu (D-CA)
Introduced January 8, 2019

AI-Generated Summary

Updated April 14, 2026 at 12:01 AM UTC

The Hack Your State Department Act requires the Secretary of State to create a public Vulnerability Disclosure Process within 180 days and to launch a short‑term bug bounty pilot within a year. The goal is to improve the State Department’s cybersecurity by giving researchers clear rules for finding and reporting flaws in internet‑facing systems and by offering compensation for valid discoveries. The law also mandates regular reporting to Congress on the program’s results. It mainly affects the State Department, security researchers, and any companies or individuals participating in the bug bounty program.

Key Provisions

  • Design and publish a Vulnerability Disclosure Process within 180 days, including guidelines, reporting methods, responsible offices, and coordination with the Attorney General and the Department of Defense;
  • Require annual reports to the House Foreign Affairs and Senate Foreign Relations committees for six years detailing numbers, severity, remediation, and resources related to disclosed vulnerabilities;
  • Establish a bug bounty pilot program within one year that pays rewards for previously unknown vulnerabilities in public‑facing State Department IT, with contracts for management, eligibility registration, and DOJ/DoD consultation;
  • Limit the bug bounty pilot to a maximum of one year and require a post‑pilot report to Congress covering participation, vulnerabilities found, remediation, compensation types, and lessons learned.

Legislative Activity

Stay on top of the latest movement without scrolling through every action

11 earlier actions
SenateIntro Referral Latest Action

Received in the Senate and Read twice and referred to the Committee on Foreign Relations.

January 23, 2019

View full timeline
HouseIntro Referral

Introduced in House

January 8, 2019

HouseIntro Referral

Referred to the House Committee on Foreign Affairs.

January 8, 2019

HouseIntro Referral

Sponsor introductory remarks on measure. (CR H981)

January 22, 2019

HouseFloor

Mr. Engel moved to suspend the rules and pass the bill.

January 22, 2019 • 5:22 PM

HouseFloor

Considered under suspension of the rules. (consideration: CR H979-981)

January 22, 2019 • 5:22 PM

HouseFloor

DEBATE - The House proceeded with forty minutes of debate on H.R. 328.

January 22, 2019 • 5:22 PM

HouseFloor

At the conclusion of debate, the Yeas and Nays were demanded and ordered. Pursuant to the provisions of clause 8, rule XX, the Chair announced that further proceedings on the motion would be postponed.

January 22, 2019 • 5:33 PM

HouseFloor

Considered as unfinished business. (consideration: CR H982-983)

January 22, 2019 • 7:01 PM

HouseFloor

Passed/agreed to in House: On motion to suspend the rules and pass the bill Agreed to by the Yeas and Nays: (2/3 required): 377 - 3 (Roll no. 45).(text: CR H979-980)

January 22, 2019 • 7:11 PM

HouseFloor

On motion to suspend the rules and pass the bill Agreed to by the Yeas and Nays: (2/3 required): 377 - 3 (Roll no. 45). (text: CR H979-980)

January 22, 2019 • 7:11 PM

HouseFloor

Motion to reconsider laid on the table Agreed to without objection.

January 22, 2019 • 7:11 PM

SenateIntro Referral

Received in the Senate and Read twice and referred to the Committee on Foreign Relations.

January 23, 2019

Floor Debate

12 members

What members said about H.R. 328 on the floor

4 Republicans8 Democrats
F. James Sensenbrenner, Jr.

Madam Speaker, due to a scheduled medical procedure, I was physically absent from the House of Representatives from January 10, 2019 to February 5, 2019. During that time, I missed 44 recorded votes.…

Eliot L. Engel
Rep. Eliot L. EngelD-NY-16 · Jan 22, 2019

Mr. Speaker, I move to suspend the rules and pass the bill (H.R. 328) to require the Secretary of State to design and establish a Vulnerability Disclosure Process (VDP) to improve Department of State…

Ted Lieu
Rep. Ted LieuD-CA-33 · Jan 22, 2019

Mr. Speaker, I thank Ranking Member McCaul for his support of this legislation and I thank Chairman Engel for his leadership of the House Foreign Affairs Committee. Mr. Speaker, I rise in support of…

Michael T. McCaul
Rep. Michael T. McCaulR-TX-10 · Jan 22, 2019

Mr. Speaker, I yield myself as much time as I may consume. Mr. Speaker, I rise in support of the Hack Your State Department Act, which will help address lingering cybersecurity gaps at the Department…

Rosa L. DeLauro
Rep. Rosa L. DeLauroD-CT-3 · Jan 24, 2019

Madam Speaker, I had an unavoidable family commitment and so I missed Roll Call vote number 44 regarding the ``NATO Support Act (H.R. 676).'' Had I been present, I would have voted ``yes.'' I missed…

Show 8 more
Eric Swalwell
Rep. Eric SwalwellD-CA-15 · Feb 28, 2019

Madam Speaker, I missed votes on Monday, February 25. Had I been present, I would have voted as follows: Roll Call Vote Number 88 (Passage of H.R. 539, the Innovators to Entrepreneurs Act): YES; Roll…

James P. McGovern
Rep. James P. McGovernD-MA-2 · Jan 23, 2019

Madam Speaker, I was unavoidably absent on Tuesday, January 22, 2019. On Roll Vote No. 44, on passage of H.R. 676--NATO Support Act, if I had been present I would have voted YES. On Roll Call Vote…

Katie Porter
Rep. Katie PorterD-CA-45 · Jan 28, 2019

Madam Speaker, I was unable to be present for votes on Tuesday, January 22, 2019. Had I been present, I would have voted as follows: Roll Call Vote Number 44 (Passage of H.R. 676, the NATO Support…

Linda T. Sánchez
Rep. Linda T. SánchezD-CA-38 · Jan 24, 2019

Madam Speaker, on Tuesday, January 22, 2019 on Roll Call Numbers 44 and 45, the NATO Support Act, H.R. 676, and the Hack Your State Department Act, H.R. 328, I was unavoidably detained and missed the…

Eric Swalwell
Rep. Eric SwalwellD-CA-15 · Jan 24, 2019

Madam Speaker, I missed votes on Tuesday, January 22. Had I been present, I would have voted as follows: Roll Call Vote Number 44 (Passage of H.R. 676, the NATO Support Act): YES; and Roll Call Vote…

Janice D. Schakowsky
Rep. Janice D. SchakowskyD-IL-9 · Jan 23, 2019

Madam Speaker, on January 22, 2019, I missed recorded votes No. 44 and No. 45 due to travel delays. Had I been present, on Roll Call No. 44, I would have voted YEA (Passage of H.R. 328); and on Roll…

Greg Walden
Rep. Greg WaldenR-OR-2 · Jan 22, 2019

Mr. Speaker, I was unable to be present for votes on January 22nd due to unavoidable travel delays. Had I been present, I would have voted ``yea'' on rollcall No. 44 and ``yea'' on rollcall No. 45.

Ron Estes
Rep. Ron EstesR-KS-4 · Jan 23, 2019

Madam Speaker, I was not present for Roll Call vote No. 45 on H.R. 328. Had I been present, I would have voted ``yea.''

Bill Text

3 versions available

Reading Mode
Latest
Referred in SenateIssued January 23, 2019

IIB

116th CONGRESS

1st Session

H. R. 328

IN THE SENATE OF THE UNITED STATES

January 23 (legislative day, January 22), 2019

Received; read twice and referred to the Committee on Foreign Relations

AN ACT

To require the Secretary of State to design and establish a Vulnerability Disclosure Process (VDP) to improve Department of State cybersecurity and a bug bounty program to identify and report vulnerabilities of internet-facing information technology of the Department of State, and for other purposes.

1.

Short title

This Act may be cited as the Hack Your State Department Act.

2.

Definitions

In this Act:

(1)

Bug bounty program

The term bug bounty program means a program under which an approved individual, organization, or company is temporarily authorized to identify and report vulnerabilities of internet-facing information technology of the Department in exchange for compensation.

(2)

Department

The term Department means the Department of State.

(3)

Information technology

The term information technology has the meaning given such term in section 11101 of title 40, United States Code.

(4)

Secretary

The term Secretary means the Secretary of State.

3.

Department of State Vulnerability Disclosure Process

(a)

In general

Not later than 180 days after the date of the enactment of this Act, the Secretary shall design, establish, and make publicly known a Vulnerability Disclosure Process (VDP) to improve Department cybersecurity by—

(1)

providing security researchers with clear guidelines for—

(A)

conducting vulnerability discovery activities directed at Department information technology; and

(B)

submitting discovered security vul­ner­a­bil­i­ties to the Department; and

(2)

creating Department procedures and infrastructure to receive and fix discovered vul­ner­a­bil­i­ties.

(b)

Requirements

In establishing the VDP pursuant to paragraph (1), the Secretary shall—

(1)

identify which Department information technology should be included in the process;

(2)

determine whether the process should differentiate among and specify the types of security vulnerabilities that may be targeted;

(3)

provide a readily available means of reporting discovered security vulnerabilities and the form in which such vulnerabilities should be reported;

(4)

identify which Department offices and positions will be responsible for receiving, prioritizing, and addressing security vulnerability disclosure reports;

(5)

consult with the Attorney General regarding how to ensure that individuals, organizations, and companies that comply with the requirements of the process are protected from prosecution under section 1030 of title 18, United States Code, and similar provisions of law for specific activities authorized under the process;

(6)

consult with the relevant offices at the Department of Defense that were responsible for launching the 2016 Vulnerability Disclosure Program, Hack the Pentagon, and subsequent Department of Defense bug bounty programs;

(7)

engage qualified interested persons, including nongovernmental sector representatives, about the structure of the process as constructive and to the extent practicable; and

(8)

award contracts to entities, as necessary, to manage the process and implement the remediation of discovered security vulnerabilities.

(c)

Annual reports

Not later than 180 days after the establishment of the VDP under subsection (a) and annually thereafter for the next six years, the Secretary of State shall submit to the Committee on Foreign Affairs of the House of Representatives and the Committee on Foreign Relations of the Senate a report on the VDP, including information relating to the following:

(1)

The number and severity, in accordance with the National Vulnerabilities Database of the National Institute of Standards and Technology, of security vulnerabilities reported.

(2)

The number of previously unidentified security vulnerabilities remediated as a result.

(3)

The current number of outstanding previously unidentified security vulnerabilities and Department of State remediation plans.

(4)

The average length of time between the reporting of security vulnerabilities and remediation of such vulnerabilities.

(5)

The resources, surge staffing, roles, and responsibilities within the Department used to implement the VDP and complete security vulnerability remediation.

(6)

Any other information the Secretary determines relevant.

4.

Department of State bug bounty pilot program

(a)

Establishment of pilot program

(1)

In general

Not later than one year after the date of the enactment of this Act, the Secretary shall establish a bug bounty pilot program to minimize security vulnerabilities of internet-facing information technology of the Department.

(2)

Requirements

In establishing the pilot program described in paragraph (1), the Secretary shall—

(A)

provide compensation for reports of previously unidentified security vulnerabilities within the websites, applications, and other internet-facing information technology of the Department that are accessible to the public;

(B)

award contracts to entities, as necessary, to manage such pilot program and for executing the remediation of security vul­ner­a­bil­i­ties identified pursuant to subparagraph (A);

(C)

identify which Department information technology should be included in such pilot program;

(D)

consult with the Attorney General on how to ensure that individuals, organizations, or companies that comply with the requirements of such pilot program are protected from prosecution under section 1030 of title 18, United States Code, and similar provisions of law for specific activities authorized under such pilot program;

(E)

consult with the relevant offices at the Department of Defense that were responsible for launching the 2016 Hack the Pentagon pilot program and subsequent Department of Defense bug bounty programs;

(F)

develop a process by which an approved individual, organization, or company can register with the entity referred to in subparagraph (B), submit to a background check as determined by the Department, and receive a determination as to eligibility for participation in such pilot program;

(G)

engage qualified interested persons, including nongovernmental sector representatives, about the structure of such pilot program as constructive and to the extent practicable; and

(H)

consult with relevant United States Government officials to ensure that such pilot program complements persistent network and vulnerability scans of the Department of State’s internet-accessible systems, such as the scans conducted pursuant to Binding Operational Directive BOD–15–01.

(3)

Duration

The pilot program established under paragraph (1) should be short-term in duration and not last longer than one year.

(b)

Report

Not later than 180 days after the date on which the bug bounty pilot program under subsection (a) is completed, the Secretary shall submit to the Committee on Foreign Relations of the Senate and the Committee on Foreign Affairs of the House of Representatives a report on such pilot program, including information relating to—

(1)

the number of approved individuals, organizations, or companies involved in such pilot program, broken down by the number of approved individuals, organizations, or companies that—

(A)

registered;

(B)

were approved;

(C)

submitted security vulnerabilities; and

(D)

received compensation;

(2)

the number and severity, in accordance with the National Vulnerabilities Database of the National Institute of Standards and Technology, of security vulnerabilities reported as part of such pilot program;

(3)

the number of previously unidentified security vulnerabilities remediated as a result of such pilot program;

(4)

the current number of outstanding previously unidentified security vulnerabilities and Department remediation plans;

(5)

the average length of time between the reporting of security vulnerabilities and remediation of such vulnerabilities;

(6)

the types of compensation provided under such pilot program; and

(7)

the lessons learned from such pilot program.

Passed the House of Representatives January 22, 2019.

Karen L. Haas,

Clerk