Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

1/2/2008
01:35 PM
Tom LaSusa
Tom LaSusa
Commentary
50%
50%

Social Security ID Protection: A Bloody Mess

A few weeks ago a notebook containing information on 268,000 blood donors was stolen from a Minnesota blood drive. The data included names, addresses, blood types, and Social Security numbers. Police suspect it was a random act, not one committed with the express intent of getting the personal data. Still, it's one just more case of data privacy woe that could be avoided if companies stopped

A few weeks ago a notebook containing information on 268,000 blood donors was stolen from a Minnesota blood drive. The data included names, addresses, blood types, and Social Security numbers. Police suspect it was a random act, not one committed with the express intent of getting the personal data. Still, it's one just more case of data privacy woe that could be avoided if companies stopped using SS numbers to identify customers.

Stolen SS numbers have contributed to untold numbers of identity and credit thefts, in some cases leaving the victim responsible to clean up the mess (often unsuccessfully). With mobile computing, customer information has become more vulnerable than ever. Encryption and diligence hasn't helped thus far -- the crack hackers can bang through the passwords and clearly our eyes can't be on these devices 24/7. Other than having notebooks handcuffed to users or banning their use, what can we do?

For one thing, eliminating Social Security numbers as a means of customer identification would be a step in the right direction. Over at the Privacy Journal, Robert Ellis Smith offers several alternatives for companies looking for other ways of identifying customers. Why not give them a special, unique password -- for example, a series of letters and numbers that either they choose or is randomly generated for them? Now, before anyone complains about 'yet another password to remember,' keep in mind that while it requires extra work on both the company (to set it up) and the customer (to remember it), we're talking about improved identity protection. I don't know about you, but I'm all for a little inconvenience if it means there's not a fake me out there somewhere taking vacations at my expense. And as Smith points out, people have been known to inaccurately provide their Social Security number to businesses anyway. Better to have them rely on a password they've written down and tucked safely in their desk at home than rely on the ever-faulty little gray cells.

If, however, your company insists on using Social Security numbers to some degree, another option could be to use the last four digits of the customer's SS number. The digits aren't enough info for a crook to use, but coupled with additional secure information a customer could provide, it's a sufficient way to identify them.

More and more, people are questioning companies that ask for their Social Security numbers. Recently, the National Association of Secretaries of State released a white paper, "Privacy, Public Access & Policymaking in State Redaction Practices," which offers advice on how to develop policies for removing Social Security numbers and other sensitive information from public documents. Why not pleasantly surprise your customers with a new alternative to identifying them and protecting their records?

What do you think? Can companies eliminate Social Security Numbers as part of the customer identification process, or do you think they are far too ensconced in the system?

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-29367
PUBLISHED: 2020-11-27
blosc2.c in Blosc C-Blosc2 through 2.0.0.beta.5 has a heap-based buffer overflow when there is a lack of space to write compressed data.
CVE-2020-26245
PUBLISHED: 2020-11-27
npm package systeminformation before version 4.30.5 is vulnerable to Prototype Pollution leading to Command Injection. The issue was fixed with a rewrite of shell sanitations to avoid prototyper pollution problems. The issue is fixed in version 4.30.5. If you cannot upgrade, be sure to check or sani...
CVE-2017-15682
PUBLISHED: 2020-11-27
In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to inject malicious JavaScript code resulting in a stored/blind XSS in the admin panel.
CVE-2017-15683
PUBLISHED: 2020-11-27
In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to create a site with specially crafted XML that allows the retrieval of OS files out-of-band.
CVE-2017-15684
PUBLISHED: 2020-11-27
Crafter CMS Crafter Studio 3.0.1 has a directory traversal vulnerability which allows unauthenticated attackers to view files from the operating system.