Chief among the concerns raised are it's vulnerability to hacking due to shoddy coding and architecture. From the Christian Science Monitor comes the following alarming story of the inevitable and possibly imminent potential for a massive rash of identity theft. There really is a lot to be very concerned about. The real lesson of ObamaCare's grossly negligent roll-out is CAVEAT EMPTOR!!! Don't be a victim of identity theft... It's a BITCH!
Obamacare website security called 'outrageous': How safe is it?
Cybersecurity professionals are voicing questions about potential red flags in the new federal health care website system that could open the door to theft of personal information.
In the two weeks since the Affordable Healthcare Act site, www.healthcare.gov, went live, most complaints have centered on long wait times with sites initially overloaded by interested visitors. In response, government officials are scrambling to get more capacity for the main site and its satellites.
But potentially far more serious questions are emerging about cybersecurity. Experts have said that hackers could “spoof” the website with a look-alike website to collect personal information, or criminals could use an automated program to try repeatedly to enter the site even if it didn’t get a login correct.
Experts have stopped short of calling these concerns “vulnerabilities” – a term that means a proven weak spot to hackers. But they say these red flags need attention.
“I’ll ask you your Social Security, your date of birth, [so] an hour later I can empty your bank account,” John McAfee, who founded the cybersecurity company of the same name but is no longer associated with it, complained on Fox News. The Obamacare websites, he said, have “no safeguards,” and the main site's architecture is "outrageous."
Read the rest of the story at the CSM site, HERE
Trainwreck. They can't build a website with $619 billion. It's like a monkey f$%#ing a football.
ReplyDeleteThe Forbes article about how the website was designed to fail is very interesting.
ReplyDeleteThanks for the tip, I'll have to read it.
Delete