<?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>user passwords exposed Archives - Claims Journal</title>
	<atom:link href="https://www.claimsjournal.com/topics/user-passwords-exposed/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.claimsjournal.com/topics/user-passwords-exposed/</link>
	<description>Insurance news and resources for the claims industry</description>
	<lastBuildDate>Mon, 11 Jun 2012 14:15:57 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://www.claimsjournal.com/app/uploads/2015/12/cropped-claimsjournal-32x32.png</url>
	<title>user passwords exposed Archives - Claims Journal</title>
	<link>https://www.claimsjournal.com/topics/user-passwords-exposed/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>LinkedIn Breach Puts Site&#8217;s Reputation on the Line</title>
		<link>https://www.claimsjournal.com/news/national/2012/06/11/208272.htm</link>
		
						<dc:creator><![CDATA[Admin]]></dc:creator>
						<pubDate>Mon, 11 Jun 2012 14:15:57 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[LinkedIn]]></category>
		<category><![CDATA[security breach]]></category>
		<category><![CDATA[user passwords exposed]]></category>
		<guid isPermaLink="false">https://www.claimsjournal.com/?p=208272</guid>

							<description><![CDATA[LinkedIn Corp&#8217;s silence on the extent of a security breach that exposed millions of user passwords has damaged its reputation among some business professionals, and may slow the growing company&#8217;s rise if the breach turns out to be more serious &#8230;]]></description>
				
		
			</item>
	</channel>
</rss>
