Episode 547 – Now Capital One Is Breached By Poor Configuration And Patch Management

[iframe style=”border:none” src=”//html5-player.libsyn.com/embed/episode/id/10708586/height/100/width//thumbnail/no/render-playlist/no/theme/custom/tdest_id/1418831/custom-color/87A93A” height=”100″ width=”100%” scrolling=”no” allowfullscreen webkitallowfullscreen mozallowfullscreen oallowfullscreen msallowfullscreen]

Another day and another breach that is bigger than the last. This time Capital One is on the block. This epsiodegoes over the breach details as they have been reported at the time of recording this and talks about how the breach happened. 

Dont forget to nominate Security In Five for a People’s Choice Podcast Award – https://www.podcastawards.com

Be aware, be safe.

Become A Patron! Patreon Page

*** Support the podcast with a cup of coffee *** – Ko-Fi Security In Five

Don’t forget to subscribe to the Security In Five Newsletter.

—————— Where you can find Security In Five ——————

Security In Five Reddit Channel r/SecurityInFive

Binary Blogger Website

Security In Five Podcast PagePodcast RSS

Twitter @securityinfive

iTunes, YouTube, TuneIn, iHeartRadio, Spotify, Stitcher

Email – bblogger@protonmail.com


Check out this episode!

Please follow and like us:
Pin Share
Previous post Episode 546 – Thank You To GenCyber And Claim Your Equifax Settlement Money
Next post Episode 548 – Micro Learning And It’s Effectiveness In Security Awareness

Enjoy this blog? Please spread the word :)

Follow by Email