TL;DR: Supplier credentials were the entry point in Target's 2013 breach, according to Klyro, and that path reached point-of-sale systems after lateral movement inside the network. Identity governance fails when third-party access is treated as low risk even though it can reach high-value systems.
Editorial analysis by NHI Mgmt Group, based on content published by Klyro: “The Target Data Breach Started With an Air Conditioning Contractor's Password”.
By the numbers:
- Target's breach exposed about 40 million payment cards and 70 million customer records.
- Third-party involvement in breaches doubled from 15% to 30% year over year.
- Supply-chain compromise costs an average of $4.91 million and takes 267 days to identify and contain.
Key questions
Q: What is the best way to scope third-party account access?
A: The best way is to assign each third-party account the minimum systems, data sets, and actions needed for one defined business purpose, then enforce time-bound access, separate credentials, and approval-based provisioning.
Q: How do microsegmentation tools reduce breach blast radius across network segments?
A: Microsegmentation tools reduce breach blast radius by enforcing fine-grained communication rules between workloads, users, and services.
Q: How do supplier credentials lead to lateral movement in enterprise networks?
A: Supplier credentials lead to lateral movement when a third party’s service account, API key, or VPN credential is reused, overprivileged, or poorly segmented, letting an attacker move from one system to another.
Practitioner guidance
- Inventory every third-party login path List supplier, contractor, and partner accounts separately from employee access and record which applications each identity can reach.
- Re-certify supplier entitlements on a fixed cadence Review the effective permissions of every external identity against its current business purpose, then remove any inherited or stale reach.
- Segment vendor portals from sensitive environments Ensure external business applications cannot traverse directly into payment, production, or other crown-jewel systems without explicit control.
Bottom line: The breach shows how third-party access can become a high-impact entry path when business scope and effective permissions diverge.
Glossary terms: Target data breach 2013, Third-Party Access, Least Privilege, Network Segmentation
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Supplier access is not low-value access: The breach worked because a business-purpose contractor account reached far beyond the work it was intended to support. That is a governance failure, not a technical curiosity, because the same pattern appears whenever external identities are granted ambient trust. The practitioner conclusion is simple: supplier identities must be treated as governed access paths, not as convenience accounts.
A question worth separating out:
Q: What should teams do when they discover that an employee account may have been exposed in a breach?
A: They should move quickly to confirm the affected account, reset credentials, and review whether the exposure touched other company services. If the account is tied to a shared workflow, access should be revoked or narrowed until the risk is contained. The response should be coordinated so employees know what changed and why.
👉 Read our full editorial: Target's supplier account turned access governance into breach fuel