July 30, 20191 min read, 123 words
Published: July 30, 2019 | 1 min read, 123 words
Multiple experts have drawn issue with Capital One’s explanations for its data breach of records on over 100 million people. Have a tip about a data breach or a security incident? You can contact Joseph Cox securely on Signal on +44 20 8133 5190, Wickr on josephcox, OTR chat on j...
CRITIC REVIEWS
There don't seem to be any reviews yet.
PUBLIC REVIEWS
Stacking the Deck
July 31, 2019
This article gives necessary context to this issue but predominately from one side. The headline states that it is Capital One's fault, which isn't proven in the article, it also pulls only quotes from Capital One critics.
July 31, 2019
Stacking the Deck
July 31, 2019
I agree with Jared F.'s review that this article is very one-sided, presenting Capital One's CEO as giving a dishonest or inauthentic apology, possibly intentionally misframing the events of the data breach. The sources in the article are security experts who have a clear incentive to critique the company for not doing more, and everyone quoted appears to be a critic or naturally untrusting of Capital One. Capital One needs to do a much better job protecting its customers private data, but this appears to have been a hacking rather than an accidental release of data.
July 31, 2019
Surface Level
August 30, 2019
This article reports a conclusion yet it also states that not all of the information is known. Based on information revealed since, it does appear that Capital One is to blame, but there are significant considerations regarding capabilities Amazon provides for securing an environment and the complexity of doing so. While this does not shift blame from Capital One to Amazon, the article would be more balanced and informative if it provide this more complete picture.
August 30, 2019
Anecdotal Evidence
July 31, 2019
There are some well sourced quotes, but no evidence is presented beyond speculation from security consultants. Capital One's only cited response was the public apology, so no attempt to corroborate with them appears to have happened.
July 31, 2019