DataBreaches.Net

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

Wisconsin senators want answers from the VA about repeated breaches

Posted on October 30, 2015 by Dissent

Earlier today, I posted an item and commentary about a breach affecting veterans in Wisconsin. Adam Schrager’s report indicated that there were recurring problems and that the VA knew about these problems but has not addressed them to prevent recurrences.  One of the problems involves the VA’s software not flagging SSN that are unhyphenated for mandatory encryption. The VA reportedly does that intentionally because flagging all 9-digit numbers would generate a lot of false positives. The VA did not explain why they didn’t therefore require that all SSN be entered with hyphens. The second problem is that VA personnel are sending information such as SSN and disability claims information to recipients who do not have the clearance to handle such sensitive information.

In an update, Adam now reports that Wisconsin senators are demanding answers from the Veterans Administration. To which DataBreaches.net says, “Good!” They should not be allowed to knowingly and repeatedly put veterans at risk of identity theft.


Related:

  • 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
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • NY: Gloversville hit by ransomware attack, paid ransom
  • 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.
Category: ExposureGovernment SectorU.S.

Post navigation

← PHP Freaks forum database hacked
Hacking Team Offering Encryption Cracking Tools to Law Enforcement Agencies →

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

  • 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
  • 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

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

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.