DataBreaches.Net

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

DoD to reduce use of Social Security numbers

Posted on March 5, 2010 by Dissent

Rick Maze reports:

The Defense Department is preparing to launch a militarywide effort to reduce the use of Social Security numbers to lower the chances of identity theft for military and civilian workers and contractors.

But the announcement, included in the March 3 Federal Register, makes clear that stopping the use of Social Security numbers altogether is not feasible.

The SSN is a prize to identity thieves, but it also has become ingrained in various military uses that can’t be fully eliminated, defense officials said. They are proposing new regulations calling for a complete review of military records and reports to determine when the number isn’t necessary.

In phases, starting in 1969 and ending in 1974, Social Security numbers replaced service numbers as the primary identifier and authenticator of military personnel.

[…]

The proposed regulation, open for comment until May 3, says there are several purposes for which SSNs remain acceptable, such as for employment and tax purposes, security clearance investigations, computer matching with other government agencies, and as the primary form of identification for Geneva Conventions purposes.

In all other cases, the proposed regulation directs a review of every instance when SSNs are used in military records to determine if a replacement is possible.

Read more in Navy Times.

The Federal Register notice can be found here.

No related posts.

Category: Government Sector

Post navigation

← ID theft charges superceded by murder indictment
(update 2) Only Wyndham-branded hotels involved in three breaches →

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

  • Russia Jailed Hacker Who Worked for Ukrainian Intelligence to Launch Cyberattacks on Critical Infrastructure
  • Kentfield Hospital victim of cyberattack by World Leaks, patient data involved
  • India’s Max Financial says hacker accessed customer data from its insurance unit
  • Brazil’s central bank service provider hacked, $140M stolen
  • Iranian and Pro-Regime Cyberattacks Against Americans (2011-Present)
  • Nigerian National Pleads Guilty to International Fraud Scheme that Defrauded Elderly U.S. Victims
  • Nova Scotia Power Data Breach Exposed Information of 280,000 Customers
  • No need to hack when it’s leaking: Brandt Kettwick Defense edition
  • SK Telecom to be fined for late data breach report, ordered to waive cancellation fees, criminal investigation into them launched
  • Louis Vuitton Korea suffers cyberattack as customer data leaked

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

  • On July 7, Gemini AI will access your WhatsApp and more. Learn how to disable it on Android.
  • German court awards Facebook user €5,000 for data protection violations
  • Record-Breaking $1.55M CCPA Settlement Against Health Information Website Publisher
  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t

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.