<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on Keep up with public wireless dangers and Wi-Fi security standards ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-135004]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/11-135004/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-19T10:09:09-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[Wi-Fi Security]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-135004-1511810]]></link>
        <description><![CDATA[Everyone knows that Wi-Fi/wireless is an easy prey for hackers. We as the security in-charge, what can we do to prevent them from attacking the targeted destination which can be easily trace by hackers? Besides than a well configured multi-layer firewall, back-door security, antivirus, anti-trojans, integrated VPN, High-Performance Web Cache, Web Filtering, Intrusion Detection, and others, is there any hardware we can use to support all this software? I've tried Authenex e-Security. It had a Strong (Web) Access Control to control both outbond and inbond access. No doubt it has a powerful tools to secure files of any type but as a professional hacker they will try to penetrate the targeted source from other dimension. Suchs as scripts, key-detecter and etc.Where else will the hacker attact from? The favourite source or easier host.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-135004-1511810]]></guid>
        <dc:creator><![CDATA[aggressive_alien@...]]></dc:creator>
        <pubDate>Wed, 13 Aug 2003 01:59:09 -0700</pubDate>
    </item>
    </channel>
</rss>

