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
Comments
Newest First  |  Oldest First  |  Threaded View
Ransomware Grabs Headlines but BEC May Be a Bigger Threat
Marc Wilczek, Digital Strategist & CIO Advisor,  10/12/2017
20 Questions to Ask Yourself before Giving a Security Conference Talk
Joshua Goldfarb, Co-founder & Chief Product Officer, IDDRA,  10/16/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Be a unicorn, not a donkey...
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
The State of Ransomware
The State of Ransomware
Ransomware has become one of the most prevalent new cybersecurity threats faced by today's enterprises. This new report from Dark Reading includes feedback from IT and IT security professionals about their organization's ransomware experiences, defense plans, and malware challenges. Find out what they had to say!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.