Risk
12/22/2011
02:41 PM
50%
50%

NIST Protects BIOS With New Security Guidelines

The standards body provides ways to detect changes to the code or configuration of a PC's startup system.

Government Innovators
Slideshow: Government Innovators
(clickimage for larger view and for full slideshow)
The organization that sets federal technology standards has provided new security guidelines for protecting the system that starts up PCs.

The National Institute for Standards and Technology (NIST) is accepting comments on new guidelines to lock down a computer's Basic Input/Output System (BIOS), which--because it is a very basic, low-level function--can cause a significant security threat if unauthorized changes are made to it, according to NIST.

The document, BIOS Integrity Measurement Guidelines, provides “integrity measurement mechanisms” that have two aims, according to NIST. One is to detect changes to the BIOS code that could allow malicious software to run during a PC's boot process, and the other is to detect changes to the configuration of the system.

The document provides several use-case scenarios associated with BIOS functions that inform the security recommendations presented in the document.

The uses cases include installing and/or verifying the correct BIOS revision for a given client; imaging the BIOS with appropriate settings; setting BIOS passwords; asserting security controls requiring physical presence, including a PC's Trusted Platform Module; and registering the endpoint identity and integrity metrics in the pertinent IT databases, according to the document.

[The National Institute for Standards and Technology also has been busy building a cloud roadmap for government. See NIST Releases Federal Cloud Roadmap, Architecture.]

The guidelines--the second in a series aimed at locking down a PC's startup system--are aimed at hardware and software vendors developing products to support BIOS integrity measurement mechanisms, as well as organizations developing these types of security technologies, according to NIST.

The standards organization published the first in its series of BIOS security guidelines in April. That document, BIOS Protection Guidelines, provided ways for computer manufacturers to build security features directly into the BIOS to prevent unauthorized modifications.

Those interested have until Jan. 20, 2012 to comment on the most recent BIOS guidelines, NIST said.

Database access controls keep information out of the wrong hands. Limit who sees what to stop leaks--accidental and otherwise. Also in the new, all-digital Dark Reading supplement: Why user provisioning isn't as simple as it sounds. Download the supplement now. (Free registration required.)

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5361
Published: 2015-04-21
Multiple cross-site request forgery (CSRF) vulnerabilities in Landesk Management Suite 9.6 and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) start, (2) stop, or (3) restart services via a request to remote/serverServices.aspx.

CVE-2014-5370
Published: 2015-04-21
Directory traversal vulnerability in the CFChart servlet (com.naryx.tagfusion.cfm.cfchartServlet) in New Atlanta BlueDragon before 7.1.1.18527 allows remote attackers to read or possibly delete arbitrary files via a .. (dot dot) in the QUERY_STRING to cfchart.cfchart.

CVE-2015-1701
Published: 2015-04-21
Unspecified vulnerability in Microsoft Windows before 8 allows local users to gain privileges via unknown vectors, as exploited in the wild in April 2015.

CVE-2015-2041
Published: 2015-04-21
net/llc/sysctl_net_llc.c in the Linux kernel before 3.19 uses an incorrect data type in a sysctl table, which allows local users to obtain potentially sensitive information from kernel memory or possibly have unspecified other impact by accessing a sysctl entry.

CVE-2015-2042
Published: 2015-04-21
net/rds/sysctl.c in the Linux kernel before 3.19 uses an incorrect data type in a sysctl table, which allows local users to obtain potentially sensitive information from kernel memory or possibly have unspecified other impact by accessing a sysctl entry.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.