<?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>Comprehensive Computer &#187; target</title>
	<atom:link href="http://www.ledanet.org/tag/target/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ledanet.org</link>
	<description>www.ledanet.org</description>
	<lastBuildDate>Wed, 01 Feb 2012 11:40:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Correlation analysis</title>
		<link>http://www.ledanet.org/correlation-analysis-2/</link>
		<comments>http://www.ledanet.org/correlation-analysis-2/#comments</comments>
		<pubDate>Sun, 04 Dec 2011 23:04:00 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[act]]></category>
		<category><![CDATA[analysis]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[correlation]]></category>
		<category><![CDATA[correlation analysis]]></category>
		<category><![CDATA[cross correlation]]></category>
		<category><![CDATA[fashion]]></category>
		<category><![CDATA[identification]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[nimda worm]]></category>
		<category><![CDATA[robust data]]></category>
		<category><![CDATA[s type]]></category>
		<category><![CDATA[slapper worm]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[target identification]]></category>
		<category><![CDATA[telltale signs]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[time range]]></category>
		<category><![CDATA[time window]]></category>
		<category><![CDATA[worm]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=253</guid>
		<description><![CDATA[Worms typically act in the same fashion, utilizing the same target identification techniques as well as the same attack routines. These leave telltale signs in the logs and can be used to track their behavior. As a worm spreads, an increasing number of hosts act as worm nodes, performing scans and attacks. The frequency of [...]]]></description>
			<content:encoded><![CDATA[<p>Worms typically act in the same fashion, utilizing the same target identification techniques as well as the same attack routines. These leave telltale signs in the logs and can be used to track their behavior. As a worm spreads, an increasing number of hosts act as worm nodes, performing scans and attacks. The frequency of these scans and attacks grows as the worm spreads to more hosts, meaning more observations will be found in any time window. These events can be analyzed through correlation analysis.</p>
<p>Simply stated, correlation analysis is the act of analyzing a data set to find the connectedness of events within the set. Autocorrelation analysis is the analysis of events of the same type, while crosscorrelation analysis looks at the interaction of two different events. The core of the analysis is to find the proximity in time of the two events being correlated. A strong correlation between the two events is indicative of a strong relationship.<br />
<span id="more-253"></span><br />
For network worms that perform active target identification, the two types of data to analyze in this fashion are scans and attacks. Because worms actively seek hosts prior to their attack, a correlation will be seen between scans and between scans and attacks within a short time range. For network worms, this correlation time is tens of seconds to several minutes. When the scans and attacks are issued by attackers, the correlation is not nearly as strong, with a large variance in the time difference between events.</p>
<p>The data for the cross-correlation analysis was taken from an introduction of the Slapper worm into a small research network used for data analysis in the research. Due to the size of the network, the number of observations is smaller than the data points used in the Nimda worm analysis, leading to a less robust data set. In this analysis, the scan performed by the Slapper worm (a request for the server’s top file in an attempt to identify the server’s type) was analyzed in relation to the time of the attack by the client. <a href="http://www.achatsachats.net/?p=25" target="_blank">Lidl</a>.</p>
<p>Correlation analysis can be performed on any data set if any one or two unique events can be measured. The time differences can be used to analyze larger events for coordinated anomalies. Worms will typically have a cluster of observations at short time intervals where other network events will usually not have such a strong association of data points.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/correlation-analysis-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Correlation analysis</title>
		<link>http://www.ledanet.org/correlation-analysis/</link>
		<comments>http://www.ledanet.org/correlation-analysis/#comments</comments>
		<pubDate>Wed, 23 Nov 2011 13:39:59 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[act]]></category>
		<category><![CDATA[analysis]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[auto correlation]]></category>
		<category><![CDATA[computer repair service]]></category>
		<category><![CDATA[correlation]]></category>
		<category><![CDATA[correlation analysis]]></category>
		<category><![CDATA[cross correlation]]></category>
		<category><![CDATA[Dallas]]></category>
		<category><![CDATA[fashion]]></category>
		<category><![CDATA[identification]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[nimda worm]]></category>
		<category><![CDATA[robust data]]></category>
		<category><![CDATA[slapper worm]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[target identification]]></category>
		<category><![CDATA[telltale signs]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[time range]]></category>
		<category><![CDATA[time window]]></category>
		<category><![CDATA[worm]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=245</guid>
		<description><![CDATA[Worms typically act in the same fashion, utilizing the same target identification techniques as well as the same attack routines. These leave telltale signs in the logs and can be used to track their behavior. As a worm spreads, an increasing number of hosts act as worm nodes, performing scans and attacks. The frequency of [...]]]></description>
			<content:encoded><![CDATA[<p>Worms typically act in the same fashion, utilizing the same target identification techniques as well as the same attack routines. These leave telltale signs in the logs and can be used to track their behavior. As a worm spreads, an increasing number of hosts act as worm nodes, performing scans and attacks. The frequency of these scans and attacks grows as the worm spreads to more hosts, meaning more observations will be found in any time window. These events can be analyzed through correlation analysis.</p>
<p>Simply stated, correlation analysis is the act of analyzing a data set to find the connectedness of events within the set. Auto correlation analysis is the analysis of events of the same type, while cross correlation analysis looks at the interaction of two different events. The core of the analysis is to find the proximity in time of the two events being correlated. A strong correlation between the two events is indicative of a strong relationship.<br />
<span id="more-245"></span><br />
For network worms that perform active target identification, the two types of data to analyze in this fashion are scans and attacks. Because worms actively seek hosts prior to their attack, a correlation will be seen between scans and between scans and attacks within a short time range. For network worms, this correlation time is tens of seconds to several minutes. When the scans and attacks are issued by attackers, the correlation is not nearly as strong, with a large variance in the time difference between events. <a href="http://ezinearticles.com/?How-to-Choose-a-On-Site-or-In-Shop-Computer-Repair-Service&#038;id=6321161" target="_blank">Computer Repair Service in Dallas TX</a>.</p>
<p>The data for the cross-correlation analysis was taken from an introduction of the Slapper worm into a small research network used for data analysis in the research. Due to the size of the network, the number of observations is smaller than the data points used in the Nimda worm analysis, leading to a less robust data set. In this analysis, the scan performed by the Slapper worm (a request for the server’s top file in an attempt to identify the server’s type) was analyzed in relation to the time of the attack by the client.</p>
<p>Correlation analysis can be performed on any data set if any one or two unique events can be measured. The time differences can be used to analyze larger events for coordinated anomalies. Worms will typically have a cluster of observations at short time intervals where other network events will usually not have such a strong association of data points.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/correlation-analysis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Embedded devices</title>
		<link>http://www.ledanet.org/embedded-devices/</link>
		<comments>http://www.ledanet.org/embedded-devices/#comments</comments>
		<pubDate>Fri, 21 Oct 2011 06:04:39 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[additional services]]></category>
		<category><![CDATA[basic programming]]></category>
		<category><![CDATA[cable modems]]></category>
		<category><![CDATA[cannot]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[default configurations]]></category>
		<category><![CDATA[device]]></category>
		<category><![CDATA[fundamental flaws]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[number]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[programming errors]]></category>
		<category><![CDATA[routers and switches]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[security implementations]]></category>
		<category><![CDATA[security vulnerabilities]]></category>
		<category><![CDATA[sort]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[trend]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=210</guid>
		<description><![CDATA[A growing trend in attacks in recent years is focusing on network-aware appliances. As devices that can attach to the network become more complex, they increasingly offer additional services for management. 
It is in these services that a number of security vulnerabilities have been discovered. These include poor default configurations, basic programming errors in the [...]]]></description>
			<content:encoded><![CDATA[<p>A growing trend in attacks in recent years is focusing on network-aware appliances. As devices that can attach to the network become more complex, they increasingly offer additional services for management. </p>
<p>It is in these services that a number of security vulnerabilities have been discovered. These include poor default configurations, basic programming errors in the services, and fundamental flaws in security implementations.<br />
<span id="more-210"></span><br />
Specific examples of this sort of device are network-based printers, broadband devices such as cable modems and DSL adapters, and even larger, more established equipment such as routers and switches. The needs being met by these embedded devices are great, and as such we cannot do without them. </p>
<p>Furthermore, an embedded device is typically loaded from firmware, making upgrades difficult to perform and even sometimes impossible. Such devices, difficult to adequately secure, pose an increasing risk to networks and a budding target for worms. Even if only used as devices in an attack via bounced packets or storage for files needed in the worm, their use cannot be ignored. Such <a href="http://www.quoteroller.com/proposal-templates/" target="_blank">proposal samples</a> could be a good references for above discussion.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/embedded-devices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Attack on UNIX server</title>
		<link>http://www.ledanet.org/attack-on-unix-server/</link>
		<comments>http://www.ledanet.org/attack-on-unix-server/#comments</comments>
		<pubDate>Fri, 21 Oct 2011 05:48:17 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[challenge]]></category>
		<category><![CDATA[classification essay]]></category>
		<category><![CDATA[community]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[mail servers]]></category>
		<category><![CDATA[networking capabilities]]></category>
		<category><![CDATA[popularity]]></category>
		<category><![CDATA[ramen worm]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[sgi irix]]></category>
		<category><![CDATA[sun solaris system]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[time unix]]></category>
		<category><![CDATA[UNIX]]></category>
		<category><![CDATA[unix servers]]></category>
		<category><![CDATA[unix types]]></category>
		<category><![CDATA[unix world]]></category>
		<category><![CDATA[vulnerability]]></category>
		<category><![CDATA[worm]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=202</guid>
		<description><![CDATA[UNIX servers are an historical target for worms. UNIX has a long history of
being a robust server system on the Internet, including its roles as Web servers,
mail servers, name servers, and file servers for the general community.
This is due to the availability of software that performs these services, the scalability of the systems, and the [...]]]></description>
			<content:encoded><![CDATA[<p>UNIX servers are an historical target for worms. UNIX has a long history of<br />
being a robust server system on the Internet, including its roles as Web servers,<br />
mail servers, name servers, and file servers for the general community.<br />
This is due to the availability of software that performs these services, the scalability of the systems, and the networking capabilities of the systems.</p>
<p>For a brief time, UNIX servers were threatened by the growing popularity of Windows servers, but the presence of UNIX servers seems to have held its footing. With the growing popularity and deployment of Linux, UNIX servers are again on the rise as worm targets. The Linux and BSD operating systems are available to the community for free.<br />
<span id="more-202"></span><br />
Furthermore, these systems run a wide number of popular services that receive considerable attention from vulnerability researchers. This is evidenced by both the Ramen worm and the Slapper worm from mid-2002.</p>
<p>UNIX systems represent a challenge to a far-reaching worm due to the heterogeneous nature of the UNIX world. A vulnerability on a Sun Solaris system that operates typically on the SPARC process series is not likely to be exploited in the same fashion on an SGI IRIX system, assuming that the vulnerability affects both system types. </p>
<p>The discussion about attack on UNIX server are still arguable, yet it is good material as <a href="http://a-classwriting.com/" target="_blank">classification essay</a>.This diversity can pose a challenge to a worm that wishes to affect all UNIX types.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/attack-on-unix-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Target of Attack &#8211; Server</title>
		<link>http://www.ledanet.org/target-of-attack-server/</link>
		<comments>http://www.ledanet.org/target-of-attack-server/#comments</comments>
		<pubDate>Fri, 21 Oct 2011 05:42:04 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[access control mechanisms]]></category>
		<category><![CDATA[advantage]]></category>
		<category><![CDATA[authentication mechanisms]]></category>
		<category><![CDATA[DECnet]]></category>
		<category><![CDATA[desktop]]></category>
		<category><![CDATA[desktop users]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[introduction]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[network changes]]></category>
		<category><![CDATA[persistent themes]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[these patches]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[trust relationships]]></category>
		<category><![CDATA[vax vms systems]]></category>
		<category><![CDATA[VMS]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=200</guid>
		<description><![CDATA[Initially, worms began attacking the major systems on the networks of the time. These have migrated from DECnet and VMS systems to the Internet at large and desktop users on a variety of networks. As the network changes, worms change to take advantage of weaknesses in the design and implementations.
It is important to understand these [...]]]></description>
			<content:encoded><![CDATA[<p>Initially, worms began attacking the major systems on the networks of the time. These have migrated from DECnet and VMS systems to the Internet at large and desktop users on a variety of networks. As the network changes, worms change to take advantage of weaknesses in the design and implementations.</p>
<p>It is important to understand these trends because they point to the future threats posed by automated attacks. These trends are reflective of the changes in usage of networks along with the growing popularity of the Internet.<br />
<span id="more-200"></span><br />
Early networks consisted mainly of servers with few workstations attached to the wider network as a whole. These systems included the VAX/VMS systems of DECnet that were affected by the HI.COM and WANK worms in the late 1980s. Each of the worms has existed through the current time and still relies on the same mechanisms. Poorly established and audited trust relationships, weak authentication mechanisms, and a failure to patch known holes have been persistent themes in the history of worms.</p>
<p>Servers represent a common target for worms. They are well connected to the network, typically are designed to accept connections from unknown parties, and have nearly nonexistent access control mechanisms for their major services. Worms take advantage of all of these server attributes, the bandwidth, access, and services provided, and use them against the network itself. <a href="http://www.quoteroller.com/" target="_blank">estimating software</a></p>
<p>Furthermore, because servers need to be available for people, server administrators have historically not brought them down to install patches without scheduling a downtime period. This is due to the introduction of new bugs or incompatibilities brought on by these patches. Worms can take advantage of this larger window of opportunity to exploit weaknesses. Even after the introduction of a widespread worm, such as after Code Red, many administrators fail to install patches, allowing worms to continue to grow in fertile ground.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/target-of-attack-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Prevalence of target</title>
		<link>http://www.ledanet.org/prevalence-of-target/</link>
		<comments>http://www.ledanet.org/prevalence-of-target/#comments</comments>
		<pubDate>Mon, 17 Oct 2011 10:02:51 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Base]]></category>
		<category><![CDATA[consideration]]></category>
		<category><![CDATA[defense mechanism]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[knitted slipper patterns]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[linux hosts]]></category>
		<category><![CDATA[mail servers]]></category>
		<category><![CDATA[nimda worm]]></category>
		<category><![CDATA[number]]></category>
		<category><![CDATA[placement]]></category>
		<category><![CDATA[port of entry]]></category>
		<category><![CDATA[potential victims]]></category>
		<category><![CDATA[ramen worm]]></category>
		<category><![CDATA[relative handful]]></category>
		<category><![CDATA[spread]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[visibility]]></category>
		<category><![CDATA[worm]]></category>
		<category><![CDATA[zero day]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=187</guid>
		<description><![CDATA[The first consideration in the evaluation of how far a worm will spread is to evaluate the target’s characteristics. The number of potential targets is an overwhelming consideration, because a large pool of potential victims will be essential to spreading to a wide base. Obviously, a worm that can only compromise a fraction of the [...]]]></description>
			<content:encoded><![CDATA[<p>The first consideration in the evaluation of how far a worm will spread is to evaluate the target’s characteristics. The number of potential targets is an overwhelming consideration, because a large pool of potential victims will be essential to spreading to a wide base. Obviously, a worm that can only compromise a fraction of the hosts on the Internet will have a lesser impact when compared to a worm that has a large base of likely victims.</p>
<p>The second major factor in the potential spread of a worm is the placement of the potential victims. To move quickly and affect a wide number of systems, the targets must be reachable from a wide number of locations. The placement of a host is a combination of the factors of its visibility as well as the bandwidth available to the host. For these two concerns, the prevalence and the visibility, Web and mail servers have made excellent targets for worms in recent history.<br />
<span id="more-187"></span><br />
Similarly, the depth of the spread of the Ramen worm, which targeted Linux hosts, was not nearly as widespread as the Nimda worm. Because Linux hosts are far fewer in number on the Internet than Windows hosts, the worm was only able to infect a relative handful of the machines on the network. This allowed for an easier cleanup by the community affected.</p>
<p>An additional consideration to note is the number of people who know about the vulnerabilities being exploited, and whether the vendor has released a patch. Zero-day exploits, which are named due to their lack of prior notice before their use, are an ideal for use within a worm. Vendors will lack patches and the community will require some time to understand the mechanism of the worm. <a href="http://freeknitted.com/why-pay-for-cheap-cotton-ballet-slippers-that-fall-apart-in-a-few-weeks-when-you-can-knit-warm-soft-cozy-ones-with-free-knitting-patterns/" target="_blank">knitted slipper patterns</a></p>
<p>Lastly, the importance of the service exploited should also be considered. A service such as DNS or HTTP is commonly passed by firewalls without any screening and is less likely to be arbitrarily shut off as an initial defense mechanism against a worm. Coupled with the widespread nature of these services, they make an ideal port of entry for malicious code.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/prevalence-of-target/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Worm Mechanisms &#8211; single point</title>
		<link>http://www.ledanet.org/worm-mechanisms-single-point/</link>
		<comments>http://www.ledanet.org/worm-mechanisms-single-point/#comments</comments>
		<pubDate>Mon, 03 Oct 2011 23:07:05 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[area]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[attacker]]></category>
		<category><![CDATA[author]]></category>
		<category><![CDATA[avenue]]></category>
		<category><![CDATA[Base]]></category>
		<category><![CDATA[behavior]]></category>
		<category><![CDATA[child]]></category>
		<category><![CDATA[child nodes]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[compromise]]></category>
		<category><![CDATA[concern]]></category>
		<category><![CDATA[discussion]]></category>
		<category><![CDATA[Distribution]]></category>
		<category><![CDATA[distribution mechanism]]></category>
		<category><![CDATA[entry]]></category>
		<category><![CDATA[essay]]></category>
		<category><![CDATA[evening]]></category>
		<category><![CDATA[file]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[hold]]></category>
		<category><![CDATA[Horse]]></category>
		<category><![CDATA[horse software]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[identification]]></category>
		<category><![CDATA[identity]]></category>
		<category><![CDATA[increase]]></category>
		<category><![CDATA[infect]]></category>
		<category><![CDATA[infection]]></category>
		<category><![CDATA[initial presence]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[internet system]]></category>
		<category><![CDATA[internet worms]]></category>
		<category><![CDATA[introduction]]></category>
		<category><![CDATA[lab]]></category>
		<category><![CDATA[malicious attacker]]></category>
		<category><![CDATA[malicious software]]></category>
		<category><![CDATA[maximum]]></category>
		<category><![CDATA[mechanism]]></category>
		<category><![CDATA[multiple networks]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[node]]></category>
		<category><![CDATA[number]]></category>
		<category><![CDATA[origin]]></category>
		<category><![CDATA[package]]></category>
		<category><![CDATA[paradigm]]></category>
		<category><![CDATA[path]]></category>
		<category><![CDATA[peer to peer network]]></category>
		<category><![CDATA[Penetration]]></category>
		<category><![CDATA[point]]></category>
		<category><![CDATA[point of entry]]></category>
		<category><![CDATA[point of origin]]></category>
		<category><![CDATA[presence]]></category>
		<category><![CDATA[public computer lab]]></category>
		<category><![CDATA[round]]></category>
		<category><![CDATA[scenario]]></category>
		<category><![CDATA[Single]]></category>
		<category><![CDATA[single point]]></category>
		<category><![CDATA[software package]]></category>
		<category><![CDATA[source]]></category>
		<category><![CDATA[source host]]></category>
		<category><![CDATA[speed]]></category>
		<category><![CDATA[subject]]></category>
		<category><![CDATA[survivability]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[target identification]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[theme]]></category>
		<category><![CDATA[trick]]></category>
		<category><![CDATA[Trojan]]></category>
		<category><![CDATA[trojan horse]]></category>
		<category><![CDATA[usage]]></category>
		<category><![CDATA[usage patterns]]></category>
		<category><![CDATA[variation]]></category>
		<category><![CDATA[variety]]></category>
		<category><![CDATA[victim]]></category>
		<category><![CDATA[way]]></category>
		<category><![CDATA[weakness]]></category>
		<category><![CDATA[worm]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=163</guid>
		<description><![CDATA[Just as the way the worm network finds its next victim is important for its speed and its long-term survivability and penetration, the way in which the worm is introduced is another concern. A common scenario to imagine is a malicious attacker introducing a worm in a public computer lab one evening. By carefully considering [...]]]></description>
			<content:encoded><![CDATA[<p>Just as the way the worm network finds its next victim is important for its speed and its long-term survivability and penetration, the way in which the worm is introduced is another concern. A common scenario to imagine is a malicious attacker introducing a worm in a public computer lab one evening. By carefully considering the point and variety of introduction mechanisms, Internet worms can achieve different goals.</p>
<p>Single point<br />
The classic paradigm of the introduction of a worm is to use a single point of origin, such as a single Internet system. This host is set up to launch the worm and infect a number of child nodes, carrying the worm with it. These new nodes then begin the next round of target identification and compromise.<br />
<span id="more-163"></span><br />
The trick is to find a well-connected and reasonably poorly monitored host. To achieve the maximum introduction from a single point, this node will have to infect several new hosts, which are also capable of a wide area of infection. This will be crucial in establishing the initial presence of the worm when it is most vulnerable, existing on only a few nodes.</p>
<p>An obvious weakness in this scenario is that the worm may be identified back to its source and ultimately its author. By combining a number of factors, including usage patterns of the source host or network, with the code base, investigators can sometimes establish the identity of the author of the malicious software.</p>
<p>One variation of this theme is to introduce the malicious software at a single point but use an accepted distribution mechanism to gain entry to the Internet. This includes a Trojan horse software package or a malicious file in a peer-to-peer network. While only a single point of entry for the software is used, it is then introduced to several computers which can then launch the worm onto multiple networks. </p>
<p>For the attacker, however, this is the easiest avenue of introducing a worm. It involves the fewest resources and, if the worm takes hold of the network early and establishes itself quickly, gives the quickest path to a stable infection.</p>
<p>The object and subject of worms and its behavior of attack are quite tickling and very interesting for writing an essay based on it. Why? because its just never ends, as long as computer technology still developing and increase, the materials and discussion just won&#8217;t end. For some people you might need to <a href="http://buyessay.org/" target="_blank">buy essays</a>, cause its more practical and they just give you good essay with correct grammar.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/worm-mechanisms-single-point/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

