Safe and Secure Federal Websites Act of 2017
Latest action · Jan 10, 2017 Referred to the House Committee on Oversight and Government Reform.
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.
- IntroducedJan 10, 2017
- Passed HouseNot reached
- Passed SenateNot reached
- To the PresidentNot reached
- Became lawNot reached
Summary
Safe and Secure Federal Websites Act of 2017
This bill 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. "New Federal PII website" is defined 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.
Beta websites designed for testing and development are exempted if users execute an agreement acknowledging the risks involved.
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 personally identifiable information, including: (1) notice, by 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 cybersecurity center designated by this bill; and (3) any additional actions that the OMB finds necessary and appropriate.
The bill requires: (1) agency heads to ensure that agency actions taken in response to a breach comply with OMB policies and procedures established by this bill; and (2) the OMB to report to Congress, by March 1 of each year, on agency compliance with such policies and procedures.
Cosponsors
Members who signed on, in the order they did.
Committees 1
Where it was sent and what each committee and subcommittee did with it, in order.
| Chamber | Committee | What it did |
|---|---|---|
| House | Oversight and Government Reform Committee | Referred Jan 10, 2017 |
Actions 2
Everything that happened, newest first.
- Jan 10, 2017Introduced in House
- Jan 10, 2017Referred to the House Committee on Oversight and Government Reform.
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.
Constitutional authority
The sponsor’s statement, as printed in the Congressional Record, vol. 163, no. 6, January 10, 2017, page H299.
Related bills 2
Companion bills and other measures the record links to this one.
| Bill | Title | Relationship | Latest action |
|---|---|---|---|
| HR 451 | Safe and Secure Federal Websites Act of 2015 | Reintroduction of | Jan 6, 2016 |
| HR 455 | Safe and Secure Federal Websites Act of 2019 | Reintroduced Bill | Jan 10, 2019 |
Titles 2
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 2017
Subjects
Assigned by the Library of Congress. Policy area: Government Operations and Politics.
Text 1
Each version as it was printed, newest first.
- Jan 10, 2017Introduced in House
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.