1-minute read
What a defender needs to know
One-minute read
HHS lists 3,756,469 people in CareCloud’s breach report. CareCloud’s August Form 10-Q says its forensic investigation confirmed that an intruder exfiltrated patient-related information from one cloud account supporting an electronic health record environment. One of six EHR environments was partly disrupted for about eight hours. CareCloud says it restored affected systems and found no later unauthorized activity tied to the incident. Public records identify personally identifiable information and protected health information without mapping specific fields to each person.
Defender takeaway
Request a tenant-level roster that maps the affected CareCloud AWS account to customer organizations and patient populations. Reconcile it against admission, encounter, billing, portal, and identity records active from March 10 through March 16. Record the source, count, applicable data categories, and notice disposition for each population.
Also request the affected AWS account and region, database identifiers, IAM principals, CloudTrail events, database audit records, snapshots, exports, and restoration evidence. Search customer-controlled identity and integration logs for service-account authentications, bulk reads, export jobs, API calls, and credential changes in the same window.
Verify the final notice population by sampling included and excluded records back to source evidence. The expected result is a one-to-one trail from each affected record to a notice decision, with affirmative evidence for every exclusion. Keep unexplained differences open with an owner and due date.