The Technical Side of the Capital One AWS Security Breach

The Technical Side of the Capital One AWS Security Breach

  • August 3, 2019
Table of Contents

The Technical Side of the Capital One AWS Security Breach

On July 19th, 2019 Capital One got the red flag that every modern company hopes to avoid – their data had been breached. Over 106 million people affected.

140,000 Social Security numbers. 80,000 bank account numbers. 1,000,000 Social Insurance Numbers.

Pretty messy right? Unfortunately, the 19th wasn’t when the breach occurred.

It turns out that Paige Thompson, aka Erratic, had done the deed between March 22nd and March 23rd 2019.

So almost 4 months earlier. In fact, it took an external tip for Capital One to realize something had happened.

So almost 4 months earlier. Though the former Amazon employee has been arrested and is facing $250k in fines and 5 years in prison…it’s left a lot of residual negativity. Why?

Because of many of the companies who’ve suffered data breaches try to brush off the responsibility of hardening their infrastructures and applications to the increased cyber crime.

Source: jcolemorrison.com

Share :
comments powered by Disqus

Related Posts

A Detailed Overview of AWS API Gateway

A Detailed Overview of AWS API Gateway

Look inside the black box of AWS API Gateway to understand authorization, method requests and responses, integration requests and responses, VTL templates, and more. AWS API Gateway is an awesome service to use as an HTTP frontend. You can use it for building serverless applications, for integrating with legacy applications, or for proxying HTTP requests directly to other AWS services.

Read More
Moving from Kube2Iam to Kiam

Moving from Kube2Iam to Kiam

At Ibotta, we chose kube2iam to assign AWS IAM Roles to containers running in our Kubernetes cluster. Lately, we’ve run into some issues with it—specifically when running a job that scores all of our service repos. This spins up a number of pods in parallel and has often failed to correctly access roles.

Read More