Judicial Watch: HHS Documents Reveal Serious Behind-the-Scenes Security Concerns

The Stench of ObamaCare
The Stench of ObamaCare
Judicial Watch
Judicial Watch

Washington, DC-(Ammoland.com)- Judicial Watch today released 944 pages of Department of Health and Human Services (HHS) records showing that the Obamacare website was launched despite serious concerns by its security testing contractor, Mitre Corporation, as well as internal executive-level apprehension about security.

Judicial Watch obtained the HHS documents in response to a court order in a Freedom of Information Act (FOIA) lawsuit (Judicial Watch v. U.S. Department of Health and Human Services (No. 1:14-cv-00430)). The lawsuit was filed in March 2014 after HHS failed to respond to a December 20, 2013, FOIA request seeking:

  • All records related to the security of the healthcare.gov web portal including, but not limited to, studies, memoranda, correspondence, electronic communications (e-mails), and slide presentations from January 1, 2012 to the present.

A July 2013 “Continuous Improvement Plan,” prepared for updates and improvements to the healthcare.gov website, defines the “Change Control Board” as a provider of final approval on new features and “politically sensitive issues.”

The documents reveal that Mitre recommended a “Denial Authorization to Operate” in the month prior to Obamacare’s launch, noting that it could not adequately test the confidentiality and integrity of the system. It said that complete end-to-end testing of the system never occurred. Miter found that 11 “moderate” security findings and eight “low” findings remained open as September 19, 2013 – 12 days before the launch.

And an unsigned “Authorization to Operate” prepared just five days before Obamacare’s launch, indicates that the site’s “validation contractor” was “unable to adequately test the confidentiality and integrity of the [Federally Facilitated Marketplace] system in full.” That contractor, Blue Canopy, noted that they were able to access data “that should not be publically accessible.”

On October 1, Americans started shopping for health insurance on healthcare.gov, and the site crashed.

In an October 2013 email exchange requesting help with an upcoming test, healthcare.gov IT security Chief Tom Schankweiler complained of a lack of a “grand strategy” in security testing the Obamacare website. Schankweiler complained about hackers hitting the site, and noted that confidential information was “growing legs and growing way beyond the normal borders.” Fryer agreed with Schankweiler, and also noted “conflict of interest issues” in the security testing.

In November senior CMS official Jon Booth discusses “a contingency system” for higher Obamacare enrollments that CMS Office of Administration wanted “kept under the radar” and “out of the spotlight, even from an internal perspective.” George Linares responds to Booth, noting that healthcare.gov was still operating without an “Authorization to Operate,” and that the “contingency system” meant they needed a plan to “close the security gap as well.”

Among the released documents is a November draft press background briefer, in which CMS officials crossed out a line that read that consumers could “trust that the information that they are providing is protected by stringent security standards” and a line that the ACA website was “compliant with the Federal Information Security Management Act.”

CMS Statement:

The privacy and security of consumers’ personal information are a top priority for us. When consumers fill out their online Marketplace applications, they can trust that the information that they are providing is protected by stringent security standards. Security testing happens on an ongoing basis using industry best practices to appropriately safeguard consumers’ personal information. The HealthCare.gov website has been determined to be compliant with the Federal Information Security Management Act (FISMA), based on standards promulgated by the National Institutes of Standards and Technology (NIST).”

In November Schankweiler notes that they were faced with a choice of exposing users’ personal identifiable information or having the website down for days, resulting in “a new round of political attacks,” He also warns of a software problem causing a “high number of security and privacy incidents.” Schankweiler’s push to fix the problem was resisted by CMS official Rebecca Fender, who worried that the fix would take the Obamacare website down “for several days.”

In early December, Schankweiler complains of a software problem that was causing “a high number of security and privacy incidents.” Later in December Schankweiler complains about a security flaw that “allows anyone to access and edit records in the health care system.”

In December2013, Colin McVeigh from the CMS Center for Consumer Information and Insurance Oversight emailed to his colleagues his concerns that: “More than a month ago we received reports that consumers were seeing other consumer’s notices through a link on the application.”

A December 2013 email exchange, two months after the site’s launch, shows CMS official Lisa Feuerberg questioning Schankweiler as to why security testing wasn’t done of the site, and another security official responded that his “one tester” couldn’t get all the ACA sites scanned in time.

“Obamacare is corrupt, as we see further proof in these FOIA documents that sensitive health information on millions of Americans was put at risk,” said Judicial Watch President Tom Fitton. “From its start, Obamacare was a project that its promoters were determined to inflict on us whether it was ready or not. And clearly it was not. Anyone who uses the Obamacare web site does so at great risk to their private information. Let this be a lesson for those in Washington who are now trying to clean up this mess.”

In September 2014, Judicial Watch released 94 pages of documents obtained from the U.S. Department of Health and Human Services (HHS) including Security Controls Assessment Test Plans sent by CMS to Mitre Corporation. CMS advised Mitre that the highest “Risk Rating” should be given to flaws that could cause “political” damage to CMS. Moderate and low “Risk Ratings” were to include those resulting in potential “public embarrassment” to the agency.

In March 2015, Judicial Watch released documents from the U.S. Department of Health and Human Services (HHS) revealing that Department of Homeland Security (DHS) worked with HHS on security for healthcare.gov.

In January 2016, Judicial Watch released documents showing federal health care officials’ concerns with the Obamacare website in two productions of records: a 143-page production and an 886-page production. The emails showed that CMS Security Officer Teresa Fryer’s refused to approve the “ATO” (Authorization to Operate).

About Judicial Watch

Judicial Watch, Inc., a conservative, non-partisan educational foundation, promotes transparency, accountability and integrity in government, politics and the law. Through its educational endeavors, Judicial Watch advocates high standards of ethics and morality in our nation’s public life and seeks to ensure that political and judicial officials do not abuse the powers entrusted to them by the American people. Judicial Watch fulfills its educational mission through litigation, investigations, and public outreach.

For more information, visit: www.JudicialWatch.org.