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

7/13/2008
07:18 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Securing Your Wireless Internet Connection (You Know You Should)

Well, it's not really breaking news, security firm Kaspersky Lab is pointing out the obvious: that most home and small business wireless networks run at a low, or no, level of security. Kaspersky Lab also listed a handful of steps that could be taken to enhance your wireless security. And while it's all good advice, it left out one of the most important.

Well, it's not really breaking news, security firm Kaspersky Lab is pointing out the obvious: that most home and small business wireless networks run at a low, or no, level of security. Kaspersky Lab also listed a handful of steps that could be taken to enhance your wireless security. And while it's all good advice, it left out one of the most important.According to the results of the Kaspersky Lab Wireless Internet Access Survey, while 57% of U.K. homes are wirelessly enabled, only 35% of the people they surveyed have taken reasonable precautions to lock down their router.

Here are the five items Kaspersky Lab listed, and they're all wise moves, especially if your wireless router is in an urban area.

1. Change the administrator password for the wireless router. Just 19% of respondents had taken this basic precaution, despite the ease with which a hacker is able to find out the manufacturer's default password and use this to access the wireless network.

2. Avoid using a password that can be guessed easily.

3. Enable encryption: WPA (Wi-Fi Protected Access) encryption is best, if the device supports it. If not, WEP (Wired Equivalent Privacy) should be used. The survey revealed that 11% had the preferred WPA, 18% had WEP, only 6% had WPA2, and 22% did not know what encryption setting they had.

4. Switch off SSID (Service Set Identifier) broadcasting. This prevents the wireless device announcing its presence to the world. Only 4% of respondents to the survey had SSID switched off.

5. Change the default SSID name of the device. It's easy for a hacker to find out the manufacturer's default name and use this to locate your wireless network. Avoid using a name that can be guessed easily: follow the guidelines provided in the section below on choosing a password.

Sure, it's just plain stupid having your router broadcast "name of manufacturer here" with a username of "admin" and the factory password. You may as well leave your front door open. But Kaspersky Lab failed to list using Network Address Translation, or NAT for short, to protect all of your devices that use your wireless connection. All you need to do is make sure you have a NAT-capable router, and set it up.

Basically, when using NAT, from the Internet it appears that only one device is accessing the Internet, and it also goes a long way to making sure a lot of different types of malware don't find their way on your system. For a good explanation on NAT, I recommend reading Steve Gibson's excellent write-up.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Overcoming the Challenge of Shorter Certificate Lifespans
Mike Cooper, Founder & CEO of Revocent,  10/15/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-27621
PUBLISHED: 2020-10-22
The FileImporter extension in MediaWiki through 1.35.0 was not properly attributing various user actions to a specific user's IP address. Instead, for various actions, it would report the IP address of an internal Wikimedia Foundation server by omitting X-Forwarded-For data. This resulted in an inab...
CVE-2020-27620
PUBLISHED: 2020-10-22
The Cosmos Skin for MediaWiki through 1.35.0 has stored XSS because MediaWiki messages were not being properly escaped. This is related to wfMessage and Html::rawElement, as demonstrated by CosmosSocialProfile::getUserGroups.
CVE-2020-27619
PUBLISHED: 2020-10-22
In Python 3 through 3.9.0, the Lib/test/multibytecodec_support.py CJK codec tests call eval() on content retrieved via HTTP.
CVE-2020-17454
PUBLISHED: 2020-10-21
WSO2 API Manager 3.1.0 and earlier has reflected XSS on the "publisher" component's admin interface. More precisely, it is possible to inject an XSS payload into the owner POST parameter, which does not filter user inputs. By putting an XSS payload in place of a valid Owner Name, a modal b...
CVE-2020-24421
PUBLISHED: 2020-10-21
Adobe InDesign version 15.1.2 (and earlier) is affected by a memory corruption vulnerability due to insecure handling of a malicious .indd file, potentially resulting in arbitrary code execution in the context of the current user. User interaction is required to exploit this vulnerability.