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

3/13/2007
03:30 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

HID Lists RFID Security Steps

In open letter to its customers, RFID vendor HID Global stands by its products, offers protective measures

RFID vendor HID Global Corp. , which has been embroiled in controversy over threats of a patent lawsuit against IOActive for an RFID cloning hack, has issued an open letter to its customers on its Website that acknowledges cloning of some RFID-based cards is indeed possible, but that its Prox-based RFID products are secure. (See HID, IOActive Butt Heads Again and Black Hat Cancels RFID Demo.)

"While we acknowledge that it may be possible, under certain conditions, to clone some proximity cards, we believe access control systems that use Prox are secure when they are combined with proper procedures and policies, and where necessary, additional layers of security such as surveillance cameras, keypad readers and/or fingerprint readers, to name a few," says HID Global president and CEO Denis R. Hébert in the letter.

HID and IOActive came to virtual blows earlier this month over a planned presentation by an IOActive researcher at Black Hat DC. IOActive yanked the HID-related presentation data from its briefing due to concerns of a patent lawsuit from HID. HID maintained that it did not pressure IOActive to stop the presentation, but that it had asked IOActive not to reveal the source code and schematics, and to provide solutions to the flaws the presentation was to highlight.

Neither side budged after meeting face-to-face at a Black Hat press conference.

Meanwhile, Hébert says in the letter to HID customers that the human element is "critical to security as well," and recommends several steps to secure access cards from being hacked, to quote:

  • Require immediate reporting of lost or stolen cards (so they can be deleted from the system)

  • Prohibit sharing or lending of cards

  • Encourage employees to shield their cards from public view when not at work (this makes sense from a privacy perspective as well if a name and picture are printed on the card)

  • Encourage reporting of suspicious activity at the facility

  • Discourage "tailgating" where one employee uses a card to gain access and others follow without using their own cards.

HID's Hébert also says RFID shielding products can provide another level of security and privacy for HID cards "when they are not being used."

— Kelly Jackson Higgins, Senior Editor, Dark Reading

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
The Problem with Artificial Intelligence in Security
Dr. Leila Powell, Lead Security Data Scientist, Panaseer,  5/26/2020
10 iOS Security Tips to Lock Down Your iPhone
Kelly Sheridan, Staff Editor, Dark Reading,  5/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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-2019-6342
PUBLISHED: 2020-05-28
An access bypass vulnerability exists when the experimental Workspaces module in Drupal 8 core is enabled. This can be mitigated by disabling the Workspaces module. It does not affect any release other than Drupal 8.7.4.
CVE-2020-11082
PUBLISHED: 2020-05-28
In Kaminari before 1.2.1, there is a vulnerability that would allow an attacker to inject arbitrary code into pages with pagination links. This has been fixed in 1.2.1.
CVE-2020-5357
PUBLISHED: 2020-05-28
Dell Dock Firmware Update Utilities for Dell Client Consumer and Commercial docking stations contain an Arbitrary File Overwrite vulnerability. The vulnerability is limited to the Dell Dock Firmware Update Utilities during the time window while being executed by an administrator. During this time wi...
CVE-2020-13660
PUBLISHED: 2020-05-28
CMS Made Simple through 2.2.14 allows XSS via a crafted File Picker profile name.
CVE-2020-11079
PUBLISHED: 2020-05-28
node-dns-sync (npm module dns-sync) through 0.2.0 allows execution of arbitrary commands . This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This has been fixed in 0.2.1.