HR 451 · 114th Congress 2015โ€“2017, ended

Safe and Secure Federal Websites Act of 2015

Latest action · Jan 6, 2016 Placed on the Union Calendar, Calendar No. 293.

Progress

Where this bill reached, and when. A stage with no date was not reached; one that failed a vote and later carried shows the date it carried.

  1. IntroducedJan 21, 2015
  2. Passed HouseNot reached
  3. Passed SenateNot reached
  4. To the PresidentNot reached
  5. Became lawNot reached

Summary

Safe and Secure Federal Websites Act of 2015

This bill establishes security and privacy requirements for new federal websites that collect personally identifiable information (PII) (i.e., information that can be used to distinguish or trace the identity of an individual or that is linked or linkable to an individual).

(Sec. 2) A federal agency may not deploy or make available to the public a new federal PII website until the agency's chief information officer (CIO) certifies to Congress that the website is fully functional and secure. The CIO must make such certification within 90 days after enactment of this Act. After such 90-day period, any new federal PII website that has not been certified must be rendered inaccessible until certification is submitted.

The prohibition does not apply to a website that is: (1) operated entirely by an entity that is independent of the federal government, or (2) in a development or testing phase (beta website). The exemption for beta websites applies only if: (1) a member of the public may access PII-related portions of the website only after executing an agreement that acknowledges the risks involved; and (2) no agency compelled, enjoined, or otherwise provided incentives for a member of the public to access such website.

The bill defines a "new federal PII website" as a website that: (1) is operated by (or under contract with) an agency; (2) elicits, collects, stores, or maintains PII and is accessible to the public; and (3) is first made accessible to the public and collects or stores PII on or after October 1, 2012. The bill also sets forth requirements that must be met to deem a new federal PII website as "secure."

(Sec. 3) The Director of the Office of Management and Budget (OMB) must establish and oversee policies and procedures for federal agencies to follow in the event of a breach of information security involving the disclosure of PII, including: (1) notice, not later than 72 hours after discovery of a breach or possible breach, to individuals whose PII could be compromised; and (2) timely reporting to a federal cybersecurity center designated by the OMB and defined in this Act.

Agency heads must ensure that agency actions taken in response to a breach of information security involving the disclosure of PII comply with OMB policies and procedures established by this Act. The OMB must report to Congress, not later than March 1 of each year, on agency compliance with such policies and procedures.

A "federal cybersecurity center" is defined to include: (1) the Department of Defense Cyber Crime Center, (2) the Intelligence Community Incident Response Center, (3) the U.S. Cyber Command Joint Operations Center, (4) the National Cyber Investigative Task Force, (5) the Central Security Service Threat Operations Center of the National Security Agency, (6) the U.S. Computer Emergency Readiness Team, and (7) any center that the OMB determines is appropriate to carry out privacy breach notice and reporting requirements.

Cosponsors 38

Members who signed on, in the order they did. Signatures ran from Jan 22, 2015 to May 18, 2015.

SeatCosponsorSigned on
R-TNScott DesJarlaisJan 22, 2015
R-CADana RohrabacherJan 28, 2015
R-GALynn A. WestmorelandJan 28, 2015
R-FLBill PoseyFeb 2, 2015
R-KYBrett GuthrieFeb 2, 2015
R-WYCynthia M. LummisFeb 2, 2015
R-MIDan BenishekFeb 2, 2015
R-WIF. James Sensenbrenner, Jr.Feb 2, 2015
R-MNJohn KlineFeb 2, 2015
R-TNMarsha BlackburnFeb 2, 2015
R-PAMike KellyFeb 2, 2015
R-VARobert HurtFeb 2, 2015
R-TXBlake FarentholdFeb 3, 2015
R-SCJoe WilsonFeb 3, 2015
R-OHRobert E. LattaFeb 3, 2015
R-INTodd RokitaFeb 3, 2015
R-OKTom ColeFeb 3, 2015
R-CAKen CalvertFeb 4, 2015
R-ILPeter J. RoskamFeb 4, 2015
R-ILAaron SchockFeb 10, 2015
R-FLDennis A. RossFeb 10, 2015
R-PAGlenn ThompsonFeb 10, 2015
R-VAH. Morgan GriffithFeb 10, 2015
R-KSLynn JenkinsFeb 10, 2015
R-IASteve KingFeb 10, 2015
R-OKFrank D. LucasFeb 25, 2015
R-COMike CoffmanFeb 25, 2015
R-NJRodney P. FrelinghuysenFeb 25, 2015
R-OHBill JohnsonMar 16, 2015
R-TNDavid P. RoeMar 16, 2015
R-NDKevin CramerMar 16, 2015
R-NVMark E. AmodeiMar 16, 2015
R-TXJohn R. CarterMay 14, 2015
R-SCMark SanfordMay 14, 2015
R-NYChris CollinsMay 18, 2015
R-AZDavid SchweikertMay 18, 2015
R-PALou BarlettaMay 18, 2015
R-NCRobert PittengerMay 18, 2015

Committees 1

Where it was sent and what each committee and subcommittee did with it, in order.

ChamberCommitteeWhat it did
HouseOversight and Government Reform Committee
Referred Jan 21, 2015Markup May 19, 2015Reported Jan 7, 2016

Actions 6

Everything that happened, newest first.

  1. Jan 6, 2016Reported (Amended) by the Committee on Oversight and Government Reform. H. Rept. 114-390.
  2. Jan 6, 2016Placed on the Union Calendar, Calendar No. 293.
  3. May 19, 2015Committee Consideration and Mark-up Session Held.
  4. May 19, 2015Ordered to be Reported (Amended) by Voice Vote.
  5. Jan 21, 2015Introduced in House

Research

What has been written about this bill: committee reports, cost estimates, the sponsor’s authority statement, printed hearings and the Congressional Research Service’s work.

Committee report

Congressional Budget Office cost estimate

  1. May 29, 2015H.R. 451, Safe and Secure Federal Websites Act of 2015As ordered reported by the House Committee on Oversight and Government Reform on May 19, 2015

Constitutional authority

Congress has the power to enact this legislation pursuant to the following: Article 1, Section 8, Clause 18, which states the Congress shall have the power ``to make all laws which shall be necessary and proper for carrying into execution the foregoing powers, and all other powers vested by this Constitution in the government of the United States, or in any department or officer thereof''

The sponsor’s statement, as printed in the Congressional Record, vol. 161, no. 10, January 21, 2015, page H481.

Related bills 1

Companion bills and other measures the record links to this one.

BillTitleRelationshipLatest action
HR 404Safe and Secure Federal Websites Act of 2017Reintroduced BillJan 10, 2017

Titles 3

Every title it has carried, official and short, at each stage.

Official Title as Introduced
To ensure the functionality and security of new Federal websites that collect personally identifiable information, and for other purposes.
Short Titles as Introduced
Safe and Secure Federal Websites Act of 2015
Short Titles as Reported to House
Safe and Secure Federal Websites Act of 2015

Subjects

Assigned by the Library of Congress. Policy area: Government Operations and Politics.

Text 2

Each version as it was printed, newest first.

  1. Jan 6, 2016Reported in House
  2. Jan 21, 2015Introduced in House

Support LegiList

This page is free, carries no paywall, and is built and maintained by one person. If the record here is useful to you, a few dollars keeps it going.

Processed by Stripe in a separate window. LegiList never sees card details.

Everything here is as published by Congress: the summary is the Congressional Research Service's, the action wording is the clerks', and the subjects are the Library of Congress's. How far it got is read from the actions themselves, taking the most recent one of each kind, so a bill that failed a vote and later passed is shown as having passed. Records come from this bill on Congress.gov and govinfo.gov; cost estimates are the Congressional Budget Office's, and the hearings are the printed hearings GovInfo publishes, which can appear months after the hearing.