FEDERALUnknownLow

Wellpoint, Inc.

bd_e7845fe3bfc8027e · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Jul 11, 2013

To disclose

—

Affected

Not disclosed

Linked

2 filings

Confidence

90%

Full breach record for Wellpoint, Inc. →3 incidents on file

Regulator's decision — not a breach notification

This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.

WellPoint Inc. settled potential HIPAA Privacy and Security Rule violations for $1.7 million. OCR found WellPoint failed to implement appropriate administrative and technical safeguards, including policies for authorizing access to an online application database, performing technical evaluations for software upgrades, and verifying access to electronic protected health information (ePHI). This resulted in the impermissible disclosure of ePHI for 612,402 individuals.

J jump to incidentP pin to compareR raw source

Incident timeline — partial

? — ?

Breach window unknown

Jul 11, 2013

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 2 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

HHS OCRbd_d950156212c850352010-07-30 · +1077dCandidate

Name: Wellpoint, Inc.
norm: wellpoint

Name: Wellpoint, Inc.
norm: wellpoint

Attack vector: Unknown
Outcome: Settledresolution agreement
Fine · as filed: $1,700,000
National provisions: 45 C.F.R. § 164.308(a)(1)(ii)(A)45 C.F.R. § 164.31245 C.F.R. § 164.310

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.
Confidence context: The agreement states the respondent, the amount and the provisions in fixed legal wording; the recited breach figures are the regulator’s restatement of the original report.

Filing propagation · 2 filings

View merged incident ↗

HHS OCRJul 30 · first

HHS OCR enforcement+1077d · this page

Pattern: first filing Jul 30 (IN), last Jul 11 — a 1077-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source ceiling

instrument + outcome
amount as filed (USD)
CFR provisions
the breach it recites
discovery date
notification clock

The dates the agreement recites belong to the underlying breach, years earlier, and are kept as evidence of WHICH breach rather than as this record’s timeline.

Source URL: https://www.hhs.gov/ocr/privacy/hipaa/enforcement/examples/wellpoint-agreement.html
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 11, 2013
Raw hash: 67dd748d3fb19a3706ac4ea7d602ebbd8275116099a59ed8de7b53f39b72c0f9

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityWellpoint, Inc.

RespondentWellpoint, Inc.

What this source establishesUnknown

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.hhs.gov