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.

Risk

Congress Proposes FISMA Overhaul

Amendments would update the 2002 law for today's federal IT environment, transfer cybersecurity oversight from Homeland Security to OMB.

Lawmakers have proposed amendments to the 10-year-old law that sets federal cybersecurity standards to account for changes that have since occurred in the federal IT environment.

Reps. Darrell Issa (R-Calif.) and Elijah Cummings (D-Md.), the chairman and ranking member of the House Oversight and Government Reform Committee, unveiled the Federal Information Security Amendments Act of 2012 to overhaul the Federal Information Security Act of 2002, or FISMA.

The act--which has been posted online--points out that the federal IT environment has become increasingly interconnected over the last 10 years, and the security industry itself also has matured.

In light of these changes, the act calls for continuous monitoring and regular assessments of federal IT systems to ensure their security; mandates the establishment of baseline security controls for agencies as a framework for gauging the effectiveness of those controls; and gives agencies more authority to make decisions about using off-the-shelf security products in their respective IT systems, among other changes.

It also would transfer much of the oversight of agency cybersecurity away from the Department of Homeland Security (DHS) and back to the Office of Management and Budget (OMB), a shift from the current dynamic.

[ The Obama administration also unveiled cybersecurity directives this week. See White House Sets Cybersecurity Priorities. ]

The OMB expanded the DHS's cybersecurity profile in 2010, and the agency has been at the forefront of much of federal cybersecurity activities since then. Indeed, the DHS and the Department of Commerce's National Institute of Standards and Technology (NIST) currently have the lion's share of overseeing agencies' FISMA guidance and implementation.

Cybersecurity has been a chief concern for the Obama administration, but despite a number of proposed laws debated in Congress, lawmakers have yet to pass comprehensive legislation to protect U.S. critical infrastructure and federal networks against cyber threats.

Last May, President Obama sent a broad cybersecurity proposal to lawmakers to overhaul the nation's cybersecurity laws as a way to speed the process along, and earlier this year various officials--including Obama's cybersecurity coordinator Howard Schmidt--also pushed lawmakers to act.

In the meantime, agencies depend on FISMA to guide them to protect federal networks. Officials already are working to integrate some of the concepts proposed by the amendment into the law. To facilitate continuous monitoring, for instance, in 2011 the DHS outlined new requirements for FISMA agencies reporting security information monthly via data feeds to CyberScope, an internal compliance tool.

The effort to achieve and maintain compliance with Sarbanes-Oxley requirements remains one of the primary drivers behind many IT security initiatives. In our Security Via SOX Compliance report, we share 10 best practices to meet SOX security-related requirements and help ensure you'll pass your next compliance audit. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3460
PUBLISHED: 2021-04-13
The Motorola MH702x devices, prior to version 2.0.0.301, do not properly verify the server certificate during communication with the support server which could lead to the communication channel being accessible by an attacker.
CVE-2021-3462
PUBLISHED: 2021-04-13
A privilege escalation vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could allow unauthorized access to the driver's device object.
CVE-2021-3463
PUBLISHED: 2021-04-13
A null pointer dereference vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could cause systems to experience a blue screen error.
CVE-2021-3471
PUBLISHED: 2021-04-13
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.
CVE-2021-3473
PUBLISHED: 2021-04-13
An internal product security audit of Lenovo XClarity Controller (XCC) discovered that the XCC configuration backup/restore password may be written to an internal XCC log buffer if Lenovo XClarity Administrator (LXCA) is used to perform the backup/restore. The backup/restore password typically exist...