DataBreaches.Net

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

NY: Glenville personal data exposed

Posted on June 24, 2010 by Dissent

Lauren Stanforth reports:

The town did not protect sensitive personal information when it used employee Social Security numbers on unsecured time sheets and unnecessarily kept credit card information of those who paid traffic fines, according to a state comptroller’s audit released Tuesday.

The audit, which reviewed practices from January 2008 to March 2009, found that town Social Security numbers were on the employees’ time sheets, and the sheets were often sent over the town’s e-mail system and paper copies were kept on desktops and in unlocked drawers. Town officials immediately abolished this practice when the state brought it to their attention, the audit stated, and now only use the last four digits of a Social Security number.

Also, credit card account information that was mailed into the town to pay for traffic infractions was retained in town records. And while the account numbers were blacked out, the numbers could easily be read by holding the paper up to light.

Read more in the Times Union.


Related:

  • Revealed: Afghan data breach after MoD official left laptop open on train
  • Former General Manager for U.S. Defense Contractor Pleads Guilty to Selling Stolen Trade Secrets to Russian Broker
  • The 4TB time bomb: when EY's cloud went public (and what it taught us)
  • Alan Turing institute launches new mission to protect UK from cyber-attacks
  • Some lower-tier ransomware gangs have formed a new RaaS alliance -- or have they? (1)
  • Uncovering Qilin attack methods exposed through multiple cases
Category: Commentaries and AnalysesGovernment Sector

Post navigation

← TX: Cases of identity theft reported
UK: Test all pregnant women for smoking, says Nice →

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

  • Checkout.com Discloses Data Breach After Extortion Attempt
  • 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

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

  • Once a Patient’s in Custody, ICE Can Be at Hospital Bedsides — But Detainees Have Rights
  • OpenAI fights order to turn over millions of ChatGPT conversations
  • 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

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.