posted on Oct, 30 2013 @ 06:05 PM
So, in their rush to get healthcare.gov up and running by Oct.1, they skipped doing end-to-end security testing of the entire website. In so doing,
Sebelius and Obama have left vulnerable to even low-level hacking attempts, the personal, confidential and financial data of any and all users of
Has the website been hacked already...and this information stolen? Probably.
Would Sebelius tell us if it had been? Probably not.
How can they be so careless with the lives and well-being of those they claim they wish to help; those who blindly go to them seeking help...only to
find their privacy and security carelessly and needlessly neglected and exposed?
The chairman of the House Intelligence Committee accused Health and Human Services Secretary Kathleen Sebelius of putting private information of
Americans at risk by failing to properly test security measures in the troubled Obamacare website.
“This is a completely unacceptable level of security,” said Rep. Mike Rogers (R., Mich.) at a hearing of the House Energy and Commerce Committee,
adding that if the website is not functioning, “you know it’s not secure.”
Sebelius said testing occurs regularly, but told Rogers she would get back to him on whether any end-to-end security test of the entire system has
ever occurred. Rogers responded that he knows there have been no such comprehensive security tests.
“High risk”: Document shows HHS launched ObamaCare website without end-to-end security testing
Via the WFB, if you watched this morning and were wondering what Mike Rogers was looking at while he was grilling Sebelius on site security, here’s
The Sept. 27 memo to Medicare chief Marylin Tavenner said a website contractor wasn’t able to test all the security controls in one complete version
of the system.
Insufficient testing “exposed a level of uncertainty that can be deemed as a high risk,” the memo said.
The memo recommended setting up a security team to address risks, conduct daily tests, and a full security test within two to three months of going
“High risk,” but they launched it anyway. The result: A flaw in the password-reset part of the site that would have made it unusually easy for
hackers to fool the site into letting them log on as other users. “
30-10-2013 by IAMTAT because: (no reason given)