Risk
12/22/2011
02:41 PM
Connect Directly
RSS
E-Mail
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
Dark Reading, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2006-1318
Published: 2014-09-19
Microsoft Office 2003 SP1 and SP2, Office XP SP3, Office 2000 SP3, Office 2004 for Mac, and Office X for Mac do not properly parse record lengths, which allows remote attackers to execute arbitrary code via a malformed control in an Office document, aka "Microsoft Office Control Vulnerability."

CVE-2012-2588
Published: 2014-09-19
Multiple cross-site scripting (XSS) vulnerabilities in MailEnable Enterprise 6.5 allow remote attackers to inject arbitrary web script or HTML via the (1) From, (2) To, or (3) Subject header or (4) body in an SMTP e-mail message.

CVE-2012-6659
Published: 2014-09-19
Cross-site scripting (XSS) vulnerability in the admin interface in Phorum before 5.2.19 allows remote attackers to inject arbitrary web script or HTML via a crafted URL.

CVE-2014-1391
Published: 2014-09-19
QT Media Foundation in Apple OS X before 10.9.5 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted movie file with RLE encoding.

CVE-2014-3614
Published: 2014-09-19
Unspecified vulnerability in PowerDNS Recursor (aka pdns_recursor) 3.6.x before 3.6.1 allows remote attackers to cause a denial of service (crash) via an unknown sequence of malformed packets.

Best of the Web
Dark Reading Radio