<?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; system</title>
	<atom:link href="http://www.ledanet.org/tag/system/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>Host Based Firewall</title>
		<link>http://www.ledanet.org/host-based-firewall/</link>
		<comments>http://www.ledanet.org/host-based-firewall/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 11:35:44 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[configure]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[major]]></category>
		<category><![CDATA[network path]]></category>
		<category><![CDATA[perimeter]]></category>
		<category><![CDATA[Personal]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[protection]]></category>
		<category><![CDATA[services]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[worms]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=300</guid>
		<description><![CDATA[Host-based firewalls are a complement to a network-based firewall. While most systems do not run host-based firewalls, instead relying on the network’s firewall to provide them with protection, at the host level more fine-grained control can be applied. This method also acts as a fail over protection for the network-based firewall should any attack bypass [...]]]></description>
			<content:encoded><![CDATA[<p>Host-based firewalls are a complement to a network-based firewall. While most systems do not run host-based firewalls, instead relying on the network’s firewall to provide them with protection, at the host level more fine-grained control can be applied. This method also acts as a fail over protection for the network-based firewall should any attack bypass that mechanism. These situations can include the penetration of a worm behind the perimeter firewall or a difference between the policy enforced by the perimeter defenses and those required by the host.</p>
<p>There are several example situations where host-based firewalls may be an appropriate solution to defending a set of hosts. These include situations where the default network security policy is absent but the security requirements for the host are more demanding.<br />
<span id="more-300"></span><br />
Alternatively, a system may wish to dynamically add addresses to its list of blocked hosts that would have otherwise been permitted into the network. The fact that any host-based firewall cannot, without some convolutions, be more liberal than the perimeter firewall between it and the Internet at large is a design issue.</p>
<p>Host-level firewalls are available in two major types. The first is a traditional firewall with statically configured rules. In this type of firewall a set of rules is established that enforces a policy. This can include coarse-grained rules such as the network ports and their associated services that are allowed to be accessed. Finer grained rules would enforce rules about which hosts are allowed to connect to these services. This type of firewall would also work well for a system with a well-defined and narrow network role, such as a network server.</p>
<p>The second type of popular host-based firewall is one that dynamically adapts to the user’s network use. Often called the personal firewall, these systems query the user to determine what applications are in use on the system. Sources are associated with applications, giving the user an easy-to-use secure Internet workstation. Combined with a default deny policy, a personal firewall on a workstation can help prevent a network worm from entering a system via a previously unauthorized network path. <a href="http://www.starksmedia.com/beauty/5081-tea-tree-oil%C2%A0uses-and-benefits.-tea-tree-oil%C2%A0for-acne%2C-hair%2C-warts%2C-nail-fungus.-where-to-buy%C2%A0tea-tree-oil-shampoo.html" target="_blank">tea tree oil shampoo</a>.</p>
<p>It is important to note that there is a limitation to this approach, however. Host-based firewalls, either a statically configured rule set or a dynamically generated policy, are ineffective at stopping worms that follow already established connect paths that are allowed via the policy. The worm will simply be a malicious network peer and compromise the security of the system it has targeted.</p>
<p>Furthermore, these host-based firewalls can be subverted by the worm itself if sufficient rights are obtained by the malicous executable. For example, upon launch the worm could issue a command to unload the firewall’s rule set, entirely nullifying the installed security monitor. This is an emerging reality for new viruses and worms.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/host-based-firewall/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Glance history of computer</title>
		<link>http://www.ledanet.org/glance-history-of-computer/</link>
		<comments>http://www.ledanet.org/glance-history-of-computer/#comments</comments>
		<pubDate>Wed, 11 Jan 2012 07:28:12 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[advance technology]]></category>
		<category><![CDATA[Apple Macintosh]]></category>
		<category><![CDATA[atomic scientists]]></category>
		<category><![CDATA[automatic calculator]]></category>
		<category><![CDATA[automatic sequence controlled calculator]]></category>
		<category><![CDATA[calculator]]></category>
		<category><![CDATA[course]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[Electronic]]></category>
		<category><![CDATA[electronic discrete variable automatic computer]]></category>
		<category><![CDATA[electronic numerical integrator]]></category>
		<category><![CDATA[electronic numerical integrator and calculator]]></category>
		<category><![CDATA[energy]]></category>
		<category><![CDATA[equipment]]></category>
		<category><![CDATA[generation]]></category>
		<category><![CDATA[german engineer]]></category>
		<category><![CDATA[history]]></category>
		<category><![CDATA[IBM]]></category>
		<category><![CDATA[konrad]]></category>
		<category><![CDATA[Konrad Zuse]]></category>
		<category><![CDATA[machine]]></category>
		<category><![CDATA[magnetic core memory]]></category>
		<category><![CDATA[mechanical calculator]]></category>
		<category><![CDATA[mechanical equipment]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[Rand]]></category>
		<category><![CDATA[result]]></category>
		<category><![CDATA[rise of technology]]></category>
		<category><![CDATA[second generation computers]]></category>
		<category><![CDATA[supercomputer ibm]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[transistor]]></category>
		<category><![CDATA[USA]]></category>
		<category><![CDATA[use]]></category>
		<category><![CDATA[vacuum tube]]></category>
		<category><![CDATA[war]]></category>
		<category><![CDATA[world war ii]]></category>
		<category><![CDATA[z3 computer]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=280</guid>
		<description><![CDATA[Unquestionable computer have been use and dig in many different aspect of human life. Lets have a look glance history of computer till we known right now.
Of course the world itself have changed, and its also causing different development of technology. And as we all know technology these days are more familiar with computer as [...]]]></description>
			<content:encoded><![CDATA[<p>Unquestionable computer have been use and dig in many different aspect of human life. Lets have a look glance history of computer till we known right now.</p>
<p>Of course the world itself have changed, and its also causing different development of technology. And as we all know technology these days are more familiar with computer as its basic power and brain. At the first development computer was use as scientific investigation, but lately its used as military advanced technology during world war II.<br />
<span id="more-280"></span><br />
Before we go deep with the history lets classified computer by its type.<br />
1. Manual equipment<br />
This might be the most simple equipment using computer as its basis, why because data processing are using man power directly.</p>
<p>2. Mechanical equipment<br />
which are mechanical equipment that being used by people and generated manually by people them self.</p>
<p>3. Mechanical Electronic<br />
This would be more advance technology which using mechanical equipment that generated automatically by electronic or motor.</p>
<p>4. Electronic Equipment.<br />
This equipment fully control and generated by electronic and using electric as its power.</p>
<p>Before the usage of computer some manual counting equipment such as abacus, numerical wheel calculator, and mechanical calculator being use for daily operation those days.</p>
<p>Then after 1940, the rise of technology began to strike the earth, starting from ENIAC (Electronic Numerical Integrator And Calculator), EDVAC Computer (Electronic Discrete Variable Automatic Computer), EDSAC COMPUTER ( Electonic Delay Storage Automatic Calculator). This first generation are pretty big of course it could be seen from the size and the usage of vacuum tube.</p>
<p>Influence from the first generation, transistor are being use to change the usage of vacuum tube, in these second generation, IBM name are became popular for its invention call LARC. Programming language as software development are quite popular during these year, such as COBOL, and FORTRAN.</p>
<p>The next generation of course the simplify transistor into smaller component, which is call as integrated circuit (IC). Here computer size are much more smaller. At these generation operating system also introduced.</p>
<p>As you could guest the fourth generation is the advanced of the latest. Ultra-Large Scale Integration (ULSI) being introduced to replace IC, it could store numbers of IC into one simple device or also famous as microprocessor.</p>
<p>These history of computer technology are a good <a href="http://customessaypapers.com/articles/how-to-write-a-great-thesis-statement/" target="_blank">thesis statement example</a>, its a material that would last, and of course looking at its impact on human life and its purposes.</p>
<p>And now as we all could see the size of computer have evolved into smaller device with high speed connection and accessibility. Lets hope these technology would evolving for better tomorrow.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/glance-history-of-computer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Honeypots and worms analysis</title>
		<link>http://www.ledanet.org/honeypots-and-worms-analysis/</link>
		<comments>http://www.ledanet.org/honeypots-and-worms-analysis/#comments</comments>
		<pubDate>Wed, 14 Dec 2011 21:52:03 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[attack signatures]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[honeypot]]></category>
		<category><![CDATA[honeypots]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[inherent risk]]></category>
		<category><![CDATA[legitimate network]]></category>
		<category><![CDATA[linux host]]></category>
		<category><![CDATA[mail system]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[outbound connections]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[solaris system]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[valuable research]]></category>
		<category><![CDATA[worm]]></category>
		<category><![CDATA[worm activity]]></category>
		<category><![CDATA[worm attacks]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=265</guid>
		<description><![CDATA[Honeypots have an inherent risk factor associated with them that has to be stated. Because a honeypot is designed to allow an attacker to enter and gain control (for the purposes of monitoring their actions), it is possible the compromised host may be used to spread more attacks. For this reason it is vital to [...]]]></description>
			<content:encoded><![CDATA[<p>Honeypots have an inherent risk factor associated with them that has to be stated. Because a honeypot is designed to allow an attacker to enter and gain control (for the purposes of monitoring their actions), it is possible the compromised host may be used to spread more attacks. For this reason it is vital to monitor it closely and both control the outbound connections as well as close the host down when it has been compromised. Also, it should never be deployed on a production subnet where it can interfere with legitimate network activities and be used to gain entry to a protected network.</p>
<p>When monitoring for worm activity, honeypots can be an invaluable tool for capturing these beasts in the wild. They require some anticipation of the services the worm will be attacking, such as a Web server or a mail system, along with other vulnerable services.<br />
<span id="more-265"></span><br />
A basic method would be to set up a host with the services installed and configured for the worm to attack. For a worm like Code Red or Nimda, this would be a default Win32 installation with IIS configured. When you wish to snare a worm such as Ramen or sadmind/IIS, you would need to install a Linux host or a Solaris system, respectively. One important step is to take a snapshot of the host using low-level tools. This will provide a baseline measurement against which you can check for alterations.</p>
<p>It is preferred that you mount the disk image on another host for analysis, which allows you a trustworthy toolset. Low-level forensics tools are preferred for this so that you can really dig into any changes that may have been made. Tools such as The Coroner’s Toolkit are valuable research tools in this arena.</p>
<p>What you would obtain, in this process, is a picture of what happens when a worm strikes a real host, complete with network signatures and binaries involved. The hope is that you would use these data to develop attack signatures to monitor for future worm attacks, data revealing how the worm was able to compromise the host, and what it uploaded (and from where) during its attack. These attack could be avoided with well preparation program or good <a href="http://www.elinext.com/" target="_blank">software development</a>.</p>
<p>Honeypot deployment strategies are a somewhat involved subject. They depend on the placement of the sensor, the types of data sought, and the level of involvement in setup and monitoring desired.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/honeypots-and-worms-analysis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Honeypots</title>
		<link>http://www.ledanet.org/honeypots/</link>
		<comments>http://www.ledanet.org/honeypots/#comments</comments>
		<pubDate>Tue, 13 Dec 2011 09:36:19 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[attacker]]></category>
		<category><![CDATA[best wordpress themes]]></category>
		<category><![CDATA[dedicated systems]]></category>
		<category><![CDATA[external monitors]]></category>
		<category><![CDATA[full security]]></category>
		<category><![CDATA[honeynet]]></category>
		<category><![CDATA[honeypot]]></category>
		<category><![CDATA[honeypots]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[memory space]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[open source versions]]></category>
		<category><![CDATA[production]]></category>
		<category><![CDATA[space]]></category>
		<category><![CDATA[Spitzner]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[value]]></category>
		<category><![CDATA[virtual hosts]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=262</guid>
		<description><![CDATA[A network honeypot is simply a system you expect to get probed or attacked so that you can analyze these data later. As defined by Spitzner, a honeynet differs from a honeypot in that it is a network of honeypots made of full production systems.
This network can be logically and geographically dispersed. Because of their [...]]]></description>
			<content:encoded><![CDATA[<p>A network honeypot is simply a system you expect to get probed or attacked so that you can analyze these data later. As defined by Spitzner, a honeynet differs from a honeypot in that it is a network of honeypots made of full production systems.</p>
<p>This network can be logically and geographically dispersed. Because of their nature, worms will indiscriminately attack any available host on the network, including honeypots. The value of this approach is that you can analyze the attack after it has happened and learn about the methods used by the attacking agent. Honeypots come in three basic varieties:<br />
<span id="more-262"></span><br />
a. Full dedicated systems, which are typically nonhardened installations of an operating system. These are installed with a minimum amount of setup in an attempt to mirror a default installation and then placed on the network. External monitors are typically used to capture the network traffic to and from the host.</p>
<p>b. Service-level honeypots are hosts that have one or more services installed in logical “jails,” areas of protected process and memory space. An attacker can probe and attack the service, but any compromise is contained to the virtual machine running on the host. Commercial as well as open-source versions of these tools are available.</p>
<p>c. Virtual hosts and networks, which provide the illusion of a host and its associated services to an attacker. This is typically housed in a single host on the network, spoofing other hosts.</p>
<p>Each of these approaches offers varying degrees of accessibility and value, along with associated risk. For instance, it can be more costly to implement a set of honeypots with full, dedicated systems, though you may capture more data with real services. A virtual honeypot, however, has an advantage in that you can more readily deploy an additional host or even network into your monitored space. As if creating website with full security but keep the essence of easiness such as with cms, you need the <a href="http://www.buysellwp.com/" target="_blank">best wordpress themes</a> for better site performance.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/honeypots/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Intranet systems</title>
		<link>http://www.ledanet.org/intranet-systems/</link>
		<comments>http://www.ledanet.org/intranet-systems/#comments</comments>
		<pubDate>Fri, 21 Oct 2011 06:01:17 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[access controls]]></category>
		<category><![CDATA[area]]></category>
		<category><![CDATA[corporate networks]]></category>
		<category><![CDATA[desktop]]></category>
		<category><![CDATA[desktop systems]]></category>
		<category><![CDATA[environment]]></category>
		<category><![CDATA[Firewalls]]></category>
		<category><![CDATA[intranet]]></category>
		<category><![CDATA[intranet systems]]></category>
		<category><![CDATA[local area network]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[persuasive paper]]></category>
		<category><![CDATA[spread]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[threat]]></category>
		<category><![CDATA[university campuses]]></category>
		<category><![CDATA[Vulnerabilities]]></category>
		<category><![CDATA[worm]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=208</guid>
		<description><![CDATA[The second threat posed by worms targeting desktop systems is posed by hosts within an intranet. These networks, often built with a local area network with common policies and services, are rich in vulnerabilities for a worm to use. A worm that can exploit vulnerabilities in such an environment is likely to spread quickly and [...]]]></description>
			<content:encoded><![CDATA[<p>The second threat posed by worms targeting desktop systems is posed by hosts within an intranet. These networks, often built with a local area network with common policies and services, are rich in vulnerabilities for a worm to use. A worm that can exploit vulnerabilities in such an environment is likely to spread quickly and deeply.</p>
<p>Intranets are typically behind firewalls and detection systems, meaning they have little protection or monitoring of the hosts within the network.<br />
<span id="more-208"></span><br />
Any worm that has gained access to the network is likely to be able to connect to almost any system within this network without problem. A lack of access controls is crucial to the spread of a worm, because restrictions only fetter the spread of such a system. The spread of the worm attack in intranet systems are consider as <a href="http://beststudentessay.com/" target="_blank">persuasive paper</a>.</p>
<p>Furthermore, intranets are typically homogeneous networks, such as corporate networks or university campuses. As such, the vulnerabilities present that the worm is using to spread itself are likely to be present on many of the systems. Worms have been shown to thrive in such homogeneous environments.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/intranet-systems/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>Central source</title>
		<link>http://www.ledanet.org/central-source/</link>
		<comments>http://www.ledanet.org/central-source/#comments</comments>
		<pubDate>Wed, 19 Oct 2011 07:24:36 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[attacker]]></category>
		<category><![CDATA[child]]></category>
		<category><![CDATA[child node]]></category>
		<category><![CDATA[child nodes]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[connection logs]]></category>
		<category><![CDATA[delivery]]></category>
		<category><![CDATA[Distribution]]></category>
		<category><![CDATA[distribution server]]></category>
		<category><![CDATA[future generations]]></category>
		<category><![CDATA[malicious attacker]]></category>
		<category><![CDATA[malicious web]]></category>
		<category><![CDATA[mechanism]]></category>
		<category><![CDATA[method]]></category>
		<category><![CDATA[network bug]]></category>
		<category><![CDATA[node]]></category>
		<category><![CDATA[parent]]></category>
		<category><![CDATA[parent node]]></category>
		<category><![CDATA[request]]></category>
		<category><![CDATA[site]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[worm]]></category>
		<category><![CDATA[worm code]]></category>
		<category><![CDATA[wrapper scripts]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=196</guid>
		<description><![CDATA[The third mechanism for worm executable delivery is through a central site. In this system, the parent node executes a request from the new child node to the central site to retrieve the programs that make up the worm code from a central site. This can include a malicious Web site or file distribution server [...]]]></description>
			<content:encoded><![CDATA[<p>The third mechanism for worm executable delivery is through a central site. In this system, the parent node executes a request from the new child node to the central site to retrieve the programs that make up the worm code from a central site. This can include a malicious Web site or file distribution server or some other system.</p>
<p>This method for delivering the worm payloads is most directly related to the methods used by attackers in manual compromises. Typically an attacker who amassed many hosts via a compromise distributes their programs to the compromised hosts from a central system. Early worms, which were wrapper scripts around the exploit process, often utilized this mechanism.<br />
<span id="more-196"></span><br />
The major advantage to this type of delivery system is that the worm can be updated with relative ease. This is because the files that make up the worm lie in a single location, so changes to this archive will affect all future generations of the worm. This can include the delivery of new exploit methods to the worm network, bug fixes, or new capabilities.</p>
<p>The biggest drawback to this method is that it is vulnerable to discovery early in the worm life cycle, such as after only a few generations for a quickly spreading worm. This is due to the high profile the distribution site will have as more child nodes make requests to it. As such, the worm becomes vulnerable to a malicious attacker or investigator. <a href="http://grossloan.com/portfolio-loan.html" target="_blank">portfolio loans</a></p>
<p>Attacks possible on these types of worm networks include the injection of poison payloads, which stop the worm in its tracks, or the enumeration, via connection logs, of the worm’s membership list. For these reasons, despite the ease of updating the worm’s capabilities, the central site distribution model for worm payloads is least attractive.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/central-source/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

