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.


Fed Wireless Networks Need Tighter Security, NIST Says

Government standards body issues guidelines designed to reduce security vulnerabilities in WLANs.

10 Companies Driving Mobile Security
10 Companies Driving Mobile Security
(click image for larger view and for slideshow)
Federal agencies should do more to consider the security of wireless networks before they deploy them because of the particular protections these networks require, according to the federal national standards organization.

A report by National Institute for Standards and Technology (NIST), released last week, provides guidelines for securing wireless local area networks (WLANs) in federal agencies. These networks are more vulnerable to intrusion due to the ease of access to them and what are often weak security configurations, as people tend to "favor convenience over security" when deploying them, according to NIST.

Pointing out these particular security needs, the report recommends that agencies set standards for configuring the security of these networks, as each component of the network--including the end-user devices that use the network--depend on this configuration.

To do this, NIST recommends an agency or organization first gather information on both the operational and security needs of the network, taking into consideration any laws and policies outside of the organization itself that might govern the network. This could mean meeting requirements of the Department of Homeland Security, Office of Management and Budget, and other agencies that have jurisdiction over agency cybersecurity, according to NIST.

[The feds are taking a new approach to combat growing threats to national security. Learn more: Homeland Security Revamps Cyber Arm.]

They also should consider not only security of the network itself but how the WLAN may affect other networks that exist nearby, according to NIST. Wireless networks are often connected to wired networks, as well as to each other, so agencies may have to consider separations between them based on security needs.

NIST also recommended that agencies continuously monitor WLANs because of their increased security risks--identifying and applying patches and verifying security configuration settings and adjusting them regularly.

"These actions should be performed at least as often for WLAN components as they are for the organization's other systems with similar security needs," according to NIST.

Indeed, continuous monitoring is a theme that has become pervasive in federal security as agencies strive to be more proactive about protecting networks rather than waiting for a problem to occur.

The Federal Information Security Management Act (FISMA), NIST's standard for federal security implementation, recently required agencies to begin reporting security data monthly to an online compliance tool called CyberScope as part of new fiscal year 2011 requirements for continuous monitoring.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment:   It's a PEN test of our cloud security.
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-01-24
yast2-security didn't use secure defaults to protect passwords. This became a problem on 2019-10-07 when configuration files that set secure settings were moved to a different location. As of the 20191022 snapshot the insecure default settings were used until yast2-security switched to stronger defa...
PUBLISHED: 2020-01-24
UNIX Symbolic Link (Symlink) Following vulnerability in the packaging of privoxy on openSUSE Leap 15.1, Factory allows local attackers to escalate from user privoxy to root. This issue affects: openSUSE Leap 15.1 privoxy version 3.0.28-lp151.1.1 and prior versions. openSUSE Factory privoxy version 3...
PUBLISHED: 2020-01-24
UNIX Symbolic Link (Symlink) Following vulnerability in the packaging of gnump3d in openSUSE Leap 15.1 allows local attackers to escalate from user gnump3d to root. This issue affects: openSUSE Leap 15.1 gnump3d version 3.0-lp151.2.1 and prior versions.
PUBLISHED: 2020-01-24
A Symbolic Link (Symlink) Following vulnerability in the packaging of munin in openSUSE Factory, Leap 15.1 allows local attackers to escalate from user munin to root. This issue affects: openSUSE Factory munin version 2.0.49-4.2 and prior versions. openSUSE Leap 15.1 munin version 2.0.40-lp151.1.1 a...
PUBLISHED: 2020-01-24
A symlink following vulnerability in the packaging of mailman in SUSE SUSE Linux Enterprise Server 11, SUSE Linux Enterprise Server 12; openSUSE Leap 15.1 allowed local attackers to escalate their privileges from user wwwrun to root. Additionally arbitrary files could be changed to group mailman. Th...