The Perry Johnson & Associates (PJ&A) settlement highlights common security failures: remote access without multifactor authentication (MFA), weak passwords, and ineffective monitoring. The $10 million settlement, with $300,000 due upfront and $9.7 million suspended unless terms are violated, followed a breach affecting at least 13.3 million people. If you're a Privacy Official with limited resources, you can't fix everything immediately. So which gap should you address first?
This guide will help you prioritize your actions.
The Decision You Are Facing
You need to prioritize fixes in three areas scrutinized by the settlement: access controls, monitoring and alerting, and governance (risk analysis, Business Associate oversight, and independent testing). Each area corresponds to a failure in the PJ&A case and a requirement under the HIPAA Security Rule.
Key Factors Affecting Your Choice
Consider these questions before deciding:
- Do you have remote access paths without MFA? Attackers entered through a remote application lacking MFA, using a compromised credential.
- Do your security tools alert a designated person? PJ&A's monitoring software logged malicious activity but didn't notify anyone, despite a request for email alerts over a year earlier.
- Is your risk analysis current, enterprise-wide, and documented? PJ&A allegedly failed to conduct an adequate security risk analysis.
- Do you have signed Business Associate agreements for all entities handling Protected Health Information (PHI)? Missing agreements with affiliated firms were alleged.
"No" answers indicate exposure. "I don't know" also means "no."
Path A: Close the Front Door (Access Controls)
Choose this path if: you lack MFA for remote access or have shared, reused, or emailed credentials.
Why: The breach began with a compromised credential and a remote application without MFA. Attackers then harvested more passwords, escalated privileges, and moved laterally. Nine accounts had nearly identical passwords, differing only by the last digit, and were unchanged for 10 months despite a 90-day policy.
What to do:
- Inventory all remote access paths: VPN, remote desktop, web applications, vendor portals.
- Enforce MFA, prioritizing accounts with privileged or database access.
- Ensure your password policy is technically enforced, not just documented.
- Prohibit credential distribution by email and implement a managed alternative.
Requirements driving this path: The HIPAA Security Rule's access control standard (45 CFR 164.312(a)) and person or entity authentication standard (164.312(d)). MFA is a practical safeguard. Encryption, also required in the settlement, is part of the Technical Safeguards family as an Addressable Specification.
Path B: Ensure Alerts Reach Someone (Monitoring and Alerting)
Choose this path if: you have MFA but can't identify who receives alerts from your monitoring tools, or you've never tested alert functionality.
Why: This failure was quiet but instructive. The tool logged attackers from late March 2023, but the company only learned of the intrusion in May 2023 when the attackers made contact. Detection technology alone didn't protect anyone; proper configuration to alert a person would have.
What to do:
- Document the alert path for each monitoring tool: trigger, recipient, backup recipient, expected response time.
- Test the system with a benign event to confirm alerts are seen.
- Track requests to enable features. A request for email alerts went unfulfilled for over a year. Use a ticketing system with an owner.
- Clarify accountability when two entities share tools. Ambiguous ownership was an issue.
Requirements driving this path: Audit controls (164.312(b)), information system activity review (164.308(a)(1)(ii)(D)), and security incident procedures (164.308(a)(6)). Unreviewed logs don't meet the activity review specification.
Path C: Strengthen Governance and Oversight
Choose this path if: your risk analysis is outdated, doesn't cover all systems with ePHI, or you lack a complete list of Business Associate agreements.
Why: Alleged violations included inadequate risk analysis and missing Business Associate agreements. These issues can turn a technical incident into a regulatory one. The settlement now requires regular security risk assessments, penetration testing, independent third-party assessments, and written security reports to senior management and boards.
What to do:
- Use the settlement's requirements as a program design guide. Adopt these measures proactively.
- Align your risk analysis methodology with NIST SP 800-66 and ensure it covers shared network files, not just primary databases.
- Reconcile your vendor inventory with actual data flows, including affiliated entities. Affiliation doesn't exempt anyone from the Business Associate agreement requirement.
- Establish a twice-yearly security briefing for leadership.
Requirements driving this path: Risk analysis and risk management (164.308(a)(1)(ii)(A) and (B)), Business Associate contracts (164.308(b) and 164.504(e)), and the Breach Notification Rule.
Summary Matrix
| If your situation is... | Start with | Primary rule driver | First action |
|---|---|---|---|
| Remote access without MFA; shared or stale passwords | Path A | 164.312(a), 164.312(d) | MFA on every remote path |
| Tools in place, alerts unrouted or untested | Path B | 164.312(b), 164.308(a)(1)(ii)(D), 164.308(a)(6) | Document and test alert routing |
| Outdated risk analysis; incomplete Business Associate inventory | Path C | 164.308(a)(1), 164.308(b) | Refresh analysis; reconcile BAAs |
A Note on Sequencing
If you answered "no" in more than one area, start with Path A. Compromised credentials were the entry point, and MFA is likely to prevent a repeat. Then, quickly address Path B to shorten response time between intrusion and detection. Path C is slower but crucial for regulatory compliance, so start it in parallel and set a completion date.
Remember, the companies neither admitted nor denied the findings, so use this as a guide to what investigators look for, not a ruling. The gaps didn't require advanced technology to close.





