4 ms·
Considering that the breach wasn't on the actual site itself but on the accounts of private companies that were tasked with receiving the applications, this isn
by dpkonofa 8y ago
Considering that the breach wasn't on the actual site itself but on the accounts of private companies that were tasked with receiving the applications, this isn't an issue with the website. More than likely, someone employees that work at these contractors had weak passwords and no limit to the number of logins. As soon as the people on the website found out, access was disabled. It sounds like they actually had their shit together at this point.
- exabrial 8y agoObviously like I said one of the best $150m, er $1.6b, taxpayer has spent. I seriously can not can't think of any other website that takes that amount of traffic and operates on a significantly lower budget.
- aplummer 8y agoWait, “can not.. can’t?” Which way are you going with this
- exabrial 8y agoIndeed.
- WillPostForFood 8y agoWikipedia?