<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://wiki.cas.mcmaster.ca/skins/common/feed.css?207"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://wiki.cas.mcmaster.ca/index.php?feed=atom&amp;target=Shahinrs&amp;title=Special%3AContributions</id>
		<title>Computing and Software Wiki - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://wiki.cas.mcmaster.ca/index.php?feed=atom&amp;target=Shahinrs&amp;title=Special%3AContributions"/>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Special:Contributions/Shahinrs"/>
		<updated>2026-04-09T21:02:30Z</updated>
		<subtitle>From Computing and Software Wiki</subtitle>
		<generator>MediaWiki 1.15.1</generator>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-14T02:40:58Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a term used to describe a specific kind of [http://en.wikipedia.org/wiki/Denial_of_service Denial-of-Service](DoS) attack. The attack is achieved by the abuse of [http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol ICMP] [http://en.wikipedia.org/wiki/Ping echo (ping)] which is sent to broadcast address. This can cause significant a increase in traffic which may block legitimate traffic, thus creating a denial of service. Smurfing victimises two parties generally, the target (the one being attacked), and the amplifier (the intermediate host which involuntarily lends its services to the attacker).&lt;br /&gt;
 &lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:brainy.jpg|thumb|165px|''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
|}&lt;br /&gt;
=What is Smurfing?=&lt;br /&gt;
'''Smurfing''' is a banking industry term used to describe the act of splitting up a large financial transaction into several smaller ones to avoid scrutiny from regulators.[1] &amp;quot;Smurfing&amp;quot; is originally derived from a cartoon, [http://en.wikipedia.org/wiki/Smurfs The Smurfs], which consisted of a large society of many small individuals. The coining of the term is attributed to Miami-based lawyer, Gregory Baldwin in the 1980s.[1]&lt;br /&gt;
&lt;br /&gt;
'''Smurging''' or a '''Smurf Attack''' in the context of network security describes the act of many small ICMP pings being used to create very large network traffic congestion. The &amp;quot;smurf&amp;quot; attack's cousin is called '''[http://en.wikipedia.org/wiki/Fraggle_attack Fraggle]''', which uses [http://en.wikipedia.org/wiki/User_Datagram_Protocol UDP] echo packets in the same fashion as the ICMP echo packets. It was a simple re-write of &amp;quot;smurf&amp;quot;.[2]&lt;br /&gt;
&lt;br /&gt;
=How does a Smurf Attack take place?=&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:Smurf2.gif|thumb|450px|''http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm#Smurf_Attack'']]&lt;br /&gt;
|}&lt;br /&gt;
In order for a Smurf Attack to take place there are three parties which need to be considered. First is the attack who orchestrates the attack. Second is the amplifier, who is usually another victim of the attack, and lastly, the target.&lt;br /&gt;
===The Attacker===&lt;br /&gt;
The attack itself is fairly simple. However the attacker will need a few things before the attack can be carried out. First the attacker will need a fast connection to the internet, and will need to find a large network, or a number of networks, that is attached to the Internet by a router that will forward ICMP requests. This network is the amplifier. The attacker will then send a ping request with a [http://en.wikipedia.org/wiki/IP_address_spoofing spoofed] source address (the address of the target) to the [http://en.wikipedia.org/wiki/Broadcast_address broadcast address] of the amplifier. The attacker has completed his portion of the attack.[3]&lt;br /&gt;
&lt;br /&gt;
===The Amplifier===&lt;br /&gt;
An amplifier is a large network that is connected to the internet with a router. The router must be able to perform an IP broadcast. When the router receives traffic to the broadcast address, it will forward the message to all the hosts on the network. If the router receives and broadcasts an ICMP ping request, most of the hosts will reply to the source address of the message. This means that if there are 500 hosts which reply to the IP broadcast, then for every 1 ping request to that amplifier, 500 ping relies are sent. When an attacker spoofs the source address of the ping requests, rather than the pings replies going back to the attacker, they will go to the spoofed address (i.e. the victim). If the attacker has a fast connection, then it can send several ping requests very quickly. The amplifier is assumed to have a much faster connection (i.e. T3) to accommodate the ping replies.[4]&lt;br /&gt;
&lt;br /&gt;
===The Target===&lt;br /&gt;
The target is generally a specific server or small network. Upon receiving the ICMP replies, the target is no longer able to make its services available to its intended users since it is busy processing these ICMP messages. This creates a DoS and render the target inaccessible to other users.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=all/&amp;gt;&lt;br /&gt;
=Prevention=&lt;br /&gt;
To prevent a router from being an amplifier, two simple configurations need to be implemented. &lt;br /&gt;
* Routers and individual hosts should not respond to ping requests to broadcast addresses.&lt;br /&gt;
* Routers should not forward packets directed to broadcast address.[5]&lt;br /&gt;
&lt;br /&gt;
An example of how to configure a router so that packets are not forwarded to broadcast addresses would be: &lt;br /&gt;
 &amp;lt;code&amp;gt;no ip directed-broadcast&amp;lt;/code&amp;gt;&lt;br /&gt;
This configuration is for a [http://en.wikipedia.org/wiki/Cisco_Systems Cisco] router.[5]&lt;br /&gt;
&lt;br /&gt;
Another router configuration is to filter ICMP requests by source addresses. By applying a filter which will reject any outgoing packets that contain a source address from a different network, you eliminate the spoofing element of a Smurf attack.[6]&lt;br /&gt;
&lt;br /&gt;
It is important to note that these prevention techniques apply only to protecting a network form being an amplifier or the source of an attack. A similar procedure is required to prevent a Fraggle attack. If, however, the security mechanisms don't adequately enforce the [http://en.wikipedia.org/wiki/Security_policy security policy] of the network, then these prevention techniques can easily be by-passed.&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
[http://en.wikipedia.org/wiki/Smurfing_%28crime%29] Structuring&lt;br /&gt;
&lt;br /&gt;
[http://www.pentics.net/denial-of-service/white-papers/smurf.cgi] The Lastest In Denial Of Service Attacks: &amp;quot;Smurfing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm] Information Warfare Going on the Offensive&lt;br /&gt;
&lt;br /&gt;
[http://www.networkworld.com/archive/1999b/0222gearhead.html] Attacked by smurf&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Smurf_attack] Smurf attack&lt;br /&gt;
&lt;br /&gt;
[http://www.academ.com/nanog/oct1997/smurfing/sld001.htm] The Lastest In Denial Of Service Attacks: &amp;quot;Smurfing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=Also See=&lt;br /&gt;
[[TCP/IP_Application_Development]]&lt;br /&gt;
&lt;br /&gt;
[[The_Great_Firewall_of_China]]&lt;br /&gt;
&lt;br /&gt;
[[Designing_a_Small_Business_Intranet]]&lt;br /&gt;
&lt;br /&gt;
[[The_Five-Layer_TCP/IP_Model:_Description/Attacks/Defense]]&lt;br /&gt;
&lt;br /&gt;
[[Social_engineering]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=External Links=&lt;br /&gt;
[http://www.webopedia.com/TERM/S/smurf.html smurf]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Ip_spoofing IP Spoofing]&lt;br /&gt;
&lt;br /&gt;
[http://www.javvin.com/networksecurity/SmurfAttack.html Smurf Attack and Fraggle Attack]&lt;br /&gt;
&lt;br /&gt;
[http://www-arc.com/sara/cve/Possible_DoS_problem.html Possible DoS (fraggle) Problem]&lt;br /&gt;
&lt;br /&gt;
[ftp://ftp.isi.edu/in-notes/rfc2267.txt Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing]&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 22:40, 13 April 2008 (EDT)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-14T00:33:45Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a form of [http://en.wikipedia.org/wiki/Denial_of_service Denial-of-Service](DoS) attack where an attacker floods a target with [http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol ICMP] [http://en.wikipedia.org/wiki/Ping echo (ping)] traffic. &lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:brainy.jpg|thumb|165px|''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
'''Smurfing''' is a banking industry term used to describe the act of splitting up a large financial transaction into several smaller ones to avoid scrutiny from regulators. &amp;quot;Smurfing&amp;quot; is originally derived from a cartoon, [http://en.wikipedia.org/wiki/Smurfs The Smurfs], which consisted of a large society of many small individuals. The coining of the term is attributed to Miami-based lawyer, Gregory Baldwin in the 1980s.&lt;br /&gt;
&lt;br /&gt;
'''Smurging''' or a '''Smurf Attack''' in the context of network security describes the act of many small ICMP pings being used to create very large network traffic congestion. The &amp;quot;smurf&amp;quot; attack's cousin is called '''[http://en.wikipedia.org/wiki/Fraggle_attack Fraggle]''', which uses [http://en.wikipedia.org/wiki/User_Datagram_Protocol UDP] echo packets in the same fashion as the ICMP echo packets. It was a simple re-write of &amp;quot;smurf&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:Smurf2.gif|thumb|450px|''http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm#Smurf_Attack'']]&lt;br /&gt;
|}&lt;br /&gt;
In order for a Smurf Attack to take place there are three parties which need to be considered. First is the attack who orchestrates the attack. Second is the amplifier, who is usually another victim of the attack, and lastly, the target.&lt;br /&gt;
===The Attacker===&lt;br /&gt;
The attack itself is fairly simple. However the attacker will need a few things before the attack can be carried out. First the attacker will need a fast connection to the internet, and will need to find a large network, or a number of networks, that is attached to the Internet by a router that will forward ICMP requests. This network is the amplifier. The attacker will then send a ping request with a [http://en.wikipedia.org/wiki/IP_address_spoofing spoofed] source address (the address of the target) to the [http://en.wikipedia.org/wiki/Broadcast_address broadcast address] of the amplifier. The attacker has completed his portion of the attack. &lt;br /&gt;
&lt;br /&gt;
===The Amplifier===&lt;br /&gt;
An amplifier is a large network that is connected to the internet with a router. The router must be able to perform an IP broadcast. When the router receives traffic to the broadcast address, it will forward the message to all the hosts on the network. If the router receives and broadcasts an ICMP ping request, most of the hosts will reply to the source address of the message. This means that if there are 500 hosts which reply to the IP broadcast, then for every 1 ping request to that amplifier, 500 ping relies are sent. When an attacker spoofs the source address of the ping requests, rather than the pings replies going back to the attacker, they will go to the spoofed address (i.e. the victim). If the attacker has a fast connection, then it can send several ping requests very quickly. The amplifier is assumed to have a much faster connection (i.e. T3) to accommodate the ping replies. &lt;br /&gt;
&lt;br /&gt;
===The Target===&lt;br /&gt;
The target is generally a specific server or small network. Upon receiving the ICMP replies, the target is no longer able to make its services available to its intended users since it is busy processing these ICMP messages. This creates a DoS and render the target inaccessible to other users.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=all/&amp;gt;&lt;br /&gt;
==Prevention==&lt;br /&gt;
To prevent a router from being an amplifier, two simple configurations need to be implemented. &lt;br /&gt;
* Routers and individual hosts should not respond to ping requests to broadcast addresses.&lt;br /&gt;
* Routers should not forward packets directed to broadcast address.&lt;br /&gt;
&lt;br /&gt;
An example of how to configure a router so that packets are not forwarded to broadcast addresses would be: &lt;br /&gt;
 &amp;lt;code&amp;gt;no ip directed-broadcast&amp;lt;/code&amp;gt;&lt;br /&gt;
This configuration is for a [http://en.wikipedia.org/wiki/Cisco_Systems Cisco] router.&lt;br /&gt;
&lt;br /&gt;
Another router configuration is to filter ICMP requests by source addresses. By applying a filter which will reject any outgoing packets that contain a source address from a different network, you eliminate the spoofing element of a Smurf attack.&lt;br /&gt;
&lt;br /&gt;
It is important to note that these prevention techniques apply only to protecting a network form being an amplifier or the source of an attack. A similar procedure is required to prevent a Fraggle attack. If, however, the security mechanisms don't adequately enforce the [http://en.wikipedia.org/wiki/Security_policy security policy] of the network, then these prevention techniques can easily be by-passed.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
* [http://www.webopedia.com/TERM/S/smurf.html smurf]&lt;br /&gt;
* [http://www.academ.com/nanog/oct1997/smurfing/sld001.htm The Lastest In Denial Of Service Attacks: &amp;quot;Smurfing&amp;quot;]&lt;br /&gt;
* [http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm Information Warfare Going on the Offensive]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Smurf_attack Smurf attack]&lt;br /&gt;
* [http://www.networkworld.com/archive/1999b/0222gearhead.html Attacked by smurf]&lt;br /&gt;
* [http://www-arc.com/sara/cve/Possible_DoS_problem.html Possible DoS (fraggle) Problem]&lt;br /&gt;
* [ftp://ftp.isi.edu/in-notes/rfc2267.txt Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing]&lt;br /&gt;
* [http://www.javvin.com/networksecurity/SmurfAttack.html Smurf Attack and Fraggle Attack]&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 20:33, 13 April 2008 (EDT)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-14T00:29:07Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a form of [http://en.wikipedia.org/wiki/Denial_of_service Denial-of-Service](DoS) attack where an attacker floods a target with [http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol ICMP] [http://en.wikipedia.org/wiki/Ping echo (ping)] traffic. &lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:brainy.jpg|thumb|165px|''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
'''Smurfing''' is a banking industry term used to describe the act of splitting up a large financial transaction into several smaller ones to avoid scrutiny from regulators. &amp;quot;Smurfing&amp;quot; is originally derived from a cartoon, [http://en.wikipedia.org/wiki/Smurfs The Smurfs], which consisted of a large society of many small individuals. The coining of the term is attributed to Miami-based lawyer, Gregory Baldwin in the 1980s.&lt;br /&gt;
&lt;br /&gt;
'''Smurging''' or a '''Smurf Attack''' in the context of network security describes the act of many small ICMP pings being used to create very large network traffic congestion. The &amp;quot;smurf&amp;quot; attack's cousin is called '''[http://en.wikipedia.org/wiki/Fraggle_attack Fraggle]''', which uses [http://en.wikipedia.org/wiki/User_Datagram_Protocol UDP] echo packets in the same fashion as the ICMP echo packets. It was a simple re-write of &amp;quot;smurf&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:Smurf2.gif|thumb|450px|''http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm#Smurf_Attack'']]&lt;br /&gt;
|}&lt;br /&gt;
In order for a Smurf Attack to take place there are three parties which need to be considered. First is the attack who orchestrates the attack. Second is the amplifier, who is usually another victim of the attack, and lastly, the target.&lt;br /&gt;
===The Attacker===&lt;br /&gt;
The attack itself is fairly simple. However the attacker will need a few things before the attack can be carried out. First the attacker will need a fast connection to the internet, and will need to find a large network, or a number of networks, that is attached to the Internet by a router that will forward ICMP requests. This network is the amplifier. The attacker will then send a ping request with a [http://en.wikipedia.org/wiki/IP_address_spoofing spoofed] source address (the address of the target) to the [http://en.wikipedia.org/wiki/Broadcast_address broadcast address] of the amplifier. The attacker has completed his portion of the attack. &lt;br /&gt;
&lt;br /&gt;
===The Amplifier===&lt;br /&gt;
An amplifier is a large network that is connected to the internet with a router. The router must be able to perform an IP broadcast. When the router receives traffic to the broadcast address, it will forward the message to all the hosts on the network. If the router receives and broadcasts an ICMP ping request, most of the hosts will reply to the source address of the message. This means that if there are 500 hosts which reply to the IP broadcast, then for every 1 ping request to that amplifier, 500 ping relies are sent. When an attacker spoofs the source address of the ping requests, rather than the pings replies going back to the attacker, they will go to the spoofed address (i.e. the victim). If the attacker has a fast connection, then it can send several ping requests very quickly. The amplifier is assumed to have a much faster connection (i.e. T3) to accommodate the ping replies. &lt;br /&gt;
&lt;br /&gt;
===The Target===&lt;br /&gt;
The target is generally a specific server or small network. Upon receiving the ICMP replies, the target is no longer able to make its services available to its intended users since it is busy processing these ICMP messages. This creates a DoS and render the target inaccessible to other users.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=all/&amp;gt;&lt;br /&gt;
==Prevention==&lt;br /&gt;
To prevent a router from being an amplifier, two simple configurations need to be implemented. &lt;br /&gt;
* Routers and individual hosts should not respond to ping requests to broadcast addresses.&lt;br /&gt;
* Routers should not forward packets directed to broadcast address.&lt;br /&gt;
&lt;br /&gt;
An example of how to configure a router so that packets are not forwarded to broadcast addresses would be: &lt;br /&gt;
 &amp;lt;code&amp;gt;no ip directed-broadcast&amp;lt;/code&amp;gt;&lt;br /&gt;
This configuration is for a [http://en.wikipedia.org/wiki/Cisco_Systems Cisco] router.&lt;br /&gt;
&lt;br /&gt;
Another router configuration is to filter ICMP requests by source addresses. By applying a filter which will reject any outgoing packets that contain a source address from a different network, you eliminate the spoofing element of a Smurf attack.&lt;br /&gt;
&lt;br /&gt;
It is important to note that these prevention techniques apply only to protecting a network form being an amplifier or the source of an attack. A similar procedure is required to prevent a Fraggle attack. If, however, the security mechanisms don't adequately enforce the [http://en.wikipedia.org/wiki/Security_policy security policy] of the network, then these prevention techniques can easily be by-passed.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
* [http://www.webopedia.com/TERM/S/smurf.html smurf]&lt;br /&gt;
* [http://www.academ.com/nanog/oct1997/smurfing/sld001.htm The Lastest In Denial Of Service Attacks: &amp;quot;Smurfing&amp;quot;]&lt;br /&gt;
* [http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm Information Warfare Going on the Offensive]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Smurf_attack Smurf attack]&lt;br /&gt;
* [http://www.networkworld.com/archive/1999b/0222gearhead.html Attacked by smurf]&lt;br /&gt;
* [http://www-arc.com/sara/cve/Possible_DoS_problem.html Possible DoS (fraggle) Problem]&lt;br /&gt;
* [ftp://ftp.isi.edu/in-notes/rfc2267.txt Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing]&lt;br /&gt;
* [http://www.javvin.com/networksecurity/SmurfAttack.html Smurf Attack and Fraggle Attack]&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-14T00:10:23Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a form of Denial-of-Service attack where an attacker floods a target with ICMP echo (ping) traffic. &lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:brainy.jpg|thumb|165px|''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
'''Smurfing''' is a banking industry term used to describe the act of splitting up a large financial transaction into several smaller ones to avoid scrutiny from regulators. &amp;quot;Smurfing&amp;quot; is originally derived from a cartoon, The Smurfs, which consisted of a large society of many small individuals. The coining of the term is attributed to Miami-based lawyer, Gregory Baldwin in the 1980s.&lt;br /&gt;
&lt;br /&gt;
'''Smurging''' or a '''Smurf Attack''' in the context of network security describes the act of many small ICMP pings being used to create very large network traffic congestion. The &amp;quot;smurf&amp;quot; attack's cousin is called '''Fraggle''', which uses UDP echo packets in the same fashion as the ICMP echo packets. It was a simple re-write of &amp;quot;smurf&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:Smurf2.gif|thumb|450px|''http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm#Smurf_Attack'']]&lt;br /&gt;
|}&lt;br /&gt;
In order for a Smurf Attack to take place there are three parties which need to be considered. First is the attack who orchestrates the attack. Second is the amplifier, who is usually another victim of the attack, and lastly, the target.&lt;br /&gt;
===The Attacker===&lt;br /&gt;
The attack itself is fairly simple. However the attacker will need a few things before the attack can be carried out. First the attacker will need a fast connection to the internet, and will need to find a large network, or a number of networks, that is attached to the Internet by a router that will forward ICMP requests. This network is the amplifier. The attacker will then send a ping request with a spoofed source address (the address of the target) to the broadcast address of the amplifier. The attacker has completed his portion of the attack. &lt;br /&gt;
&lt;br /&gt;
===The Amplifier===&lt;br /&gt;
An amplifier is a large network that is connected to the internet with a router. The router must be able to perform an IP broadcast. When the router receives traffic to the broadcast address, it will forward the message to all the hosts on the network. If the router receives and broadcasts an ICMP ping request, most of the hosts will reply to the source address of the message. This means that if there are 500 hosts which reply to the IP broadcast, then for every 1 ping request to that amplifier, 500 ping relies are sent. When an attacker spoofs the source address of the ping requests, rather than the pings replies going back to the attacker, they will go to the spoofed address (i.e. the victim). If the attacker has a fast connection, then it can send several ping requests very quickly. The amplifier is assumed to have a much faster connection (i.e. T3) to accommodate the ping replies. &lt;br /&gt;
&lt;br /&gt;
===The Target===&lt;br /&gt;
The target is generally a specific server or small network. Upon receiving the ICMP replies, the target is no longer able to make its services available to its intended users since it is busy processing these ICMP messages. This creates a Denial-of-Service and render the target inaccessible to other users.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=all/&amp;gt;&lt;br /&gt;
==Prevention==&lt;br /&gt;
To prevent a router from being an amplifier, two simple configurations need to be implemented. &lt;br /&gt;
* Routers and individual hosts should not respond to ping requests to broadcast addresses.&lt;br /&gt;
* Routers should not forward packets directed to broadcast address.&lt;br /&gt;
&lt;br /&gt;
An example of how to configure a router so that packets are not forwarded to broadcast addresses would be: &lt;br /&gt;
 &amp;lt;code&amp;gt;no ip directed-broadcast&amp;lt;/code&amp;gt;&lt;br /&gt;
This configuration is for a [[Cisco Systems|Cisco]] router.&lt;br /&gt;
&lt;br /&gt;
Another router configuration is to filter ICMP requests by source addresses. By applying a filter which will reject any outgoing packets that contain a source address from a different network, you eliminate the spoofing element of a Smurf attack.&lt;br /&gt;
&lt;br /&gt;
It is important to note that these prevention techniques apply only to protecting a network form being an amplifier or the source of an attack. A similar procedure is required to prevent a Fraggle attack. If, however, the security mechanism don't adequately enforce the security policy of the network, then these prevention techniques can easily be by-passed.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
* [http://www.webopedia.com/TERM/S/smurf.html smurf]&lt;br /&gt;
* [http://www.academ.com/nanog/oct1997/smurfing/sld001.htm The Lastest In Denial Of Service Attacks: &amp;quot;Smurfing&amp;quot;]&lt;br /&gt;
* [http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm Information Warfare Going on the Offensive]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Smurf_attack Smurf attack]&lt;br /&gt;
* [http://www.networkworld.com/archive/1999b/0222gearhead.html Attacked by smurf]&lt;br /&gt;
* [http://www-arc.com/sara/cve/Possible_DoS_problem.html Possible DoS (fraggle) Problem]&lt;br /&gt;
* [ftp://ftp.isi.edu/in-notes/rfc2267.txt Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing]&lt;br /&gt;
* [http://www.javvin.com/networksecurity/SmurfAttack.html Smurf Attack and Fraggle Attack]&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-13T21:19:24Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a form of Denial-of-Service attack where an attacker floods a target with ICMP echo (ping) traffic. &lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:brainy.jpg|thumb|165px|''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
'''Smurfing''' is a banking industry term used to describe the act of splitting up a large financial transaction into several smaller ones to avoid scrutiny from regulators. &amp;quot;Smurfing&amp;quot; is originally derived from a cartoon, The Smurfs, which consisted of a large society of many small individuals. The coining of the term is attributed to Miami-based lawyer, Gregory Baldwin in the 1980s.&lt;br /&gt;
&lt;br /&gt;
'''Smurging''' or a '''Smurf Attack''' in the context of network security describes the act of many small ICMP pings being used to create very large network traffic congestion. The &amp;quot;smurf&amp;quot; attack's cousin is called '''Fraggle''', which uses UDP echo packets in the same fashion as the ICMP echo packets. It was a simple re-write of &amp;quot;smurf&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:Smurf2.gif|thumb|450px|''http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm#Smurf_Attack'']]&lt;br /&gt;
|}&lt;br /&gt;
In order for a Smurf Attack to take place there are three parties which need to be considered. First is the attack who orcastrates the attack. Second is the amplifier, who is usually another victim of the attack, and lastly, the target.&lt;br /&gt;
===The Attacker===&lt;br /&gt;
The attack itself is fairly simple. However the attacker will need a few things before the attack can be carried out. First the attacker will need a fast connection to the internet, and will need to find a large network, or a number of networks, that is attached to the Internet by a router that will forward ICMP requests. This network is the amplifier. The attacker will then send a ping request with a spoofed source address (the address of the target) to the broadcast address of the amplifier. The attacker has completed his portion of the attack. &lt;br /&gt;
&lt;br /&gt;
===The Amplifier===&lt;br /&gt;
An amplifier is a large network that is connected to the internet with a router. The router must be able to perform an IP broadcast. When the router receives traffic to the broadcast address, it will forward the message to all the hosts on the network. If the router receives and broadcasts an ICMP ping request, most of the hosts will reply to the source address of the message. This means that if there are 500 hosts which reply to the IP broadcast, then for every 1 ping request to that amplifier, 500 ping relies are sent. When an attacker spoofs the source address of the ping requests, rather than the pings replies going back to the attacker, they will go to the spoofed address (i.e. the victim). If the attacker has a fast connection, then it can send several ping requests very quickly. The amplifier is assumed to have a much faster connection (i.e. T3) to accommodate the ping replies. &lt;br /&gt;
&lt;br /&gt;
===The Target===&lt;br /&gt;
The target is generally a specific server or small network. Upon receiving the ICMP replies, the target is no longer able to make its services available to its intended users since it is busy processing these ICMP messages. This creates a Denial-of-Service and render the target unaccessible to other users.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=all/&amp;gt;&lt;br /&gt;
==Prevention==&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
http://www.webopedia.com/TERM/S/smurf.html&lt;br /&gt;
http://www.pentics.net/denial-of-service/white-papers/smurf.cgi&lt;br /&gt;
http://www.academ.com/nanog/oct1997/smurfing/sld001.htm&lt;br /&gt;
http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm&lt;br /&gt;
http://en.wikipedia.org/wiki/Smurf_attack&lt;br /&gt;
http://www.networkworld.com/archive/1999b/0222gearhead.html&lt;br /&gt;
http://www-arc.com/sara/cve/Possible_DoS_problem.html&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-13T21:12:31Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a form of Denial-of-Service attack where an attacker floods a target with ICMP echo (ping) traffic. &lt;br /&gt;
&lt;br /&gt;
[[Image:brainy.jpg|thumb|165px|right|&lt;br /&gt;
''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
'''Smurfing''' is a banking industry term used to describe the act of splitting up a large financial transaction into several smaller ones to avoid scrutiny from regulators. &amp;quot;Smurfing&amp;quot; is originally derived from a cartoon, The Smurfs, which consisted of a large society of many small individuals. The coining of the term is attributed to Miami-based lawyer, Gregory Baldwin in the 1980s.&lt;br /&gt;
&lt;br /&gt;
'''Smurging''' or a '''Smurf Attack''' in the context of network security describes the act of many small ICMP pings being used to create very large network traffic congestion. The &amp;quot;smurf&amp;quot; attack's cousin is called '''Fraggle''', which uses UDP echo packets in the same fashion as the ICMP echo packets. It was a simple re-write of &amp;quot;smurf&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:Smurf2.gif|thumb|450px|''http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm#Smurf_Attack'']]&lt;br /&gt;
|}&lt;br /&gt;
In order for a Smurf Attack to take place there are three parties which need to be considered. First is the attack who orcastrates the attack. Second is the amplifier, who is usually another victim of the attack, and lastly, the target.&lt;br /&gt;
===The Attacker===&lt;br /&gt;
The attack itself is fairly simple. However the attacker will need a few things before the attack can be carried out. First the attacker will need a fast connection to the internet, and will need to find a large network, or a number of networks, that is attached to the Internet by a router that will forward ICMP requests. This network is the amplifier. The attacker will then send a ping request with a spoofed source address (the address of the target) to the broadcast address of the amplifier. The attacker has completed his portion of the attack. &lt;br /&gt;
&lt;br /&gt;
===The Amplifier===&lt;br /&gt;
An amplifier is a large network that is connected to the internet with a router. The router must be able to perform an IP broadcast. When the router receives traffic to the broadcast address, it will forward the message to all the hosts on the network. If the router receives and broadcasts an ICMP ping request, most of the hosts will reply to the source address of the message. This means that if there are 500 hosts which reply to the IP broadcast, then for every 1 ping request to that amplifier, 500 ping relies are sent. When an attacker spoofs the source address of the ping requests, rather than the pings replies going back to the attacker, they will go to the spoofed address (i.e. the victim). If the attacker has a fast connection, then it can send several ping requests very quickly. The amplifier is assumed to have a much faster connection (i.e. T3) to accommodate the ping replies. &lt;br /&gt;
&lt;br /&gt;
===The Target===&lt;br /&gt;
The target is generally a specific server or small network. Upon receiving the ICMP replies, the target is no longer able to make its services available to its intended users since it is busy processing these ICMP messages. This creates a Denial-of-Service and render the target unaccessible to other users.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=all/&amp;gt;&lt;br /&gt;
==Prevention==&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
http://www.webopedia.com/TERM/S/smurf.html&lt;br /&gt;
http://www.pentics.net/denial-of-service/white-papers/smurf.cgi&lt;br /&gt;
http://www.academ.com/nanog/oct1997/smurfing/sld001.htm&lt;br /&gt;
http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm&lt;br /&gt;
http://en.wikipedia.org/wiki/Smurf_attack&lt;br /&gt;
http://www.networkworld.com/archive/1999b/0222gearhead.html&lt;br /&gt;
http://www-arc.com/sara/cve/Possible_DoS_problem.html&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-13T21:12:05Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a form of Denial-of-Service attack where an attacker floods a target with ICMP echo (ping) traffic. &lt;br /&gt;
&lt;br /&gt;
[[Image:brainy.jpg|thumb|165px|right|&lt;br /&gt;
''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
'''Smurfing''' is a banking industry term used to describe the act of splitting up a large financial transaction into several smaller ones to avoid scrutiny from regulators. &amp;quot;Smurfing&amp;quot; is originally derived from a cartoon, The Smurfs, which consisted of a large society of many small individuals. The coining of the term is attributed to Miami-based lawyer, Gregory Baldwin in the 1980s.&lt;br /&gt;
&lt;br /&gt;
'''Smurging''' or a '''Smurf Attack''' in the context of network security describes the act of many small ICMP pings being used to create very large network traffic congestion. The &amp;quot;smurf&amp;quot; attack's cousin is called '''Fraggle''', which uses UDP echo packets in the same fashion as the ICMP echo packets. It was a simple re-write of &amp;quot;smurf&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:Smurf2.gif|thumb|450px|''http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm#Smurf_Attack'']]&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In order for a Smurf Attack to take place there are three parties which need to be considered. First is the attack who orcastrates the attack. Second is the amplifier, who is usually another victim of the attack, and lastly, the target.&lt;br /&gt;
===The Attacker===&lt;br /&gt;
The attack itself is fairly simple. However the attacker will need a few things before the attack can be carried out. First the attacker will need a fast connection to the internet, and will need to find a large network, or a number of networks, that is attached to the Internet by a router that will forward ICMP requests. This network is the amplifier. The attacker will then send a ping request with a spoofed source address (the address of the target) to the broadcast address of the amplifier. The attacker has completed his portion of the attack. &lt;br /&gt;
&lt;br /&gt;
===The Amplifier===&lt;br /&gt;
An amplifier is a large network that is connected to the internet with a router. The router must be able to perform an IP broadcast. When the router receives traffic to the broadcast address, it will forward the message to all the hosts on the network. If the router receives and broadcasts an ICMP ping request, most of the hosts will reply to the source address of the message. This means that if there are 500 hosts which reply to the IP broadcast, then for every 1 ping request to that amplifier, 500 ping relies are sent. When an attacker spoofs the source address of the ping requests, rather than the pings replies going back to the attacker, they will go to the spoofed address (i.e. the victim). If the attacker has a fast connection, then it can send several ping requests very quickly. The amplifier is assumed to have a much faster connection (i.e. T3) to accommodate the ping replies. &lt;br /&gt;
&lt;br /&gt;
===The Target===&lt;br /&gt;
The target is generally a specific server or small network. Upon receiving the ICMP replies, the target is no longer able to make its services available to its intended users since it is busy processing these ICMP messages. This creates a Denial-of-Service and render the target unaccessible to other users.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=all/&amp;gt;&lt;br /&gt;
==Prevention==&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
http://www.webopedia.com/TERM/S/smurf.html&lt;br /&gt;
http://www.pentics.net/denial-of-service/white-papers/smurf.cgi&lt;br /&gt;
http://www.academ.com/nanog/oct1997/smurfing/sld001.htm&lt;br /&gt;
http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm&lt;br /&gt;
http://en.wikipedia.org/wiki/Smurf_attack&lt;br /&gt;
http://www.networkworld.com/archive/1999b/0222gearhead.html&lt;br /&gt;
http://www-arc.com/sara/cve/Possible_DoS_problem.html&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-13T21:10:41Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a form of Denial-of-Service attack where an attacker floods a target with ICMP echo (ping) traffic. &lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:brainy.jpg|thumb|165px|right|&lt;br /&gt;
''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
'''Smurfing''' is a banking industry term used to describe the act of splitting up a large financial transaction into several smaller ones to avoid scrutiny from regulators. &amp;quot;Smurfing&amp;quot; is originally derived from a cartoon, The Smurfs, which consisted of a large society of many small individuals. The coining of the term is attributed to Miami-based lawyer, Gregory Baldwin in the 1980s.&lt;br /&gt;
&lt;br /&gt;
'''Smurging''' or a '''Smurf Attack''' in the context of network security describes the act of many small ICMP pings being used to create very large network traffic congestion. The &amp;quot;smurf&amp;quot; attack's cousin is called '''Fraggle''', which uses UDP echo packets in the same fashion as the ICMP echo packets. It was a simple re-write of &amp;quot;smurf&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
{|align=&amp;quot;right&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:Smurf2.gif|thumb|450px|''http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm#Smurf_Attack'']]&lt;br /&gt;
|}&lt;br /&gt;
In order for a Smurf Attack to take place there are three parties which need to be considered. First is the attack who orcastrates the attack. Second is the amplifier, who is usually another victim of the attack, and lastly, the target.&lt;br /&gt;
===The Attacker===&lt;br /&gt;
The attack itself is fairly simple. However the attacker will need a few things before the attack can be carried out. First the attacker will need a fast connection to the internet, and will need to find a large network, or a number of networks, that is attached to the Internet by a router that will forward ICMP requests. This network is the amplifier. The attacker will then send a ping request with a spoofed source address (the address of the target) to the broadcast address of the amplifier. The attacker has completed his portion of the attack. &lt;br /&gt;
&lt;br /&gt;
===The Amplifier===&lt;br /&gt;
An amplifier is a large network that is connected to the internet with a router. The router must be able to perform an IP broadcast. When the router receives traffic to the broadcast address, it will forward the message to all the hosts on the network. If the router receives and broadcasts an ICMP ping request, most of the hosts will reply to the source address of the message. This means that if there are 500 hosts which reply to the IP broadcast, then for every 1 ping request to that amplifier, 500 ping relies are sent. When an attacker spoofs the source address of the ping requests, rather than the pings replies going back to the attacker, they will go to the spoofed address (i.e. the victim). If the attacker has a fast connection, then it can send several ping requests very quickly. The amplifier is assumed to have a much faster connection (i.e. T3) to accommodate the ping replies. &lt;br /&gt;
&lt;br /&gt;
===The Target===&lt;br /&gt;
The target is generally a specific server or small network. Upon receiving the ICMP replies, the target is no longer able to make its services available to its intended users since it is busy processing these ICMP messages. This creates a Denial-of-Service and render the target unaccessible to other users.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=all/&amp;gt;&lt;br /&gt;
==Prevention==&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
http://www.webopedia.com/TERM/S/smurf.html&lt;br /&gt;
http://www.pentics.net/denial-of-service/white-papers/smurf.cgi&lt;br /&gt;
http://www.academ.com/nanog/oct1997/smurfing/sld001.htm&lt;br /&gt;
http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm&lt;br /&gt;
http://en.wikipedia.org/wiki/Smurf_attack&lt;br /&gt;
http://www.networkworld.com/archive/1999b/0222gearhead.html&lt;br /&gt;
http://www-arc.com/sara/cve/Possible_DoS_problem.html&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/File:Smurf2.gif</id>
		<title>File:Smurf2.gif</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/File:Smurf2.gif"/>
				<updated>2008-04-13T20:21:47Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-13T20:19:57Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a form of Denial-of-Service attack where an attacker floods a target with ICMP echo (ping) traffic. &lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:brainy.jpg|thumb|165px|right|&lt;br /&gt;
''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
'''Smurfing''' is a banking industry term used to describe the act of splitting up a large financial transaction into several smaller ones to avoid scrutiny from regulators. &amp;quot;Smurfing&amp;quot; is originally derived from a cartoon, The Smurfs, which consisted of a large society of many small individuals. The coining of the term is attributed to Miami-based lawyer, Gregory Baldwin in the 1980s.&lt;br /&gt;
&lt;br /&gt;
'''Smurging''' or a '''Smurf Attack''' in the context of network security describes the act of many small ICMP pings being used to create very large network traffic congestion. &lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
In order for a Smurf Attack to take place there are three parties which need to be considered. First is the attack who orcastrates the attack. Second is the amplifier, who is usually another victim of the attack, and lastly, the target.&lt;br /&gt;
===The Attacker===&lt;br /&gt;
&lt;br /&gt;
===The Amplifier===&lt;br /&gt;
&lt;br /&gt;
===The Target===&lt;br /&gt;
&lt;br /&gt;
==Prevention==&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
http://www.webopedia.com/TERM/S/smurf.html&lt;br /&gt;
http://www.pentics.net/denial-of-service/white-papers/smurf.cgi&lt;br /&gt;
http://www.academ.com/nanog/oct1997/smurfing/sld001.htm&lt;br /&gt;
http://faculty.ed.umuc.edu/~meinkej/inss690/cummins/cummins.htm&lt;br /&gt;
http://en.wikipedia.org/wiki/Smurf_attack&lt;br /&gt;
http://www.networkworld.com/archive/1999b/0222gearhead.html&lt;br /&gt;
http://www-arc.com/sara/cve/Possible_DoS_problem.html&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-11T22:36:09Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a way of generating a lot of computer network traffic to a victim site. That is, it is a type of denial-of-service attack. Specifically, it floods a target system via spoofed broadcast ping messages.&lt;br /&gt;
&lt;br /&gt;
In such an attack, a perpetrator sends a large amount of ICMP echo (ping) traffic to IP broadcast addresses, all of it having a spoofed source address of the intended victim. If the routing device delivering traffic to those broadcast addresses delivers the IP broadcast to all hosts (for example via a layer 2 broadcast), most hosts on that IP network will take the ICMP echo request and reply to it with an echo reply, multiplying the traffic by the number of hosts responding. On a multi-access broadcast network, hundreds of machines might reply to each packet.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:brainy.jpg|thumb|165px|right|&lt;br /&gt;
''Brainy Smurf''&amp;lt;br&amp;gt;Smurfs, as a society, were against any sort of attack.]]&lt;br /&gt;
&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
&lt;br /&gt;
==Prevention==&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/File:Brainy.jpg</id>
		<title>File:Brainy.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/File:Brainy.jpg"/>
				<updated>2008-04-11T22:24:33Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Smurfing</id>
		<title>Smurfing</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Smurfing"/>
				<updated>2008-04-11T22:21:55Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;New page: '''Smurfing''' or a '''Smurf Attack''' is a way of generating a lot of computer network traffic to a victim site. That is, it is a type of denial-of-service attack. Specifically, it floods...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Smurfing''' or a '''Smurf Attack''' is a way of generating a lot of computer network traffic to a victim site. That is, it is a type of denial-of-service attack. Specifically, it floods a target system via spoofed broadcast ping messages.&lt;br /&gt;
&lt;br /&gt;
In such an attack, a perpetrator sends a large amount of ICMP echo (ping) traffic to IP broadcast addresses, all of it having a spoofed source address of the intended victim. If the routing device delivering traffic to those broadcast addresses delivers the IP broadcast to all hosts (for example via a layer 2 broadcast), most hosts on that IP network will take the ICMP echo request and reply to it with an echo reply, multiplying the traffic by the number of hosts responding. On a multi-access broadcast network, hundreds of machines might reply to each packet.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What is Smurfing?==&lt;br /&gt;
&lt;br /&gt;
==How does a Smurf Attack take place?==&lt;br /&gt;
&lt;br /&gt;
==Prevention==&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-12-04T00:25:12Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social Engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricking the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg|thumb|300px|right|&lt;br /&gt;
'''[http://en.wikipedia.org/wiki/Kevin_Mitnick Kevin David Mitnick]'''&lt;br /&gt;
&amp;lt;br&amp;gt;''Born October 6, 1963''&amp;lt;br&amp;gt;&lt;br /&gt;
Convicted of computer related crimes using social engineering.]]&lt;br /&gt;
&lt;br /&gt;
==What is Social Engineering?==&lt;br /&gt;
Social Engineering is the manipulation of people to further a person's motives using various methods. “The art and science of getting people to comply to your wishes” - [http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt Bernz]. This &amp;quot;compliance&amp;quot; is generally associated with the acquisition of electronic information. However, Social Engineering can also apply to a border definition which encompasses any kind personal manipulation in an attempt to gain something dishonestly. The manipulation is performed by &amp;quot;tricking&amp;quot; the mark (the unsuspecting victim) into a false sense of trust which is them abused to obtain the sought objective.&lt;br /&gt;
&lt;br /&gt;
==Aspects of Social Engineering==&lt;br /&gt;
A social engineering attack can be thought of as process with two key components; human and the system. The human component requires the social engineer to gain the trust of whom ever has access to the system.&lt;br /&gt;
===Human===&lt;br /&gt;
The human element in social engineering attacks is the method in which the objectives are carried out. Human beings are generally the weakest part of any security system because they can be tricked or corrupted. By attacking the people who have access to what social engineers want, the objectives of a social engineer can be obtained more easily. People like system administrator, maintenance people, or employees can all potential jeopardized a secure system by giving out information that to someone who they consider to be trustworthy.&lt;br /&gt;
&lt;br /&gt;
===System===&lt;br /&gt;
The system refers to any potentially closed system which contains something a social engineer wants. A social engineering attack is only successful if the social engineer has knowledge about the inner workings of the system. Knowledge like protocols, terminology, names of people, important dates, etc., provide social engineers ammunition to construct a persona which is then used to manipulate the people who have access to the system.&lt;br /&gt;
&lt;br /&gt;
==Methods of Social Engineering==&lt;br /&gt;
===By Phone===&lt;br /&gt;
This is the most common method of social engineering attacks. An attacker will call the mark, using a persona, and gain the mark's trust. Then the attacker will request information which then might be used to perform another social engineering attack. Help desks are prone to this kind of attack since they are trained to be friendly and give out information. They are also minimally educated in areas of security. An example of this type of attack might be the following scenario. An attacker calls a help desk and asks to speak to the supervisor. When the supervisor answers, the attacker explains that he is the system administrator and that there is a problem with the system. Then the attacker asks the supervisor to login to the system. The attacker then states that he is unable to see the login on his end and that this is a problem. Then the attacker asks the supervisor to give him the login information so that he can try. Once the supervisor has done this, the attacker tells the supervisor that everything seems to be ok and the supervisor is none the wiser.&lt;br /&gt;
&lt;br /&gt;
Another example of a phone attack is when the attacker calls a person in the middle of the night posing as someone from a bank. The attacker asks if they have just made a suspicious purchase (a very large amount or in another country). When the mark says no, the attacker asks for the credit card number for verification, then says the charges will be removed from the account.&lt;br /&gt;
&lt;br /&gt;
Social Engineering can take on many forms on the phone and can have many different objectives. The most notable social engineer in 1990's was [http://en.wikipedia.org/wiki/Kevin_Mitnick Kevin Mitnick]. He was arrest in 1995 and convicted of illegally gaining access to computer networks and stealing intellectual property. Mitnick's methods relied on the use of phone calls to the companies which he attacked and the use of the [[The_Mitnick_attack|Mitnick Attack]]. Mitnick served 5 years in prison and now runs a security consulting company which gives security advice to companies.&lt;br /&gt;
&lt;br /&gt;
===Online===&lt;br /&gt;
Online social engineering attacks are similar to phone attacks, in that they pose as a legitimate entity which the mark will trust. Many online attacks are spread through [[Phishing|phishing]]. This type of social engineering assumes that most users use the same login and password for many internet sites, so by getting the user to sign up for a new site, they will be giving up their login information. These sites might be in the form of new sites which the use might be interested in, or they might pose as sites which the user already has an account for and ask the user to try and login again. The latter example can take for in the following. The mark receives an email informing him that he needs to update his PayPal password by clicking the provided link and logging in. Failure to do so will result in the termination of the account after a specified period. Once the mark clicks on the link, and enters his login information, a message is displayed which confirms the change. The link the mark has clicked on, however, was a link to the attacker's site which simply records the login information.&lt;br /&gt;
&lt;br /&gt;
===Persuasion===&lt;br /&gt;
Persuasion is the core of social engineering attacks. This method is used in all social engineering attacks and relies on the attacker's grasp of the human psyche. The attacker's ability to persuade is determined by two things. Firstly the attacker must be able to gain trust. This can be accomplished using various techniques. The most common of which are creating a persona by impersonation (such as [[Identity_Theft|identity theft]] or imitation. An attacker can pose as either an existing employee or pose as a generic employee. For example, an attacker calling an office can say that his name is Bob Anderson with employee number 123456 (where Bob Anderson is an existing employ who works at a different branch with that employee number), or he can say he's Dale Johnson, a new system administrator brought in to fix the recent system failures (where Dale Johnson is a made up name). The use of these personas provides the social engineer with the appearance of authenticity which is used to build the mark's trust. Once this authenticity is established, the attacker must then complete the persuasion by implementing the second step, manipulation. This is accomplished by providing a convincing reason to the mark to give the attacker what he wants. This can be a colourful background story, a tempting offer, or even guilt the mark into compliance. The point is to make the mark believe that the persona that is being used is legitimate and that the requests being made are genuine. If a social engineer can master these two elements then he will be very persuasive.&lt;br /&gt;
&lt;br /&gt;
===Dumpster Diving===&lt;br /&gt;
Dumpster Diving, also known as trashing, is the &amp;quot;snooping&amp;quot; through trash to collect information. It is a very effective method of obtaining many different types of information. The premise is that many companies and individuals don't apply a high level of security in their garbage because they feel as though what they throw out is no longer relevant. However, much of the trash being discarded can collectively provide the social engineer with the tools needed to create personas and learn about the inner workings of the system. Trash like old user and password lists, company directories, event calendars, printouts of source code and even obsolete hardware can contain information that is relevant to the current state of the system. In particular the social engineer can learn about the company’s protocols, terminology and many employee's names and other personal information.&lt;br /&gt;
&lt;br /&gt;
===Reverse Social Engineering===&lt;br /&gt;
The objective in reverse social engineering is to have the mark ask the attacker for information, rather than the other way around. The advantage of this method is that the attacker can give out information that will suit his motives. For example, an attacker can call the supervisor of an office and inform him that there is maintenance scheduled on the office network and if people have problems accessing the system that they should call the attacker. Then the attacker will create a network outage and when the employees call, he can retrieve their login information. This kind of attack requires a significant amount of preparation; however, it can yield very successful results.&lt;br /&gt;
&lt;br /&gt;
==Protection==&lt;br /&gt;
To protect against social engineering attacks, a company should implement [http://en.wikipedia.org/wiki/Security_policy security policies] which deal with both physical and psychological elements. Standard physical security mechanisms should be implemented which take into account network protection, password protection, and a system of securely disposing of trash. In addition, the policies should cover the education and training of employees to help recognize a social engineering attack. This kind of training should deal with how these attacks can happen, specific examples, and methods in which employees can authenticate who they are speaking with. It should also stress the importance of not giving out information that is not [http://en.wikipedia.org/wiki/Need_to_know need-to-know] or confidential (such as passwords). In general a good practice of [[Information_security_awareness|information security awareness]] will provide employees with a more sceptical attitude in giving out information.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
Bernz: “The complete Social Engineering FAQ!”&lt;br /&gt;
http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt&lt;br /&gt;
&lt;br /&gt;
Sarah Granger : “Social Engineering Fundamentals”, SecurityFocus, December 18, 2001&lt;br /&gt;
http://www.securityfocus.com/infocus/1527&lt;br /&gt;
&lt;br /&gt;
“Social engineering (security)”, Wikipedia, November 19, 2007&lt;br /&gt;
http://en.wikipedia.org/wiki/Social_engineering_(computer_security)&lt;br /&gt;
&lt;br /&gt;
“social engineering”, SearchSecurity, October 10, 2006&lt;br /&gt;
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci531120,00.html&lt;br /&gt;
&lt;br /&gt;
Mitnick, Kevin: “My first RSA Conference,” SecurityFocus, April 30, 2001&lt;br /&gt;
http://www.securityfocus.com/news/199&lt;br /&gt;
&lt;br /&gt;
Leslie Hawthorn: “Social Engineering”, O’Reilly Network, March 10, 2006&lt;br /&gt;
http://www.oreilly.com/pub/a/womenintech/2007/09/04/social-engineering.html&lt;br /&gt;
&lt;br /&gt;
“Social Engineering”, McGuill Network Communications Services, September 7, 2007&lt;br /&gt;
http://www.mcgill.ca/ncs/products/security/threatsdangers/socialeng/&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
[[User:Shahinrs|Shahinrs]] 19:25, 3 December 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-12-04T00:21:18Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social Engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricking the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg|thumb|300px|right|&lt;br /&gt;
'''[http://en.wikipedia.org/wiki/Kevin_Mitnick Kevin David Mitnick]'''&lt;br /&gt;
&amp;lt;br&amp;gt;''Born October 6, 1963''&amp;lt;br&amp;gt;&lt;br /&gt;
Convicted of computer related crimes using social engineering.]]&lt;br /&gt;
&lt;br /&gt;
==What is Social Engineering?==&lt;br /&gt;
Social Engineering is the manipulation of people to further a person's motives using various methods. “The art and science of getting people to comply to your wishes” - [http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt Bernz]. This &amp;quot;compliance&amp;quot; is generally associated with the acquisition of electronic information. However, Social Engineering can also apply to a border definition which encompasses any kind personal manipulation in an attempt to gain something dishonestly. The manipulation is performed by &amp;quot;tricking&amp;quot; the mark (the unsuspecting victim) into a false sense of trust which is them abused to obtain the sought objective.&lt;br /&gt;
&lt;br /&gt;
==Aspects of Social Engineering==&lt;br /&gt;
A social engineering attack can be thought of as process with two key components; human and the system. The human component requires the social engineer to gain the trust of whom ever has access to the system.&lt;br /&gt;
===Human===&lt;br /&gt;
The human element in social engineering attacks is the method in which the objectives are carried out. Human beings are generally the weakest part of any security system because they can be tricked or corrupted. By attacking the people who have access to what social engineers want, the objectives of a social engineer can be obtained more easily. People like system administrator, maintenance people, or employees can all potential jeopardized a secure system by giving out information that to someone who they consider to be trustworthy.&lt;br /&gt;
&lt;br /&gt;
===System===&lt;br /&gt;
The system refers to any potentially closed system which contains something a social engineer wants. A social engineering attack is only successful if the social engineer has knowledge about the inner workings of the system. Knowledge like protocols, terminology, names of people, important dates, etc., provide social engineers ammunition to construct a persona which is then used to manipulate the people who have access to the system.&lt;br /&gt;
&lt;br /&gt;
==Methods of Social Engineering==&lt;br /&gt;
===By Phone===&lt;br /&gt;
This is the most common method of social engineering attacks. An attacker will call the mark, using a persona, and gain the mark's trust. Then the attacker will request information which then might be used to perform another social engineering attack. Help desks are prone to this kind of attack since they are trained to be friendly and give out information. They are also minimally educated in areas of security. An example of this type of attack might be the following scenario. An attacker calls a help desk and asks to speak to the supervisor. When the supervisor answers, the attacker explains that he is the system administrator and that there is a problem with the system. Then the attacker asks the supervisor to login to the system. The attacker then states that he is unable to see the login on his end and that this is a problem. Then the attacker asks the supervisor to give him the login information so that he can try. Once the supervisor has done this, the attacker tells the supervisor that everything seems to be ok and the supervisor is none the wiser.&lt;br /&gt;
&lt;br /&gt;
Another example of a phone attack is when the attacker calls a person in the middle of the night posing as someone from a bank. The attacker asks if they have just made a suspicious purchase (a very large amount or in another country). When the mark says no, the attacker asks for the credit card number for verification, then says the charges will be removed from the account.&lt;br /&gt;
&lt;br /&gt;
Social Engineering can take on many forms on the phone and can have many different objectives. The most notable social engineer in 1990's was [http://en.wikipedia.org/wiki/Kevin_Mitnick Kevin Mitnick]. He was arrest in 1995 and convicted of illegally gaining access to computer networks and stealing intellectual property. Mitnick's methods relied on the use of phone calls to the companies which he attacked and the use of the [[The_Mitnick_attack|Mitnick Attack]]. Mitnick served 5 years in prison and now runs a security consulting company which gives security advice to companies.&lt;br /&gt;
&lt;br /&gt;
===Online===&lt;br /&gt;
Online social engineering attacks are similar to phone attacks, in that they pose as a legitimate entity which the mark will trust. Many online attacks are spread through [[Phishing|phishing]]. This type of social engineering assumes that most users use the same login and password for many internet sites, so by getting the user to sign up for a new site, they will be giving up their login information. These sites might be in the form of new sites which the use might be interested in, or they might pose as sites which the user already has an account for and ask the user to try and login again. The latter example can take for in the following. The mark receives an email informing him that he needs to update his PayPal password by clicking the provided link and logging in. Failure to do so will result in the termination of the account after a specified period. Once the mark clicks on the link, and enters his login information, a message is displayed which confirms the change. The link the mark has clicked on, however, was a link to the attacker's site which simply records the login information.&lt;br /&gt;
&lt;br /&gt;
===Persuasion===&lt;br /&gt;
Persuasion is the core of social engineering attacks. This method is used in all social engineering attacks and relies on the attacker's grasp of the human psyche. The attacker's ability to persuade is determined by two things. Firstly the attacker must be able to gain trust. This can be accomplished using various techniques. The most common of which are creating a persona by impersonation (such as [[Identity_Theft|identity theft]] or imitation. An attacker can pose as either an existing employee or pose as a generic employee. For example, an attacker calling an office can say that his name is Bob Anderson with employee number 123456 (where Bob Anderson is an existing employ who works at a different branch with that employee number), or he can say he's Dale Johnson, a new system administrator brought in to fix the recent system failures (where Dale Johnson is a made up name). The use of these personas provides the social engineer with the appearance of authenticity which is used to build the mark's trust. Once this authenticity is established, the attacker must then complete the persuasion by implementing the second step, manipulation. This is accomplished by providing a convincing reason to the mark to give the attacker what he wants. This can be a colourful background story, a tempting offer, or even guilt the mark into compliance. The point is to make the mark believe that the persona that is being used is legitimate and that the requests being made are genuine. If a social engineer can master these two elements then he will be very persuasive.&lt;br /&gt;
&lt;br /&gt;
===Dumpster Diving===&lt;br /&gt;
Dumpster Diving, also known as trashing, is the &amp;quot;snooping&amp;quot; through trash to collect information. It is a very effective method of obtaining many different types of information. The premise is that many companies and individuals don't apply a high level of security in their garbage because they feel as though what they throw out is no longer relevant. However, much of the trash being discarded can collectively provide the social engineer with the tools needed to create personas and learn about the inner workings of the system. Trash like old user and password lists, company directories, event calendars, printouts of source code and even obsolete hardware can contain information that is relevant to the current state of the system. In particular the social engineer can learn about the company’s protocols, terminology and many employee's names and other personal information.&lt;br /&gt;
&lt;br /&gt;
===Reverse Social Engineering===&lt;br /&gt;
The objective in reverse social engineering is to have the mark ask the attacker for information, rather than the other way around. The advantage of this method is that the attacker can give out information that will suit his motives. For example, an attacker can call the supervisor of an office and inform him that there is maintenance scheduled on the office network and if people have problems accessing the system that they should call the attacker. Then the attacker will create a network outage and when the employees call, he can retrieve their login information. This kind of attack requires a significant amount of preparation; however, it can yield very successful results.&lt;br /&gt;
&lt;br /&gt;
==Protection==&lt;br /&gt;
To protect against social engineering attacks, a company should implement [http://en.wikipedia.org/wiki/Security_policy security policies] which deal with both physical and psychological elements. Standard physical security mechanisms should be implemented which take into account network protection, password protection, and a system of securely disposing of trash. In addition, the policies should cover the education and training of employees to help recognize a social engineering attack. This kind of training should deal with how these attacks can happen, specific examples, and methods in which employees can authenticate who they are speaking with. It should also stress the importance of not giving out information that is not [http://en.wikipedia.org/wiki/Need_to_know need-to-know] or confidential (such as passwords). In general a good practice of [[Information_security_awareness|information security awareness]] will provide employees with a more sceptical attitude in giving out information.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
Bernz: “The complete Social Engineering FAQ!”&lt;br /&gt;
http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt&lt;br /&gt;
&lt;br /&gt;
Sarah Granger : “Social Engineering Fundamentals”, SecurityFocus, December 18, 2001&lt;br /&gt;
http://www.securityfocus.com/infocus/1527&lt;br /&gt;
&lt;br /&gt;
“Social engineering (security)”, Wikipedia, November 19, 2007&lt;br /&gt;
http://en.wikipedia.org/wiki/Social_engineering_(computer_security)&lt;br /&gt;
&lt;br /&gt;
“social engineering”, SearchSecurity, October 10, 2006&lt;br /&gt;
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci531120,00.html&lt;br /&gt;
&lt;br /&gt;
Mitnick, Kevin: “My first RSA Conference,” SecurityFocus, April 30, 2001&lt;br /&gt;
http://www.securityfocus.com/news/199&lt;br /&gt;
&lt;br /&gt;
Leslie Hawthorn: “Social Engineering”, O’Reilly Network, March 10, 2006&lt;br /&gt;
http://www.oreilly.com/pub/a/womenintech/2007/09/04/social-engineering.html&lt;br /&gt;
&lt;br /&gt;
“Social Engineering”, McGuill Network Communications Services, September 7, 2007&lt;br /&gt;
http://www.mcgill.ca/ncs/products/security/threatsdangers/socialeng/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]]&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-12-04T00:07:36Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social Engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricking the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg|thumb|300px|right|&lt;br /&gt;
'''Kevin David Mitnick'''&lt;br /&gt;
&amp;lt;br&amp;gt;''Born October 6, 1963''&amp;lt;br&amp;gt;&lt;br /&gt;
Convicted of computer related crimes using social engineering.]]&lt;br /&gt;
&lt;br /&gt;
==What is Social Engineering?==&lt;br /&gt;
Social Engineering is the manipulation of people to further a person's motives using various methods. “The art and science of getting people to comply to your wishes” - [http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt Bernz]. This &amp;quot;compliance&amp;quot; is generally associated with the acquisition of electronic information. However, Social Engineering can also apply to a border definition which encompasses any kind personal manipulation in an attempt to gain something dishonestly. The manipulation is performed by &amp;quot;tricking&amp;quot; the mark (the unsuspecting victim) into a false sense of trust which is them abused to obtain the sought objective.&lt;br /&gt;
&lt;br /&gt;
==Aspects of Social Engineering==&lt;br /&gt;
A social engineering attack can be thought of as process with two key components; human and the system. The human component requires the social engineer to gain the trust of whom ever has access to the system.&lt;br /&gt;
===Human===&lt;br /&gt;
The human element in social engineering attacks is the method in which the objectives are carried out. Human beings are generally the weakest part of any security system because they can be tricked or corrupted. By attacking the people who have access to what a social engineer wants, the objectives of a social engineer can be reach more easily. People like system administrator, maintenance people, or employees can all potential jeopardized a secure system by giving out information that to someone who they consider to be trustworthy.&lt;br /&gt;
&lt;br /&gt;
===System===&lt;br /&gt;
The system refers to any potentially closed system which contains something a social engineer wants. A social engineering attack is only successful if the social engineer has knowledge about the inner workings of the system. Knowledge like protocols, terminology, names of people, important dates, etc., provide a social engineer ammunition to construct a persona which is then used to manipulate the people who have access to the system.&lt;br /&gt;
&lt;br /&gt;
==Methods of Social Engineering==&lt;br /&gt;
===By Phone===&lt;br /&gt;
This is the most common method of social engineering attacks. An attacker will call the mark, using a persona, and gain the mark's trust. Then the attacker will request information which then might be used to perform another social engineering attack. Help desks are prone to this kind of attack since they are trained to be friendly and give out information. They are also minimally educated in areas of security. An example of this type of attack might be the following scenario. An attacker calls a help desk and asks to speak to the supervisor. When the supervisor answer, the attacker explains that he is the system administrator and that there is a problem with the system. Then the attacker asks the supervisor to login to the system. The attacker then states that he is unable to see the login on his end and that this is a problem. Then the attacker asks the supervisor to give him the login information so that he can try. Once the supervisor has done this, the attacker tells the supervisor that everything seems to be ok and the supervisor is none the wiser.&lt;br /&gt;
&lt;br /&gt;
Another example of a phone attack is when the attacker calls a person in the middle of the night posing as someone from a bank. The attacker asks if they have just made a suspicious purchase (a very large amount or in another country). When the mark says no, the attacker asks for the credit card number for verification, then says the charges will be removed from the account.&lt;br /&gt;
&lt;br /&gt;
Social Engineering can take on many forms on the phone and can have many different objectives. The most notable social engineer in 1990's was Kevin Mitnick. He was arrest in 1995 and convicted of illegally gaining access to computer networks and stealing intellectual property. Mitnick's methods relied on the use of phone calls to the companies which he attacked and the use of the [[The_Mitnick_attack|Mitnick Attack]]. Mitnick served 5 years in prison and now runs a security consulting company which gives security advice to companies.&lt;br /&gt;
&lt;br /&gt;
===Online===&lt;br /&gt;
Online social engineering attacks are similar to phone attacks, in that they pose as a legitimate entity which the mark will trust. Many online attacks are spread through [[Phishing|phishing]]. This type of social engineering assumes that most users use the same login and password for many internet sites, so by getting the user to sign up for a new site, they will be giving up their login information. These sites might be in the form of new sites which the use might be interested in, or they might pose as sites which the user already has an account for and ask the user to try and login again. The latter example can take for in the following. The mark receives an email informing him that he needs to update his PayPal password by clicking the provided link and logging in. Failure to do so will result in the termination of the account after a specified period. Once the mark clicks on the link, and enters his login information, a message is displayed which confirms the change. The link the mark has clicked on however, was a link to the attacker's site which simply records the login information.&lt;br /&gt;
&lt;br /&gt;
===Persuasion===&lt;br /&gt;
Persuasion is the core of social engineering attacks. This method is used in all social engineering attacks and relies on the attacker's grasp of the human psyche. The attacker's ability to persuade is determined by two things. Firstly the attacker must be able to gain trust. This can be accomplished using various techniques. The most common of which are creating a persona by impersonation (such as [[Identity_Theft|identity theft]] or imitation. An attacker can pose as either an existing employee or pose as a generic employee. For example, an attacker calling an office can say that his name is Bob Anderson with employee number 123456 (where Bob Anderson is an existing employ who works at a different branch with that employee number), or he can say he's Dale Johnson, a new system administrator brought in to fix the recent system failures (where Dale Johnson is a made up name). The use of these persona provides the social engineer with a the appearance of authenticity which is used to build the mark's trust. Once this authenticity is established, the attacker must then complete the persuasion by implementing the second step, manipulation. This is accomplished by providing a convincing reason to the mark to give the attacker what he wants. This can be a colorful background story, a tempting offer, or even guiling the mark into compliance. The point is to make the mark believe that the persona that is being used is legitimate and that the requests being made are genuine. If a social engineer can master these two elements then he will be very persuasive.&lt;br /&gt;
&lt;br /&gt;
===Dumpster Diving===&lt;br /&gt;
Dumpster Diving, also known as trashing, is the &amp;quot;snooping&amp;quot; through trash to collect information. It is a very effective method of obtaining many different types of information. The premis is that many companies and individuals don't apply a high level of security in their garbage because they feel as though what they throw out is no longer relevant. However, much of the trash being discarded can collectively provide the social engineer with the tools needed to create personas and learn about the inner workings of the system. Trash like old user and password lists, company directories, event calenders, printouts of source code and even obsolete hardware can contain information that is relevant to the current state of the system. In particular the social engineer can learn about the companies protocols, terminology and many employee's names and other personal information.&lt;br /&gt;
&lt;br /&gt;
===Reverse Social Engineering===&lt;br /&gt;
The objective in reverse social engineering is to have the mark ask the attacker for information, rather than the other way around. The advantage of this method is that the attacker can give out information that will suit his motives. For example, an attacker can call the supervisor of an office and inform him that there is maintenance scheduled on the office network and if people have problems accessing the system that they should call the attacker. Then the attacker will create a network outage and when the employees call, he can retrieve their login information. This kind of attack requires a significant amount of preperation, however it can yield very successful results.&lt;br /&gt;
&lt;br /&gt;
==Protection==&lt;br /&gt;
To protect against social engineering attacks, a company should implement security policies which deal with both physical and psychological elements. Standard physical security mechanisms should be implemented which take into account network protection, password protection, and a system of securely disposing of trash. In addition, the policies should cover the education and training of emplyees to help recognize a social engineering attack. This kind of training should deal with how these attacks can happen, specific examples, and methods in which employees can authenticate who they are speaking with. It should also stress the importance of not giving out information that is not need-to-know or confidential (such as passwords). In general a good practice of [[Information_security_awareness|information security awareness]] will provide employees with a more skeptical attitude in giving out information.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
Bernz: “The complete Social Engineering FAQ!”&lt;br /&gt;
http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt&lt;br /&gt;
&lt;br /&gt;
Sarah Granger : “Social Engineering Fundamentals”, SecurityFocus, December 18, 2001&lt;br /&gt;
http://www.securityfocus.com/infocus/1527&lt;br /&gt;
&lt;br /&gt;
“Social engineering (security)”, Wikipedia, November 19, 2007&lt;br /&gt;
http://en.wikipedia.org/wiki/Social_engineering_(computer_security)&lt;br /&gt;
&lt;br /&gt;
“social engineering”, SearchSecurity, October 10, 2006&lt;br /&gt;
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci531120,00.html&lt;br /&gt;
&lt;br /&gt;
Mitnick, Kevin: “My first RSA Conference,” SecurityFocus, April 30, 2001&lt;br /&gt;
http://www.securityfocus.com/news/199&lt;br /&gt;
&lt;br /&gt;
Leslie Hawthorn: “Social Engineering”, O’Reilly Network, March 10, 2006&lt;br /&gt;
http://www.oreilly.com/pub/a/womenintech/2007/09/04/social-engineering.html&lt;br /&gt;
&lt;br /&gt;
“Social Engineering”, McGuill Network Communications Services, September 7, 2007&lt;br /&gt;
http://www.mcgill.ca/ncs/products/security/threatsdangers/socialeng/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-12-04T00:04:27Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social Engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricking the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg|thumb|300px|right|&lt;br /&gt;
'''Kevin David Mitnick'''&lt;br /&gt;
&amp;lt;br&amp;gt;''Born October 6, 1963''&amp;lt;br&amp;gt;&lt;br /&gt;
Convicted of computer related crimes using social engineering.]]&lt;br /&gt;
&lt;br /&gt;
==What is Social Engineering?==&lt;br /&gt;
Social Engineering is the manipulation of people to further a person's motives using various methods. “The art and science of getting people to comply to your wishes” - [http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt Bernz]. This &amp;quot;compliance&amp;quot; is generally associated with the acquisition of electronic information. However, Social Engineering can also apply to a border definition which encompasses any kind personal manipulation in an attempt to gain something dishonestly. The manipulation is performed by &amp;quot;tricking&amp;quot; the mark (the unsuspecting victim) into a false sense of trust which is them abused to obtain the sought objective.&lt;br /&gt;
&lt;br /&gt;
==Aspects of Social Engineering==&lt;br /&gt;
A social engineering attack can be thought of as process with two key components; human and the system. The human component requires the social engineer to gain the trust of whom ever has access to the system.&lt;br /&gt;
===Human===&lt;br /&gt;
The human element in social engineering attacks is the method in which the objectives are carried out. Human beings are generally the weakest part of any security system because they can be tricked or corrupted. By attacking the people who have access to what a social engineer wants, the objectives of a social engineer can be reach more easily. People like system administrator, maintenance people, or employees can all potential jeopardized a secure system by giving out information that to someone who they consider to be trustworthy.&lt;br /&gt;
&lt;br /&gt;
===System===&lt;br /&gt;
The system refers to any potentially closed system which contains something a social engineer wants. A social engineering attack is only successful if the social engineer has knowledge about the inner workings of the system. Knowledge like protocols, terminology, names of people, important dates, etc., provide a social engineer ammunition to construct a persona which is then used to manipulate the people who have access to the system.&lt;br /&gt;
&lt;br /&gt;
==Methods of Social Engineering==&lt;br /&gt;
===By Phone===&lt;br /&gt;
This is the most common method of social engineering attacks. An attacker will call the mark, using a persona, and gain the mark's trust. Then the attacker will request information which then might be used to perform another social engineering attack. Help desks are prone to this kind of attack since they are trained to be friendly and give out information. They are also minimally educated in areas of security. An example of this type of attack might be the following scenario. An attacker calls a help desk and asks to speak to the supervisor. When the supervisor answer, the attacker explains that he is the system administrator and that there is a problem with the system. Then the attacker asks the supervisor to login to the system. The attacker then states that he is unable to see the login on his end and that this is a problem. Then the attacker asks the supervisor to give him the login information so that he can try. Once the supervisor has done this, the attacker tells the supervisor that everything seems to be ok and the supervisor is none the wiser.&lt;br /&gt;
&lt;br /&gt;
Another example of a phone attack is when the attacker calls a person in the middle of the night posing as someone from a bank. The attacker asks if they have just made a suspicious purchase (a very large amount or in another country). When the mark says no, the attacker asks for the credit card number for verification, then says the charges will be removed from the account.&lt;br /&gt;
&lt;br /&gt;
Social Engineering can take on many forms on the phone and can have many different objectives. The most notable social engineer in 1990's was Kevin Mitnick. He was arrest in 1995 and convicted of illegally gaining access to computer networks and stealing intellectual property. Mitnick's methods relied on the use of phone calls to the companies which he attacked and the use of the [[The_Mitnick_attack|Mitnick Attack]]. Mitnick served 5 years in prison and now runs a security consulting company which gives security advice to companies.&lt;br /&gt;
&lt;br /&gt;
===Online===&lt;br /&gt;
Online social engineering attacks are similar to phone attacks, in that they pose as a legitimate entity which the mark will trust. Many online attacks are spread through [[Phishing|phishing]]. This type of social engineering assumes that most users use the same login and password for many internet sites, so by getting the user to sign up for a new site, they will be giving up their login information. These sites might be in the form of new sites which the use might be interested in, or they might pose as sites which the user already has an account for and ask the user to try and login again. The latter example can take for in the following. The mark receives an email informing him that he needs to update his PayPal password by clicking the provided link and logging in. Failure to do so will result in the termination of the account after a specified period. Once the mark clicks on the link, and enters his login information, a message is displayed which confirms the change. The link the mark has clicked on however, was a link to the attacker's site which simply records the login information.&lt;br /&gt;
&lt;br /&gt;
===Persuasion===&lt;br /&gt;
Persuasion is the core of social engineering attacks. This method is used in all social engineering attacks and relies on the attacker's grasp of the human psyche. The attacker's ability to persuade is determined by two things. Firstly the attacker must be able to gain trust. This can be accomplished using various techniques. The most common of which are creating a persona by impersonation (such as [[Identity_Theft||identity theft]] or imitation. An attacker can pose as either an existing employee or pose as a generic employee. For example, an attacker calling an office can say that his name is Bob Anderson with employee number 123456 (where Bob Anderson is an existing employ who works at a different branch with that employee number), or he can say he's Dale Johnson, a new system administrator brought in to fix the recent system failures (where Dale Johnson is a made up name). The use of these persona provides the social engineer with a the appearance of authenticity which is used to build the mark's trust. Once this authenticity is established, the attacker must then complete the persuasion by implementing the second step, manipulation. This is accomplished by providing a convincing reason to the mark to give the attacker what he wants. This can be a colorful background story, a tempting offer, or even guiling the mark into compliance. The point is to make the mark believe that the persona that is being used is legitimate and that the requests being made are genuine. If a social engineer can master these two elements then he will be very persuasive.&lt;br /&gt;
&lt;br /&gt;
===Dumpster Diving===&lt;br /&gt;
Dumpster Diving, also known as trashing, is the &amp;quot;snooping&amp;quot; through trash to collect information. It is a very effective method of obtaining many different types of information. The premis is that many companies and individuals don't apply a high level of security in their garbage because they feel as though what they throw out is no longer relevant. However, much of the trash being discarded can collectively provide the social engineer with the tools needed to create personas and learn about the inner workings of the system. Trash like old user and password lists, company directories, event calenders, printouts of source code and even obsolete hardware can contain information that is relevant to the current state of the system. In particular the social engineer can learn about the companies protocols, terminology and many employee's names and other personal information.&lt;br /&gt;
&lt;br /&gt;
===Reverse Social Engineering===&lt;br /&gt;
The objective in reverse social engineering is to have the mark ask the attacker for information, rather than the other way around. The advantage of this method is that the attacker can give out information that will suit his motives. For example, an attacker can call the supervisor of an office and inform him that there is maintenance scheduled on the office network and if people have problems accessing the system that they should call the attacker. Then the attacker will create a network outage and when the employees call, he can retrieve their login information. This kind of attack requires a significant amount of preperation, however it can yield very successful results.&lt;br /&gt;
&lt;br /&gt;
==Protection==&lt;br /&gt;
To protect against social engineering attacks, a company should implement security policies which deal with both physical and psychological elements. Standard physical security mechanisms should be implemented which take into account network protection, password protection, and a system of securely disposing of trash. In addition, the policies should cover the education and training of emplyees to help recognize a social engineering attack. This kind of training should deal with how these attacks can happen, specific examples, and methods in which employees can authenticate who they are speaking with. It should also stress the importance of not giving out information that is not need-to-know or confidential (such as passwords).&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
Bernz: “The complete Social Engineering FAQ!”&lt;br /&gt;
http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt&lt;br /&gt;
&lt;br /&gt;
Sarah Granger : “Social Engineering Fundamentals”, SecurityFocus, December 18, 2001&lt;br /&gt;
http://www.securityfocus.com/infocus/1527&lt;br /&gt;
&lt;br /&gt;
“Social engineering (security)”, Wikipedia, November 19, 2007&lt;br /&gt;
http://en.wikipedia.org/wiki/Social_engineering_(computer_security)&lt;br /&gt;
&lt;br /&gt;
“social engineering”, SearchSecurity, October 10, 2006&lt;br /&gt;
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci531120,00.html&lt;br /&gt;
&lt;br /&gt;
Mitnick, Kevin: “My first RSA Conference,” SecurityFocus, April 30, 2001&lt;br /&gt;
http://www.securityfocus.com/news/199&lt;br /&gt;
&lt;br /&gt;
Leslie Hawthorn: “Social Engineering”, O’Reilly Network, March 10, 2006&lt;br /&gt;
http://www.oreilly.com/pub/a/womenintech/2007/09/04/social-engineering.html&lt;br /&gt;
&lt;br /&gt;
“Social Engineering”, McGuill Network Communications Services, September 7, 2007&lt;br /&gt;
http://www.mcgill.ca/ncs/products/security/threatsdangers/socialeng/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-12-03T23:34:37Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social Engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricking the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg|thumb|300px|right|&lt;br /&gt;
'''Kevin David Mitnick'''&lt;br /&gt;
&amp;lt;br&amp;gt;''Born October 6, 1963''&amp;lt;br&amp;gt;&lt;br /&gt;
Convicted of computer related crimes using social engineering.]]&lt;br /&gt;
&lt;br /&gt;
==What is Social Engineering?==&lt;br /&gt;
Social Engineering is the manipulation of people to further a person's motives using various methods. “The art and science of getting people to comply to your wishes” - [http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt Bernz]. This &amp;quot;compliance&amp;quot; is generally associated with the acquisition of electronic information. However, Social Engineering can also apply to a border definition which encompasses any kind personal manipulation in an attempt to gain something dishonestly. The manipulation is performed by &amp;quot;tricking&amp;quot; the mark (the unsuspecting victim) into a false sense of trust which is them abused to obtain the sought objective.&lt;br /&gt;
&lt;br /&gt;
==Aspects of Social Engineering==&lt;br /&gt;
A social engineering attack can be thought of as process with two key components; human and the system. The human component requires the social engineer to gain the trust of whom ever has access to the system.&lt;br /&gt;
===Human===&lt;br /&gt;
The human element in social engineering attacks is the method in which the objectives are carried out. Human beings are generally the weakest part of any security system because they can be tricked or corrupted. By attacking the people who have access to what a social engineer wants, the objectives of a social engineer can be reach more easily. People like system administrator, maintenance people, or employees can all potential jeopardized a secure system by giving out information that to someone who they consider to be trustworthy.&lt;br /&gt;
&lt;br /&gt;
===System===&lt;br /&gt;
The system refers to any potentially closed system which contains something a social engineer wants. A social engineering attack is only successful if the social engineer has knowledge about the inner workings of the system. Knowledge like protocols, terminology, names of people, important dates, etc., provide a social engineer ammunition to construct a persona which is then used to manipulate the people who have access to the system.&lt;br /&gt;
&lt;br /&gt;
==Methods of Social Engineering==&lt;br /&gt;
===By Phone===&lt;br /&gt;
This is the most common method of social engineering attacks. An attacker will call the mark, using a persona, and gain the mark's trust. Then the attacker will request information which then might be used to perform another social engineering attack. Help desks are prone to this kind of attack since they are trained to be friendly and give out information. They are also minimally educated in areas of security. An example of this type of attack might be the following scenario. An attacker calls a help desk and asks to speak to the supervisor. When the supervisor answer, the attacker explains that he is the system administrator and that there is a problem with the system. Then the attacker asks the supervisor to login to the system. The attacker then states that he is unable to see the login on his end and that this is a problem. Then the attacker asks the supervisor to give him the login information so that he can try. Once the supervisor has done this, the attacker tells the supervisor that everything seems to be ok and the supervisor is none the wiser.&lt;br /&gt;
&lt;br /&gt;
Another example of a phone attack is when the attacker calls a person in the middle of the night posing as someone from a bank. The attacker asks if they have just made a suspicious purchase (a very large amount or in another country). When the mark says no, the attacker asks for the credit card number for verification, then says the charges will be removed from the account.&lt;br /&gt;
&lt;br /&gt;
Social Engineering can take on many forms on the phone and can have many different objectives. The most notable social engineer in 1990's was Kevin Mitnick. He was arrest in 1995 and convicted of illegally gaining access to computer networks and stealing intellectual property. Mitnick's methods relied on the use of phone calls to the companies which he attacked. Mitnick served 5 years in prison and now runs a security consulting company which gives security advice to companies.&lt;br /&gt;
&lt;br /&gt;
===Online===&lt;br /&gt;
Online social engineering attacks are similar to phone attacks, in that they pose as a legitimate entity which the mark will trust. Many online attacks are spread through phishing. This type of social engineering assumes that most users use the same login and password for many internet sites, so by getting the user to sign up for a new site, they will be giving up their login information. These sites might be in the form of new sites which the use might be interested in, or they might pose as sites which the user already has an account for and ask the user to try and login again. The latter example can take for in the following. The mark receives an email informing him that he needs to update his PayPal password by clicking the provided link and logging in. Failure to do so will result in the termination of the account after a specified period. Once the mark clicks on the link, and enters his login information, a message is displayed which confirms the change. The link the mark has clicked on however, was a link to the attacker's site which simply records the login information.&lt;br /&gt;
&lt;br /&gt;
===Persuasion===&lt;br /&gt;
Persuasion is the core of social engineering attacks. This method is used in all social engineering attacks and relies on the attacker's grasp of the human psyche. The attacker's ability to persuade is determined by two things. Firstly the attacker must be able to gain trust. This can be accomplished using various techniques. The most common of which are creating a persona by impersonation or imitation. An attacker can pose as either an existing employee or pose as a generic employee. For example, an attacker calling an office can say that his name is Bob Anderson with employee number 123456 (where Bob Anderson is an existing employ who works at a different branch with that employee number), or he can say he's Dale Johnson, a new system administrator brought in to fix the recent system failures (where Dale Johnson is a made up name). The use of these persona provides the social engineer with a the appearance of authenticity which is used to build the mark's trust. Once this authenticity is established, the attacker must then complete the persuasion by implementing the second step, manipulation. This is accomplished by providing a convincing reason to the mark to give the attacker what he wants. This can be a colorful background story, a tempting offer, or even guiling the mark into compliance. The point is to make the mark believe that the persona that is being used is legitimate and that the requests being made are genuine. If a social engineer can master these two elements then he will be very persuasive.&lt;br /&gt;
&lt;br /&gt;
===Dumpster Diving===&lt;br /&gt;
Dumpster Diving, also known as trashing, is the &amp;quot;snooping&amp;quot; through trash to collect information. It is a very effective method of obtaining many different types of information. The premis is that many companies and individuals don't apply a high level of security in their garbage because they feel as though what they throw out is no longer relevant. However, much of the trash being discarded can collectively provide the social engineer with the tools needed to create personas and learn about the inner workings of the system. Trash like old user and password lists, company directories, event calenders, printouts of source code and even obsolete hardware can contain information that is relevant to the current state of the system. In particular the social engineer can learn about the companies protocals, termonology and many emplyee's names and other personal information.&lt;br /&gt;
&lt;br /&gt;
===Reverse Social Engineering===&lt;br /&gt;
*Pretend to be someone in a position of authority&lt;br /&gt;
**employees will ask him for information&lt;br /&gt;
*Most difficult method to pull off&lt;br /&gt;
**requires lots of preparation&lt;br /&gt;
**but can yield the most successful results&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Protection==&lt;br /&gt;
*Security policies dealing with both physical and psychological elements&lt;br /&gt;
**Standard physical security mechanisms&lt;br /&gt;
***networks protection&lt;br /&gt;
***good password protection&lt;br /&gt;
***secure disposal of trash&lt;br /&gt;
***standard security measures we’ve discussed in class&lt;br /&gt;
**Education and training of employees&lt;br /&gt;
***Making employees aware of Social Engineering&lt;br /&gt;
***better recognize an attack&lt;br /&gt;
***Authentication&lt;br /&gt;
****Making sure the person they are speaking with is that person&lt;br /&gt;
**Availability of ANY information&lt;br /&gt;
***only give out information that’s need-to-know&lt;br /&gt;
***Don’t give out confidential information&lt;br /&gt;
&lt;br /&gt;
==Conclusion==&lt;br /&gt;
*Social Engineering attacks are very difficult to protect against. &lt;br /&gt;
*A system’s security is only as strong as the people who maintain it. &lt;br /&gt;
*With proper training, a social Engineering attack can be made extremely difficult. &lt;br /&gt;
*However, it can never been fully projected against. &lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
Bernz: “The complete Social Engineering FAQ!”&lt;br /&gt;
http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt&lt;br /&gt;
&lt;br /&gt;
Sarah Granger : “Social Engineering Fundamentals”, SecurityFocus, December 18, 2001&lt;br /&gt;
http://www.securityfocus.com/infocus/1527&lt;br /&gt;
&lt;br /&gt;
“Social engineering (security)”, Wikipedia, November 19, 2007&lt;br /&gt;
http://en.wikipedia.org/wiki/Social_engineering_(computer_security)&lt;br /&gt;
&lt;br /&gt;
“social engineering”, SearchSecurity, October 10, 2006&lt;br /&gt;
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci531120,00.html&lt;br /&gt;
&lt;br /&gt;
Mitnick, Kevin: “My first RSA Conference,” SecurityFocus, April 30, 2001&lt;br /&gt;
http://www.securityfocus.com/news/199&lt;br /&gt;
&lt;br /&gt;
Leslie Hawthorn: “Social Engineering”, O’Reilly Network, March 10, 2006&lt;br /&gt;
http://www.oreilly.com/pub/a/womenintech/2007/09/04/social-engineering.html&lt;br /&gt;
&lt;br /&gt;
“Social Engineering”, McGuill Network Communications Services, September 7, 2007&lt;br /&gt;
http://www.mcgill.ca/ncs/products/security/threatsdangers/socialeng/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-12-03T09:16:29Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social Engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricking the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg|thumb|300px|right|&lt;br /&gt;
'''Kevin David Mitnick'''&lt;br /&gt;
&amp;lt;br&amp;gt;''Born October 6, 1963''&amp;lt;br&amp;gt;&lt;br /&gt;
Convicted of computer related crimes using social engineering.]]&lt;br /&gt;
&lt;br /&gt;
==What is Social Engineering?==&lt;br /&gt;
Social Engineering is the manipulation of people to further a person's motives using various methods. “The art and science of getting people to comply to your wishes” - [http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt Bernz]. This &amp;quot;compliance&amp;quot; is generally associated with the acquisition of electronic information. However, Social Engineering can also apply to a border definition which encompasses any kind personal manipulation in an attempt to gain something dishonestly. The manipulation is performed by &amp;quot;tricking&amp;quot; the mark (the unsuspecting victim) into a false sense of trust which is them abused to obtain the sought objective.&lt;br /&gt;
&lt;br /&gt;
==Aspects of Social Engineering==&lt;br /&gt;
A social engineering attack can be thought of as process with two key components; human and the system. The human component requires the social engineer to gain the trust of whom ever has access to the system.&lt;br /&gt;
===Human===&lt;br /&gt;
The human element in social engineering attacks is the method in which the objectives are carried out. Human beings are generally the weakest part of any security system because they can be tricked or corrupted. By attacking the people who have access to what a social engineer wants, the objectives of a social engineer can be reach more easily. People like system administrator, maintenance people, or employees can all potential jeopardized a secure system by giving out information that to someone who they consider to be trustworthy.&lt;br /&gt;
&lt;br /&gt;
===System===&lt;br /&gt;
The system refers to any potentially closed system which contains something a social engineer wants. A social engineering attack is only successful if the social engineer has knowledge about the inner workings of the system. Knowledge like protocols, terminology, names of people, important dates, etc., provide a social engineer ammunition to construct a persona which is then used to manipulate the people who have access to the system.&lt;br /&gt;
&lt;br /&gt;
==Methods of Social Engineering==&lt;br /&gt;
===By Phone===&lt;br /&gt;
This is the most common method of social engineering attacks. An attacker will call the mark, using a persona, and gain the mark's trust. Then the attacker will request information which then might be used to perform another social engineering attack.&lt;br /&gt;
*Most common method&lt;br /&gt;
*Call a company and imitate someone in a position of authority or relevance.&lt;br /&gt;
**Supervisor, manager, system admin.&lt;br /&gt;
***pretend they can’t log into the system&lt;br /&gt;
***or that they need your login to troubleshoot&lt;br /&gt;
*Help desks are most prone to this&lt;br /&gt;
**used to helping people&lt;br /&gt;
**trained to give out information and be friendly&lt;br /&gt;
**want to move on to next call&lt;br /&gt;
**minimally educated in security area&lt;br /&gt;
&lt;br /&gt;
===Online===&lt;br /&gt;
*Many people use same password and login for internet sites&lt;br /&gt;
**Using methods like Phishing can allow the Social Engineer to obtain lots of information about a person&lt;br /&gt;
&lt;br /&gt;
===Persuasion===&lt;br /&gt;
*The true strength of a Social Engineer&lt;br /&gt;
*Gaining trust by&lt;br /&gt;
**impersonation (identiy theft)&lt;br /&gt;
**imitation (made up identity)&lt;br /&gt;
*Uses psychological methods&lt;br /&gt;
**Guilt&lt;br /&gt;
**Tempting offers&lt;br /&gt;
&lt;br /&gt;
===Dumpster Diving===&lt;br /&gt;
*also known as trashing&lt;br /&gt;
*looking through garbage for information&lt;br /&gt;
*Many companies don’t implement any method of security for their garbage&lt;br /&gt;
**user and password lists&lt;br /&gt;
**Company directories&lt;br /&gt;
**Event calendars&lt;br /&gt;
**obsolete computers&lt;br /&gt;
**printouts of source codes&lt;br /&gt;
**The more a Social Engineer knows about:&lt;br /&gt;
***a company&lt;br /&gt;
***their protocols&lt;br /&gt;
***terminology&lt;br /&gt;
***the more likely he’ll be able to succeed.&lt;br /&gt;
&lt;br /&gt;
===Reverse Social Engineering===&lt;br /&gt;
*Pretend to be someone in a position of authority&lt;br /&gt;
**employees will ask him for information&lt;br /&gt;
*Most difficult method to pull off&lt;br /&gt;
**requires lots of preparation&lt;br /&gt;
**but can yield the most successful results&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Protection==&lt;br /&gt;
*Security policies dealing with both physical and psychological elements&lt;br /&gt;
**Standard physical security mechanisms&lt;br /&gt;
***networks protection&lt;br /&gt;
***good password protection&lt;br /&gt;
***secure disposal of trash&lt;br /&gt;
***standard security measures we’ve discussed in class&lt;br /&gt;
**Education and training of employees&lt;br /&gt;
***Making employees aware of Social Engineering&lt;br /&gt;
***better recognize an attack&lt;br /&gt;
***Authentication&lt;br /&gt;
****Making sure the person they are speaking with is that person&lt;br /&gt;
**Availability of ANY information&lt;br /&gt;
***only give out information that’s need-to-know&lt;br /&gt;
***Don’t give out confidential information&lt;br /&gt;
&lt;br /&gt;
==Conclusion==&lt;br /&gt;
*Social Engineering attacks are very difficult to protect against. &lt;br /&gt;
*A system’s security is only as strong as the people who maintain it. &lt;br /&gt;
*With proper training, a social Engineering attack can be made extremely difficult. &lt;br /&gt;
*However, it can never been fully projected against. &lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
Bernz: “The complete Social Engineering FAQ!”&lt;br /&gt;
http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt&lt;br /&gt;
&lt;br /&gt;
Sarah Granger : “Social Engineering Fundamentals”, SecurityFocus, December 18, 2001&lt;br /&gt;
http://www.securityfocus.com/infocus/1527&lt;br /&gt;
&lt;br /&gt;
“Social engineering (security)”, Wikipedia, November 19, 2007&lt;br /&gt;
http://en.wikipedia.org/wiki/Social_engineering_(computer_security)&lt;br /&gt;
&lt;br /&gt;
“social engineering”, SearchSecurity, October 10, 2006&lt;br /&gt;
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci531120,00.html&lt;br /&gt;
&lt;br /&gt;
Mitnick, Kevin: “My first RSA Conference,” SecurityFocus, April 30, 2001&lt;br /&gt;
http://www.securityfocus.com/news/199&lt;br /&gt;
&lt;br /&gt;
Leslie Hawthorn: “Social Engineering”, O’Reilly Network, March 10, 2006&lt;br /&gt;
http://www.oreilly.com/pub/a/womenintech/2007/09/04/social-engineering.html&lt;br /&gt;
&lt;br /&gt;
“Social Engineering”, McGuill Network Communications Services, September 7, 2007&lt;br /&gt;
http://www.mcgill.ca/ncs/products/security/threatsdangers/socialeng/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-12-03T07:58:36Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social Engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricking the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg|thumb|300px|right|&lt;br /&gt;
'''Kevin David Mitnick'''&lt;br /&gt;
&amp;lt;br&amp;gt;''Born October 6, 1963''&amp;lt;br&amp;gt;&lt;br /&gt;
Convicted of computer related crimes using social engineering.]]&lt;br /&gt;
&lt;br /&gt;
==What is Social Engineering?==&lt;br /&gt;
Social Engineering is?&lt;br /&gt;
*“the art and science of getting people to comply to your wishes” - Bernz. &lt;br /&gt;
*Attacks human side of information security&lt;br /&gt;
*not mind control or coercion.&lt;br /&gt;
*but rather “ticking” people &lt;br /&gt;
**do what you want them to do&lt;br /&gt;
**give you information that you might not have access to&lt;br /&gt;
&lt;br /&gt;
==Aspects of Social Engineering==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Human===&lt;br /&gt;
*Humans are  generally the weakest part of any security system&lt;br /&gt;
**System admins, maintenance people, employees&lt;br /&gt;
***all have access to the system&lt;br /&gt;
***any one of them can jeopardize security if they are not careful&lt;br /&gt;
***knowingly or unknowingly&lt;br /&gt;
*All Social Engineering attacks have something in common&lt;br /&gt;
**Take advantage of a human being’s trust&lt;br /&gt;
*Need 2 things for a Social Engineering attack&lt;br /&gt;
**A knowledge of the system being attacked&lt;br /&gt;
***Lots of background work&lt;br /&gt;
***Terminology&lt;br /&gt;
***Names of people and places&lt;br /&gt;
***Protocols being used&lt;br /&gt;
***The ability to gain people’s trust&lt;br /&gt;
&lt;br /&gt;
===Hardware===&lt;br /&gt;
&lt;br /&gt;
==Notable Examples==&lt;br /&gt;
&lt;br /&gt;
==Methods of Social Engineering==&lt;br /&gt;
===By Phone===&lt;br /&gt;
*Most common method&lt;br /&gt;
*Call a company and imitate someone in a position of authority or relevance.&lt;br /&gt;
**Supervisor, manager, system admin.&lt;br /&gt;
***pretend they can’t log into the system&lt;br /&gt;
***or that they need your login to troubleshoot&lt;br /&gt;
*Help desks are most prone to this&lt;br /&gt;
**used to helping people&lt;br /&gt;
**trained to give out information and be friendly&lt;br /&gt;
**want to move on to next call&lt;br /&gt;
**minimally educated in security area&lt;br /&gt;
&lt;br /&gt;
===Online===&lt;br /&gt;
*Many people use same password and login for internet sites&lt;br /&gt;
**Using methods like Phishing can allow the Social Engineer to obtain lots of information about a person&lt;br /&gt;
&lt;br /&gt;
===Persuasion===&lt;br /&gt;
*The true strength of a Social Engineer&lt;br /&gt;
*Gaining trust by&lt;br /&gt;
**impersonation (identiy theft)&lt;br /&gt;
**imitation (made up identity)&lt;br /&gt;
*Uses psychological methods&lt;br /&gt;
**Guilt&lt;br /&gt;
**Tempting offers&lt;br /&gt;
&lt;br /&gt;
===Dumpster Diving===&lt;br /&gt;
*also known as trashing&lt;br /&gt;
*looking through garbage for information&lt;br /&gt;
*Many companies don’t implement any method of security for their garbage&lt;br /&gt;
**user and password lists&lt;br /&gt;
**Company directories&lt;br /&gt;
**Event calendars&lt;br /&gt;
**obsolete computers&lt;br /&gt;
**printouts of source codes&lt;br /&gt;
**The more a Social Engineer knows about:&lt;br /&gt;
***a company&lt;br /&gt;
***their protocols&lt;br /&gt;
***terminology&lt;br /&gt;
***the more likely he’ll be able to succeed.&lt;br /&gt;
&lt;br /&gt;
===Reverse Social Engineering===&lt;br /&gt;
*Pretend to be someone in a position of authority&lt;br /&gt;
**employees will ask him for information&lt;br /&gt;
*Most difficult method to pull off&lt;br /&gt;
**requires lots of preparation&lt;br /&gt;
**but can yield the most successful results&lt;br /&gt;
&lt;br /&gt;
==Protection==&lt;br /&gt;
*Security policies dealing with both physical and psychological elements&lt;br /&gt;
**Standard physical security mechanisms&lt;br /&gt;
***networks protection&lt;br /&gt;
***good password protection&lt;br /&gt;
***secure disposal of trash&lt;br /&gt;
***standard security measures we’ve discussed in class&lt;br /&gt;
**Education and training of employees&lt;br /&gt;
***Making employees aware of Social Engineering&lt;br /&gt;
***better recognize an attack&lt;br /&gt;
***Authentication&lt;br /&gt;
****Making sure the person they are speaking with is that person&lt;br /&gt;
**Availability of ANY information&lt;br /&gt;
***only give out information that’s need-to-know&lt;br /&gt;
***Don’t give out confidential information&lt;br /&gt;
&lt;br /&gt;
==Conclusion==&lt;br /&gt;
*Social Engineering attacks are very difficult to protect against. &lt;br /&gt;
*A system’s security is only as strong as the people who maintain it. &lt;br /&gt;
*With proper training, a social Engineering attack can be made extremely difficult. &lt;br /&gt;
*However, it can never been fully projected against. &lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
Bernz: “The complete Social Engineering FAQ!”&lt;br /&gt;
http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt&lt;br /&gt;
&lt;br /&gt;
Sarah Granger : “Social Engineering Fundamentals”, SecurityFocus, December 18, 2001&lt;br /&gt;
http://www.securityfocus.com/infocus/1527&lt;br /&gt;
&lt;br /&gt;
“Social engineering (security)”, Wikipedia, November 19, 2007&lt;br /&gt;
http://en.wikipedia.org/wiki/Social_engineering_(computer_security)&lt;br /&gt;
&lt;br /&gt;
“social engineering”, SearchSecurity, October 10, 2006&lt;br /&gt;
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci531120,00.html&lt;br /&gt;
&lt;br /&gt;
Mitnick, Kevin: “My first RSA Conference,” SecurityFocus, April 30, 2001&lt;br /&gt;
http://www.securityfocus.com/news/199&lt;br /&gt;
&lt;br /&gt;
Leslie Hawthorn: “Social Engineering”, O’Reilly Network, March 10, 2006&lt;br /&gt;
http://www.oreilly.com/pub/a/womenintech/2007/09/04/social-engineering.html&lt;br /&gt;
&lt;br /&gt;
“Social Engineering”, McGuill Network Communications Services, September 7, 2007&lt;br /&gt;
http://www.mcgill.ca/ncs/products/security/threatsdangers/socialeng/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-11-30T23:47:41Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricking the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
 {| __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg|thumb|300px|right|&lt;br /&gt;
'''Kevin David Mitnick'''&lt;br /&gt;
&amp;lt;br&amp;gt;''Born October 6, 1963''&amp;lt;br&amp;gt;&lt;br /&gt;
Convicted of computer related crimes using social engineering.]]&lt;br /&gt;
&lt;br /&gt;
==What is Social Engineering?==&lt;br /&gt;
Social Engineering is?&lt;br /&gt;
*“the art and science of getting people to comply to your wishes” - Bernz. &lt;br /&gt;
*Attacks human side of information security&lt;br /&gt;
*not mind control or coercion.&lt;br /&gt;
*but rather “ticking” people &lt;br /&gt;
**do what you want them to do&lt;br /&gt;
**give you information that you might not have access to&lt;br /&gt;
&lt;br /&gt;
==Aspects of Social Engineering==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Human===&lt;br /&gt;
*Humans are  generally the weakest part of any security system&lt;br /&gt;
**System admins, maintenance people, employees&lt;br /&gt;
***all have access to the system&lt;br /&gt;
***any one of them can jeopardize security if they are not careful&lt;br /&gt;
***knowingly or unknowingly&lt;br /&gt;
*All Social Engineering attacks have something in common&lt;br /&gt;
**Take advantage of a human being’s trust&lt;br /&gt;
*Need 2 things for a Social Engineering attack&lt;br /&gt;
**A knowledge of the system being attacked&lt;br /&gt;
***Lots of background work&lt;br /&gt;
***Terminology&lt;br /&gt;
***Names of people and places&lt;br /&gt;
***Protocols being used&lt;br /&gt;
***The ability to gain people’s trust&lt;br /&gt;
&lt;br /&gt;
===Hardware===&lt;br /&gt;
&lt;br /&gt;
==Notable Examples==&lt;br /&gt;
&lt;br /&gt;
==Methods of Social Engineering==&lt;br /&gt;
===By Phone===&lt;br /&gt;
*Most common method&lt;br /&gt;
*Call a company and imitate someone in a position of authority or relevance.&lt;br /&gt;
**Supervisor, manager, system admin.&lt;br /&gt;
***pretend they can’t log into the system&lt;br /&gt;
***or that they need your login to troubleshoot&lt;br /&gt;
*Help desks are most prone to this&lt;br /&gt;
**used to helping people&lt;br /&gt;
**trained to give out information and be friendly&lt;br /&gt;
**want to move on to next call&lt;br /&gt;
**minimally educated in security area&lt;br /&gt;
&lt;br /&gt;
===Online===&lt;br /&gt;
*Many people use same password and login for internet sites&lt;br /&gt;
**Using methods like Phishing can allow the Social Engineer to obtain lots of information about a person&lt;br /&gt;
&lt;br /&gt;
===Persuasion===&lt;br /&gt;
*The true strength of a Social Engineer&lt;br /&gt;
*Gaining trust by&lt;br /&gt;
**impersonation (identiy theft)&lt;br /&gt;
**imitation (made up identity)&lt;br /&gt;
*Uses psychological methods&lt;br /&gt;
**Guilt&lt;br /&gt;
**Tempting offers&lt;br /&gt;
&lt;br /&gt;
===Dumpster Diving===&lt;br /&gt;
*also known as trashing&lt;br /&gt;
*looking through garbage for information&lt;br /&gt;
*Many companies don’t implement any method of security for their garbage&lt;br /&gt;
**user and password lists&lt;br /&gt;
**Company directories&lt;br /&gt;
**Event calendars&lt;br /&gt;
**obsolete computers&lt;br /&gt;
**printouts of source codes&lt;br /&gt;
**The more a Social Engineer knows about:&lt;br /&gt;
***a company&lt;br /&gt;
***their protocols&lt;br /&gt;
***terminology&lt;br /&gt;
***the more likely he’ll be able to succeed.&lt;br /&gt;
&lt;br /&gt;
===Reverse Social Engineering===&lt;br /&gt;
*Pretend to be someone in a position of authority&lt;br /&gt;
**employees will ask him for information&lt;br /&gt;
*Most difficult method to pull off&lt;br /&gt;
**requires lots of preparation&lt;br /&gt;
**but can yield the most successful results&lt;br /&gt;
&lt;br /&gt;
==Protection==&lt;br /&gt;
*Security policies dealing with both physical and psychological elements&lt;br /&gt;
**Standard physical security mechanisms&lt;br /&gt;
***networks protection&lt;br /&gt;
***good password protection&lt;br /&gt;
***secure disposal of trash&lt;br /&gt;
***standard security measures we’ve discussed in class&lt;br /&gt;
**Education and training of employees&lt;br /&gt;
***Making employees aware of Social Engineering&lt;br /&gt;
***better recognize an attack&lt;br /&gt;
***Authentication&lt;br /&gt;
****Making sure the person they are speaking with is that person&lt;br /&gt;
**Availability of ANY information&lt;br /&gt;
***only give out information that’s need-to-know&lt;br /&gt;
***Don’t give out confidential information&lt;br /&gt;
&lt;br /&gt;
==Conclusion==&lt;br /&gt;
*Social Engineering attacks are very difficult to protect against. &lt;br /&gt;
*A system’s security is only as strong as the people who maintain it. &lt;br /&gt;
*With proper training, a social Engineering attack can be made extremely difficult. &lt;br /&gt;
*However, it can never been fully projected against. &lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
Bernz: “The complete Social Engineering FAQ!”&lt;br /&gt;
http://www.morehouse.org/hin/blckcrwl/hack/soceng.txt&lt;br /&gt;
&lt;br /&gt;
Sarah Granger : “Social Engineering Fundamentals”, SecurityFocus, December 18, 2001&lt;br /&gt;
http://www.securityfocus.com/infocus/1527&lt;br /&gt;
&lt;br /&gt;
“Social engineering (security)”, Wikipedia, November 19, 2007&lt;br /&gt;
http://en.wikipedia.org/wiki/Social_engineering_(computer_security)&lt;br /&gt;
&lt;br /&gt;
“social engineering”, SearchSecurity, October 10, 2006&lt;br /&gt;
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci531120,00.html&lt;br /&gt;
&lt;br /&gt;
Mitnick, Kevin: “My first RSA Conference,” SecurityFocus, April 30, 2001&lt;br /&gt;
http://www.securityfocus.com/news/199&lt;br /&gt;
&lt;br /&gt;
Leslie Hawthorn: “Social Engineering”, O’Reilly Network, March 10, 2006&lt;br /&gt;
http://www.oreilly.com/pub/a/womenintech/2007/09/04/social-engineering.html&lt;br /&gt;
&lt;br /&gt;
“Social Engineering”, McGuill Network Communications Services, September 7, 2007&lt;br /&gt;
http://www.mcgill.ca/ncs/products/security/threatsdangers/socialeng/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-11-30T23:16:40Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricker the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Social engineering techniques and terms==&lt;br /&gt;
All social engineering techniques are based on specific attributes of human decision-making known as [[List of cognitive biases|cognitive biases]].&amp;lt;ref&amp;gt;CSEPS Course Workbook, unit 3&amp;lt;/ref&amp;gt; These biases, sometimes called &amp;quot;bugs in the human hardware,&amp;quot; are exploited in various combinations to create attack techniques, some of which are listed here:&lt;br /&gt;
&lt;br /&gt;
In computer security, social engineering is a term that describes a non-technical kind of intrusion that relies heavily on human interaction and often involves tricking other people to break normal security procedures. A social engineer runs what used to be called a &amp;quot;con game&amp;quot;. For example, a person using social engineering to break into a computer network would try to gain the confidence of someone who is authorized to access the network in order to get them to reveal information that compromises the network's security. They might call the authorized employee with some kind of urgent problem; social engineers often rely on the natural helpfulness of people as well as on their weaknesses. Appeal to vanity, appeal to authority, and old-fashioned eavesdropping are typical social engineering techniques.&lt;br /&gt;
&lt;br /&gt;
Another aspect of social engineering relies on people's inability to keep up with a culture that relies heavily on information technology. Social engineers rely on the fact that people are not aware of the value of the information they possess and are careless about protecting it. Frequently, social engineers will search dumpsters for valuable information, memorize access codes by looking over someone's shoulder (shoulder surfing), or take advantage of people's natural inclination to choose passwords that are meaningful to them but can be easily guessed. Security experts propose that as our culture becomes more dependent on information, social engineering will remain the greatest threat to any security system. Prevention includes educating people about the value of information, training them to protect it, and increasing people's awareness of how social engineers operate.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-11-30T23:09:58Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricker the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Social engineering techniques and terms==&lt;br /&gt;
All social engineering techniques are based on specific attributes of human decision-making known as [[List of cognitive biases|cognitive biases]].&amp;lt;ref&amp;gt;CSEPS Course Workbook, unit 3&amp;lt;/ref&amp;gt; These biases, sometimes called &amp;quot;bugs in the human hardware,&amp;quot; are exploited in various combinations to create attack techniques, some of which are listed here:&lt;br /&gt;
&lt;br /&gt;
In computer security, social engineering is a term that describes a non-technical kind of intrusion that relies heavily on human interaction and often involves tricking other people to break normal security procedures. A social engineer runs what used to be called a &amp;quot;con game&amp;quot;. For example, a person using social engineering to break into a computer network would try to gain the confidence of someone who is authorized to access the network in order to get them to reveal information that compromises the network's security. They might call the authorized employee with some kind of urgent problem; social engineers often rely on the natural helpfulness of people as well as on their weaknesses. Appeal to vanity, appeal to authority, and old-fashioned eavesdropping are typical social engineering techniques.&lt;br /&gt;
&lt;br /&gt;
Another aspect of social engineering relies on people's inability to keep up with a culture that relies heavily on information technology. Social engineers rely on the fact that people are not aware of the value of the information they possess and are careless about protecting it. Frequently, social engineers will search dumpsters for valuable information, memorize access codes by looking over someone's shoulder (shoulder surfing), or take advantage of people's natural inclination to choose passwords that are meaningful to them but can be easily guessed. Security experts propose that as our culture becomes more dependent on information, social engineering will remain the greatest threat to any security system. Prevention includes educating people about the value of information, training them to protect it, and increasing people's awareness of how social engineers operate.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-11-30T22:35:33Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricker the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
[[Image:Mitnick.jpg]]&lt;br /&gt;
&lt;br /&gt;
==Social engineering techniques and terms==&lt;br /&gt;
All social engineering techniques are based on specific attributes of human decision-making known as [[List of cognitive biases|cognitive biases]].&amp;lt;ref&amp;gt;CSEPS Course Workbook, unit 3&amp;lt;/ref&amp;gt; These biases, sometimes called &amp;quot;bugs in the human hardware,&amp;quot; are exploited in various combinations to create attack techniques, some of which are listed here:&lt;br /&gt;
&lt;br /&gt;
In computer security, social engineering is a term that describes a non-technical kind of intrusion that relies heavily on human interaction and often involves tricking other people to break normal security procedures. A social engineer runs what used to be called a &amp;quot;con game&amp;quot;. For example, a person using social engineering to break into a computer network would try to gain the confidence of someone who is authorized to access the network in order to get them to reveal information that compromises the network's security. They might call the authorized employee with some kind of urgent problem; social engineers often rely on the natural helpfulness of people as well as on their weaknesses. Appeal to vanity, appeal to authority, and old-fashioned eavesdropping are typical social engineering techniques.&lt;br /&gt;
&lt;br /&gt;
Another aspect of social engineering relies on people's inability to keep up with a culture that relies heavily on information technology. Social engineers rely on the fact that people are not aware of the value of the information they possess and are careless about protecting it. Frequently, social engineers will search dumpsters for valuable information, memorize access codes by looking over someone's shoulder (shoulder surfing), or take advantage of people's natural inclination to choose passwords that are meaningful to them but can be easily guessed. Security experts propose that as our culture becomes more dependent on information, social engineering will remain the greatest threat to any security system. Prevention includes educating people about the value of information, training them to protect it, and increasing people's awareness of how social engineers operate.&lt;br /&gt;
[[Image:https://www.aiga.org/Resources/SymbolSigns/gif_large/01_telephone_inv.gif]]&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/File:Mitnick.jpg</id>
		<title>File:Mitnick.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/File:Mitnick.jpg"/>
				<updated>2007-11-30T22:30:32Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Kevin David Mitnick (born October 6, 1963) is one of the most notable computer hackers of the 1990's. He was convicted of computer related crimes in the late 1990's and served five years in prison (four of which were pre-trial). Mitnick was released on January 21, 2000 and now runs Mitnick Security Consulting, which is a computer security consulting company.&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/File:Mitnick.jpg</id>
		<title>File:Mitnick.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/File:Mitnick.jpg"/>
				<updated>2007-11-30T22:29:51Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Kevin David Mitnick (born October 6, 1963) is one of the most notable computer hackers of the 1990's. He was convicted of computer related crimes in the 1990's and served five years in prison (four of which were pre-trial). Mitnick was released on January 21, 2000 and now runs Mitnick Security Consulting, which is a computer security consulting company.&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/File:Mitnick.jpg</id>
		<title>File:Mitnick.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/File:Mitnick.jpg"/>
				<updated>2007-11-30T22:18:37Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;Kevin Mitnick, one of the most notable social engineers&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Kevin Mitnick, one of the most notable social engineers&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	<entry>
		<id>http://wiki.cas.mcmaster.ca/index.php/Social_engineering</id>
		<title>Social engineering</title>
		<link rel="alternate" type="text/html" href="http://wiki.cas.mcmaster.ca/index.php/Social_engineering"/>
				<updated>2007-11-07T12:36:31Z</updated>
		
		<summary type="html">&lt;p&gt;Shahinrs:&amp;#32;New page: '''Social engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is ...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Social engineering''' is a term used in computer science that referees to a non-technical type of security attack. This attack relies on the human element in any security system and is made vulnerable by exploiting a person's trust in the attacker to divulge sensitive or insensitive information. This is often accomplished by misleading or tricker the person getting attacked. In many cases, the attacked never know that they have been attacked.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Social engineering techniques and terms==&lt;br /&gt;
All social engineering techniques are based on specific attributes of human decision-making known as [[List of cognitive biases|cognitive biases]].&amp;lt;ref&amp;gt;CSEPS Course Workbook, unit 3&amp;lt;/ref&amp;gt; These biases, sometimes called &amp;quot;bugs in the human hardware,&amp;quot; are exploited in various combinations to create attack techniques, some of which are listed here:&lt;br /&gt;
&lt;br /&gt;
In computer security, social engineering is a term that describes a non-technical kind of intrusion that relies heavily on human interaction and often involves tricking other people to break normal security procedures. A social engineer runs what used to be called a &amp;quot;con game&amp;quot;. For example, a person using social engineering to break into a computer network would try to gain the confidence of someone who is authorized to access the network in order to get them to reveal information that compromises the network's security. They might call the authorized employee with some kind of urgent problem; social engineers often rely on the natural helpfulness of people as well as on their weaknesses. Appeal to vanity, appeal to authority, and old-fashioned eavesdropping are typical social engineering techniques.&lt;br /&gt;
&lt;br /&gt;
Another aspect of social engineering relies on people's inability to keep up with a culture that relies heavily on information technology. Social engineers rely on the fact that people are not aware of the value of the information they possess and are careless about protecting it. Frequently, social engineers will search dumpsters for valuable information, memorize access codes by looking over someone's shoulder (shoulder surfing), or take advantage of people's natural inclination to choose passwords that are meaningful to them but can be easily guessed. Security experts propose that as our culture becomes more dependent on information, social engineering will remain the greatest threat to any security system. Prevention includes educating people about the value of information, training them to protect it, and increasing people's awareness of how social engineers operate.&lt;br /&gt;
[[Image:https://www.aiga.org/Resources/SymbolSigns/gif_large/01_telephone_inv.gif]]&lt;br /&gt;
--[[User:Shahinrs|Shahinrs]] 07:36, 7 November 2007 (EST)&lt;/div&gt;</summary>
		<author><name>Shahinrs</name></author>	</entry>

	</feed>