Could your organization handle a $10 million settlement? That's the potential cost facing Perry Johnson & Associates and its affiliates after a 2023 breach affecting about 13.3 million individuals. The initial penalty is $300,000, with up to $9.7 million more if they don't meet the agreed terms.
The failures in this case are basic and might be present in your organization right now.
Why These Mistakes Keep Happening
Security debt builds quietly. Remote access is set up quickly during staffing shortages. Monitoring tools are installed but not configured. Retention schedules are written but not enforced. None of this seems urgent until a breach occurs.
There's also an ownership issue. IT assumes compliance is managing controls, while compliance thinks IT has it covered. This disconnect is where breaches occur. The HIPAA Security Rule mandates risk analysis and management because no single person has the full picture.
Enforcement has changed too. Penalties aren't just from class actions or the OCR. State attorneys general are taking action, as seen in New York's settlements with Labcorp ($2.3 million) and Illuminate Education ($1.7 million). The HHS has also been active, with settlements like $800,000 from Lehigh Valley Health Network for a ransomware response and $700,000 from Ambry Genetics for a phishing attack.
Mistake 1: Leaving Remote Access Without MFA
Why it happens: MFA can be inconvenient, leading to complaints from staff under pressure. Legacy systems may not support MFA, so upgrades are delayed. The Security Rule requires person or entity authentication, but doesn't specify technology, leading some to think passwords are enough.
The consequence: In the PJ&A case, hackers used a single employee's credentials to access the network. Without MFA, one password was all it took for a breach that lasted months.
The fix: Implement MFA on all remote access points, not just those in policy documents. Inventory VPNs, remote desktops, webmail, cloud admin consoles, and vendor portals. Prioritize accounts with access to electronic Protected Health Information (ePHI). If MFA can't be enforced, document the compensating control and when it will be retired.
Mistake 2: Collecting Logs but Never Alerting on Them
Why it happens: Installing a monitoring tool feels like completing a task. Tuning alerts is tedious and often delayed.
The consequence: PJI's software recorded malicious activity but didn't send alerts. They only learned of the breach when hackers contacted them two weeks later. Detection was in place, but response was not.
The fix: Treat logging and alerting as separate tasks. The Security Rule's information system activity review requires a process, not just data storage. Identify high-priority events, assign owners, and test alert paths quarterly by simulating benign events.
Mistake 3: Storing ePHI Unencrypted at Rest
Why it happens: Encryption is an Addressable Specification under HIPAA, often misunderstood as optional. Older file systems may not meet current encryption standards, and teams hesitate to update them.
The consequence: Attackers accessed unencrypted files with sensitive PHI. Encrypting these files could have significantly altered the breach's impact.
The fix: Encrypt ePHI at rest on servers, databases, backups, and endpoints. Use NIST SP 800-66 as a guide for encryption decisions. Document reasons for not encrypting data. Proper encryption can influence whether an incident is reportable under the Breach Notification Rule.
Mistake 4: Keeping Data Long After It's Needed
Why it happens: Deleting data seems risky, while keeping it seems harmless. Retention policies exist, but disposal procedures are often lacking.
The consequence: The scope of a breach grows with the data you retain. The settlement mandates that Perry Johnson companies maintain policies for data collection, use, retention, and disposal, highlighting retention as a security measure.
The fix: Create a data inventory linking each dataset to a retention period, owner, and disposal method. For Business Associates, align retention with contract terms and ensure ePHI is returned or destroyed as required.
Mistake 5: Treating Risk Analysis as a One-Time Project
Why it happens: Risk analysis is a major task, so it's often done once and forgotten. However, environments change, affecting risk profiles.
The consequence: The settlement requires annual risk assessments, indicating regulatory expectations. Outdated analysis misses critical vulnerabilities.
The fix: Conduct risk analysis annually and after significant changes. Ensure findings lead to a remediation plan with clear ownership and deadlines. Regulators expect both analysis and follow-through.
Prevention Checklist
- Enforce MFA on all remote access paths, including vendor and admin accounts.
- Document and enforce password management standards.
- Ensure monitoring tools generate alerts with assigned responders.
- Test alert-to-response time quarterly.
- Encrypt ePHI at rest or document Addressable Specification decisions.
- Maintain an asset inventory showing ePHI locations.
- Implement and execute retention and disposal procedures.
- Complete risk analysis annually and after major changes.
- Assign owners and due dates to remediation items.
- Keep an updated incident response plan and conduct regular exercises.
- Specify security expectations and data return or destruction in Business Associate Agreements.
If you can't check every box, start with MFA and alerting. These gaps turned one employee's credentials into a multi-state enforcement action.





