DataBreaches.Net

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

Faculty, staff ID threatened

Posted on September 2, 2010 by Dissent

Sarah Krimm reports:

At 8:55 a.m. on Thursday, Aug. 26 an e-mail containing the Social Security number, driver’s license number, and first and last name of 2,484 full and part-time ASU [Arkansas State University] employees was sent to 144 ASU e-mail addresses.

This information breach has raised concern among affected faculty, as identity theft becomes a risk when Social Security numbers are disclosed.

[…]

ITS explained in an e-mail sent to each user affected by the breach that Social Security numbers were collected during the registration process to register drivers with the Arkansas Department of Finance and Administration. The reason for this is prior to 2000, the State of Arkansas used Social Security numbers as driver’s license numbers.

“The file contained personal information of employees who had filed for (a) authorization to drive a [Arkansas] State University vehicle, or (b) permission to be reimbursed for driving their personal vehicle on [Arkansas] State [University] business,” Hoeting said. “What happens is our Travel Office is required to register those employees with the state, and it checks their driving record and other things, to make sure they’re legally able to drive those vehicles, and that’s essentially what the file was.”

Hoeting said it was his understanding that the 144 recipients of those files were a part of a distribution group that receives a newsletter from the Travel Office.

Read more in The Herald.

Category: Breach IncidentsEducation SectorExposureU.S.

Post navigation

← West Virginia accounting firm employee sentenced for ID theft
KCI working to contain employee data breach →

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

  • AT&T gets preliminary approval for $177 million data breach settlement
  • Aflac notifies SEC of breach suspected to be work of Scattered Spider
  • Former JBLM soldier pleads guilty to attempting to share military secrets with China
  • No, the 16 billion credentials leak is not a new data breach — a wake-up call about fake news (Updated)
  • Tonga’s health system hit by cyberattack (1)
  • Russia Expert Falls Prey to Elite Hackers Disguised as US Officials
  • Proposed class action settlement in In re Netgain Technology litigation
  • Qilin Offers “Call a lawyer” Button For Affiliates Attempting To Extort Ransoms From Victims Who Won’t Pay
  • Ireland’s Data Protection Commission publishes 2024 Annual Report
  • The headlines suggested Freedman Healthcare suffered a ransomware attack that affected patient data. The reality was quite different.

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

  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data
  • US Judge Invalidates Biden Rule Protecting Privacy for Abortions
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[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.