<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss'><id>tag:blogger.com,1999:blog-2476227841670103833</id><updated>2009-10-23T11:11:21.252-07:00</updated><title type='text'>SecurityMetrics</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://blog.securitymetrics.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default?orderby=updated'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>SecurityMetrics</name><uri>http://www.blogger.com/profile/07621955675614021035</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>13</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-4350588762234659175</id><published>2009-07-27T10:04:00.001-07:00</published><updated>2009-07-27T10:04:45.028-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Compliance'/><category scheme='http://www.blogger.com/atom/ns#' term='IT risk'/><title type='text'>New research: Biggest card security risk is at merchant level</title><content type='html'>&lt;p&gt;Malware, counterfeit card fraud and card-not-present fraud are at the top of the list of threats to merchants today, according to a new report from the research firm &lt;a href="http://www.aitegroup.com/"&gt;Aite Group&lt;/a&gt; this month. The research report highlighted merchants as the most vulnerable position in the card data security ecosystem.&lt;/p&gt;  &lt;p&gt;The report, “Card Data Security: In Search of a Technology Solution,” talked to heads of risk management for North American issuing banks or payment processors to determine what they saw as the biggest card security problems, the responsibilities of stakeholders and possible security solutions that could minimize the risk.&lt;/p&gt;  &lt;p&gt;Who is most at risk? The report says 62% of survey respondents said the merchants, followed by acquirers, with 43% of the respondents naming this group as vulnerable or very vulnerable to security breaches. ISOs may have the least to worry about, with only 30% of respondents calling them vulnerable or very vulnerable to security breaches.&lt;/p&gt;  &lt;p&gt;Aite’s Nick Holland points out that the promising solution of shifting the industry from magnetic stripe cards to smart cards, also called EMV architecture, may never happen.&amp;#160; Holland&amp;#160; warns that&amp;#160; “with the deeply entrenched magnetic stripe infrastructure in the United States, and the cost and effort involved in transitioning stakeholders to chip and PIN infrastructure,” may preclude a move to more secure EMV architectures. &lt;/p&gt;  &lt;p&gt;More info on the report is &lt;a href="http://www.aitegroup.com/reports/200907011.php"&gt;here&lt;/a&gt;. &lt;/p&gt;  &lt;p&gt;Aite is also currently offering a survey for C-level technology and operations executives at North American banks to participate in to share their views on IT strategy trends in the banking industry. Click &lt;a href="http://aitegroup.com/Survey_IT_Strategy.php"&gt;here&lt;/a&gt; to participate.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-4350588762234659175?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/4350588762234659175'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/4350588762234659175'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2009/07/new-research-biggest-card-security-risk.html' title='New research: Biggest card security risk is at merchant level'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-858340006988362862</id><published>2009-07-24T12:24:00.001-07:00</published><updated>2009-07-24T12:24:39.993-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Compliance'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI Tips/Tricks'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI'/><title type='text'>Nearly 90% ‘trying to implement PCI Compliance process’ says report</title><content type='html'>&lt;p&gt;A new report out from the &lt;a href="http://www.theiia.org/"&gt;Institute of Internal Auditors&lt;/a&gt; reveals that nearly 90 percent of companies surveyed are trying to implement a PCI compliance process. The report also says that 56 percent of companies are in compliance with PCI DSS today. &lt;/p&gt;  &lt;p&gt;The entire report, “Moving Toward PCI Compliance,” is available &lt;a href="www.theIIA.org."&gt;here&lt;/a&gt;.&amp;#160; &lt;/p&gt;  &lt;p&gt;As a bonus the report offers some tips for internal auditors to help achieve PCI Compliance from the IT Compliance Institute as well. &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-858340006988362862?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/858340006988362862'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/858340006988362862'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2009/07/nearly-90-trying-to-implement-pci.html' title='Nearly 90% ‘trying to implement PCI Compliance process’ says report'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-7518477143242050921</id><published>2009-06-30T22:37:00.001-07:00</published><updated>2009-07-02T12:55:55.818-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='forensics'/><category scheme='http://www.blogger.com/atom/ns#' term='Compliance'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI DSS'/><category scheme='http://www.blogger.com/atom/ns#' term='security breach'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI Tips/Tricks'/><title type='text'>Has your third party vendor put you at risk?</title><content type='html'>&lt;p&gt;Since 2006, over 70 retailers and payment processors have disclosed breaches that involved tens of millions of credit and debit card numbers, this &lt;a href="http://www.journalgazette.net/article/20090629/BIZ/306299952/1031/BIZ"&gt;according to the Privacy Rights Clearinghouse.&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;As more and more small businesses comply with PCI DSS and are considering their systems' resilience to attack, being hacked by a bad guy is still –as it should be -- of utmost concern in the eyes of most business owners. &lt;/p&gt;  &lt;p&gt;But what if your security expert is the one that puts you at risk? Would you know?&lt;/p&gt;  &lt;p&gt;A business person runs a business. Regulations like PCI DSS and &lt;a href="http://www.networkworld.com/news/2009/021209-mass-data-privacy.html"&gt;other security&lt;/a&gt; laws are increasingly making business owners responsible for ensuring the integrity of their computer systems and credit card data. While simple processes such as where to store paper credit card data or ensuring systems are locked in an appropriate facility within the business are fairly routine processes for a business owner to address, ensuring that computer systems are not only PCI-compliant but resilient to a hack goes beyond most business owners’ expertise. &lt;/p&gt;  &lt;p&gt;Most often a business will engage a 'security expert.' If a new system is required and deployed that could offer ‘improved’ security, most businesses rely on their &lt;a href="http://en.wikipedia.org/wiki/Point_of_sale"&gt;POS (Point of Sale)&lt;/a&gt; vendor to set up a system in a secure manner – an arguably reasonable expectation. &lt;/p&gt;  &lt;p&gt;Not so fast. Our &lt;a href="http://www.securitymetrics.com/"&gt;forensics team&lt;/a&gt; was recently called in to perform an investigation for a small business owner in the Southeastern US that was hacked. In reviewing the log files and performing our investigation we uncovered a very disturbing fact -- the third party vendor had left behind information on the system that detailed several other businesses in the region that were also under contract to that same vendor including passwords and computer configuration data. &lt;/p&gt;  &lt;p&gt;It was, in this case, a POS vendor and not a security vendor that had performed the system’s security setup. Attackers then used this information to access the other businesses named in the documentation left behind by the vendor. In each instance it was found that the business was set-up uniformly and exactly as&amp;#160; each of the other businesses were set up, thereby making them all insecure. Additionally, each business had been set up to utilize the exact same &lt;b&gt;&lt;i&gt;default &lt;/i&gt;&lt;/b&gt;passwords for each location, giving the attacker immediate administrative access to over 40 additional businesses.&lt;/p&gt;  &lt;p&gt;There are reasons to be concerned about leaving your data security in someone else’s' hands. Your customers entrust your business to protect the information they share with you. Breaching that trust could mean less business and could be far more damaging than monetary consequences like paying a fine for a security breach or a noncompliance fee to Visa.&lt;/p&gt;  &lt;p&gt;Picking your security vendor, and learning how your business can be more secure working with third party security or other vendor should be a critical decision for any business owner. &lt;/p&gt;  &lt;p&gt;&lt;em&gt;-Dave Ellis, &lt;/em&gt;Director, Forensic Investigations&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-7518477143242050921?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/7518477143242050921'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/7518477143242050921'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2009/06/has-your-third-party-vendor-put-you-at.html' title='Has your third party vendor put you at risk?'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-8416608870525598280</id><published>2009-06-30T11:07:00.001-07:00</published><updated>2009-06-30T11:07:12.432-07:00</updated><title type='text'>MasterCard’s changes could affect 2000 merchants</title><content type='html'>&lt;p&gt;SearchSecurity’s Marcia Savage put together a great summary and industry response to increased PCI requirements &lt;a href="http://blog.securitymetrics.com/2009/06/mastercard-requires-authorized-qsa-for.html"&gt;announced last week by MasterCard&lt;/a&gt;. &lt;/p&gt;  &lt;p&gt;The new rules, she &lt;a href="http://searchsecurity.techtarget.com/news/article/0,289142,sid14_gci1360442,00.html"&gt;reports,&lt;/a&gt; will mean that merchants processing between one and six million transactions annually will, or Level 2 merchants, will be required to use a PCI-approved auditor to complete an annual onsite data security assessment by Dec. 31, 2010.&lt;/p&gt;  &lt;p&gt;MasterCard estimates that “fewer than 2,000 merchants will be directly affected by the revised rules” according to the report. &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-8416608870525598280?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/8416608870525598280'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/8416608870525598280'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2009/06/mastercards-changes-could-affect-2000.html' title='MasterCard’s changes could affect 2000 merchants'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-4697239041525903933</id><published>2009-06-26T23:59:00.001-07:00</published><updated>2009-06-27T00:01:59.738-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Security'/><category scheme='http://www.blogger.com/atom/ns#' term='Compliance'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI DSS'/><category scheme='http://www.blogger.com/atom/ns#' term='security breach'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI'/><title type='text'>Just What Is the Cost of a Breach?</title><content type='html'>&lt;p&gt;What is the cost of a breach to a retailer?&lt;/p&gt;  &lt;p&gt;We get&amp;#160; asked this question all the time. Putting a number on this is exceptionally hard with so many variables coming into play. We expect that it is “a lot”&amp;#160; -- as TJX companies found out this week.&lt;/p&gt;  &lt;p&gt;The company, which owns large volume discount retailers T.J. Maxx and Marshall stores, was the victim of perhaps the largest credit card breach disclosed by a retailer to date. This week it was announced that that have settled lawsuits with over 41 states in a deal. Back in January 2007 TJX disclosed that its systems were hacked over a period of 18 months without security detecting the theft.&lt;/p&gt;  &lt;p&gt;Under the terms of the settlement, the company has agreed to pay $9.75 million according to multiple reports. &lt;/p&gt;  &lt;p&gt;SearchSecurity has a complete recap of the settlement &lt;a href="http://searchsecurity.techtarget.com/news/article/0,289142,sid14_gci1360065,00.html#"&gt;here.&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-4697239041525903933?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/4697239041525903933'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/4697239041525903933'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2009/06/cost-of-breach.html' title='Just What Is the Cost of a Breach?'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-56155421286455234</id><published>2009-06-23T17:28:00.001-07:00</published><updated>2009-06-24T17:27:02.449-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='QSA'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI DSS'/><category scheme='http://www.blogger.com/atom/ns#' term='MasterCard'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI'/><title type='text'>MasterCard Requires ‘Authorized’ QSA for Level 1 &amp; 2 Merchants</title><content type='html'>&lt;p&gt;MasterCard announced a new &lt;a href="http://www.mastercard.com/us/sdp/merchants/merchant_levels.html#"&gt;requirement&lt;/a&gt; for Level 1 and Level 2 Merchants, mandating these two groups must use an authorized Qualified Security Assessor (QSA) to conduct a PCI DSS security assessment.&amp;#160; &lt;/p&gt;  &lt;p&gt;The requirement has a &amp;quot;due date&amp;quot; of December 31, 2010, meaning that each Level 1 and 2 merchant must submit proof of compliance filed by an authorized QSA by that date versus the date you would START working with a QSA.&amp;#160; &lt;/p&gt;  &lt;p&gt;Based on our experience validating PCI DSS compliance for Level 1 and Level 2 merchants over the past 5 years, achieving full compliance is not something to put off until sometime in 2010.&amp;#160; Many large merchants required as much as 18+ months to get compliant and not one was accomplished in less than 10 months.&amp;#160; Many of these merchants had already conducted their own internal PCI audit or completed SAQ's and had felt pretty good about their compliance program.&amp;#160; &lt;/p&gt;  &lt;p&gt;Larger merchants should begin a program with an authorized QSA as soon as possible, no matter how compliant you ‘think’ you are.&amp;#160; If network and processes are in good shape, it could work out that you are done &amp;quot;early&amp;quot; for the MasterCard deadline – though chances are,&amp;#160; you will need the time to prepare for a compliant PCI-DSS assessment.&lt;/p&gt;  &lt;p&gt;Level 1 merchants are defined as those that store, transmit, or process more than 6 million MasterCard transactions/accounts per year and Level 2 are those that handle between 1 million and 6 million annually. &lt;/p&gt;  &lt;p&gt;&lt;em&gt;-Gary&lt;/em&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-56155421286455234?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/56155421286455234'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/56155421286455234'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2009/06/mastercard-requires-authorized-qsa-for.html' title='MasterCard Requires ‘Authorized’ QSA for Level 1 &amp;amp; 2 Merchants'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-6048897736425779446</id><published>2009-06-17T15:00:00.001-07:00</published><updated>2009-06-17T15:00:57.135-07:00</updated><title type='text'>Who oversees payment security?</title><content type='html'>&lt;p&gt;A recent Visa-Economist poll of global executives was released at &lt;a href="usa.visa.com/download/merchants/2009-security-summit-summary.pdf "&gt;Visa’s Summit this Spring&lt;/a&gt;. The report demonstrated that over 75 percent said a C-level executive is now responsible for payment security within their company, which is a great indicator of data security being given more prominence in business. &lt;/p&gt;  &lt;p&gt;Moving the charter of safeguarding data to the C-Suite is a good start but thanks to investment and innovative security solutions, &lt;em&gt;“fraud rates in the credit card industry remain near all-time lows,”&lt;/em&gt; said &lt;a href="http://www.corporate.visa.com/md/dl/documents/downloads/EllenRichey09SummitRemarks.pdf"&gt;Ellen Richey, Chief Enterprise Risk Officer, Visa Inc.&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;Richey goes on to note the real progress and inroads PCI has made, pointing to 90% of large U.S. merchants now validating compliance and goes into details about the Heartland breach, how a vigilant PCI can contribute to overall data security and the state of data security in credit cards in her talk. &lt;/p&gt;  &lt;p&gt;Good read…&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-6048897736425779446?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/6048897736425779446'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/6048897736425779446'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2009/06/who-oversees-payment-security.html' title='Who oversees payment security?'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-1540727296249349607</id><published>2009-06-12T01:08:00.001-07:00</published><updated>2009-06-12T01:08:18.661-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Security'/><category scheme='http://www.blogger.com/atom/ns#' term='IT risk'/><category scheme='http://www.blogger.com/atom/ns#' term='security breach'/><title type='text'>Nokia mobile phone (circa-2003) gains popularity as online banking hack</title><content type='html'>&lt;p&gt;Investigators have figured out why there has been a surge in sales of a particular entry-level Nokia mobile phone circa 2003 -- it at allows users to hack into bank accounts. &lt;/p&gt;  &lt;p&gt;Turns out that authorities have known European gangs have been searching out the phone for some time but this is &lt;a href="http://www.pcworld.com/businesscenter/article/165326/investigators_replicate_nokia_1100_online_banking_hack.html"&gt;the first reported&lt;/a&gt; duplication of the online banking hack being used to gain access to victim's bank accounts. Specific models of the Nokia 1100, from one specific factory &lt;a href="http://www.thestandard.com/news/2009/04/21/nokia-we-dont-know-why-criminals-want-our-old-phones"&gt;according to the report,&lt;/a&gt; have been indicated in the hack. Just last month Nokia said that they had no idea why the uptick in recent demand and interest in the older model device. &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-1540727296249349607?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/1540727296249349607'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/1540727296249349607'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2009/06/nokia-mobile-phone-circa-2003-gains.html' title='Nokia mobile phone (circa-2003) gains popularity as online banking hack'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-303142873417896983</id><published>2009-05-21T10:43:00.001-07:00</published><updated>2009-05-21T11:03:23.444-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Compliance'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI DSS'/><category scheme='http://www.blogger.com/atom/ns#' term='IT risk'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI Tips/Tricks'/><title type='text'>To store or not to store, the top PCI Question</title><content type='html'>&lt;p&gt;One of the most frequent questions we get asked by merchants is where they should store their cardholder data. The answer to this question is a resounding - you shouldn't store any cardholder data! &lt;/p&gt;  &lt;p&gt;In reality that is not entirely possible for all merchants. We recommend that merchants should not store cardholder data unless it is absolutely essential to do business. In the word of &lt;a href="https://www.pcisecuritystandards.org/docs/saq_d_v1-1.doc"&gt;PCI DSS&lt;/a&gt; words it: &amp;quot;3.1 Keep cardholder data storage to a minimum&amp;quot;.&amp;#160; &lt;/p&gt;  &lt;p&gt;Thieves cannot steal what is not there.&amp;#160; Before a merchant gets hacked they often feel it is very important to store card data. Once a merchant experiences an attack, we have seen that mindset shift into one that tries to find a way to eliminate card data from their system entirely.&lt;/p&gt;  &lt;p&gt;For Point-of-Sale transactions where the credit card is physically present, it best to adopt real-time authorization and settlement.&amp;#160; By doing so, the merchant can push the card data completely off of their systems. They never store it in the first place. If the merchant is storing the card number and batching out once a day, the merchant is required to comply with &lt;a href="https://www.pcisecuritystandards.org/docs/saq_d_v1-1.doc"&gt;SAQ-D&lt;/a&gt;.&lt;/p&gt;  &lt;p&gt;If batching is required, try to set up a system where a compliant processing solution captures all card data upon authorization, returning only an authorization code to the merchant.&amp;#160; This approach ensures that cardholder data is removed entirely from the system at the time of authorization. The merchant later batches using the authorization codes instead of the cardholder data, eliminating the risk entirely. &lt;/p&gt;  &lt;p&gt;For recurring billing transactions merchants will need to store customer card data, billing information, and other sensitive data. To reduce risk in this situation the merchant must never, under any circumstances, store the security code (CVV2, CVV, etc.) following the very first authorization.&amp;#160; There are no exceptions to this requirement. PCI DSS says &amp;quot;Sensitive authentication data must not be stored after authorization (even if encrypted).&amp;quot;&amp;#160; &lt;/p&gt;  &lt;p&gt;Requirement 3 details the entire cardholder data storage rules of PCI DSS.&lt;/p&gt;  &lt;p&gt;&lt;em&gt;-Lee, Strategic Accounts&lt;/em&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-303142873417896983?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/303142873417896983'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/303142873417896983'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2009/05/to-store-or-not-to-store-top-pci.html' title='To store or not to store, the top PCI Question'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-2782344582562245856</id><published>2008-02-04T09:05:00.000-08:00</published><updated>2008-02-04T09:10:03.863-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Security'/><category scheme='http://www.blogger.com/atom/ns#' term='IT risk'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI'/><title type='text'>Businesses now "expect" data security breaches</title><content type='html'>&lt;span class="296352817-01022008"  style="font-family:trebuchet ms;"&gt;&lt;span style="font-size:85%;"&gt;&lt;a href="http://www.symantec.com/"&gt;Symantec's&lt;/a&gt;&lt;/span&gt;&lt;span style="font-size:85%;"&gt; second annual &lt;a href="http://www.symantec.com/business/theme.jsp?themeid=inform"&gt;IT risk management survey&lt;/a&gt; &lt;/span&gt;&lt;span style="font-size:85%;"&gt;indicates that 59% of businesses concede that "a major loss  of customer information is expected once every five years" and on-average each  breach "exposes the data of more than 785,000 customers."&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt; &lt;div  style="font-family:trebuchet ms;"&gt;&lt;span class="296352817-01022008"&gt;&lt;/span&gt; &lt;/div&gt; &lt;div  style="font-family:trebuchet ms;"&gt;&lt;span style="font-size:85%;"&gt;&lt;span class="296352817-01022008"&gt;More.  &lt;/span&gt;&lt;span class="296352817-01022008"&gt;Of those surveyed 69 percent said they  believe they will encounter at least one minor incident per month, with 63  percent predicting a major IT failure at least once a  year.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt; &lt;div  style="font-family:trebuchet ms;"&gt;&lt;span class="296352817-01022008"&gt;&lt;/span&gt; &lt;/div&gt; &lt;div  style="font-family:trebuchet ms;"&gt;&lt;span class="296352817-01022008"&gt;&lt;span class="296352817-01022008"&gt;&lt;span style="font-size:85%;"&gt;The survey also pointed to compliance, and ensuring you are  operating in accordance with regulations like PCI DSS, are continuing to drive  IT security priorities. In fact,  "IT availability management and compliance  projects are just as important, if not more important, than traditional IT  security efforts." &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="296352817-01022008"&gt;&lt;span class="296352817-01022008"&gt;&lt;span style="font-size:85%;"&gt;Survey participants reported  compliance (68 percent), performance (70 percent), and availability (78  percent) as serious or critical risks factors in the data center.&lt;br /&gt;&lt;br /&gt; &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt; &lt;div  style="font-family:trebuchet ms;"&gt;&lt;span class="296352817-01022008"&gt;&lt;span class="296352817-01022008"&gt;&lt;/span&gt;&lt;/span&gt; &lt;/div&gt; &lt;div  style="font-family:trebuchet ms;"&gt;&lt;span class="296352817-01022008"&gt;&lt;span class="296352817-01022008"&gt;&lt;span style="font-size:85%;"&gt;You can sign up and view the survey &lt;a href="http://www.symantec.com/business/theme.jsp?themeid=inform"&gt;here&lt;/a&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt; &lt;div&gt;&lt;span class="296352817-01022008"&gt;&lt;span style=";font-family:Arial;font-size:85%;"  &gt;&lt;span class="296352817-01022008"&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-2782344582562245856?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/2782344582562245856'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/2782344582562245856'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2008/02/businesses-now-expect-data-security.html' title='Businesses now &quot;expect&quot; data security breaches'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-1410558317015529724</id><published>2008-01-24T17:35:00.000-08:00</published><updated>2008-01-24T17:42:00.509-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Security'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI DSS'/><category scheme='http://www.blogger.com/atom/ns#' term='Visa'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI'/><title type='text'>Visa Says 2007 Saw 'Significant' PCI Progress Among US Retailers</title><content type='html'>Visa released a &lt;a href="http://www.corporate.visa.com/md/nr/press753.jsp?src=home"&gt;statement this week&lt;/a&gt; about the state of PCI compliance. They say that "as of the end of 2007, more than three-fourths of the largest U.S. merchants (those processing six million or more Visa transactions annually) and nearly two-thirds of medium-sized merchants (those processing between one million and six million Visa transactions annually) have now validated their compliance with the P&lt;a href="https://www.pcisecuritystandards.org/"&gt;ayment Card Industry Data Security Standard&lt;/a&gt; (PCI DSS). Merchants in these two categories account for approximately two-thirds of Visa's U.S. transaction volume."&lt;br /&gt;&lt;br /&gt;The numbers? Visa points to a jump from "12 percent in March 2006 to 77 percent" by year end among large vendors and says medium-sized merchants, "compliance grew from 15 percent in December 2006 to 62 percent."&lt;br /&gt;&lt;br /&gt;The company is calling for complete compliance among its entire merchant base -- all the way down to small merchants, or Level 4s. In fact, Visa says "100 percent of active U.S. acquirers have submitted plans to Visa and are in the process of implementing their security programs."&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-1410558317015529724?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/1410558317015529724'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/1410558317015529724'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2008/01/visa-says-2007-saw-significant-pci.html' title='Visa Says 2007 Saw &apos;Significant&apos; PCI Progress Among US Retailers'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-5136417525137526025</id><published>2007-12-21T13:17:00.000-08:00</published><updated>2007-12-21T13:19:55.785-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='PCI DSS'/><category scheme='http://www.blogger.com/atom/ns#' term='Misc'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI'/><title type='text'>Could PCI Could Stem Voter Fraud?</title><content type='html'>It could happen if a report out of Ohio is any indication. Came upon this interesting post over at the &lt;a href="http://www.treasuryinstitute.org/blog/"&gt;TreasuryInstitute's blog&lt;/a&gt; on yet another use for PCI standards. They point to an &lt;a href="http://www.sos.state.oh.us/sos/info/EVEREST/14-AcademicFinalEVERESTReport.pdf"&gt;interesting study &lt;/a&gt;(download here) that used PCI DSS as a benchmark to assess the integrity of voting systems in Ohio.&lt;br /&gt;&lt;br /&gt;A team of computer scientists were commissioned by the Ohio Secretary of State to "assess the reliability, accessibility, and security of electronic voting systems used in Ohio." The team compared systems against a common baseline of information security practices -- in this case PCI DSS -- to determine the security risk in voting systems used in the state. The report notes that "The framework was originally designed to be applied to credit card processing systems, but easily extends itself to any form or critical data." It makes sense.&lt;br /&gt;&lt;br /&gt;Ohio has long been considered a state crucial in the outcome of past presidential elections and voter fraud in that state has been a hot topic As a result of the security assessment, Jennifer Brunner, Ohio’s secretary of state, has said that voting system in &lt;a href="http://news.cincypost.com/apps/pbcs.dll/article?AID=/20071220/NEWS01/712200371"&gt;Ohio is insecure &lt;/a&gt; and is proposing to replace all the states’ voting machines with optical-scan machines for a more secure and clear audit trail.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-5136417525137526025?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/5136417525137526025'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/5136417525137526025'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2007/12/could-pci-could-stem-voter-fraud.html' title='Could PCI Could Stem Voter Fraud?'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry><entry><id>tag:blogger.com,1999:blog-2476227841670103833.post-8422724765871461291</id><published>2007-12-05T13:14:00.000-08:00</published><updated>2007-12-05T14:21:31.978-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Security'/><category scheme='http://www.blogger.com/atom/ns#' term='SecurityMetrics News'/><category scheme='http://www.blogger.com/atom/ns#' term='Compliance'/><category scheme='http://www.blogger.com/atom/ns#' term='PCI'/><title type='text'>The TJMaxx Lesson</title><content type='html'>&lt;div  style="text-align: left;font-family:trebuchet ms;"&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;Visa has struck a  deal with TJMaxx to settle what may be the &lt;a href="http://www.darkreading.com/document.asp?doc_id=120810"&gt;biggest breach in customer data in history&lt;/a&gt;. TJMaxx &lt;a href="http://www.zdnetasia.com/news/security/0,39044215,62035146,00.htm"&gt;has offered $40.9 M US as a settlement&lt;/a&gt; over their security incident and has  until 2009 to be fully compliant with &lt;a href="https://www.pcisecuritystandards.org/"&gt;PCI DSS&lt;/a&gt; according to published reports.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt; &lt;/div&gt;&lt;div  style="text-align: left;font-family:trebuchet ms;"&gt; &lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div  style="text-align: left;font-family:trebuchet ms;"&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;The TJMaxx incident  was certainly bad for consumer. Some estimates claim that close to 100  million customer accounts were compromised, while TJMaxx &lt;a href="http://www.zdnetasia.com/news/security/0,39044215,62011583,00.htm"&gt;publicly acknowledged 45 million  customer accounts were compromised&lt;/a&gt; in a statement last year. In an effort to prevent future issues, legislation was  proposed in several states to compel businesses to secure customer data. Proposals were drafted in California, Illinois and a few other states.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div  style="text-align: left;font-family:trebuchet ms;"&gt; &lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div  style="text-align: left;font-family:trebuchet ms;"&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;Ironically, the  "TJMaxx lesson" has been good for Level 1 retailers and the security  industry providing PCI compliance solutions. The discount retailer had some unfortunate timing on their disclosure, and as the first big  breach of customer data to gain broad exposure it quickly became  the litmus test for other Level 1s. It is a great reference for what is compliant and what is not.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div  style="text-align: left;font-family:trebuchet ms;"&gt; &lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div  style="text-align: left;font-family:trebuchet ms;"&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;Under the recently announced deal, it seems that Visa will continue to work with TJMaxx and has agreed to reduce some fines. Some critics have said that the company &lt;a href="http://www.boston.com/business/globe/articles/2007/12/04/tjx_escapes_a_beating/"&gt;has fared well &lt;/a&gt;throughout this ordeal and point to strong sales. But fines are just one of the costs that TJMaxx or any retailer caught in this situation also endure. Damage to reputation and other indirect costs are immeasurable.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;An  interesting part of the settement agreement between Visa and TJMaxx requires the merchant to promote PCI DSS and &lt;a href="http://www.digitaltransactions.net/newsstory.cfm?newsid=1596"&gt;raise awareness of the risk of noncompliance  for the next two years&lt;/a&gt;. Talk about being the poster child for PCI DSS  Compliance!&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div face="trebuchet ms" style="text-align: left;"&gt; &lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div face="trebuchet ms" style="text-align: left;"&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;December 31st marks the next major deadline in PCI Compliance as level 2 merchants must be in compliance. Level 2 merchants should heed the "TJMaxx lesson" and make sure they can prove their comformance.  Being the first to  fail is not a good thing we have learned. And retailers have a &lt;a href="http://news.google.com/news?source=ig&amp;amp;hl=en&amp;amp;rlz=&amp;amp;q=pci+data&amp;amp;um=1&amp;amp;ie=UTF-8&amp;amp;sa=N&amp;amp;tab=wn"&gt;bad case of PCI Confusion&lt;/a&gt; according to eWeek's Evan Shuman.&lt;br /&gt;&lt;br /&gt;To help minimize any confusion today we  started offering a quick start&lt;span style=";color:black;" &gt;  Site Certification program priced from $139.99 US  for a single IP address for the first year to help Level 2s  (and others!) meet the &lt;a href="http://www.delawareonline.com/apps/pbcs.dll/article?AID=/20071125/BUSINESS/711250314/1003"&gt;upcoming &lt;/a&gt;&lt;/span&gt;&lt;a href="http://www.delawareonline.com/apps/pbcs.dll/article?AID=/20071125/BUSINESS/711250314/1003"&gt;&lt;st1:date ls="trans" month="12" day="31" year="2007"&gt;&lt;/st1:date&gt;&lt;/a&gt;&lt;span style=";color:black;" &gt;&lt;a href="http://www.delawareonline.com/apps/pbcs.dll/article?AID=/20071125/BUSINESS/711250314/1003"&gt;deadline&lt;/a&gt; or just to &lt;a href="http://usa.visa.com/merchants/risk_management/cisp.html"&gt;reduce overall risks&lt;/a&gt; associated with payment card processing.  It's usually $699, so that is an 80% savings to jumpstart your PCI Compliance program.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div face="trebuchet ms" style="text-align: left;"&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;&lt;span style=";color:black;" &gt;&lt;/span&gt;&lt;/span&gt; &lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div style="font-family: trebuchet ms; text-align: left;"&gt; &lt;/div&gt;&lt;div face="trebuchet ms" style="text-align: left;"&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;&lt;span style=";color:black;" &gt;Call us. &lt;/span&gt;&lt;/span&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;&lt;span style=";color:black;" &gt;801 705 5665. &lt;/span&gt;&lt;/span&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;&lt;span style=";color:black;" &gt;We love to talk about PCI :-) &lt;/span&gt;&lt;/span&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;&lt;span style=";color:black;" &gt;We can handle all of your PCI issues -- from forensics after an attack to scanning to auditing to designing a strategy tailored to your needs. &lt;/span&gt;&lt;/span&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;&lt;span style=";color:black;" &gt;We've seen it all. Really.&lt;/span&gt;&lt;/span&gt;&lt;span class="272454505-05122007"  style="font-size:85%;"&gt;&lt;span style=";color:black;" &gt; &lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;span class="272454505-05122007"&gt;&lt;span style=";font-family:'Trebuchet MS';font-size:10;color:black;"   &gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2476227841670103833-8422724765871461291?l=blog.securitymetrics.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/8422724765871461291'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2476227841670103833/posts/default/8422724765871461291'/><link rel='alternate' type='text/html' href='http://blog.securitymetrics.com/2007/12/why-tjmaxx-was-good-thing-for-pci-or.html' title='The TJMaxx Lesson'/><author><name>SecurityMetrics PR</name><uri>http://www.blogger.com/profile/08957699674723265360</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01697192380214837056'/></author></entry></feed>