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.


Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/14/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Lock-Pickers Face an Uncertain Future Online
Seth Rosenblatt, Contributing Writer,  8/10/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-08-13
ABBYY network license server in ABBYY FineReader 15 before Release 4 (aka allows escalation of privileges by local users via manipulations involving files and using symbolic links.
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.