<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Discover the Secret World Of Online Security! &#187; internet security</title>
	<atom:link href="http://onlineworldsecurity.com/tag/internet-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://onlineworldsecurity.com</link>
	<description>Get the Latest and Hottest News and Releases about Online Security, Internet and Computer Security at Online World Security</description>
	<lastBuildDate>Thu, 28 Jan 2010 18:44:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Internet Security Vulnerabilities on an application layer of OSI model</title>
		<link>http://onlineworldsecurity.com/16/internet-security-vulnerabilities-on-an-application-layer-of-osi-model/</link>
		<comments>http://onlineworldsecurity.com/16/internet-security-vulnerabilities-on-an-application-layer-of-osi-model/#comments</comments>
		<pubDate>Tue, 21 Aug 2007 05:18:05 +0000</pubDate>
		<dc:creator>Online World Security</dc:creator>
				<category><![CDATA[Internet Security Paradigms and Models]]></category>
		<category><![CDATA[Main]]></category>
		<category><![CDATA[OS Security]]></category>
		<category><![CDATA[applicaion layer exploits]]></category>
		<category><![CDATA[internet security]]></category>
		<category><![CDATA[osi model]]></category>

		<guid isPermaLink="false">http://onlineworldsecurity.com/2007/08/21/internet-security-vulnerabilities-on-an-application-layer-of-osi-model/</guid>
		<description><![CDATA[To facilitate the distribution of the malicious code, the combination of several techniques and methods is used. Quite often large spam networks are utilized for the initial distribution of the spam emails. In order to avoid current malware filters, no virus is usually embedded in the email. Instead, the reader is sent to the malicious url. The web-based url is used for automatic download of the exploit.]]></description>
		<wfw:commentRss>http://onlineworldsecurity.com/16/internet-security-vulnerabilities-on-an-application-layer-of-osi-model/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OSI, TCP/IP and the inherent flaws of both models</title>
		<link>http://onlineworldsecurity.com/15/osi-tcpip-and-the-inherent-flaws-of-both-models/</link>
		<comments>http://onlineworldsecurity.com/15/osi-tcpip-and-the-inherent-flaws-of-both-models/#comments</comments>
		<pubDate>Sun, 19 Aug 2007 04:02:42 +0000</pubDate>
		<dc:creator>Online World Security</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[OS Security]]></category>
		<category><![CDATA[internet security]]></category>
		<category><![CDATA[internet security protocols]]></category>
		<category><![CDATA[osi flaws]]></category>
		<category><![CDATA[tcp/ip vulnerabilities]]></category>

		<guid isPermaLink="false">http://onlineworldsecurity.com/2007/08/19/osi-tcpip-and-the-inherent-flaws-of-both-models/</guid>
		<description><![CDATA[IP version 4 is completely insecure, so big hopes were cherished for the introduction of IP version 6. At least it will allow to positively identify the source of attack.
Plus, ping sweeps won’t work anymore simply because of the size of subnets that would have to be scanned. And broadcast will be changed to multicast, thus reducing the number of hosts that will be able to intercept communication. Plus it would be more difficult for worms to spread.  Of course the mandatory inclusion of IPSec in the IPv6 could theoretically be helpful too]]></description>
		<wfw:commentRss>http://onlineworldsecurity.com/15/osi-tcpip-and-the-inherent-flaws-of-both-models/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

