Skip to main content
Promotional banner ad for the Penetration Testing Report Kit
HIPAA Failures Behind a $10M Multi-State SettlementBreach & Risk Assessment
5 min readFor Legal and Compliance Teams

HIPAA Failures Behind a $10M Multi-State Settlement

Scope: What This Guide Covers

This guide examines the security and compliance failures alleged in the settlement involving Perry Johnson & Associates (PJ&A), four affiliated firms, and the attorneys general of New York, New Jersey, Connecticut, and Michigan. It provides a control checklist your team can use for audits.

The focus is on three areas: remote access authentication, security monitoring and alerting, and the HIPAA administrative requirements reportedly missed. It doesn't cover state-specific penalty calculations or pending class actions.

The companies neither admitted nor denied the findings. Consider these allegations as a useful audit template, not established facts.

Key Concepts and Definitions

Multifactor authentication (MFA): Verification using two or more independent factors. Hackers accessed an application that didn't require MFA, using compromised employee credentials.

Security risk analysis: A required assessment of risks to electronic protected health information (ePHI) under the HIPAA Security Rule. Investigators alleged the companies never conducted an adequate one.

Business associate agreement (BAA): A contract required when a vendor or affiliate handles protected health information. The states alleged missing BAAs with PJ&A-affiliated firms that had PHI access.

Alert configuration: The process that turns a logging tool into a detection tool. Here, the monitoring software recorded the intruders but notified no one.

Dwell time: The gap between initial access and discovery. Access began in March 2023; the companies learned of the hack in May 2023 when the attackers contacted them with a ransom demand.

Requirements Breakdown

The settlement and the underlying allegations relate to these obligations. Refer to the regulation text directly in your audits; the HIPAA citations below are standard Security and Breach Notification Rule references.

1. Risk analysis and management. The Security Rule requires an accurate and thorough assessment of risks to ePHI (45 CFR 164.308(a)(1)(ii)(A)), plus a risk management process to reduce them. The settlement mandates regular security risk assessments and penetration testing.

2. Access control and authentication. Person or entity authentication is required under 45 CFR 164.312(d). The settlement requires stronger access controls and MFA.

3. Audit controls and monitoring. Systems must record and examine activity (45 CFR 164.312(b)), and information system activity review is an administrative requirement (45 CFR 164.308(a)(1)(ii)(D)). The settlement requires automated security alerts and enhanced threat monitoring.

4. Business associate contracts. Required under 45 CFR 164.308(b) and 164.502(e). The settlement requires stronger oversight of vendors and subcontractors.

5. Breach notification. Governed by 45 CFR 164.400-414. The states alleged deficiencies here too. The companies never reviewed the shared network files that attackers accessed, making accurate notification difficult.

6. Governance. The settlement requires independent third-party assessments within 90 days of becoming active, then annually for three years, and written security reports to senior management and boards at least twice a year.

Implementation Guidance

Close the MFA gap first. Inventory every remote access path, not just the VPN. The breach vector was an application. List every internet-reachable application that accepts credentials, and confirm MFA is enforced. Check service accounts and legacy applications separately.

Treat alert routing as a testable control. A PJ&A administrator asked a sister firm's administrator in February 2022 to enable email alerts. They were never configured. That request sat unresolved for over a year. Your team should:

  • Assign a named owner for every alert-enabling request.
  • Run a quarterly test that generates a known-bad event and confirms a human receives the alert.
  • Track open monitoring tickets with an aging threshold, escalating anything stale.
  • Confirm alert routing across affiliates and shared tools, since the failure crossed two companies.

Audit credential hygiene against policy. Investigators found nine accounts with nearly identical passwords differing only by the final digit, distributed by email, one message reaching an employee of another company. The passwords stayed unchanged for about 10 months despite a 90-day policy. Compare policy to actual password age in your directory. Distribute initial credentials through a secrets manager or out-of-band process, never email.

Map data and BAAs together. Build a list of every entity touching PHI, including affiliates under common ownership. Common ownership doesn't remove the contract requirement. Match each entity to an executed BAA.

Review file shares. Shared network files held additional personal data and PHI that was never reviewed after the intrusion. Run Data Discovery on shared drives before an incident, so you can scope exposure quickly.

Plan for wind-down. Several named companies are now inactive. The settlement requires return or secure destruction of sensitive information held by inactive entities. Build Secure Deletion and Data Purging steps into any divestiture or shutdown plan.

Common Pitfalls

  • Logging without alerting. Collection is not detection.
  • Policy without enforcement. A 90-day rotation rule means nothing if unchecked.
  • Assuming affiliates are covered. Related companies still need documented agreements.
  • Verbal or ticket-based handoffs between sister firms. Cross-entity requests need an owner and a deadline.
  • Skipping scope analysis after an incident. Unreviewed files leave you unable to state who was affected.
  • MFA on the perimeter only. One unprotected application undid the rest.

Quick Reference Table

Control area Alleged failure Requirement reference Audit test
Remote access No MFA on application used for entry 45 CFR 164.312(d) List all remote paths; verify enforced MFA
Monitoring Software logged activity, sent no alerts 45 CFR 164.312(b); 164.308(a)(1)(ii)(D) Trigger test event; confirm human receipt
Passwords Near-identical credentials, emailed, unchanged about 10 months 45 CFR 164.308(a)(5)(ii)(D) Compare password age to policy
Risk analysis No adequate security risk analysis 45 CFR 164.308(a)(1)(ii)(A) Date and scope of last analysis
BAAs Missing agreements with affiliates 45 CFR 164.308(b); 164.502(e) Entity-to-BAA match list
Breach notification Deficiencies alleged; exposure scope uncertain 45 CFR 164.400-414 Run a tabletop with data scoping
Governance No board-level reporting Settlement terms Twice-yearly written reports
Inactive entities PHI retained after wind-down Settlement terms Documented Secure Deletion records

The financial terms show how the risk is priced: an initial $300,000 payment, with $9.7 million suspended unless the companies breach the agreement or their financial representations prove materially inaccurate. The larger cost is the multi-year obligation to prove your controls work.

Promotional banner highlighting failures found in PCI audits and how to spot the gaps

You Might Also Like