recommended reading

Navy aims to limit use of Social Security numbers

The Navy's chief information officer has instructed service organizations to eliminate the use of, or hide or mask service members' Social Security numbers whenever possible while the Defense Department develops a servicewide plan to reduce reliance on the information.

The Navy, along with the other military services, is awaiting Defense guidance for substituting other identifiers where Social Security numbers now are required because the numbers are involved in nearly 70 percent of service data breaches and are a key element in identify theft and fraud, Navy officials said. Officials devoted the most recent issue of CHIPS magazine, the Navy's leading IT publication, to the topic.

Chief Information Officer Terry A. Halvorsen said safeguarding personally identifiable information must be a priority at every level of the Navy, from the people who handle such personal information to the leaders responsible for security controls, training and oversight. "The unauthorized disclosure of the SSN associated with a person's name may result in real consequences," Halvorsen said in the magazine. "I still see too many forms requiring the full SSN when it is not required; we need to get better at this."

Under the Navy's reduction plan, officials must justify the request for Social Security numbers on all Navy and Marine Corps forms and eliminate their use on all unofficial forms. The eventual goal is to have a unique Defense Department ID replace Social Security numbers across all the services. Defense expects to begin removing Social Security numbers from bar codes on service member ID cards by 2012.

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.


When you download a report, your information may be shared with the underwriters of that document.