PlainBillCongress, translated.Legislation. Context. Public interest.Referred to the House Committee on Oversight and Government Reform.
Congressional Research Service
Version 00 · Introduced in House · Jan 10, 2017
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.
Showing the opening paragraphs of the official summary.
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.
People & committees
Rep. Fleischmann, Charles J. "Chuck" [R-TN-3] · R–TN
Legislative record
A procedural vote is different from passage. Passage in one chamber does not establish enactment. Explore the glossary.
Referred to the House Committee on Oversight and Government Reform.
Introduced in House
Introduced in House
Primary sources
Text links open the official source. We currently store references to these documents.
Source last updated: Aug 11, 2025. Consult Congress.gov for the current record.
AI Conversation Starters
Choose a perspective, copy a prompt, and paste it into your preferred AI. Each prompt includes the bill version and available official source links, and asks for counterarguments as well as supporting evidence.
Analyze H.R.404 as objectively as possible. Explain its main provisions, who would be affected, possible benefits and harms, implementation, exceptions, and uncertainties. Present the strongest arguments for and against it, and identify evidence needed to assess its public impact.
Examine H.R.404 through a progressive lens, focusing on fairness, access, economic inequality, and effects on vulnerable communities. Explain potential benefits, costs, and unintended consequences. Consider the strongest counterarguments and distinguish stated goals from demonstrated outcomes.
Examine H.R.404 through a conservative lens, focusing on fiscal responsibility, institutional stability, federalism, and the scope of government. Explain potential benefits, costs, and unintended consequences. Consider the strongest counterarguments and any provisions that challenge this perspective.
Examine H.R.404 through a civil-liberties and limited-government lens. Consider individual rights, privacy, voluntary choice, accountability, and government power. Explain tradeoffs, possible safeguards, and the strongest counterarguments without assuming the proposal is beneficial or harmful.