<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Identity Theft Attacks</title>
	<atom:link href="http://www.gnucitizen.org/blog/identity-theft-attacks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gnucitizen.org/blog/identity-theft-attacks/</link>
	<description>Information Security Think Tank</description>
	<lastBuildDate>Sat, 02 Feb 2013 17:50:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Abhinav Vaid</title>
		<link>http://www.gnucitizen.org/blog/identity-theft-attacks/comment-page-1/#comment-126450</link>
		<dc:creator>Abhinav Vaid</dc:creator>
		<pubDate>Sat, 04 Apr 2009 18:55:52 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=2507#comment-126450</guid>
		<description>As a rule of thumb, I think one should should never ever disclose any personal information over the phone irrespective of what the caller says/claims. The only exception could be if you&#039;ve identified the no (caller id), &amp; hence know the caller.

Although giving ssn&#039;s or credit card numbers (especially the later one is like giving a blank cheque to a professional cheat.</description>
		<content:encoded><![CDATA[<p>As a rule of thumb, I think one should should never ever disclose any personal information over the phone irrespective of what the caller says/claims. The only exception could be if you&#8217;ve identified the no (caller id), &#038; hence know the caller.</p>
<p>Although giving ssn&#8217;s or credit card numbers (especially the later one is like giving a blank cheque to a professional cheat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pagvac</title>
		<link>http://www.gnucitizen.org/blog/identity-theft-attacks/comment-page-1/#comment-126071</link>
		<dc:creator>pagvac</dc:creator>
		<pubDate>Sun, 22 Feb 2009 16:41:28 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=2507#comment-126071</guid>
		<description>sometimes credit card DBs get compromised, but the  PANs are split across different DBs as a defense in depth mechanism. This is why in some carding forums you can only buy partial credit card #s. The reason why scammers buy them is because it allows them to perform targeted attacks where the victim feels the attacker is a legitimate entity because some info is previously known (even if that info is not complete). Think of customized phishing over email and phone.</description>
		<content:encoded><![CDATA[<p>sometimes credit card DBs get compromised, but the  PANs are split across different DBs as a defense in depth mechanism. This is why in some carding forums you can only buy partial credit card #s. The reason why scammers buy them is because it allows them to perform targeted attacks where the victim feels the attacker is a legitimate entity because some info is previously known (even if that info is not complete). Think of customized phishing over email and phone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hugh</title>
		<link>http://www.gnucitizen.org/blog/identity-theft-attacks/comment-page-1/#comment-125964</link>
		<dc:creator>Hugh</dc:creator>
		<pubDate>Sat, 14 Feb 2009 06:10:24 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=2507#comment-125964</guid>
		<description>I concur that problem is in the process, but perhaps the best defense is to avoid the temptation of giving personal information on the phone unless you can verify the ligitimacy of the person at the other end</description>
		<content:encoded><![CDATA[<p>I concur that problem is in the process, but perhaps the best defense is to avoid the temptation of giving personal information on the phone unless you can verify the ligitimacy of the person at the other end</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shoaib Yousuf</title>
		<link>http://www.gnucitizen.org/blog/identity-theft-attacks/comment-page-1/#comment-125915</link>
		<dc:creator>Shoaib Yousuf</dc:creator>
		<pubDate>Tue, 10 Feb 2009 22:47:22 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=2507#comment-125915</guid>
		<description>Recently i was investigating a case, in which scammer sent out a Paypal phishing email to a user, user was fooled and he gave out all his details except his credit card numbers. Scammer rang the user as he got all the details from the phishing email, pretending a call from Paypal. He mentioned, we sent out you an email but unfortunately you didn&#039;t provide a valid credit card number, user thought this is legitmate call and he gave his credit card details.

After one month, he noticed 3k fraudulent charges on this credit card plus he lost his identity.

Shoaib</description>
		<content:encoded><![CDATA[<p>Recently i was investigating a case, in which scammer sent out a Paypal phishing email to a user, user was fooled and he gave out all his details except his credit card numbers. Scammer rang the user as he got all the details from the phishing email, pretending a call from Paypal. He mentioned, we sent out you an email but unfortunately you didn&#8217;t provide a valid credit card number, user thought this is legitmate call and he gave his credit card details.</p>
<p>After one month, he noticed 3k fraudulent charges on this credit card plus he lost his identity.</p>
<p>Shoaib</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TroyC</title>
		<link>http://www.gnucitizen.org/blog/identity-theft-attacks/comment-page-1/#comment-125914</link>
		<dc:creator>TroyC</dc:creator>
		<pubDate>Tue, 10 Feb 2009 21:37:44 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=2507#comment-125914</guid>
		<description>Perhaps ask the caller to send a digitally signed email.  Another option could be to provide you with a piece of your information that noone else would know.  A simple right or wrong scenario.  The caller would ask is your first three SSNs are ###?  If they are not, hang up.  If they are, proceed.  Personally I like the digitally signed email better.</description>
		<content:encoded><![CDATA[<p>Perhaps ask the caller to send a digitally signed email.  Another option could be to provide you with a piece of your information that noone else would know.  A simple right or wrong scenario.  The caller would ask is your first three SSNs are ###?  If they are not, hang up.  If they are, proceed.  Personally I like the digitally signed email better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pdp</title>
		<link>http://www.gnucitizen.org/blog/identity-theft-attacks/comment-page-1/#comment-125913</link>
		<dc:creator>pdp</dc:creator>
		<pubDate>Tue, 10 Feb 2009 21:30:24 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=2507#comment-125913</guid>
		<description>absolutely!</description>
		<content:encoded><![CDATA[<p>absolutely!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kierznowski</title>
		<link>http://www.gnucitizen.org/blog/identity-theft-attacks/comment-page-1/#comment-125910</link>
		<dc:creator>David Kierznowski</dc:creator>
		<pubDate>Tue, 10 Feb 2009 17:24:24 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=2507#comment-125910</guid>
		<description>There is a currently a targetted scam in UK where the chaps phoning you already have your address and part of your bank details. 

Its so much easier to fall into this trap if the guys on the phone already know a fair bit about you before you even start the conversation.</description>
		<content:encoded><![CDATA[<p>There is a currently a targetted scam in UK where the chaps phoning you already have your address and part of your bank details. </p>
<p>Its so much easier to fall into this trap if the guys on the phone already know a fair bit about you before you even start the conversation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Identity Theft Attacks &#124; GNUCITIZEN &#124; identitythefthelp.info</title>
		<link>http://www.gnucitizen.org/blog/identity-theft-attacks/comment-page-1/#comment-125874</link>
		<dc:creator>Identity Theft Attacks &#124; GNUCITIZEN &#124; identitythefthelp.info</dc:creator>
		<pubDate>Sun, 08 Feb 2009 16:37:51 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=2507#comment-125874</guid>
		<description>[...] Identity Theft Attacks &#124; GNUCITIZENSHARETHIS.addEntry({ title: &quot;Identity Theft Attacks &#124; GNUCITIZEN&quot;, url: &quot;http://www.identitythefthelp.info/articles-concerning-identity-theft/identity-theft-attacks-gnucitizen/52&quot; }); [...]</description>
		<content:encoded><![CDATA[<p>[...] Identity Theft Attacks | GNUCITIZENSHARETHIS.addEntry({ title: &#8220;Identity Theft Attacks | GNUCITIZEN&#8221;, url: &#8220;http://www.identitythefthelp.info/articles-concerning-identity-theft/identity-theft-attacks-gnucitizen/52&#8243; }); [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Identity Theft Attacks &#124; GNUCITIZEN &#124; Identity Theft Facts and Figures</title>
		<link>http://www.gnucitizen.org/blog/identity-theft-attacks/comment-page-1/#comment-125866</link>
		<dc:creator>Identity Theft Attacks &#124; GNUCITIZEN &#124; Identity Theft Facts and Figures</dc:creator>
		<pubDate>Sat, 07 Feb 2009 19:28:30 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=2507#comment-125866</guid>
		<description>[...] Identity Theft Attacks &#124; GNUCITIZENSHARETHIS.addEntry({ title: &quot;Identity Theft Attacks &#124; GNUCITIZEN&quot;, url: &quot;http://www.identitytheftfactsandfigures.info/2009/02/07/identity-theft-attacks-gnucitizen/&quot; }); [...]</description>
		<content:encoded><![CDATA[<p>[...] Identity Theft Attacks | GNUCITIZENSHARETHIS.addEntry({ title: &#8220;Identity Theft Attacks | GNUCITIZEN&#8221;, url: &#8220;http://www.identitytheftfactsandfigures.info/2009/02/07/identity-theft-attacks-gnucitizen/&#8221; }); [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
