Latest / Decrypted: The UK Cyber Briefing / ASOS shows how one convincing phone call becomes a customer data breach
Transcript
- 0:03This is Decrypted. Saturday, the seventeenth of October, twenty twenty-six.
- 0:08This is the evening edition.
- 0:12Ay-soss shows how one convincing phone call becomes a customer data breach.
- 0:19Ay-soss has now said how its breach began, and it owes less to clever malware than to a convincing strange
- 0:27r. On 8 October, the retailer told customers that an attacker posed as a trusted contact to get an employee's
- 0:35login details. Those details were then used on third-party platforms Ay-soss relies on to talk to its customer
- 0:43s. Ten days on, it's a tidy case study of a pattern every UK board should recognise.
- 0:50The weak point was a person, but the weakness was a design choice.
- 0:55So, what has Ay-soss actually said?
- 1:01On 6 October, a push notification reached customers through Ay-soss's own app.
- 1:08It claimed the company had been hacked, and alleged that a Snowflake environment was compromised.
- 1:13Ay-soss said no customer passwords or payment card information were accessed.
- 1:19Snowflake said the incident did not result from a vulnerability, weakness, flaw or misconfiguration in its se
- 1:26rvice. The B B C reported that a group calling itself Xuanyewen claimed to have used Simon AI, a marketing pl
- 1:35atform built on Snowflake.
- 1:36Ay-soss has not confirmed that, so treat it as a claim.
- 1:41The B B C also reported that a sample of the stolen data went beyond the "basic contact details" Ay-soss firs
- 1:49t mentioned. It included addresses, customer numbers and search terms.
- 1:55Ay-soss has not said how many customers are affected.
- 1:58How does something like this actually work?
- 2:03Think of a hotel where one master key opens every floor.
- 2:08The front desk hands it over to anyone who rings up and sounds like head office.
- 2:12The employee's login was the key.
- 2:15The marketing platform was the floor holding the customer file.
- 2:19Nothing here needed an exploit or malware, which is why it's hard to catch.
- 2:25A defender would see a valid sign-in, then a large pull of customer records, then a message sent by a legitim
- 2:31ate tool. So you're watching for unusual volume and unusual sending, not for malicious code.
- 2:38So what should companies do differently?
- 2:42Four design decisions would have changed the outcome, and none of them is exotic.
- 2:47First, phishing-resistant sign-in.
- 2:50Use passkeys or hardware security keys for anyone who can reach customer data.
- 2:56A persuasive caller can talk someone out of a password.
- 2:59They cannot talk a hardware key out of a drawer.
- 3:03Second, least privilege. A marketing login shouldn't be able to export complete customer profiles, and a bul
- 3:10k download should need a second approval.
- 3:12Third, two people to message everyone.
- 3:16Sending to the whole customer base through your own app should never be one account's decision.
- 3:21Fourth, treat suppliers' platforms as your own estate.
- 3:26Apply the same sign-in rules, and keep the logs where you can read them.
- 3:30The cost is mostly friction and a rollout project, not new technology.
- 3:35Set that against customers hearing about your breach from your own app.
- 3:39As always, this is opinion, not advice.
- 3:44That was Decrypted. The written version and every source are linked in the show notes.
- 3:50Thanks for listening.