TL;DR: A phished employee login can become a customer messaging and data-access incident when third-party access is too broad, according to NeuralTrust. Customer channels need separate approval and tighter governance when read and send rights sit together.
Editorial analysis by NHI Mgmt Group, based on content published by NeuralTrust: “ASOS Breach: Third-Party AI Risk in the UK”.
Key questions
Q: Why do stolen vendor credentials create such a high fraud risk in payment workflows?
A: Stolen vendor credentials are valuable because they let attackers impersonate legitimate payees and redirect funds without immediately breaking normal business processes.
Q: What are the signs that third-party vulnerability governance is failing?
A: The main signals are long vendor response times, repeated exposure in shared components, and a growing gap between confirmed findings and actual patches.
Q: What breaks when a third-party tool has both customer-data access and messaging rights?
A: A single compromised identity can expose data and impersonate the brand in the same incident.
Practitioner guidance
- Inventory every vendor with read or send rights List all third-party tools, including AI-enabled ones, that can read customer data, trigger customer messages, or access production systems.
- Separate data access from customer messaging Design third-party permissions so no single account can both query customer records and send brand-facing notifications without an additional approval step.
- Replace shared logins with phishing-resistant access Remove shared portal passwords and move privileged third-party access to phishing-resistant MFA with unique credentials.
Bottom line: The ASOS incident shows that a stolen employee login can become a supplier-side customer messaging problem when third-party access is too broad.
Glossary terms: Delegated Access, Third-Party Identity, Blast Radius, Phishing-Resistant MFA
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Third-party AI risk is fundamentally a privileged access problem. The ASOS case shows that the security question is not whether a supplier uses AI, but whether that supplier can act on customer data or customer channels with standing authority. Once a third party can both read and send, it is operating like an external privileged identity. Practitioners should govern those identities with the same seriousness they apply to internal admin access.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How should organisations respond when identity compromise reaches privileged systems?
A: Organisations should contain identity compromise as a production incident, not just an IAM event. That means isolating affected identity paths, revoking suspicious trust relationships, validating provider configurations, and checking downstream systems that rely on the same authentication plane. Identity teams and operations teams need to work from the same containment plan.
👉 Read our full editorial: ASOS breach shows delegated access can turn phishing into abuse