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.

IoT
5/20/2016
01:58 PM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

5 Tips for Protecting Firmware From Attacks

Don't let hackers take advantage of holes in firmware. Here's how to stop them.
Previous
1 of 6
Next

Just about every component on a computer system contains firmware. Many people just think of the firmware on the system BIOS on a PC, but network interface cards, embedded controllers, graphics cards, USB sticks, mice, keyboards and of course, routers and switches all have firmware.

Yuriy Bulygin and John Loucaides, security researchers at Intel Security, point out that hackers attack firmware because they know many security and IT managers aren’t paying attention to it. They say security teams are so overwhelmed by the prevailing threat landscape, that they have their hands full just deploying the basics, like firewalls, intrusion prevention systems and sandboxes.

“Hackers are depending on security managers ignoring firmware, which means that spreading awareness that firmware must be protected is very important,” Loucaides says.

Bulygin and Loucaides say hackers attack firmware for three main reasons:

  • Persistence. Security mangers can clean up malware on most systems with antivirus software or sandbox it and then remediate with software. Not so with firmware. Compromised firmware could cause malware to keep coming back even after normal remediation actions. 
  • Stealth. Normal mechanisms for detecting malware do not examine firmware. Therefore, compromised firmware can be used to hide malicious behavior for a long time.
  • Full access. If malware can control system firmware, it gains full access to the system. Normal protection mechanisms used by an OS or virtual machine rely on platform characteristics that are controlled by firmware. By altering firmware, malware can usually bypass existing measures.

While much of this may be alarming, there are steps security managers can take to protect their organizations from attacks on firmware. Bulygin and Loucaides outline five tips that help security managers become aware of the issue and offer ways to take steps to plug any potential holes in firmware.

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 6
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
hilalashwaq411
50%
50%
hilalashwaq411,
User Rank: Apprentice
8/27/2016 | 12:46:54 AM
Thank you
Thanks for the wonderful tips! Aside from installing anti malware software (like antivirus - ESET Antivirus etc), one's innocence of malware must be addressed. Be informed and cautious all the time.
honey143
50%
50%
honey143,
User Rank: Apprentice
5/26/2016 | 3:37:44 AM
greetings!!
Awesome article very informative..
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.