<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[[SecurityRatty] tag: okemo]]></title>
    <link>http://securityratty.com/tag/okemo</link>
    <description></description>
    <pubDate>Tue, 01 Apr 2008 16:44:59 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[PCI compliance, building the base]]></title>
      <link>http://securityratty.com/article/ddd7130b171cf628c993b909a4292619</link>
      <guid>http://securityratty.com/article/ddd7130b171cf628c993b909a4292619</guid>
      <description><![CDATA[Blogger: Randall Gamby
An alarming trend is beginning to surface within SMB PCI compliant companies, like Hannaford Brothers ( http://www.networkworld.com/news/2008/031708-hannaford-data-breach.html...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>Blogger: Randall Gamby</p>

<p>An alarming trend is beginning to surface within SMB “PCI compliant” companies, like Hannaford Brothers (<a href="http://www.networkworld.com/news/2008/031708-hannaford-data-breach.html">http://www.networkworld.com/news/2008/031708-hannaford-data-breach.html</a>), Okemo Mountain Resort (<a href="http://www.okemo.com/okemowinter/security_update.asp">http://www.okemo.com/okemowinter/security_update.asp</a>), etc. Credit data is being stolen!&nbsp; While this is exceedingly bad, I have a theory on why this is happening.&nbsp; </p>

<p>Before I get into my theory I’d first like to talk about military bases.&nbsp; As we all know, the military contains a lot of top secret information.&nbsp; So how does, say the U.S. Army, protect it?&nbsp; First, they classify what information needs to be protected.&nbsp; Next they find a piece of property that they can physically secure.&nbsp; Once the property has been thoroughly checked (no listening devices or mines buried in the ground) they construct a series of secure buildings to house the data. They then put up a fence with a limited number of gates with guard houses and guards to protect it. Then, most importantly, after certifying the security of the base, they use sentries to periodically patrol the perimeter of the grounds to ensure unauthorized access is not gained by spies sneaking in under the fence.</p>

<p>So what does this have to do with PCI compliance for SMBs?&nbsp; Well the process of PCI certification is similar to what a military branch would do to secure their information.&nbsp; Enterprises identify and classify what data falls under PCI compliance. They validate that the systems that contain the information are controlled properly and are locked down through processes and technologies. Then they build a fence of security around the systems to ensure only properly authorized personnel have access to them.&nbsp; Finally they certify that the protections meet PCI compliance requirements. But unlike the military, I theorize that a lot of SMBs, short on personnel and resources, quit here.&nbsp; In exploring the topic I’ve found that there’s an attitude by some executives that PCI compliance is a gate.&nbsp; Once SMB organizations achieve PCI compliance, some move on to the next pressing security problem.&nbsp; But this is the wrong attitude.&nbsp; Just as the military found out eons ago, they must be constantly on guard because spies are always looking for kinks in the defense perimeter in order to slip in and gain access to information without authorization.&nbsp; </p>

<p>It seems that SMBs are the most at risk of not having “guard patrols” constantly patrolling the perimeter due to the cost and resources needed to monitor and report on the security’s on-going effectiveness and the bad guys are now sneaking in stealing the very data they created these defenses to protect. </p>

<p>So what’s the warning? Whether you’re a SMB or Global Enterprise, PCI compliance is a gate, that’s pretty much a fact, but it can’t be left unguarded.&nbsp; Time, money and resources must be allocated on an on-going basis else the bad guys will sneak in undetected and you may find yourself making a breach disclosure that wasn’t detected until it was too late.</p></div>
<img src="http://feeds.feedburner.com/~r/SecurityAndRiskManagementStrategiesBlog/~4/310488267" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 12 Jun 2008 07:54:22 +0000</pubDate>
      <category domain="http://securityratty.com/tag/pci compliance">pci compliance</category>
      <category domain="http://securityratty.com/tag/pci compliance requirements">pci compliance requirements</category>
      <category domain="http://securityratty.com/tag/military">military</category>
      <category domain="http://securityratty.com/tag/top secret information">top secret information</category>
      <category domain="http://securityratty.com/tag/military branch">military branch</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/guard">guard</category>
      <category domain="http://securityratty.com/tag/guard houses">guard houses</category>
      <category domain="http://securityratty.com/tag/data">data</category>
      <source url="http://feeds.feedburner.com/~r/SecurityAndRiskManagementStrategiesBlog/~3/310488267/pci-compliance.html">PCI compliance, building the base</source>
    </item>
    <item>
      <title><![CDATA[PCI compliance, building the base]]></title>
      <link>http://securityratty.com/article/76ccae9d968892639b29b7cad153cd24</link>
      <guid>http://securityratty.com/article/76ccae9d968892639b29b7cad153cd24</guid>
      <description><![CDATA[Blogger: Randall Gamby
An alarming trend is beginning to surface within SMB ???PCI compliant??? companies, like Hannaford Brothers (...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>Blogger: Randall Gamby</p>

<p>An alarming trend is beginning to surface within SMB ???PCI compliant??? companies, like Hannaford Brothers (<a href="http://www.networkworld.com/news/2008/031708-hannaford-data-breach.html">http://www.networkworld.com/news/2008/031708-hannaford-data-breach.html</a>), Okemo Mountain Resort (<a href="http://www.okemo.com/okemowinter/security_update.asp">http://www.okemo.com/okemowinter/security_update.asp</a>), etc. Credit data is being stolen!&nbsp; While this is exceedingly bad, I have a theory on why this is happening.&nbsp; </p>

<p>Before I get into my theory I???d first like to talk about military bases.&nbsp; As we all know, the military contains a lot of top secret information.&nbsp; So how does, say the U.S. Army, protect it?&nbsp; First, they classify what information needs to be protected.&nbsp; Next they find a piece of property that they can physically secure.&nbsp; Once the property has been thoroughly checked (no listening devices or mines buried in the ground) they construct a series of secure buildings to house the data. They then put up a fence with a limited number of gates with guard houses and guards to protect it. Then, most importantly, after certifying the security of the base, they use sentries to periodically patrol the perimeter of the grounds to ensure unauthorized access is not gained by spies sneaking in under the fence.</p>

<p>So what does this have to do with PCI compliance for SMBs?&nbsp; Well the process of PCI certification is similar to what a military branch would do to secure their information.&nbsp; Enterprises identify and classify what data falls under PCI compliance. They validate that the systems that contain the information are controlled properly and are locked down through processes and technologies. Then they build a fence of security around the systems to ensure only properly authorized personnel have access to them.&nbsp; Finally they certify that the protections meet PCI compliance requirements. But unlike the military, I theorize that a lot of SMBs, short on personnel and resources, quit here.&nbsp; In exploring the topic I???ve found that there???s an attitude by some executives that PCI compliance is a gate.&nbsp; Once SMB organizations achieve PCI compliance, some move on to the next pressing security problem.&nbsp; But this is the wrong attitude.&nbsp; Just as the military found out eons ago, they must be constantly on guard because spies are always looking for kinks in the defense perimeter in order to slip in and gain access to information without authorization.&nbsp; </p>

<p>It seems that SMBs are the most at risk of not having ???guard patrols??? constantly patrolling the perimeter due to the cost and resources needed to monitor and report on the security???s on-going effectiveness and the bad guys are now sneaking in stealing the very data they created these defenses to protect. </p>

<p>So what???s the warning? Whether you???re a SMB or Global Enterprise, PCI compliance is a gate, that???s pretty much a fact, but it can???t be left unguarded.&nbsp; Time, money and resources must be allocated on an on-going basis else the bad guys will sneak in undetected and you may find yourself making a breach disclosure that wasn???t detected until it was too late.</p></div>
]]></content:encoded>
      <pubDate>Thu, 12 Jun 2008 07:54:22 +0000</pubDate>
      <category domain="http://securityratty.com/tag/pci compliance">pci compliance</category>
      <category domain="http://securityratty.com/tag/pci compliance requirements">pci compliance requirements</category>
      <category domain="http://securityratty.com/tag/military">military</category>
      <category domain="http://securityratty.com/tag/top secret information">top secret information</category>
      <category domain="http://securityratty.com/tag/military branch">military branch</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/credit data">credit data</category>
      <category domain="http://securityratty.com/tag/guard">guard</category>
      <source url="http://srmsblog.burtongroup.com/2008/06/pci-compliance.html">PCI compliance, building the base</source>
    </item>
    <item>
      <title><![CDATA[Q&A: Bob Russo talks about the PCI Council]]></title>
      <link>http://securityratty.com/article/bdfeb4b09c22e22fbbb446672ad531a6</link>
      <guid>http://securityratty.com/article/bdfeb4b09c22e22fbbb446672ad531a6</guid>
      <description><![CDATA[Bob Russo, the general manager of the PCI Security Standards Council, spoke with Computerworld's Jaikumar Vijayan about the organization's current thinking on the PCI standard, what's changed since he...]]></description>
      <content:encoded><![CDATA[Bob Russo, the general manager of the PCI Security Standards Council, spoke with Computerworld's Jaikumar Vijayan about the organization's current thinking on the PCI standard, what's changed since he took the helm in 2007, and what he makes so far of the Hannaford and Okemo Ski Resort data breaches.
<p><a href="http://feeds.computerworld.com/~a/Computerworld/Security/News?a=og27H9"><img src="http://feeds.computerworld.com/~a/Computerworld/Security/News?i=og27H9" border="0"></img></a></p><img src="http://feeds.computerworld.com/~r/Computerworld/Security/News/~4/271344299" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 16 Apr 2008 07:16:23 +0000</pubDate>
      <category domain="http://securityratty.com/tag/bob russo">bob russo</category>
      <category domain="http://securityratty.com/tag/pci standard">pci standard</category>
      <category domain="http://securityratty.com/tag/jaikumar vijayan">jaikumar vijayan</category>
      <category domain="http://securityratty.com/tag/helm">helm</category>
      <category domain="http://securityratty.com/tag/hannaford">hannaford</category>
      <category domain="http://securityratty.com/tag/computerworld">computerworld</category>
      <category domain="http://securityratty.com/tag/manager">manager</category>
      <category domain="http://securityratty.com/tag/current">current</category>
      <category domain="http://securityratty.com/tag/organization">organization</category>
      <source url="http://feeds.computerworld.com/~r/Computerworld/Security/News/~3/271344299/article.do">Q&amp;A: Bob Russo talks about the PCI Council</source>
    </item>
    <item>
      <title><![CDATA[Vermont ski area reports Hannaford-like theft of payment card data]]></title>
      <link>http://securityratty.com/article/76e281f15c1cbbe5e474dd201352737a</link>
      <guid>http://securityratty.com/article/76e281f15c1cbbe5e474dd201352737a</guid>
      <description><![CDATA[The Okemo Mountain Resort in Vermont said that credit card data may have been stolen during a system intrusion, with at least some of the information being taken as cards were being...]]></description>
      <content:encoded><![CDATA[The Okemo Mountain Resort in Vermont said that credit card data may have been stolen during a system intrusion, with at least some of the information being taken as cards were being swiped.
<p><a href="http://feeds.computerworld.com/~a/Computerworld/Security/News?a=BAcQ38"><img src="http://feeds.computerworld.com/~a/Computerworld/Security/News?i=BAcQ38" border="0"></img></a></p><img src="http://feeds.computerworld.com/~r/Computerworld/Security/News/~4/262743704" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 02 Apr 2008 09:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/credit card data">credit card data</category>
      <category domain="http://securityratty.com/tag/okemo mountain resort">okemo mountain resort</category>
      <category domain="http://securityratty.com/tag/vermont">vermont</category>
      <category domain="http://securityratty.com/tag/system intrusion">system intrusion</category>
      <category domain="http://securityratty.com/tag/cards">cards</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <source url="http://feeds.computerworld.com/~r/Computerworld/Security/News/~3/262743704/article.do">Vermont ski area reports Hannaford-like theft of payment card data</source>
    </item>
    <item>
      <title><![CDATA[Ski area reports Hannaford-like theft of payment card data]]></title>
      <link>http://securityratty.com/article/e32ff097e56781ea8247e1b7e358e4a7</link>
      <guid>http://securityratty.com/article/e32ff097e56781ea8247e1b7e358e4a7</guid>
      <description><![CDATA[In a security breach that sounds similar to the one disclosed by Hannaford Bros. Co. last month, the Okemo Mountain Resort ski area in Vermont announced this week that data from more than 46,000...]]></description>
      <content:encoded><![CDATA[In a security breach that sounds similar to the one disclosed by Hannaford Bros. Co. last month, the Okemo Mountain Resort ski area in Vermont announced this week that data from more than 46,000 credit and debit card transactions may have been compromised during a system intrusion over a 16-day period in February.]]></content:encoded>
      <pubDate>Tue, 01 Apr 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/debit card transactions">debit card transactions</category>
      <category domain="http://securityratty.com/tag/hannaford bros">hannaford bros</category>
      <category domain="http://securityratty.com/tag/16-day period">16-day period</category>
      <category domain="http://securityratty.com/tag/sounds similar">sounds similar</category>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/security breach">security breach</category>
      <category domain="http://securityratty.com/tag/system intrusion">system intrusion</category>
      <category domain="http://securityratty.com/tag/credit">credit</category>
      <category domain="http://securityratty.com/tag/week">week</category>
      <source url="http://www.networkworld.com/news/2008/040208-ski-area-reports-hannaford-like-theft.html?fsrc=rss-security">Ski area reports Hannaford-like theft of payment card data</source>
    </item>
    <item>
      <title><![CDATA[Intrusion at Okemo Mountain Resort exposes customers]]></title>
      <link>http://securityratty.com/article/c7de24cbe0e0c51223e6fa063616f877</link>
      <guid>http://securityratty.com/article/c7de24cbe0e0c51223e6fa063616f877</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
3/31/08

Organization
Okemo Mountain Resort

Contractor/Consultant/Branch
None

Victims
Customers

Number Affected
46,569

Types of Data
credit card data...]]></description>
      <content:encoded><![CDATA[Technorati Tag: <a href="http://technorati.com/tag/security+breach" rel="tag">Security Breach</a><br><br>
<img src="http://breachblog.com/images/95781-88451/okemo.jpg" align="right" height="48" width="175"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>3/31/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.okemo.com/okemowinter/">Okemo Mountain Resort</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>None<br><br><span style="font-weight: bold;">Victims:</span><br>Customers<br><br><span style="font-weight: bold;">Number Affected:</span><br>46,569<br><br><span style="font-weight: bold;">Types of Data:</span><br>"credit card data including cardholder names, account numbers and expiration dates"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"Okemo Mountain Resort said Monday that hackers broke into its computer network and potentially gained access to credit card data from 28,168 transactions between Feb. 7 and Feb. 22 and 18,401 credit cards between January and March 2006."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.okemo.com/okemowinter/security_update.asp">Okemo Mountain Resort News Release</a> <br><a href="http://www.timesargus.com/apps/pbcs.dll/article?AID=/20080401/NEWS02/804010390/1003/NEWS02">Barre-Montpelier Times Argus</a> <br><a href="http://www.businessweek.com/ap/financialnews/D8VOMSOG0.htm">BusinessWeek</a> <br><a href="http://www.wtnh.com/Global/story.asp?S=8098892&amp;nav=3YeX">WTNH Channel 8 News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Okemo Mountain Resort<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>Okemo Mountain Resort today announced that it has been a recent target of criminal efforts to gain access to credit data by infiltration of its computer network at Okemo Mountain Ski Area.<br><br>Okemo believes the intruder gained potential access to credit card data including cardholder names, account numbers and expiration dates.<br><br>An expert in data security and forensics hired by Okemo to assist in the investigation and response to the incident has informed Okemo that its computer system was improperly accessed by an outside party for a 16 day period between February 7, 2008 and February 22, 2008.<br><br>Affected consumers potentially include those who used their credit cards at Okemo during such dates as well as those who did so from January through March of 2006. <br><br>The forensic review determined that the intruder may have accessed credit card data from up to 28,168 credit card transactions processed at Okemo during the 16 day period in February.&nbsp; The actual number of credit cards holders involved in the transactions is likely to be smaller because multiple transactions may have been processed on a single card.<br><br>In addition, there may have been access to 18,401 individual credit cards used at Okemo from January through March 2006, many of which are believed to have expired.<br><br>Okemo spokeswoman Bonnie MacPherson said Monday the company has not heard of any customers subjected to fraud as a result of the breach.<br><br>Upon discovery of this intrusion, Okemo promptly initiated security measures to block the infiltration and protect any personal information transmitted through its system from any further unauthorized access.<br><span style="font-style: italic;">[Evan] How do you suppose Okemo discovered this intrusion?&nbsp; Did a customer report unauthorized charges?&nbsp; Was the incident stumbled upon or detected during information security reviews of critical systems?</span><br style="font-style: italic;"><br>Okemo has provided notice to Visa, MasterCard and American Express and is cooperating fully with the credit card companies to notify potentially affected cardholders.<br><br>Okemo does not have sufficient information to directly contact cardholders.<br><br>Okemo has been informed that the banks, which issued the credit cards, will be provided with information necessary to notify their cardholders.<br><br>Okemo has also notified law enforcement and is providing notice to State Attorneys General and appropriate regulatory agencies.<br><br>Okemo will continue to carefully monitor the security of its systems moving forward.<br><span style="font-style: italic;">[Evan] Okemo (and all organizations) should "carefully monitor the security of its systems" continually.&nbsp; This "should" go without saying.&nbsp; Especially systems that are used in the collection, creation, storage, or transmission of confidential information.&nbsp; </span><br style="font-style: italic;"><br>Okemo has been advised by Federal law enforcement officials that the matter is currently under investigation.<br><br>Okemo will provide updates on this incident on its website: <a href="http://www.okemo.com.%C2%A0">www.okemo.com.&nbsp;</a> For further information or assistance, cardholders are encouraged to call the following Toll Free Number, 1-866-756-5366.&nbsp; Okemo can also be contacted at Okemo Mountain Resort, 77 Okemo Ridge Road, Ludlow, VT 05149.<br><br>"As a result of this, we've increased the firewall capability and added some software and taken some additional precautions," she said. (Okemo spokeswoman Bonnie MacPherson)<br><span style="font-style: italic;">[Evan] Huh?</span><br><br><span style="font-weight: bold;">Commentary:</span><br>I appreciate Okemo's news release.&nbsp; Some of the things that I didn't notice were an apology to the affected consumers, any words from Okemo leadership or any details about how this breach occurred.<br><br>Intrusions are coming in bunches lately. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown</font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/04/01/okemo.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 01 Apr 2008 16:44:59 +0000</pubDate>
      <category domain="http://securityratty.com/tag/okemo">okemo</category>
      <category domain="http://securityratty.com/tag/okemo mountain resort">okemo mountain resort</category>
      <category domain="http://securityratty.com/tag/okemo leadership">okemo leadership</category>
      <category domain="http://securityratty.com/tag/okemo ridge road">okemo ridge road</category>
      <category domain="http://securityratty.com/tag/evan okemo">evan okemo</category>
      <category domain="http://securityratty.com/tag/okemo promptly">okemo promptly</category>
      <category domain="http://securityratty.com/tag/evan">evan</category>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/credit data">credit data</category>
      <source url="http://breachblog.com/2008/04/01/okemo.aspx">Intrusion at Okemo Mountain Resort exposes customers</source>
    </item>
  </channel>
</rss>
