HR 3635 · 113th Congress 2013–2015, ended

Safe and Secure Federal Websites Act of 2014

Fact sheet

Latest action · Jul 29, 2014 Received in the Senate and Read twice and referred to the Committee on Homeland Security and Governmental Affairs.

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. IntroducedDec 3, 2013
  2. Passed HouseJul 28, 2014
  3. Passed SenateNot reached
  4. To the PresidentNot reached
  5. Became lawNot reached

Summary

Safe and Secure Federal Websites Act of 2014 - (Sec. 2) Prohibits a federal agency from deploying or making available to the public a new federal personally identifiable information website (new Federal PII Website) until the chief information officer of the agency submits a certification to Congress that the website is fully functional and secure, as those terms are defined by this Act. Defines "new Federal PII website" as a website that: (1) is operated by (or under contract with) an agency; (2) elicits, collects, stores, or maintains personally identifiable information (i.e., information that can be used to identify an individual, such as a social security number, a date and place of birth, a mother's maiden name, biometric records, or other information linked to an individual); and (3) is first made accessible to the public and collects or stores personally identifiable information on or after October 1, 2012.

Exempts beta websites designed for testing and development if users execute an agreement acknowledging the risks involved.

(Sec. 3) Directs the Director of the Office of Management and Budget (OMB) to establish and oversee policies and procedures for federal agencies to follow in the event of a breach of information security involving the disclosure of personally identifiable information, including: (1) notice, not later than 72 hours after discovery of a breach or possible breach, to individuals whose personally identifiable information could be compromised as a result of such breach; (2) timely reporting to a federal cyber security center designated by this Act; and (3) any additional actions that the Director finds necessary and appropriate.

Requires: (1) agency heads to ensure that agency actions taken in response to a breach comply with OMB policies and procedures established by this Act; and (2) the OMB Director to report to Congress, not later than March 1 of each year, on agency compliance with such policies and procedures.

Cosponsors 126

Members who signed on, in the order they did. Signatures ran from Jan 8, 2014 to Apr 29, 2014.

SeatCosponsorSigned on
R-MIBill HuizengaJan 8, 2014
R-WYCynthia M. LummisJan 8, 2014
R-MIDan BenishekJan 8, 2014
R-GAJack KingstonJan 8, 2014
R-SCJeff DuncanJan 8, 2014
R-SCJoe WilsonJan 8, 2014
R-GALynn A. WestmorelandJan 8, 2014
R-NCMark MeadowsJan 8, 2014
R-TNMarsha BlackburnJan 8, 2014
R-MNMichele BachmannJan 8, 2014
R-ALMo BrooksJan 8, 2014
R-FLTed S. YohoJan 8, 2014
R-MITim WalbergJan 8, 2014
R-OKTom ColeJan 8, 2014
R-KYAndy BarrJan 9, 2014

Actions 13

Everything that happened, newest first.

  1. Jul 29, 2014Received in the Senate and Read twice and referred to the Committee on Homeland Security and Governmental Affairs.
  2. Jul 28, 2014Considered under suspension of the rules. (consideration: CR H6935-6936)
  3. Jul 28, 2014DEBATE - The House proceeded with forty minutes of debate on H.R. 3635.
  4. Jul 28, 2014Motion to reconsider laid on the table Agreed to without objection.
  5. Jul 28, 2014Mr. Bentivolio moved to suspend the rules and pass the bill, as amended.

Subjects

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

Text 4

Each version as it was printed, newest first.

  1. Jul 29, 2014Referred in Senate
  2. Jul 28, 2014Engrossed in House
  3. Jul 28, 2014Reported in House
  4. Dec 3, 2013Introduced 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.