DataBreaches.Net

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

CT: Willimantic town employees’ information was on unattended laptop stolen from employee’s office

Posted on September 24, 2012 by Dissent

Alison Shea reports:

Willimantic police are asking for the public’s help in recovering a laptop containing town employees’ information that was stolen from Town Hall a week ago.

Police said in a release late Sunday that a town employee had left the laptop unattended in his office in Windham Town Hall from 10 a.m. to noon on Sept. 17 while he was in a meeting. When he returned, the laptop was gone, police said.

Read more on Norwich Bulletin.


Related:

  • Revealed: Afghan data breach after MoD official left laptop open on train
  • Snowflake Loses Two More Bids to Dismiss Data Breach Plaintiffs
  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • Former General Manager for U.S. Defense Contractor Pleads Guilty to Selling Stolen Trade Secrets to Russian Broker
  • Alan Turing institute launches new mission to protect UK from cyber-attacks
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
Category: Breach IncidentsGovernment SectorTheftU.S.

Post navigation

← Potential Tulsa website hacker victims notified (update: nothing to see here, move along)
TX: Police warn of ID theft →

2 thoughts on “CT: Willimantic town employees’ information was on unattended laptop stolen from employee’s office”

  1. Helen Lawson says:
    September 25, 2012 at 8:49 am

    Employers like these need to start thinking about FACTA penalties, if nothing else. Having ID theft protection in place as an employee benefit can help them respond quickly to mitigate.

  2. IA Eng says:
    September 26, 2012 at 9:36 am

    Security only works if some more common sense practices are in place. Some may be a pain is the rump, but they are effective.

    1. No matter where – secure the laptop with a cable to something heavy.
    2. No lock on the door ? no security cameras, guards or otherwise ?
    3. No tracking software installed like LO-JACK for laptops? Some OEM packages may include this.
    4. Lock out attempts set to a low number, AND requires an Administrator to login and unlock?

    Password protected laptops aren’t enough when it comes to PII – It should be encrypted with some sort of approved software. Depending on the operating system, password protected laptops can be cracked within a matter of minutes, or using a specific boot disk, the password can be changed and data accessed.

    One can only guess the motivation behind the theft. One may try to immediately pawn the item for quick cash trying to dump the item before the item is reported stolen.

    Tracking down the potential thief may be hard, but one can look at people who have visited the buiding to make payments, inquiries or simply browsed services available at the site. The web server logs may assist somehow, like looking at the IP addresses over the past week and seeing if those can be helpful – especially if they were viewing workers profile information and any meetings that are on the website. Another avenue is the periodicity of meetings – if these meetings are the same time each week, some one (insider or outsider) may have noticed the laptop is commonly used, unsecure and unattended in an (open or closed?) office/cubicle.

    In this day and age, its alot safer to have data stored on a network device and access, modify and save that data as needed. That way there aren’t multiple copies of the same data which multiple people have modified over time. Plus, if set up correctly, if the system is rebooted most of the META data may be scrubbed. The government should have encrypted hard drives like that thumbdrive – after 10 unsuccessful log-in attempts in a row, the hard drive can render itself useless.

Comments are closed.

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

  • 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
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs

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

  • 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
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

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.