DataBreaches.Net

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

Oregon State U. notifies 34,000 of computer virus

Posted on July 14, 2010 by Dissent

Clearly Oregon State University does not pay enough attention to security bloggers who have derided such trite phrases as “in an abundance of caution.” Their press release from today:

Oregon State University is notifying 34,000 current and former employees that a computer containing some of their personal information was recently infected by a virus, even though the university’s computer experts say it is “highly unlikely” that the virus put any of that information in the hands of unauthorized users, OSU officials say.

The university is making the notification out of an abundance of caution and to comply with both the letter and spirit of the Oregon Consumer Identity Theft Protection Act. While there is no evidence that individual information has been accessed by a third party, officials are going to such lengths, in part, because records for many of those employed between 1999 and 2005 contained Social Security numbers as the “unique identifier” in each employee’s record, and the presence of those numbers raises the potential, however remote, of identity theft.

“We don’t want to unnecessarily alarm individuals, because in this case we have no evidence that any data was extracted, nor any evidence of identity theft linked to this security breach,” said Jon Dolan, chief information security officer for OSU. “Notifying individuals gives them the opportunity to take preventive measures, should they so choose, to place extra protections on their credit information and further minimize any individual risk.”

Each of the individuals whose records are involved is receiving a letter this week outlining the data breach and providing options for protecting their data against exploitation. Those options range from simply monitoring their financial accounts and credit reports to placing a freeze on their credit files.

OSU has also opened a hotline for individuals who may have additional questions or concerns (541-737-1007) and an e-mail address for those who would like to express their concerns in writing: [email protected].

Officials have also created a web-based question-and-answer page to help address additional concerns individuals may have: http://oregonstate.edu/incidentresponse.

“We take seriously the fact that identity theft has become an important problem in recent years and that as an institution required to collect a significant amount of personal data from our employees, we have responsibilities to safeguard that data,” said Dolan. “So in the rare event that a breach like this happens, we feel it’s our duty to go above and beyond to raise awareness and encourage preventive measures. By doing so, we hope there will be no further problems associated with this incident.”


Related:

  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • NY: Gloversville hit by ransomware attack, paid ransom
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Confidence in ransomware recovery is high but actual success rates remain low
  • 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
Category: Breach IncidentsEducation SectorMalwareU.S.

Post navigation

← Senators re-introduce bill to improve security, require notification of breaches
List of 1,300 Alleged Illegal Immigrants Released in Utah →

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

  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals
  • Gates Down: Third Circuit Says Breaking Employer Computer Access Policies Is Not Hacking
  • Short-term renewal of cyber information sharing law appears in bill to end shutdown
  • Yanluowang ransomware IAB pleads guilty
  • Lawsuit Alleges Ex-Intel Employee Hid 18,000 Sensitive Documents Prior to Leaving the Company
  • HIPAA, but for non-Covered Entities?
  • Manassas City Public Schools close on Monday due to cyberattack

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map
  • EPIC Publishes New Whitepaper Detailing Privacy Risks of Government Data Mining Programs
  • Modern cars are spying on you. Here’s what you can do about it.

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.