Back to all lessons
Awareness Lessons
last week

iRhythm Breach: Third-Party App Risk Exposes 360,000 Patients

Hackers accessed and exfiltrated sensitive patient data from third-party-hosted business applications used by iRhythm, a medical device company, over a five-day window in June. The root issue lies in insufficient oversight of third-party vendors and the applications they host, which created a blind spot in iRhythm's security perimeter. In healthcare, where patient data carries heightened regulatory and ethical sensitivity, third-party risk is especially dangerous because breached data can enable identity theft, insurance fraud, and targeted phishing. This incident underscores that organizations are only as secure as their weakest external dependency — and that vendor-hosted environments require the same rigorous controls as internal systems.

Tactical Insight

Immediate actions

  • Conduct an emergency audit of all third-party-hosted applications to verify current access controls and patch levels.
  • Force credential rotation and review session tokens for any accounts connected to the affected third-party applications.
  • Engage the third-party vendors involved to obtain full incident reports and confirm the breach vector has been closed.

Long-term improvements

  • Enforce contractual security requirements (e.g., SOC 2, HITRUST) for all vendors handling protected health information (PHI).
  • Implement a formal Third-Party Risk Management (TPRM) program with periodic security assessments and right-to-audit clauses.
  • Apply the principle of least privilege to all third-party application integrations, limiting vendor access to only the data strictly necessary.

Detection measures

  • Deploy Data Loss Prevention (DLP) tools and behavioral analytics to detect abnormal data exfiltration from third-party-hosted environments.
  • Establish continuous monitoring and alerting for unusual access patterns or bulk data queries against applications containing PHI.
  • Require vendors to provide real-time security event logs to your SIEM so that cross-environment threats can be correlated quickly.

Back this up with a control

All controls and vendors

Training helps people spot this. These controls make the attack fail even on the day someone does not.