<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ITAC Blog &#187; Full Disclosure</title>
	<atom:link href="http://itacidentityblog.com/tag/full-disclosure/feed" rel="self" type="application/rss+xml" />
	<link>http://itacidentityblog.com</link>
	<description></description>
	<lastBuildDate>Wed, 28 Dec 2011 15:59:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Breaking News:  T-Mobile Confirms Breach, But Says Customers Are Safe</title>
		<link>http://itacidentityblog.com/breaking-news-t-mobile-confirms-breach-but-says-customers-are-safe</link>
		<comments>http://itacidentityblog.com/breaking-news-t-mobile-confirms-breach-but-says-customers-are-safe#comments</comments>
		<pubDate>Tue, 09 Jun 2009 15:35:10 +0000</pubDate>
		<dc:creator>ITACadmin</dc:creator>
				<category><![CDATA[Daily News]]></category>
		<category><![CDATA[Data Breach]]></category>
		<category><![CDATA[Full Disclosure]]></category>
		<category><![CDATA[Identity Theft Assistance Center]]></category>
		<category><![CDATA[ITAC]]></category>
		<category><![CDATA[T-Mobile Breach]]></category>

		<guid isPermaLink="false">http://itacidentityblog.com/?p=435</guid>
		<description><![CDATA[It is official.  T-Mobile confirmed that the breach that occurred over the weekend &#8212; posted on the Full Disclosure mailing list &#8212; is for real.  Some speculated that it may have been a hoax, but alas that was not the case.  The company did say that customers are not at risk, and [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://itacidentityblog.com/wp-content/uploads/2009/06/t-mobile1.jpg" alt="t-mobile1" title="t-mobile1" width="135" height="90" class="alignleft size-full wp-image-436" />It is official.  T-Mobile <a href="http://www.eweek.com/c/a/Security/TMobile-Confirms-Breach-But-Says-Customers-Safe-507228/">confirmed</a> that the breach that occurred over the weekend &#8212; posted on the Full Disclosure mailing list &#8212; is for real.  Some speculated that it may have been a hoax, but alas that was not the case.  The company did say that customers are not at risk, and is continuing the investigate the breach.  </p>
<p>T-Mobile also said that is is unable to disclose additional information at this time, but stated customers “can be assured if there is any evidence that customer information has been compromised, we would inform those affected as quickly as possible.&#8221; </p>
<p>Stay tuned for more coverage of this breach!  </p>
]]></content:encoded>
			<wfw:commentRss>http://itacidentityblog.com/breaking-news-t-mobile-confirms-breach-but-says-customers-are-safe/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>T-Mobile Investigates Potential Breach; Bad Guys Posted it on Full Disclosure</title>
		<link>http://itacidentityblog.com/t-mobile-investigates-potential-breach-bad-guys-posted-it-on-full-disclosure</link>
		<comments>http://itacidentityblog.com/t-mobile-investigates-potential-breach-bad-guys-posted-it-on-full-disclosure#comments</comments>
		<pubDate>Mon, 08 Jun 2009 15:22:23 +0000</pubDate>
		<dc:creator>ITACadmin</dc:creator>
				<category><![CDATA[Daily News]]></category>
		<category><![CDATA[Data Breach]]></category>
		<category><![CDATA[Full Disclosure]]></category>
		<category><![CDATA[hackers]]></category>
		<category><![CDATA[ID Theft]]></category>
		<category><![CDATA[Potential Breach]]></category>
		<category><![CDATA[T-Mobile Data Breach]]></category>

		<guid isPermaLink="false">http://itacidentityblog.com/?p=431</guid>
		<description><![CDATA[<img class="alignleft size-full wp-image-432" title="t-mobile" src="http://itacidentityblog.com/wp-content/uploads/2009/06/t-mobile.jpg" alt="t-mobile" width="135" height="90" />You have to appreciate online forums like "Full Disclosure," which serves as an an unmoderated destination where people can post information on security vulnerabilities.  This also means that bad guys can post updates on their activities.  Case in point: the potential T-Mobile breach. The company is investigating <a href="http://seclists.org/fulldisclosure/2009/Jun/0062.html#start">a claim</a> that a massive amount of internal data has been stolen from the telecommunication operator's servers, a company spokesman said Monday.]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-432" title="t-mobile" src="http://itacidentityblog.com/wp-content/uploads/2009/06/t-mobile.jpg" alt="t-mobile" width="135" height="90" />You have to appreciate online forums like &#8220;Full Disclosure,&#8221; which serves as an an unmoderated destination where people can post information on security vulnerabilities.  This also means that bad guys can post updates on their activities.  Case in point: the potential T-Mobile breach. The company is investigating <a href="http://seclists.org/fulldisclosure/2009/Jun/0062.html#start">a claim</a> that a massive amount of internal data has been stolen from the telecommunication operator&#8217;s servers, a company spokesman said Monday.</p>
<p>On Saturday, some bad guys posted a message about T-Mobile saying that had completed a massive breach and have been unsuccessful in selling the data to a T-Mobile competitor.    No word yet from T-Mobile as to whether the breach actually happened.  The word on the streets is that Full Disclosure contains posts and information from wanna-be hackers who make fales claims about breaches they had completed.  We will be tracking this one.  So, stay tuned!</p>
]]></content:encoded>
			<wfw:commentRss>http://itacidentityblog.com/t-mobile-investigates-potential-breach-bad-guys-posted-it-on-full-disclosure/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

