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

Identifying With DHS

Department of Homeland Security struck a balance between caution and flexibility in its personal ID plan

It's a complicated thing, this feeling I have about identity. On the one hand, I think that any system purporting to accurately identify someone should do just that. Whether we're talking about authentication for a computer network or a driver's license, an ID system should be positive and hard to spoof. With that said, I don't want to have to show ID any more than absolutely necessary. I like single sign-on for computer systems, and I think that in the course of an average day, no one should need more than my word and a handshake about just who I am.

These conflicting feelings are common among U.S. citizens. Add technological issues and you have plenty of reasons to be cautious about radical changes to the way we implement our most common ID systems. The Real ID Initiative, coming out of the wide range of responses to the attacks of 9/11, was intended to make driver's licenses more reliable as a form of ID.

At various times, it was suggested that the cards encode biometric information, such as a fingerprint, that they carry additional personal data in the form of an RFID chip. There was also the suggestion that state driver's licenses become a de facto national ID card, with the state data bases linked into a national system controlled by one or another federal government agency. Predictably, some states loved the idea while others were strongly opposed.

The proposed standard has now been released, and I have to say I think they got the broad outline right. (See Homeland Security Issues Specs for Controversial Real ID.) Using a barcode rather than RFID makes it impossible for someone to snag your personal information while the card is still in your wallet. I'd have been somewhat happier with a 3D barcode, rather than the 2D system called for, but that's a nit. By declining to mandate technology that's not currently up to the job, the DHS has shown uncommon sanity in what has been, and will be, a contentious process.

They got it even better by not disallowing RFID and biometrics from state licenses. If a particular state feels the need for either of these technologies and wants to work with suppliers to build a next-generation ID system that doesn't threaten the privacy of its citizens, no one at DHS is saying no. A state makes a far better laboratory than does a nation, and I'm sure that some states will forge ahead. When they do, they'll help build a better system that can ultimately be adopted by other states. Just look how well the touch-screen voting system rollout has worked.

The touch-screen voting experience is a good reason for DHS to have been quite conservative here. It's important not only that the ID system work, but that the citizens have confidence in its operation. I think most of us want meaningful identification systems, but we don't want to risk ending up with something worse than we have now. DHS has answered the concerns with a well conceived proposal.

— Curt Franklin is an enthusiastic security geek who used to be one of the Power Rangers (the red one, we think). His checkered past includes stints as a security consultant, an IT staffer at the University of Florida, security editor at Network Computing, chief podcaster for CMP Technology, and various editorial positions at places like InternetWeek, Byte, and Hog Monthly. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.