<?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>Target Archives - Wealth Building Tips</title>
	<atom:link href="https://blog.valuechecks.net/tag/target/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Make Plans To Succeed</description>
	<lastBuildDate>Tue, 16 Jan 2018 23:44:33 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.5</generator>
	<item>
		<title>What&#8217;s New With The Target Security Breach?</title>
		<link>https://blog.valuechecks.net/whats-new-with-the-target-security-breach/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=whats-new-with-the-target-security-breach</link>
		
		<dc:creator><![CDATA[Sherry Tingley]]></dc:creator>
		<pubDate>Fri, 07 Mar 2014 19:45:25 +0000</pubDate>
				<category><![CDATA[Banking]]></category>
		<category><![CDATA[Bank of America]]></category>
		<category><![CDATA[Credit Cards]]></category>
		<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Target]]></category>
		<guid isPermaLink="false">https://blog.valuechecks.net/?p=492</guid>

					<description><![CDATA[<p>The biggest known corporate breach in U.S. history was perpetrated on Target in November, 2013. Hundreds of stories have been written about it in the news, on blogs and magazines. That comes as no surprise considering the current number of customers affected reaches upwards of 100 million. The looming question in consumers minds remains. Who [&#8230;]</p>
<p>The post <a href="https://blog.valuechecks.net/whats-new-with-the-target-security-breach/">What&#8217;s New With The Target Security Breach?</a> appeared first on <a href="https://blog.valuechecks.net">Wealth Building Tips</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="https://blog.valuechecks.net/wp-content/uploads/2014/03/target-breach.jpg"><img fetchpriority="high" decoding="async" class="alignright size-full wp-image-493" alt="target-breach" src="https://blog.valuechecks.net/wp-content/uploads/2014/03/target-breach.jpg" width="255" height="198" alt="Target Security Breach" /></a>The biggest known corporate breach in U.S. history was perpetrated on Target in November, 2013. Hundreds of stories have been written about it in the news, on blogs and magazines. That comes as no surprise considering the current number of customers affected reaches upwards of 100 million.</p>
<p>The looming question in consumers minds remains. Who is responsible for the Target credit and debit card breach?  Brian Krebs,  and American journalist and investigative reporter who runs a <a href="https://krebsonsecurity.com/2014/03/sally-beauty-hit-by-credit-card-breach/">computer security website</a> has identified a likely suspect &#8211; Andrew Hodrievski of Odessa, Ukraine. Attempts to contact the suspect proved futile, but Krebs was able to email an associate of Hodrievski.  After exchanging emails with the associate, Krebs Security was offered $10,000 <em>not to publish</em> the incriminating information.  Hodrievski has not been arrested or questioned.</p>
<h2>How Did They Do It?</h2>
<p>The who question may have been answered, but the how question is still somewhat of a mystery to the public. Investigators have determined that the hackers were able to breach Target&#8217;s security through a third party vendor. Fazio Mechanical Service provided heating and air conditioning for the stores. After hacking into Fazio’s computer they gained the vendor&#8217;s username and password into Target. The hackers then used the same username and password to hack into the point of sale information where all customer information is stored.</p>
<p>Hackers then uploaded software to retrieve customer data for them. They tested the software on a handful of registers. Within two days they had access to a majority of Target&#8217;s cash registers and point of sale information. Thus the fraud began. Once they had customer data they sold the data on underground internet sites. The value of this data has gone down significantly as banks have purchased the same data, disabled cards and reissued new ones.</p>
<p>Investigators think the vulnerability was caused by the lack of two factor authentication for remote access, which is required by PCI Data Security Standards. PCI Standards help merchants to secure all Point Of Sale transactions.  Apparently Target used one network for most of their data while they should have been two different networks.  Isolating  3rd party remote access for vendors and customer data would have added another security measure needed and possibly helped prevent this type of security breach.</p>
<h2>Latest News</h2>
<p>Beth M. Jacob, chief information officer and executive vice president for Target’s technology services resigned from her position on Wednesday, March 5, 2013, just one week after Target posted their 4th quarter losses of $1.5 billion dollars compared to the previous year’s figures. More encouraging news in this case would have been that the criminal behind the attack was arrested.</p>
<h2>Consumer Protection</h2>
<p>For consumers who are now worried about their accounts being drained by complete strangers there is no magic bullet. The best thing to do at this point is to learn how to set up automatic alerts from your bank to your cell phone any time a transaction on your account occurs. You can then call the bank immediately when you discover any unauthorized transaction and prevent further loss.</p>
<p>The post <a href="https://blog.valuechecks.net/whats-new-with-the-target-security-breach/">What&#8217;s New With The Target Security Breach?</a> appeared first on <a href="https://blog.valuechecks.net">Wealth Building Tips</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
