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

Image Source: hackaday.com

Image Source: hackaday.com

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..
44% of Security Threats Start in the Cloud
Kelly Sheridan, Staff Editor, Dark Reading,  2/19/2020
Zero-Factor Authentication: Owning Our Data
Nick Selby, Chief Security Officer at Paxos Trust Company,  2/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9405
PUBLISHED: 2020-02-26
IBL Online Weather before 4.3.5a allows unauthenticated reflected XSS via the redirect page.
CVE-2020-9406
PUBLISHED: 2020-02-26
IBL Online Weather before 4.3.5a allows unauthenticated eval injection via the queryBCP method of the Auxiliary Service.
CVE-2020-9407
PUBLISHED: 2020-02-26
IBL Online Weather before 4.3.5a allows attackers to obtain sensitive information by reading the IWEBSERVICE_JSONRPC_COOKIE cookie.
CVE-2020-9398
PUBLISHED: 2020-02-25
ISPConfig before 3.1.15p3, when the undocumented reverse_proxy_panel_allowed=sites option is manually enabled, allows SQL Injection.
CVE-2015-5201
PUBLISHED: 2020-02-25
VDSM and libvirt in Red Hat Enterprise Virtualization Hypervisor (aka RHEV-H) 7-7.x before 7-7.2-20151119.0 and 6-6.x before 6-6.7-20151117.0 as packaged in Red Hat Enterprise Virtualization before 3.5.6 when VSDM is run with -spice disable-ticketing and a VM is suspended and then restored, allows r...