top of page
Writer's pictureToBeSecured

Update on Capital One $80 Million Fine - Hacking Incident

Good evening and welcome back to another post from ToBeSecured everyone. If you're new to my blog, thank you for taking the time out to read and support my brand. ToBeSecured brings awareness of the many issues in the technology world. You can always find the latest news relating to privacy and security right here! On today's blog post, I'll give a brief update on the Capital One hacking incident that occurred on last year - July 2019.


Recap: Capital One said that the data of 100 million U.S. customers was illegally accessed in a breach federal prosecutors said was perpetrated by a Seattle woman who allegedly hacked the bank’s server at a cloud-computing company. Six million Canadian customers were also affected.



Federal prosecutors said that sometime between March 12 and July 17 of 2019, Paige A. Thompson, 33, of Seattle hacked Capital One’s rented server space. The Department of Justice alleges Thompson “posted on the information sharing site GitHub about her theft of information from the servers storing Capital One data.”


The Treasury Department Bureau announced Thursday that the company would be fined. About 140,000 Social Security numbers and 80,000 bank account numbers were exposed in the 2019 hack. The data breach happened while Capital One was moving data to the cloud. The Office of the Comptroller of the Currency, the bureau which assessed the fine, said Capital One’s “risk assessment processes” were below an average/normal level at the time.


Paige has been charged with the hack by federal prosecutors, is set to stand trial in February, and she's also accused of dozens of other hacking incidents.


What are your thoughts on this topic? Subscribe to my blog if you haven't already and follow my Instagram - ToBeSecured for CyberTuesday vlogs. I have launched my YouTube channel and you can find me by simply typing Kassirer Dunn into the search engine. Thank you for tuning in and remember ToBeSecured!




17 views0 comments

Comments

Couldn’t Load Comments
It looks like there was a technical problem. Try reconnecting or refreshing the page.
bottom of page