DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

CA: Notice to Individuals Regarding Privacy Incident Involving Capitol Administrators, Inc.

Posted on May 12, 2018 by Dissent

Notice how they do not tell us when the phishing attack occurred – only when they concluded their investigation of it.  So when was this attack, and when was it actually discovered for purposes of the 60-day clock?  And how many people are being notified? From their substitute notice on their web site:

Capitol Administrators, Inc. (“Capitol”) understands the importance of protecting the information it maintains. This notice relates to information of some members of the group health plans it provides claims processing and related services to.

Capitol is a third party administrator hired by companies to provide benefits administration.  To accomplish this function, our clients, medical providers and others provide us with data about Plan participants, including certain types of personal and medical information.

On March 30, 2018, Capitol learned through a forensic investigation of a phishing email incident that certain emails and attachments had been accessed by an unauthorized person.  Upon first learning of the phishing incident, Capitol took immediate steps to secure the account, conduct an internal investigation, and enhance the security of its system. Capitol also engaged a leading cyber security firm to perform an investigation.  That investigation determined that an unauthorized individual accessed certain emails and attachments in a small number of Capitol employees’ email accounts.  While the investigation could not determine if the attachments to the emails had been opened by the unauthorized person that possibility could not be ruled out.  The emails and attachments contained member information provided to Capitol in connection with their group health plans. This information included names and some or all of the following: Social Security numbers, medical information, and/or health insurance numbers.

Out of an abundance of caution, Capitol began notifying the potentially affected individuals on May 11, 2018 and we have established a dedicated call center to answer any questions.  If you believe you may be affected by this incident but did not receive a letter by Monday, May 28, 2018, please call 1-833-219-9090, Monday-Friday between 9:00 a.m. and 6:00 p.m., Eastern Time.

Capitol regrets that this incident occurred.  In addition to providing notice of the incident, Capitol has taken various steps to enhance its existing network and email security, including implementing multi-factor authentication and upgrading its security center, as well as providing education and training to its employees to help prevent a similar incident from happening in the future.


Related:

  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
Category: Health DataPhishingU.S.

Post navigation

← CA: Teen who phished his school district: “It was like stealing candy from a baby”
OR: LaPorte & Associates notifies clients of laptop theft →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Washington Post hack exposes personal data of John Bolton, almost 10,000 others
  • Draft UK Cyber Security and Resilience Bill Enters UK Parliament
  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Maryland Privacy Crackdown Raises Bar for Disclosure Compliance
  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.