<?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; access</title>
	<atom:link href="http://www.ledanet.org/tag/access/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>Black hole monitoring</title>
		<link>http://www.ledanet.org/black-hole-monitoring/</link>
		<comments>http://www.ledanet.org/black-hole-monitoring/#comments</comments>
		<pubDate>Wed, 14 Dec 2011 21:56:59 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[flood attacks]]></category>
		<category><![CDATA[hole]]></category>
		<category><![CDATA[internet worms]]></category>
		<category><![CDATA[method]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[network space]]></category>
		<category><![CDATA[packet floods]]></category>
		<category><![CDATA[reply]]></category>
		<category><![CDATA[reply packets]]></category>
		<category><![CDATA[service advertisements]]></category>
		<category><![CDATA[space]]></category>
		<category><![CDATA[space worm]]></category>
		<category><![CDATA[SYN]]></category>
		<category><![CDATA[syn ack]]></category>
		<category><![CDATA[syn flood]]></category>
		<category><![CDATA[traffic]]></category>
		<category><![CDATA[worm]]></category>
		<category><![CDATA[worm detection]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=267</guid>
		<description><![CDATA[The implementation of unused IP space in worm tracking has proven to be an even more effective technique in worm detection and tracking. This unallocated, unadvertised network space has no DNS entries, but does have valid routes to reach it. Because it is not in use (no machines are deployed within it) and no photons [...]]]></description>
			<content:encoded><![CDATA[<p>The implementation of unused IP space in worm tracking has proven to be an even more effective technique in worm detection and tracking. This unallocated, unadvertised network space has no DNS entries, but does have valid routes to reach it. Because it is not in use (no machines are deployed within it) and no photons are traveling along the fiber, it is called a dark space or a black hole network.</p>
<p>Monitoring this dark IP space is effective because of the persistent and complete coverage by Internet worms. Worms, unlike many real attackers, do not monitor DNS entries or service advertisements to determine who to attack. They simply find a network block to scan and begin doing so. Hits in that space are therefore interesting, because no legitimate traffic (in the absence of DNS, application, or routing errors) should be seen in that network.<br />
<span id="more-267"></span><br />
Black hole monitoring generally can be done in one of three ways. The first is to monitor what is called backscatter, or the reply packets sent by spoofed sources. If the forged source lies within the monitored dark network space, the replies will be visible. These include SYN-ACK and RST packets from SYN flood attacks, and ICMP errors and control messages from packet floods.</p>
<p>The second method is to simply monitor the number of requests for access to the unallocated network space. These requests are typically monitored by a router that advertises routes to these networks internally. The requests for those routes can be measured either by the flow export data or from the routing table data maintained by the system.</p>
<p>The third method is to view the network or subnet as a black hole and anything going into it as interesting traffic. This monitors both reply packets as well as requests, such as SYN packets from worms and other scans. While some spurious traffic is certain to enter this space, worm traffic will also enter this monitored area. Captured signatures can then provide a basis for worm analysis, allowing for an estimation of the spread and activity of a worm. <a href="http://www.cogniteq.com/" target="_blank">mobile app development</a>.</p>
<p>This third type of black hole monitor differs from honeypots in a significant way. Rather than pretending to be a complete host, with services and characteristics of an operating system, the black hole will simply complete a connection request and nothing else. </p>
<p>Black hole network data can be acquired in two ways. The first is to use the exported flow logs from routing and switching equipment to mine for access attempts to unallocated network space. The second is to place a passive network monitor either at the entrance to the network or listening on router interfaces that serve the unallocated network spaces.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/black-hole-monitoring/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>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>Random Scanning</title>
		<link>http://www.ledanet.org/random-scanning/</link>
		<comments>http://www.ledanet.org/random-scanning/#comments</comments>
		<pubDate>Thu, 29 Sep 2011 15:41:56 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[aggressiveness]]></category>
		<category><![CDATA[amount]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[attacker]]></category>
		<category><![CDATA[block]]></category>
		<category><![CDATA[Cable]]></category>
		<category><![CDATA[cable modem]]></category>
		<category><![CDATA[class]]></category>
		<category><![CDATA[Classically]]></category>
		<category><![CDATA[cleanup]]></category>
		<category><![CDATA[cleanup efforts]]></category>
		<category><![CDATA[cluster]]></category>
		<category><![CDATA[compromise]]></category>
		<category><![CDATA[corporate networks]]></category>
		<category><![CDATA[course]]></category>
		<category><![CDATA[coverage]]></category>
		<category><![CDATA[exploits]]></category>
		<category><![CDATA[generator]]></category>
		<category><![CDATA[hop]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[infect]]></category>
		<category><![CDATA[infestation]]></category>
		<category><![CDATA[information]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[internet security]]></category>
		<category><![CDATA[island]]></category>
		<category><![CDATA[likelihood]]></category>
		<category><![CDATA[link]]></category>
		<category><![CDATA[maximum]]></category>
		<category><![CDATA[method]]></category>
		<category><![CDATA[middle]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[modem]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[network space]]></category>
		<category><![CDATA[node]]></category>
		<category><![CDATA[noisy]]></category>
		<category><![CDATA[number]]></category>
		<category><![CDATA[Online]]></category>
		<category><![CDATA[pace]]></category>
		<category><![CDATA[pattern]]></category>
		<category><![CDATA[period]]></category>
		<category><![CDATA[persistence]]></category>
		<category><![CDATA[pool]]></category>
		<category><![CDATA[potential victims]]></category>
		<category><![CDATA[presence]]></category>
		<category><![CDATA[random network]]></category>
		<category><![CDATA[random number generator]]></category>
		<category><![CDATA[random walk]]></category>
		<category><![CDATA[random walks]]></category>
		<category><![CDATA[range]]></category>
		<category><![CDATA[research]]></category>
		<category><![CDATA[section]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[sense]]></category>
		<category><![CDATA[space]]></category>
		<category><![CDATA[spread]]></category>
		<category><![CDATA[survivability]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[target network]]></category>
		<category><![CDATA[Thirdly]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[tracking]]></category>
		<category><![CDATA[traffic]]></category>
		<category><![CDATA[traffic issues]]></category>
		<category><![CDATA[type]]></category>
		<category><![CDATA[use]]></category>
		<category><![CDATA[value]]></category>
		<category><![CDATA[walk]]></category>
		<category><![CDATA[way]]></category>
		<category><![CDATA[worm]]></category>
		<category><![CDATA[worms]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=155</guid>
		<description><![CDATA[The spread of the worm in its most basic sense depends most greatly on how it chooses its victims. This not only affects the spread and pace of the worm network, but also its survivability and persistence as cleanup efforts begin. Classically, worms have used random walks of the Internet to find hosts and attack. [...]]]></description>
			<content:encoded><![CDATA[<p>The spread of the worm in its most basic sense depends most greatly on how it chooses its victims. This not only affects the spread and pace of the worm network, but also its survivability and persistence as cleanup efforts begin. Classically, worms have used random walks of the Internet to find hosts and attack. However, new attack models have emerged that demonstrate increased aggressiveness.</p>
<p>The simplest way for a worm to spread as far as it can is to use random network scanning. In this method, the worm node randomly generates a network to scan, typically a block of 65,000 hosts (a /16 network) or 256 hosts (a /24) in a target network block. This worm node then begins to search for potential victims in that network space and attacks vulnerable hosts. This random walk is the classic spread model for network-based worms.<br />
<span id="more-155"></span><br />
However, there are some issues with this method, of course. The first is that the pool of addresses in use on the Internet tends to cluster to the middle, typically between 128/8 and 220/8. However, sizable and interesting networks reside outside of this, such as cable modem networks in 24/4 and 64/4, along with several large, well-known corporate networks in this range. To be effective, the worm should focus its efforts on hosts that are likely to be vulnerable to its exploits as well as being widely found.</p>
<p>Secondly, it is easy to pick a network block that is sparsely populated. This then wastes the node’s time by scanning a network section that will contain few, if any, hosts it can attack or compromise. The likelihood of this is dependent on the network space chosen. Several of the class A networks below 127/8 that are almost completely unused. Some of these networks are used by researchers to study Internet security patterns or traffic issues.</p>
<p>Thirdly, it is important to have a good random number generator in use to achieve almost complete coverage of the chosen range. A weak random number generator will mean that some networks will be disproportionately scanned. Some networks may not be scanned at all when this occurs.</p>
<p>The advantages of this type of scanning are that, when properly executed, near total coverage of the Internet can be accomplished within a brief period of time. This can be of value for an attacker who wishes to gain access to the maximum number of hosts in a reasonable amount of time. Second, this type of worm is bound to be more persistent than a directed or island based scanning worm. Not every network will be able to eradicate the worm infestation, and the worm will hop from one network to others randomly, constantly finding a host to infect.</p>
<p>While the worm is likely to find a vulnerable host it can compromise within a potentially rich network, it is likely to hop out of the network again as it randomly generates a new network to scan. Also, this type of scanning pattern is very noisy and highly visible. As described above, the scanning of sparsely populated networks is likely, and a simple tracking of this will reveal the presence of a worm. Get more details information of worms with searching it online or from other research <a href="http://essaysreasy.org/" target="_blank">link</a> or articles.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/random-scanning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Command Interface</title>
		<link>http://www.ledanet.org/command-interface/</link>
		<comments>http://www.ledanet.org/command-interface/#comments</comments>
		<pubDate>Mon, 26 Sep 2011 09:35:02 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[ability]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[attacker]]></category>
		<category><![CDATA[back door]]></category>
		<category><![CDATA[capability]]></category>
		<category><![CDATA[channel]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[combination]]></category>
		<category><![CDATA[Command]]></category>
		<category><![CDATA[command execution]]></category>
		<category><![CDATA[command interface]]></category>
		<category><![CDATA[command shell]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[communication channel]]></category>
		<category><![CDATA[company]]></category>
		<category><![CDATA[computer problems]]></category>
		<category><![CDATA[conclusion]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[control mechanism]]></category>
		<category><![CDATA[daemon]]></category>
		<category><![CDATA[DDoS]]></category>
		<category><![CDATA[directory]]></category>
		<category><![CDATA[Door]]></category>
		<category><![CDATA[download]]></category>
		<category><![CDATA[easy access]]></category>
		<category><![CDATA[electronic mail]]></category>
		<category><![CDATA[essay]]></category>
		<category><![CDATA[example]]></category>
		<category><![CDATA[execution]]></category>
		<category><![CDATA[fashion]]></category>
		<category><![CDATA[flood]]></category>
		<category><![CDATA[hierarchy]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[login]]></category>
		<category><![CDATA[mail]]></category>
		<category><![CDATA[mechanism]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[network packets]]></category>
		<category><![CDATA[old style]]></category>
		<category><![CDATA[pass]]></category>
		<category><![CDATA[pathway]]></category>
		<category><![CDATA[phrase]]></category>
		<category><![CDATA[Red]]></category>
		<category><![CDATA[root]]></category>
		<category><![CDATA[root directory]]></category>
		<category><![CDATA[route]]></category>
		<category><![CDATA[sequence]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[shell]]></category>
		<category><![CDATA[shell level]]></category>
		<category><![CDATA[solution]]></category>
		<category><![CDATA[style]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[upload]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[value]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[web requests]]></category>
		<category><![CDATA[worm]]></category>
		<category><![CDATA[writing company]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=139</guid>
		<description><![CDATA[Having established a system of interconnected nodes, their value can be increased by means of a control mechanism. The command interface provides this capability to the worm nodes. This interface can be interactive, such as a user shell, or indirect, such as electronic mail or a sequence of network packets.
Through the combination of the communication [...]]]></description>
			<content:encoded><![CDATA[<p>Having established a system of interconnected nodes, their value can be increased by means of a control mechanism. The command interface provides this capability to the worm nodes. This interface can be interactive, such as a user shell, or indirect, such as electronic mail or a sequence of network packets.</p>
<p>Through the combination of the communication channel and the command interface, the worm network resembles a DDoS network. In this model, a hierarchy of nodes exists that can provide a distributed command execution pathway, effectively magnifying the actions of a host.<br />
<span id="more-139"></span><br />
Traditionally, hackers will leave some mechanism to regain control to a system once they have compromised it. This is typically called a back door because it provides another route of access, behind the scenes, to the system.</p>
<p>These mechanisms can include a modified login daemon configured to accept a special pass phrase or variable to give the attack easy access again. Code Red, for example, placed the command shell in the root directory of the Web server, allowing for system-level access via Web requests.</p>
<p>The command interface in a worm network can include the ability to upload or download files, flood a target with network packets, or provide unrestricted shell-level access to a host. This interface in a worm network can also be used by other worm nodes in an automated fashion or manually by an attacker.</p>
<p>Command interface might look old style, but it is proven effective and faster solution on computer problems, some <a href="http://firstessaycompany.com/" target="_blank">essay writing company</a> also agree with these conclusion and they also provide writing about it as well.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/command-interface/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Attack Elements</title>
		<link>http://www.ledanet.org/attack-elements/</link>
		<comments>http://www.ledanet.org/attack-elements/#comments</comments>
		<pubDate>Wed, 21 Sep 2011 11:32:44 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[admi]]></category>
		<category><![CDATA[administrator]]></category>
		<category><![CDATA[alert]]></category>
		<category><![CDATA[application]]></category>
		<category><![CDATA[area]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[aware application]]></category>
		<category><![CDATA[being]]></category>
		<category><![CDATA[buffer]]></category>
		<category><![CDATA[buffer overflows]]></category>
		<category><![CDATA[cannot]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[client socket]]></category>
		<category><![CDATA[clog]]></category>
		<category><![CDATA[component]]></category>
		<category><![CDATA[compromise]]></category>
		<category><![CDATA[credential]]></category>
		<category><![CDATA[cycle]]></category>
		<category><![CDATA[detection]]></category>
		<category><![CDATA[e mail]]></category>
		<category><![CDATA[element]]></category>
		<category><![CDATA[entry]]></category>
		<category><![CDATA[escalation]]></category>
		<category><![CDATA[example]]></category>
		<category><![CDATA[exploits]]></category>
		<category><![CDATA[factor]]></category>
		<category><![CDATA[gain entry]]></category>
		<category><![CDATA[generation]]></category>
		<category><![CDATA[Horse]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[infection]]></category>
		<category><![CDATA[instance]]></category>
		<category><![CDATA[intrusion]]></category>
		<category><![CDATA[intrusion detection systems]]></category>
		<category><![CDATA[latter]]></category>
		<category><![CDATA[macroscopic view]]></category>
		<category><![CDATA[mail client]]></category>
		<category><![CDATA[method]]></category>
		<category><![CDATA[migration]]></category>
		<category><![CDATA[monitoring]]></category>
		<category><![CDATA[monitoring systems]]></category>
		<category><![CDATA[nature]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[network component]]></category>
		<category><![CDATA[Online]]></category>
		<category><![CDATA[opencart]]></category>
		<category><![CDATA[platform]]></category>
		<category><![CDATA[presence]]></category>
		<category><![CDATA[prevalent element]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[session]]></category>
		<category><![CDATA[session hijacking]]></category>
		<category><![CDATA[shop]]></category>
		<category><![CDATA[signature]]></category>
		<category><![CDATA[signature generation]]></category>
		<category><![CDATA[socket]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[systems gain]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[target platforms]]></category>
		<category><![CDATA[theft]]></category>
		<category><![CDATA[Trojan]]></category>
		<category><![CDATA[trojan horse]]></category>
		<category><![CDATA[type]]></category>
		<category><![CDATA[use]]></category>
		<category><![CDATA[vectors]]></category>
		<category><![CDATA[victim]]></category>
		<category><![CDATA[view]]></category>
		<category><![CDATA[weight]]></category>
		<category><![CDATA[worm]]></category>
		<category><![CDATA[zencart]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=134</guid>
		<description><![CDATA[The worm’s attack components are their most visible and prevalent element. This is the means by which worm systems gain entry on remote systems and begin their infection cycle. These methods can include the standard remote exploits, such as buffer overflows, cgi-bin errors, or similar, or they can include Trojan horse methods. An example of [...]]]></description>
			<content:encoded><![CDATA[<p>The worm’s attack components are their most visible and prevalent element. This is the means by which worm systems gain entry on remote systems and begin their infection cycle. These methods can include the standard remote exploits, such as buffer overflows, cgi-bin errors, or similar, or they can include Trojan horse methods. An example of the latter would be the use of an infected executable being sent to an e-mail client by a worm as one of its attack vectors.</p>
<p>This component has to be further subdivided into two portions: the platform on which the worm is executing and the platform of the target. This attack element can be a compiled binary or an interpreted script, which utilizes a network component from the attacking host, such as a client socket or a network aware application, to transfer itself to its victim.<br />
<span id="more-134"></span><br />
A main factor of the attack component is the nature of the target being attacked, specifically its platform and operating system. Attack components that are limited to one platform or method rely on finding hosts vulnerable to only this particular exploit. For a worm to support multiple vectors of compromise or various target platforms of a similar type, it must be large.</p>
<p>This extra weight can slow down any one instance of a worm attack or, in a macroscopic view, more quickly clog the network. Other attacks include session hijacking and credential theft (such as passwords and cookies) attacks. Here the attack does not involve any escalation of privileges, but does assist the worm in gaining access to additional systems.</p>
<p>These attack elements are also most often used in intrusion detection signature generation. Since the attack is executed between two hosts and over the network, it is visible to monitoring systems. This provides the most accessible wide area monitoring of the network for the presence of an active worm. However, it requires a signature of the attack to trigger an alert. Furthermore, passive intrusion detection systems cannot stop the worm, and the administrator is alerted to the presence of the worm only as it gains another host.</p>
<p>The most important attack is online shop attack, when it happens, several things should be done such as migration <a href="http://www.shopping-cart-migration.com/shopping-cart-migration-options/868-opencart-to-zencart-migration" target="_blank">opencart vs zencart</a>, so it is important to keep your sites secure.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/attack-elements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Network Coverage</title>
		<link>http://www.ledanet.org/network-coverage/</link>
		<comments>http://www.ledanet.org/network-coverage/#comments</comments>
		<pubDate>Fri, 19 Aug 2011 14:52:21 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[address]]></category>
		<category><![CDATA[anyone]]></category>
		<category><![CDATA[area]]></category>
		<category><![CDATA[bandwidth]]></category>
		<category><![CDATA[budget]]></category>
		<category><![CDATA[Cable]]></category>
		<category><![CDATA[cable network]]></category>
		<category><![CDATA[common security]]></category>
		<category><![CDATA[computer]]></category>
		<category><![CDATA[computer technology]]></category>
		<category><![CDATA[configure]]></category>
		<category><![CDATA[connection]]></category>
		<category><![CDATA[connection quality]]></category>
		<category><![CDATA[course]]></category>
		<category><![CDATA[coverage]]></category>
		<category><![CDATA[coverage area]]></category>
		<category><![CDATA[distance]]></category>
		<category><![CDATA[environment]]></category>
		<category><![CDATA[hub]]></category>
		<category><![CDATA[installation]]></category>
		<category><![CDATA[kind]]></category>
		<category><![CDATA[length]]></category>
		<category><![CDATA[limit]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[mac address filtering]]></category>
		<category><![CDATA[mac environment]]></category>
		<category><![CDATA[money]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[network coverage]]></category>
		<category><![CDATA[network planning]]></category>
		<category><![CDATA[obstacle]]></category>
		<category><![CDATA[parameter]]></category>
		<category><![CDATA[password]]></category>
		<category><![CDATA[peripherals]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[problem]]></category>
		<category><![CDATA[program]]></category>
		<category><![CDATA[protection]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[safe security]]></category>
		<category><![CDATA[second]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[security protection]]></category>
		<category><![CDATA[sequence]]></category>
		<category><![CDATA[signal]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[stable network]]></category>
		<category><![CDATA[supportive tools]]></category>
		<category><![CDATA[survey]]></category>
		<category><![CDATA[survey software]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[way]]></category>
		<category><![CDATA[wireless survey]]></category>
		<category><![CDATA[world]]></category>

		<guid isPermaLink="false">http://www.ledanet.org/?p=97</guid>
		<description><![CDATA[Since computer technology were introduced, the other related supportive tools are also improving. One of it is Network, with network we could travel the world less then a second, there are no limit to far and no obstacle to hard.
Network itself rely on connection quality, which the first and still being used until now is [...]]]></description>
			<content:encoded><![CDATA[<p>Since computer technology were introduced, the other related supportive tools are also improving. One of it is Network, with network we could travel the world less then a second, there are no limit to far and no obstacle to hard.</p>
<p>Network itself rely on connection quality, which the first and still being used until now is cable. Cable itself also being used for common electric peripherals.<br />
<span id="more-97"></span><br />
With cable of course the limits is the distance which are limited by the length of the cable. And it will cost more extra budget to buy long cable. Also in network we also know that we do need a hub or switch every 95 km to extend the network.</p>
<p>Those kind of problem were solve with wireless network devices. Without required lots of cable, and with simple installation, all we need is just configure the parameter, and also save more money to spend.</p>
<p>With wireless network, either way, required more safe security protection, why because the signal could be catched by anyone on the coverage area. Unlike the cable network which is install directly into specified users, wireless network divided by sequence of security, the most common security used are mac address filtering, and encripted password.</p>
<p>Thus, security just not enough, for better network coverage and connection access, limiting the bandwidth sent to users, and correct network planning are very helpful to establish stable network connection. For wireless network monitoring some program such as <a href="http://www.netspotapp.com/" target="_blank">wireless survey software</a> could help you monitor your network and control your network connection plans and its working in Mac environment as well.</p>]]></content:encoded>
			<wfw:commentRss>http://www.ledanet.org/network-coverage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

