<?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"
	>
<channel>
	<title>Comments on: Vishing Incidents: A Preview of the Road Ahead</title>
	<atom:link href="http://www.riskbloggers.com/jimreavis/2008/03/vishing-incidents-a-preview-of-the-road-ahead/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.riskbloggers.com/jimreavis/2008/03/vishing-incidents-a-preview-of-the-road-ahead/</link>
	<description>Security Wisdom Ahead of the Curve</description>
	<pubDate>Mon, 12 May 2008 03:39:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Larry J. Hughes, Jr.</title>
		<link>http://www.riskbloggers.com/jimreavis/2008/03/vishing-incidents-a-preview-of-the-road-ahead/#comment-3958</link>
		<dc:creator>Larry J. Hughes, Jr.</dc:creator>
		<pubDate>Sun, 27 Apr 2008 05:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.riskbloggers.com/jimreavis/2008/03/vishing-incidents-a-preview-of-the-road-ahead/#comment-3958</guid>
		<description>I was the recipient of a vish in March.  It read:

  "Free VZW msg.  UR on track 2 incur charges for Minute, Data or Message usage.  Call 888-453-1922 NOW to discuss options!  2 stop txt msgs from VZW, reply X"

Knowing it wasn't Verizon I phoned the number anyway (with caller ID blocked) to see what would happen.  

  Visher:  Hello?

  Me:  Is this Verizon?  I got a text message about using too many minutes.

  Visher:  Uh, yeah.  What's your social security number?

  Me:  [click]

I phoned Verizon to report it, and the poor woman I spoke with didn't have a clue what to do about it.

I just tried the number again and got a recording that Verizon is closed and to try  again during business hours. Either Verizon has seized the number and is now using it for real (!), or Visher has pilfered their voice message and was out celebrating on somebody else's credit card.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->I was the recipient of a vish in March.  It read:</p>
<p>  &#8220;Free VZW msg.  UR on track 2 incur charges for Minute, Data or Message usage.  Call 888-453-1922 NOW to discuss options!  2 stop txt msgs from VZW, reply X&#8221;</p>
<p>Knowing it wasn&#8217;t Verizon I phoned the number anyway (with caller ID blocked) to see what would happen.  </p>
<p>  Visher:  Hello?</p>
<p>  Me:  Is this Verizon?  I got a text message about using too many minutes.</p>
<p>  Visher:  Uh, yeah.  What&#8217;s your social security number?</p>
<p>  Me:  [click]</p>
<p>I phoned Verizon to report it, and the poor woman I spoke with didn&#8217;t have a clue what to do about it.</p>
<p>I just tried the number again and got a recording that Verizon is closed and to try  again during business hours. Either Verizon has seized the number and is now using it for real (!), or Visher has pilfered their voice message and was out celebrating on somebody else&#8217;s credit card.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.riskbloggers.com/jimreavis/2008/03/vishing-incidents-a-preview-of-the-road-ahead/#comment-3905</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 17 Mar 2008 16:43:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.riskbloggers.com/jimreavis/2008/03/vishing-incidents-a-preview-of-the-road-ahead/#comment-3905</guid>
		<description>Add to this the fact that most people take Caller ID as the literal truth and something that can always be trusted (when in fact it can trivially be spoofed to read anything you want) and you have a recipe for disaster, people won't even be able to properly screen calls.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->Add to this the fact that most people take Caller ID as the literal truth and something that can always be trusted (when in fact it can trivially be spoofed to read anything you want) and you have a recipe for disaster, people won&#8217;t even be able to properly screen calls.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
</channel>
</rss>
