Lessons Learned (or not) From the Dixons Carphone Breach

Watch Now

To watch this webinar you’ll need an Infosecurity Magazine account. Log in or sign up below.

Log In

Sign Up

Get up-to-the-minute news and opinions, plus access to a wide assortment of Information Security resources that will keep you current and informed.

This will be used to identify you if you take part in our online comments.

Your password should:

  • be at least eight characters long
  • be no more than 25 characters long
  • contain at least one uppercase, lowercase and special character
  • contain at least one digit
  • only contain alphanumeric characters or ~!@#$%^&*()_-+=?.

For more information explaining how we use your information please see our privacy policy.

By registering you agree with our terms and conditions.

The Dixons Carphone breach was reported to the Information Commissioner's Office in June, after the GDPR compliance deadline of 25th May, with a subsequent announcement that the incident had affected the personal data of 10 million records, significantly higher than initially stated. Could this have been caused by one or many security failings, and if so, how could they have been avoided? And why did it take so long to uncover the hack?

In this webinar, we will look back at the stories of the loss, understand what the technological and human failings were, and how you can avoid being in the same position in future.

Key takeaways:

  • Why your online business is vulnerable to the fast-evolving threat landscape
  • What your best practices should be to avoid this sort of breach happening to you 
  • How to ensure your web app security policy is compliant with your business
  • How a "Zero Trust" approach could have prevented the breach


Helen Davenport

Director at Gowling WLG

Max  Pritchard

Max Pritchard Senior Pre-Sales Consultant, Activereach Ltd

Brought to You by

Should you register for this event your information will be shared with the sponsor indicated above. See our privacy policy for more information.