Sponsored Content
Special Forums Cybersecurity IT Security RSS Your Social Security Number (SSN) - Shouldn't you Control It? Post 302218070 by Linux Bot on Thursday 24th of July 2008 10:05:37 AM
Old 07-24-2008
Your Social Security Number (SSN) - Shouldn't you Control It?

Last week, I saw two stories on a local television network, about two different local organizations that exposed Social Security Numbers (SSN) through two different forms of media: electronic communications and the U.S. Mail. I have chosen to leave the names of the organization absent in this posting, because the stories are not important, but rather the level of importance these stories had as compared to other less related stories. In the total of roughly 5 minutes given to these individual stories through a local news station, the impact has left me thinking about how desensitized our society must be as it relates to the protection of the SSN. Security has always been considered critical to controlling access to systems, but who is controlling access to data? Data in itself is the reason for protecting systems, but somehow, data gets exposed, and it has nothing to do with security of the system.

If the Social Security Number represents your identify, why can't you control how it is used. According to the Social Security Administration (SSA) Publication No. 05-10064, October 2007 "the Social Security Administration protects your Social Security number and keeps your records confidential." But what about the hundreds of other organizations that have your SSN? Are they providing the same guarantee when protect your personal information?

These two stories carelessly exposed the SSN, not by a lack of protection in the systems, but a lack of protection in handling the data (specifically the SSN). I believe just as online services such as banking and other financial institutions are requiring more and more methods of identity authentication to access their online sites for performing routine financial and transaction-based functions, the SSN needs to be upgraded to require multiple layers of security to represent ones identity, such as a consumer chosen pin, or a loopback verification that gives you the consumer insight into when and how your SSN has been used. Until these measures have been implemented, your SSN may never be within your control.


Image
Image

More...
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

help removing dashes from social security number

I have a file containing social security numbers with the format ###-##-####. I need to read each record in this file, reformat the SSN to the format #########, and write the record with the reformatted SSN to a new file. I am a UNIX newbie. I think I need to use either the sed or awk commands, but... (2 Replies)
Discussion started by: Marcia P
2 Replies

2. What is on Your Mind?

Social Security number?

We have now been living in Vence for 3 months. My husband works for a large IT company. How do we get hold of our Social Security numbers and Carte Vitale please? Thanks (4 Replies)
Discussion started by: shanekol
4 Replies

3. Cybersecurity

Does anyone know any ways to protect social security number?

Hello everybody, I have been using my social security number for my taxation purposes. But, I have been recently intimidated by my lawyer that since the crime of identity theft has been on the high I should be careful in using it. I am really concerned about this and need to know whether there are... (1 Reply)
Discussion started by: shanekol
1 Replies

4. Shell Programming and Scripting

How to Control Number of Processes Running

Hi Is there a way to count how many processes a script has started, count how many of these have finished, and make the script wait if their difference goes over a given threshold? I am using a script to repeatedly execute a code (~100x) which converts 2 data files into one .plt which is in... (4 Replies)
Discussion started by: drbones
4 Replies
MooseX::Types::Common::String(3pm)			User Contributed Perl Documentation			MooseX::Types::Common::String(3pm)

NAME
MooseX::Types::Common::String - Commonly used string types SYNOPSIS
use MooseX::Types::Common::String qw/SimpleStr/; has short_str => (is => 'rw', isa => SimpleStr); ... #this will fail $object->short_str("string with breaks"); DESCRIPTION
A set of commonly-used string type constraints that do not ship with Moose by default. o SimpleStr A Str with no new-line characters. o NonEmptySimpleStr A Str with no new-line characters and length > 0 o LowerCaseSimpleStr A Str with no new-line characters, length > 0 and no uppercase characters A coercion exists via "lc" from NonEmptySimpleStr o UpperCaseSimpleStr A Str with no new-line characters, length > 0 and no lowercase characters A coercion exists via "uc" from NonEmptySimpleStr o Password o StrongPassword o NonEmptyStr A Str with length > 0 o LowerCaseStr A Str with length > 0 and no uppercase characters. A coercion exists via "lc" from NonEmptyStr o UpperCaseStr A Str with length > 0 and no lowercase characters. A coercion exists via "uc" from NonEmptyStr o NumericCode A Str with no new-line characters that consists of only Numeric characters. Examples include, Social Security Numbers, PINs, Postal Codes, HTTP Status Codes, etc. Supports attempting to coerce from a string that has punctuation in it ( e.g credit card number 4111-1111-1111-1111 ). SEE ALSO
o MooseX::Types::Common::Numeric AUTHORS
Please see:: MooseX::Types::Common perl v5.14.2 2012-06-14 MooseX::Types::Common::String(3pm)
All times are GMT -4. The time now is 03:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy