<?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: license]]></title>
    <link>http://securityratty.com/tag/license</link>
    <description></description>
    <pubDate>Tue, 03 Jun 2008 09:34:56 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[A thin line between blog theft and promotion - another opinion]]></title>
      <link>http://securityratty.com/article/8db8f65e1fa8fce8c11d7b631ccf2157</link>
      <guid>http://securityratty.com/article/8db8f65e1fa8fce8c11d7b631ccf2157</guid>
      <description><![CDATA[Rich Mogull has been writing a bit about his disagreement with a the SecurityRatty site posting his content (original posts here and here ). These posts have set off a rash of comments and other...]]></description>
      <content:encoded><![CDATA[<p>Rich Mogull has been writing a bit about his disagreement with a the <a href="http://securityratty.com/">SecurityRatty</a> site posting his content (original posts <a href="http://securosis.com/2008/07/02/securityratty-is-slimey-content-stealing-thief/">here</a> and <a href="http://securosis.com/2008/07/02/i-win/">here</a>). These posts have set off a rash of comments and other articles on both sides of this issue. Finally Rich wrote his <a href="http://securosis.com/2008/07/02/defining-blog-content-theft/">defining post on this topic here</a>. Rich's position is that he owns his words. Ratty took them without his permission, ads nothing to the conversation or commentary at all and actually hosts the content rather than just linking to it. Now for those who don't know, SecurityRatty is a site allegedly owned and operated by some Russian CISSP dude. Basically, they claim they are an RSS aggregator and they just republish blog posts in their entirety. A couple of things to note though:<br><br>1. SecurityRatty does not usually add any content of their own or edit the posts in any way<br>2. They link back to the blogs or articles which are aggregated<br>3. They do appear to sell some advertising on the site<br>4. You can search their aggregated content on their site<br>5. At least recently they are removing content and feeds from their site if you request it.<br>6. They did not ask anyones permission that I know of before posting content<br><br>OK, now that the groundwork is laid, let me give my Shimel view on this. I disagree with Rich. Hey it is a big world and I think there is room for a dissenting opinion here. The reasons I disagree with Rich are:<br><br>1. Though Ratty plainly posts up others content, he does not hold it out as his own. He plainly gives credit to those who actually created the words and in fact links back to their sites.<br>2. Rich is publishing his data under a creative commons license, I am not sure if the meager ad on Ratty would qualify this as a commercial site.<br>3. Rich distinguishes what Ratty does from Google and other search engines (who clearly profit from Rich's content) by the fact that they just point to it. Not all together true. They also keep a cached copy of the content that you can go to as well.<br>4. The fact is that I have a tough time seeing any harm to Rich here. In fact if Ratty were not pointing back to Rich's site, if he did not make it as easy to see that it is just an aggregate feed or if Ratty were adding his own comments and not clearly delineating his from Rich's, I would feel differently. Some of this is directly in contrast to Rich who says that if Ratty did add his own views to Rich's, that would make it right by him.<br>5. Finally, I would go even further than Rich not being harmed by Ratty. I think Rich actually benefits from Ratty. It is yet another outlet for Rich's content and though not everyone reading it at Ratty may go back to Rich's site, they do know it is him and can go back easily. In fact if Rich did advertise at his site, I could understand him losing hits at his site. Otherwise if Ratty just pointed back, one could say the more hits Ratty generates, it could cost Rich more money. Much like people who link to graphics hosted elsewhere.<br><br>So, Rich I see that Ratty has stopped aggregating your content so that should be enough of a victory for you. In the long run though I think it is a Pyrrhic victory and you would have been better off with Ratty publicizing your words.</p><blockquote></blockquote>
<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=HqzgQX"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=HqzgQX" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=URCj2J"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=URCj2J" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=LcKVkJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=LcKVkJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=d4OmHJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=d4OmHJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=uX21WJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=uX21WJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=4Efv2j"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=4Efv2j" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=RwzMJj"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=RwzMJj" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/326305454" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 03 Jul 2008 18:24:36 +0000</pubDate>
      <category domain="http://securityratty.com/tag/posts">posts</category>
      <category domain="http://securityratty.com/tag/ratty plainly posts">ratty plainly posts</category>
      <category domain="http://securityratty.com/tag/rich distinguishes">rich distinguishes</category>
      <category domain="http://securityratty.com/tag/rich">rich</category>
      <category domain="http://securityratty.com/tag/rich mogull">rich mogull</category>
      <category domain="http://securityratty.com/tag/cost rich">cost rich</category>
      <category domain="http://securityratty.com/tag/plainly">plainly</category>
      <category domain="http://securityratty.com/tag/ratty">ratty</category>
      <category domain="http://securityratty.com/tag/securityratty">securityratty</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/326305454/a-thin-line-bet.html">A thin line between blog theft and promotion - another opinion</source>
    </item>
    <item>
      <title><![CDATA[Even the Rich and Famous pay the price for being Dishonest and Unethical]]></title>
      <link>http://securityratty.com/article/bddc2473e5205464ce579dd702e7a914</link>
      <guid>http://securityratty.com/article/bddc2473e5205464ce579dd702e7a914</guid>
      <description><![CDATA[All of our courses - in the U.S. and over seas, begin with the same message - ETHICS is the keystone of our profession and our success. It's a shame that famed litigator - Richard &quot;Dickie&quot; Scruggs...]]></description>
      <content:encoded><![CDATA[All of our courses - in the U.S. and over seas, begin with the same message - ETHICS is the keystone of our profession and our success.  It's a shame that famed litigator - Richard "Dickie" Scruggs forgot that lesson.    <br /><span id="fullpost"><br />In yesterday's Washington Post, the headline reads; "<a href="http://www.washingtonpost.com/wp-dyn/content/article/2008/06/27/AR2008062703609_2.html">Famed Litigator </a>Gets 5-Year Term for Conspiracy to bribe Judge".  For those who are not familiar with him, Scruggs became one of the wealthiest and most famous lawyers in the country by taking on tobacco, insurance and asbestos companies.  <br /><br />What did he do? Well, for starters (and what they were able to prove), he attempted to bribe Lafayette County Circuit Court Judge Henry Lackey by offering him $50,000.00.  U.S. District Judge Neal Biggers Jr., called Scruggs' conduct "reprehensible" and told him that he picked the wrong Judge to bribe.  In addition to the 5 year jail term, he was fined $250,000.00 and lost his law license.<br /><br />You really got to love it when Justice is rightfully served.  Unfortunately, it makes me wonder how many more sleazy lawyers around the country and unethical Judges are not getting reported and prosecuted.  It is a little too hard to believe that Scruggs is the only dirt-bag in the legal profession.  We welcome the message it sends out; "nobody is above the law".  <br /><br />Like most, if not all common criminals, Richerd Scruggs became greedy.  In 1990, Scruggs became famous for suing tobacco companies and winning lawsuits that resulted in a $206 BILLION dollar settlement.  If his take of that was just 10%, he walked away with a cool $20.6 Billion dollars.  A film was even made about the case - "The Insider" starred Al Pacino and Russell Crowe.<br /><br />A decade later he is trying to bribe a Judge with $50,000?  I would say it was a combination of greed and power going to his head.  Maybe that is why the "Post" reported that he nearly fainted and swayed from side to side when the Judge scolded him.  He had to sit down before the sentence was read out.  He must have believed that he was untouchable.<br /><br />It's just a shame that he wasn't touched with a heavier sentence.  A twenty year sentence would have sent out an even more powerful message.  Still and all, the idea of wearing a prison jumpsuit and eating balogna sandwiches is probably like a life sentence to someone who believed themselves to be above the law.<br /><br />The article claims that many high profile friends petitioned Judge Biggers for leniency when sentencing Scruggs.  He's lucky I am not the warden at his jail.  I think he would be a perfect candidate for the toilet cleaning squad.          <br /></span><div class="blogger-post-footer">Visit Sexton Executive Security at www.sextonsecurity.com</div>]]></content:encoded>
      <pubDate>Sun, 29 Jun 2008 12:05:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/wrong judge">wrong judge</category>
      <category domain="http://securityratty.com/tag/judge">judge</category>
      <category domain="http://securityratty.com/tag/bribe judge">bribe judge</category>
      <category domain="http://securityratty.com/tag/richerd scruggs">richerd scruggs</category>
      <category domain="http://securityratty.com/tag/scruggs">scruggs</category>
      <category domain="http://securityratty.com/tag/sentence">sentence</category>
      <category domain="http://securityratty.com/tag/famous">famous</category>
      <category domain="http://securityratty.com/tag/heavier sentence">heavier sentence</category>
      <category domain="http://securityratty.com/tag/life sentence">life sentence</category>
      <source url="http://www.thebulletproofblog.com/2008/06/even-rich-and-famous-pay-price-for.html">Even the Rich and Famous pay the price for being Dishonest and Unethical</source>
    </item>
    <item>
      <title><![CDATA[Errant email exposed Department of Consumer Affairs personal information]]></title>
      <link>http://securityratty.com/article/ca6f5be22b8296dc3dbda7041339d863</link>
      <guid>http://securityratty.com/article/ca6f5be22b8296dc3dbda7041339d863</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/23/08

Organization
State of California

Contractor/Consultant/Branch
Department of Consumer Affairs

Victims
employees, contractors and board members...]]></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/caldca.jpg" width="169" align="right" height="65"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/23/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.ca.gov/">State of California</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.dca.ca.gov/">Department of Consumer Affairs</a><br><br><span style="font-weight: bold;">Victims:</span><br>"employees, contractors and board members"<br><br><span style="font-weight: bold;">Number Affected:</span><br>5,000<br><br><span style="font-weight: bold;">Types of Data:</span><br>Names, Social Security numbers, salaries and job titles<br><br><span style="font-weight: bold;">Breach Description:</span><br>"The state Department of Consumer Affairs (DCA) has sent letters to 5,000 employees, contractors and board members warning them of a security breach that has compromised their names and social security numbers. "<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.capitolweekly.net/article.php?_adctlid=v%7Cjq2q43wvsl855o%7Cx7o1tt8kp1c3g5&amp;issueId=x79xdv8us2oeyp&amp;xid=x7csom3a3og08k">Capitol Weekly</a> <br><a href="http://www.centralvalleybusinesstimes.com/stories/001/?ID=9111">Central Valley Business Times</a> <br><a href="http://www.pogowasright.org/article.php?story=20080624114400847">Props to PogoWasRight</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Malcolm Maclachlan, Capitol Weekly<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>The state Department of Consumer Affairs (DCA) has sent letters to 5,000 employees, contractors and board members warning them of a security breach that has compromised their names and social security numbers.<br><br>About 2,800 of the people on the list are current, full-time employees of the DCA.<br><br>The document also included some former employees and numerous contractors, such as people who proctor state job examinations.<br><br>The rest of the names were employees and board members of the 56 professional boards and bureaus administered by the DCA, such as the Bureau of Automotive Repair and the Medical Board.<br><br>The breach occurred on June 5 or 6 when a Microsoft Word document was improperly transmitted electronically outside of the department, said DCA spokesman Russ Heimerich.<br><br>The document also contained the salaries and titles of everyone on the list, but Heimerich noted that this was public information.<br><br>"The thing that is troubling to us is that information was coupled with their social security numbers," Heimerich said.<br><span style="font-style: italic;">[Evan] Troubling to you?&nbsp; It's probably hard for the victims to have much sympathy.</span><br><br>The main danger with giving away a social security number is that it can be used to set up new credit cards, loans or purchases in someone's name.<br><br>However, a thief would generally need other information that was not included and could be harder to get, such as addresses, phone numbers and driver's license numbers.<br><span style="font-style: italic;">[Evan] Addresses and phone numbers are usually pretty easy to obtain and I would think are much easier to get than Social Security numbers.&nbsp; Unless of course, somebody emails them to you.</span><br><br>The DCA is the main state agency charged with protecting consumers in California.<br><span style="font-style: italic;">[Evan] Ironic.</span><br><br>From 2003 to 2007, it also housed the office charged with educating consumers and businesses about identity theft and fraud.<br><span style="font-style: italic;">[Evan] More Ironic</span><br><br>One agency whose employees were not on the list is the California Office of Privacy Protection (OPP).<br><br>Heimerich said the incident is still being investigated, and that he could not disclose who had received the document.<br><br>He said that so far there is no evidence that any information has been used. It was not even clear the recipient had opened the document.<br><br>"We know that it left the building and that it wound up somewhere it shouldn't have wound up," Heimerich. "We're looking into how that happened."<br><br>“We kind of know where it was sent,” Mr. Heimerich says<br><span style="font-style: italic;">[Evan] Sounds obvious, but did anyone check "Sent Items"?&nbsp; Yeah, probably.&nbsp; Seriously though, does the California DCA not log email sends and receives?&nbsp; It's hard to believe that the sender does not recall to whom they sent the email and there is no evidence of where it was sent.</span><br><br>The breach was discovered on Monday, June 9<br><span style="font-style: italic;">[Evan] It took 3 or 4 days for the DCA to discover the breach.</span><br><br>People's whose names were on the list were sent an email the next day and an official letter a week later.<br><span style="font-style: italic;">[Evan] Excellent quick notification.&nbsp; The earlier that a breach is detected and communicated to the data owner, the better.</span><br><br>Heimerich said the DCA will pay for a year of free credit reports and provide fraud insurance of up to $25,000 for everyone on the list.<br><span style="font-style: italic;">[Evan] One year of protection does not adequately protect information that has a lifespan that far exceeds that one year.&nbsp; Most bad guys (or gals) know that the "standard" organization response to a breach includes one year of free credit monitoring/protection, so many of them wait a year to use the information.&nbsp; It is also important to point out that just because a person monitors their credit, does not mean that their identity isn't being used elsewhere.&nbsp; It's a scary thought, but it's a broken system.</span><br><br>He said the DCA had not yet determined how much these protections were going to cost. <br><span style="font-style: italic;">[Evan] You can estimate the cost yourself.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>I like how Microsoft Outlook helps me when I am typing an email address in the "To:" field of my email.&nbsp; It saves me some keystrokes and a few precious seconds.&nbsp; Sometimes I am in such a hurry that I don't even notice that Outlook put in the wrong email address.&nbsp; I type my email, click send and away I go onto another task.&nbsp; A couple of days later, I get a call from a customer asking where their information is.&nbsp; I state that I sent it to them a couple of days ago, but they claim to have never gotten my email.&nbsp; I look through my sent items, and HOLY #*@^!&nbsp; I just sent some confidential (sensitive and potentially damaging) information to a competitor instead of my customer.<br><br>Sound conceivable?&nbsp; Have you ever sent an embarrassing email to the wrong person?&nbsp; It is very easy to do if your not paying attention.<br><br>There are a number of controls us information security guys can put in place to reduce the risk of this happening.&nbsp; One of the best is information security training and awareness (kind of an administrative control). <br><br><span style="font-weight: bold;">Past Breaches:</span><br><span style="font-weight: bold;">State of California:</span><br>March, 2008 - <a href="http://breachblog.com/2008/03/31/caldoc.aspx">San Quentin visitor and volunteer information lost</a> </font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/06/24/caldca.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 24 Jun 2008 13:51:19 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/email">email</category>
      <category domain="http://securityratty.com/tag/volunteer information lost">volunteer information lost</category>
      <category domain="http://securityratty.com/tag/wrong email address">wrong email address</category>
      <category domain="http://securityratty.com/tag/email address">email address</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/adequately protect information">adequately protect information</category>
      <category domain="http://securityratty.com/tag/credit cards">credit cards</category>
      <category domain="http://securityratty.com/tag/credit">credit</category>
      <source url="http://breachblog.com/2008/06/24/caldca.aspx">Errant email exposed Department of Consumer Affairs personal information</source>
    </item>
    <item>
      <title><![CDATA[Petroleum Wholesale charged with exposing customers]]></title>
      <link>http://securityratty.com/article/1e0eee4c18853dda51b902995e1d952a</link>
      <guid>http://securityratty.com/article/1e0eee4c18853dda51b902995e1d952a</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/19/08

Organization
Petroleum Wholesale, L. P

Contractor/Consultant/Branch
None

Victims
Customers

Number Affected
Unknown

Types of Data
sensitive...]]></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/pw.jpg" width="200" align="right" height="93"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/19/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.petroleumwholesale.com/sunmart.web/homepage.html">Petroleum Wholesale, L. P.</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>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>"sensitive personal information, including Social Security numbers, bank account numbers, and credit or debit card information"<br><br><span style="font-weight: bold;">Breach Description:</span><br>”HOUSTON -- Petroleum Wholesale, which operated Sunmart Travel Centers and Convenience Stores in 10 states, was charged by the Texas Attorney General of improperly disposing of customer records"<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.hcnonline.com/site/news.cfm?newsid=19788139&amp;BRD=1574&amp;PAG=461&amp;dept_id=532238&amp;rfi=6">The Pasadena Citizen</a> <br><a href="http://www.khou.com/news/local/crime/stories/khou080619_jj_storeid.1c30dcf3.html">KHOU-TV Channel 11 News</a> <br><a href="http://www.csnews.com/csn/news/article_display.jsp?vnu_content_id=1003819492">Convenience Store News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The Pasadena Citizen<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>HOUSTON - Texas Attorney General Greg Abbott today charged Houston-based Petroleum Wholesale, L.P., which operates Sunmart Travel Centers &amp; Convenience Stores in 10 states, for exposing its customers to identity theft.<br><br>According to the state's enforcement action, Petroleum Wholesale improperly discarded customer records containing sensitive personal information, including Social Security numbers, bank account numbers, and credit or debit card information.<br><br>"This defendant is charged with failing to protect its customers' sensitive information," Attorney General Abbott said.<br><br>"With more than 20,000 Texas victims each year, identity theft remains one of the nation's fastest-growing crimes. The Office of the Attorney General will continue working to protect Texans from identity theft."<br><br>Investigators with the Office of the Attorney General (OAG) discovered that the company improperly discarded hundreds of customer records in a publicly-accessible trash container outside its former headquarters.<br><span style="font-style: italic;">[Evan] According to information posted on the Petroleum Wholesale web site, "Petroleum Wholesale services more than 350 retail locations throughout ten states."&nbsp; This breach has the potential to affect many, many people.</span><br><br>According to investigators, the records included sales receipts with customers' names and full credit or debit card numbers with expiration dates.<br><br>The records also included returned checks, along with forms listing customers' names, banking routing numbers, driver's license and Social Security numbers.<br><br>The defendant is charged with violating the 2005 Identity Theft Enforcement and Protection Act, which requires the safeguarding and proper destruction of clients' sensitive personal information.<br><br>State law establishes penalties of up to $50,000 per violation of the Act.<br><span style="font-style: italic;">[Evan] This could add up quick.&nbsp; What's a better business decision, a few hundred bucks for a cross-cut shredder and accompanying procedures, or fifty grand per incident?&nbsp; Although, I am not sure that a shredder and procedures are not all that is needed in Petroleum Wholesale's information security program (assuming one exists).</span><br><br>The OAG also charged the company with violating Chapter 35 of the Business and Commerce Code, which requires businesses to develop retention and disposal procedures for their clients' personal information.<br><br>The law provides for civil penalties of up to $500 for each abandoned record.<br><br>For more information about preventing identity theft, contact the Office of the Attorney General at (800) 252-8011 or visit the agency's Web site at <a href="http://www.texasattorneygeneral.gov.<br><br><span">www.texasattorneygeneral.gov.<br><br><span</a> style="font-weight: bold;">Commentary:</span><br>One question that isn't clear from the news reports is whether or not this was a common practice at Petroleum Wholesale.&nbsp; Organizations should take heed of this case.&nbsp; I think actions taken by Mr. Abbott and other State Attorney Generals will only become more frequent.<br><br>I look forward to more information in the future about this case. <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/06/22/pw.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Sun, 22 Jun 2008 17:58:23 +0000</pubDate>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/petroleum wholesale">petroleum wholesale</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/company">company</category>
      <category domain="http://securityratty.com/tag/company improperly">company improperly</category>
      <category domain="http://securityratty.com/tag/improperly">improperly</category>
      <category domain="http://securityratty.com/tag/debit card information">debit card information</category>
      <category domain="http://securityratty.com/tag/debit card">debit card</category>
      <source url="http://breachblog.com/2008/06/22/pw.aspx">Petroleum Wholesale charged with exposing customers</source>
    </item>
    <item>
      <title><![CDATA[Another brick in the wall to limit blogging]]></title>
      <link>http://securityratty.com/article/938d64252078beb3e8e96d82052b0dc3</link>
      <guid>http://securityratty.com/article/938d64252078beb3e8e96d82052b0dc3</guid>
      <description><![CDATA[First it was the EU looking at passing a law that would require bloggers to disclose their identity and affiliation. Now the AP is looking to enforce a new license that would require payments when a...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p><a onclick="window.open(this.href, '_blank', 'width=300,height=300,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false" href="http://www.stillsecureafteralltheseyears.com/.shared/image.html?/photos/uncategorized/2008/06/17/brick_in_the_wall.jpg"><img title="Brick_in_the_wall" height="200" alt="Brick_in_the_wall" src="http://www.stillsecureafteralltheseyears.com/ashimmy/images/2008/06/17/brick_in_the_wall.jpg" width="200" border="0" style="FLOAT: left; MARGIN: 0px 5px 5px 0px" /></a> First it was the <a href="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/06/eu-bloggers-und.html">EU looking at passing a law</a> that would require bloggers to disclose their identity and affiliation. Now the <a class="zem_slink" title="Associated Press" href="http://ap.org/" rel="homepage">AP</a> is looking to enforce a new license that would require payments when a blogger puts an excerpt from an AP article in their blog.&nbsp; My friend <a href="http://www.crn.com/software/208700252">Kevin McLaughlin blogged on this over at Channel Web blog</a> today. Basically the AP says that if you excerpt more than 5 words you need to start paying them fees.&nbsp; Kevin reached out to me and I gave him my views on this one.</p>

<p>I think that it is a really short sighted move by the AP.&nbsp; First of all it shows they really don't understand blogging.&nbsp; Blogging is about taking an idea which often comes from another source and putting the bloggers own spin and ideas behind it. In this way topics are built on one blog at a time with each blogger adding a bit more to the conversation. Each additional blog on topic enriches those blogs and articles that preceded it.&nbsp; As I said in the Channel Web article, it is like a jazz musician playing a riff on top of a line already laid down.</p>

<p>In real terms blogging on the AP content will only generate more views and interest in the AP content.&nbsp; AP is just a dinosaur with this type of view and will soon go the way of dinosaurs if they try to enforce this. In the meantime bloggers can talk about an AP article, but don't link to it and don't excerpt from it. I suspect that the next thing is we will have a replay of the inbound links litigation we had 8 years ago.&nbsp; In the meantime blogging will continue to march on with AP or not. </p>

<fieldset class="zemanta-related"><legend>Related articles</legend><ul class="zemanta-article-ul"><li class="zemanta-article-ul-li"><a title="Open in new window" href="http://www.marketingvox.com/ap-blogging-group-to-create-unified-guidelines-039294/?camp=rssfeed&amp;src=mv&amp;type=textlink">AP, Blogging Group to Create Unified Guidelines</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://www.socialmediatoday.com/SMC/37470">AP to Restrict Content Use on Blogs</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://billhobbs.com/2008/06/bet_on_the_bloggers.html">Bet on the Bloggers</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://www.paidcontent.org/entry/419-ap-wants-change-in-blog-excerpting-just-not-sure-what/">AP Wants Change In Blog Excerpting, Just Not Sure What</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://www.dailykos.com/storyonly/2008/6/16/145135/241">AP's clash with bloggers, fair use</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://techdirt.com/articles/20080616/0635571413.shtml">Associated Press Digs Its Own Grave Deeper; Wants To Create Its Own Fair Use Rules</a> [via Zemanta]</li></ul></fieldset> <div class="zemanta-pixie" style="MARGIN-TOP: 10px; HEIGHT: 15px"><a class="zemanta-pixie-a" title="Zemified by Zemanta" href="http://reblog.zemanta.com/zemified/41559f22-3b30-4fc0-8281-96493f59c454/"><img class="zemanta-pixie-img" alt="Zemanta Pixie" src="http://img.zemanta.com/reblog_a.png?x-id=41559f22-3b30-4fc0-8281-96493f59c454" style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; FLOAT: right; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none" /></a></div></div>
]]></content:encoded>
      <pubDate>Tue, 17 Jun 2008 20:36:22 +0000</pubDate>
      <category domain="http://securityratty.com/tag/meantime">meantime</category>
      <category domain="http://securityratty.com/tag/channel web blog">channel web blog</category>
      <category domain="http://securityratty.com/tag/meantime bloggers">meantime bloggers</category>
      <category domain="http://securityratty.com/tag/blog">blog</category>
      <category domain="http://securityratty.com/tag/bloggers">bloggers</category>
      <category domain="http://securityratty.com/tag/zemanta">zemanta</category>
      <category domain="http://securityratty.com/tag/additional blog">additional blog</category>
      <category domain="http://securityratty.com/tag/channel web article">channel web article</category>
      <category domain="http://securityratty.com/tag/require bloggers">require bloggers</category>
      <source url="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/06/another-brick-i.html">Another brick in the wall to limit blogging</source>
    </item>
    <item>
      <title><![CDATA[Another brick in the wall to limit blogging]]></title>
      <link>http://securityratty.com/article/7e611d432f89d17bbd84446e9ed804d5</link>
      <guid>http://securityratty.com/article/7e611d432f89d17bbd84446e9ed804d5</guid>
      <description><![CDATA[First it was the EU looking at passing a law that would require bloggers to disclose their identity and affiliation. Now the AP is looking to enforce a new license that would require payments when a...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p><a onclick="window.open(this.href, '_blank', 'width=300,height=300,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false" href="http://www.stillsecureafteralltheseyears.com/.shared/image.html?/photos/uncategorized/2008/06/17/brick_in_the_wall.jpg"><img title="Brick_in_the_wall" height="200" alt="Brick_in_the_wall" src="http://www.stillsecureafteralltheseyears.com/ashimmy/images/2008/06/17/brick_in_the_wall.jpg" width="200" border="0" style="FLOAT: left; MARGIN: 0px 5px 5px 0px" /></a> First it was the <a href="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/06/eu-bloggers-und.html">EU looking at passing a law</a> that would require bloggers to disclose their identity and affiliation. Now the <a class="zem_slink" title="Associated Press" href="http://ap.org/" rel="homepage">AP</a> is looking to enforce a new license that would require payments when a blogger puts an excerpt from an AP article in their blog.&nbsp; My friend <a href="http://www.crn.com/software/208700252">Kevin McLaughlin blogged on this over at Channel Web blog</a> today. Basically the AP says that if you excerpt more than 5 words you need to start paying them fees.&nbsp; Kevin reached out to me and I gave him my views on this one.</p>

<p>I think that it is a really short sighted move by the AP.&nbsp; First of all it shows they really don't understand blogging.&nbsp; Blogging is about taking an idea which often comes from another source and putting the bloggers own spin and ideas behind it. In this way topics are built on one blog at a time with each blogger adding a bit more to the conversation. Each additional blog on topic enriches those blogs and articles that preceded it.&nbsp; As I said in the Channel Web article, it is like a jazz musician playing a riff on top of a line already laid down.</p>

<p>In real terms blogging on the AP content will only generate more views and interest in the AP content.&nbsp; AP is just a dinosaur with this type of view and will soon go the way of dinosaurs if they try to enforce this. In the meantime bloggers can talk about an AP article, but don't link to it and don't excerpt from it. I suspect that the next thing is we will have a replay of the inbound links litigation we had 8 years ago.&nbsp; In the meantime blogging will continue to march on with AP or not. </p>

<fieldset class="zemanta-related"><legend>Related articles</legend><ul class="zemanta-article-ul"><li class="zemanta-article-ul-li"><a title="Open in new window" href="http://www.marketingvox.com/ap-blogging-group-to-create-unified-guidelines-039294/?camp=rssfeed&amp;src=mv&amp;type=textlink">AP, Blogging Group to Create Unified Guidelines</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://www.socialmediatoday.com/SMC/37470">AP to Restrict Content Use on Blogs</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://billhobbs.com/2008/06/bet_on_the_bloggers.html">Bet on the Bloggers</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://www.paidcontent.org/entry/419-ap-wants-change-in-blog-excerpting-just-not-sure-what/">AP Wants Change In Blog Excerpting, Just Not Sure What</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://www.dailykos.com/storyonly/2008/6/16/145135/241">AP's clash with bloggers, fair use</a> [via Zemanta] </li>

<li class="zemanta-article-ul-li"><a title="Open in new window" href="http://techdirt.com/articles/20080616/0635571413.shtml">Associated Press Digs Its Own Grave Deeper; Wants To Create Its Own Fair Use Rules</a> [via Zemanta]</li></ul></fieldset> <div class="zemanta-pixie" style="MARGIN-TOP: 10px; HEIGHT: 15px"><a class="zemanta-pixie-a" title="Zemified by Zemanta" href="http://reblog.zemanta.com/zemified/41559f22-3b30-4fc0-8281-96493f59c454/"><img class="zemanta-pixie-img" alt="Zemanta Pixie" src="http://img.zemanta.com/reblog_a.png?x-id=41559f22-3b30-4fc0-8281-96493f59c454" style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; FLOAT: right; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none" /></a></div></div>

<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=xhThfi"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=xhThfi" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=DAozrI"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=DAozrI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=CTEbYI"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=CTEbYI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=XuZl8I"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=XuZl8I" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=xe0kiI"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=xe0kiI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=zkNEvi"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=zkNEvi" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=HIYt0i"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=HIYt0i" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/314331248" height="1" width="1"/>]]></content:encoded>
      <pubDate>Tue, 17 Jun 2008 19:43:03 +0000</pubDate>
      <category domain="http://securityratty.com/tag/meantime">meantime</category>
      <category domain="http://securityratty.com/tag/channel web blog">channel web blog</category>
      <category domain="http://securityratty.com/tag/meantime bloggers">meantime bloggers</category>
      <category domain="http://securityratty.com/tag/blog">blog</category>
      <category domain="http://securityratty.com/tag/bloggers">bloggers</category>
      <category domain="http://securityratty.com/tag/zemanta">zemanta</category>
      <category domain="http://securityratty.com/tag/additional blog">additional blog</category>
      <category domain="http://securityratty.com/tag/channel web article">channel web article</category>
      <category domain="http://securityratty.com/tag/require bloggers">require bloggers</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/314331248/another-brick-i.html">Another brick in the wall to limit blogging</source>
    </item>
    <item>
      <title><![CDATA[Loving customers frustrate security firms too]]></title>
      <link>http://securityratty.com/article/90258e9f33623bc8f6064f70d8abd5d6</link>
      <guid>http://securityratty.com/article/90258e9f33623bc8f6064f70d8abd5d6</guid>
      <description><![CDATA[Roger Grimes has a good article up on his InfoWorld, Security Advisory blog entitled &quot; Security firms frustrate loving customers &quot;. Roger details some specific examples of how security vendors just...]]></description>
      <content:encoded><![CDATA[<p>Roger Grimes has a good article up on his InfoWorld, Security Advisory blog entitled "<a href="http://weblog.infoworld.com/securityadviser/archives/2008/06/security_firms.html">Security firms frustrate loving customers</a>". Roger details some specific examples of how security vendors just don't "show the love" to customers and prospective customers, with the result being lost business. Roger highlights three examples: <br><br><strong>1.</strong> <strong>Making renewals a manual process with those annoying phone trees</strong>. I agree, when I hear the press 1 for this and press 2 for this, my blood starts to boil. There is no reason that this just can't be built into the product to renew over the web. Security or no, any software vendor not doing it this is just plain crazy.<br><strong><br>2. Calling into a company with a sales inquiry and the sales guy never calls back</strong>. This one just kills me. When doing due diligence on potential acquisitions at a prior company I would call in or email with a sales inquiry and wait to see how long it would take for them to get back to me. It was a good indication of how well the sales organization and company functioned.<br><br><strong>3. Killing the deal with one sided, overly legal and burdensome terms</strong>. Another one that I battle all the time. The CFO has to be able to recognize revenue so needs specific T&amp;Cs. The lawyers want to protect the vendor against all eventualities and is doing his job. You want to make as few warranties and representations as possible to limit your liability. The result, the customer gets one sided, unfair document with fine print on maintenance pricing, renewals, SLAs, etc. Most customers don't even read the EULA. Take a lot at some of the ones with software you have bought. It may surprise you.<br><br>But in my best Fox News voice, lets be fair and balanced. So in that vein, let me give you 3 specific examples of how loving customers frustrate security firms:<br><br><strong>1. The guys who picked the product leave and the new guy comes in and doesn't have a clue.</strong> This happens all the time, especially in the government. One guy or team buys the product for a specific reason and has all of the expertise. The new folks come in and even if they know your product is there, they don't know why or how to use it. They may feel they inherited this product and have their own favorite product in this category. They can't wait to replace you and either don't use the product at all or blame the problems of the world on it.<br><br><strong>2. Buying the product and than "other priorities" delay implementation.</strong> A surefire recipe for shelfware. When I see this happening I tell our folks better to be a pain in the butt and force them to use the product they bought than to sit around watching the license expire on the shelf. The longer the product sits, the more it becomes a nice to have, rather than a must have, that drove the sale. Now sure, one can say that what does the vendor care, the customer paid. If he doesn't use it, less support costs. But you don't get renewals, you don't get upsells or referrals without customers using product.<br><strong><br>3. Using the product in unintended ways.</strong> Another favorite heartburn of mine. Customers figure just because the application runs Linux underneath, why can"t I run (You Name It). We recently had a customer that was chewing up support hours like the dial at a gas pump today. It turns out the problems we all due to the all of the other software that he had put on the box, not to mention editing .conf files, database tables, etc. It is hard enough supporting the software we developed. It is a whole another story supporting software that you have written.<br><br>So Roger, yes the customer is always right and security vendors have to get their act together if they want to survive, let alone compete in these tough economic times. But customers certainly don't make the job any easier with some of the shenanigans they pull.</p>
<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=zkXRhU"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=zkXRhU" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=Lqo4nI"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=Lqo4nI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=SmwKYI"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=SmwKYI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=nQ1xDI"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=nQ1xDI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=23iD7I"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=23iD7I" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=ewSG9i"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=ewSG9i" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=axWNoi"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=axWNoi" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/311509491" height="1" width="1"/>]]></content:encoded>
      <pubDate>Fri, 13 Jun 2008 15:45:37 +0000</pubDate>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/security firms">security firms</category>
      <category domain="http://securityratty.com/tag/customers">customers</category>
      <category domain="http://securityratty.com/tag/product">product</category>
      <category domain="http://securityratty.com/tag/product sits">product sits</category>
      <category domain="http://securityratty.com/tag/favorite product">favorite product</category>
      <category domain="http://securityratty.com/tag/prospective customers">prospective customers</category>
      <category domain="http://securityratty.com/tag/software vendor">software vendor</category>
      <category domain="http://securityratty.com/tag/vendor">vendor</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/311509491/loving-customer.html">Loving customers frustrate security firms too</source>
    </item>
    <item>
      <title><![CDATA[Personal information found in Boca Raton dumpsters]]></title>
      <link>http://securityratty.com/article/71b6542daf7a2738ad171ba74ac33144</link>
      <guid>http://securityratty.com/article/71b6542daf7a2738ad171ba74ac33144</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/4/08

Organization
Wheeler's Moving Company

Contractor/Consultant/Branch
None

Victims
Employees, job applicants and customers

Number Affected...]]></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/nodiving.jpg" align="right" height="175" width="107"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/4/08<br><br><span style="font-weight: bold;">Organization: </span><br>Wheeler's Moving Company<br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>None<br><br><span style="font-weight: bold;">Victims:</span><br>Employees, job applicants and customers<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>"files containing driver's licenses, social security numbers, telephone numbers, addresses and birth dates"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"BOCA RATON, FL (Fox29) - Piles and piles of personal files with tax information, social security numbers and license numbers, were found in a Boca Raton dumpster. These dumpsters are located between a set of warehouses here on Northwest First Avenue."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.wflxfox29.com/Global/story.asp?S=8416813">WFLX Fox 29 News</a> <br><a href="http://www.cbs12.com/news/says_4707977___article.html/building_owner.html">WPEC Channel 12 News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Chuck Weber, WFLX Fox 29 News<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>BOCA RATON, FL (Fox29) - Piles and piles of personal files with tax information, social security numbers and license numbers, were found in a Boca Raton dumpster.<br><br>Dumpsters on Northwest 1st Avenue Boca Raton were found full of files and paperwork with personal information - names, addresses, drivers licenses and some social security numbers - all out in the open for the taking.<br><span style="font-style: italic;">[Evan] I think we would be surprised at how common it is for organizations to throw confidential information in the garbage (instead of shredding).&nbsp; Unauthorized disclosure of confidential information including personal information, trade secrets, intellectual property, draft press releases, etc. can be very damaging.</span><br><br>The dumped personal records inside, apparently belonged to Wheeler's Moving Company. <br><br>containing information on employees or job applicants, and some customers<br><br>Some files even dated back as far as 20 years or more.<br><br>After contacting the Wheeler's Moving Company, they claimed to have moved out of Boca Raton and into Jupiter about a year ago and they had no idea this had happened. <br><br>Building owner Charles Wheeler, former owner of the moving company, says, "In my heart I don't think it's going to be a problem. And I didn't realize until I heard from you guys that there was something sensitive in there. And it should have never been thrown out."<br><br>Wheeler says he didn't think any sensitive documents were still inside.<br><span style="font-style: italic;">[Evan] A complete lack of awareness.&nbsp; Business owners and leaders (everyone really) need to be more aware of the security implications involving the information they create, collect, use, store, and discard.&nbsp; Thieves are.</span><br><br>Police received a call Monday, and were able to clean up a majority of this dumpster.<br><br>There are currently some remnants of the files out there, but officials are doing their best to protect the people on these files so their identities are not stolen and get these files and papers shredded properly.<br><br>all the documents have since been shredded.<br><br>Wheeler says from now on, he will shred all unneeded documents.<br><br><span style="font-weight: bold;">Victim Reaction:</span><br>"I'm taken aback; I really almost shaking. The fact that records could be around for all these years,"<br><br>"It shouldn't have been available to anybody, but nobody has done anything."<br><br>"It's very frightening to think of that it was available, and that it could have happened,"<br><br><span style="font-weight: bold;">Commentary:</span><br>I feel bad for small business owners that aren't aware of or properly trained in risk management and information security.&nbsp; It's easy to be angry with them, but too many of them just don't know any better.&nbsp; <br><br>Obviously, I feel bad for the victims too.<br><br></font><font size="2"><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/06/10/wheelers.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 10 Jun 2008 06:24:10 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/boca raton">boca raton</category>
      <category domain="http://securityratty.com/tag/dumpster">dumpster</category>
      <category domain="http://securityratty.com/tag/boca raton dumpster">boca raton dumpster</category>
      <category domain="http://securityratty.com/tag/confidential information">confidential information</category>
      <category domain="http://securityratty.com/tag/files">files</category>
      <category domain="http://securityratty.com/tag/personal files">personal files</category>
      <category domain="http://securityratty.com/tag/owner charles wheeler">owner charles wheeler</category>
      <source url="http://breachblog.com/2008/06/10/wheelers.aspx">Personal information found in Boca Raton dumpsters</source>
    </item>
    <item>
      <title><![CDATA[Know the Difference Between a NAC Client and a 1X Supplicant]]></title>
      <link>http://securityratty.com/article/adf59ca50b712d79b7d1031b80a28400</link>
      <guid>http://securityratty.com/article/adf59ca50b712d79b7d1031b80a28400</guid>
      <description><![CDATA[Now that weve started implementing NAC solutions with 802.1X, we (as an industry) have muddied the lines between the two technologies and even the software involved
Understanding the difference...]]></description>
      <content:encoded><![CDATA[<p>Now that we&#8217;ve started implementing NAC solutions with 802.1X, we (as an industry) have&nbsp;muddied the lines between the two technologies and even the software involved. </p><p>Understanding the difference between a NAC Client and an 802.1X Supplicant can save you much time, confusion and - yes - MONEY. </p><p><strong>How does it save money</strong>? I figured most of you would glob on to that one first- hang on, I&#8217;ll get to it in a minute ;). </p><p><span class="sizeGreater20"><strong>NAC Clients.</strong></span> Most network-based NAC vendors, such as <a class="offsite-link-inline" href="http://www.cisco.com/" target="_blank"><u>Cisco</u></a>, <a class="offsite-link-inline" href="http://www.juniper.com/" target="_blank"><u>Juniper</u></a>, <a class="offsite-link-inline" href="http://www.stillsecure.com/" target="_blank"><u>StillSecure</u></a> and <a class="offsite-link-inline" href="http://www.procurve.com/" target="_blank"><u>ProCurve</u></a> have some type of NAC Client or Endpoint Integrity Agent provided as part of their NAC solution. The NAC Client is a software agent that sits on the endpoint and collects statement of health or posture of the endpoint and communicates that back to whatever NAC controller you&#8217;re using.&nbsp;(Most of these guys offer some type of agent-less or transient-agent posture checking too, but this doesn&#8217;t apply here.) </p><p>The NAC Client may also provide additional security functions such as host enforcement or it may serve as an encryption termination point for IPSec tunnels created between the endpoint and a firewall, for example. I&#8217;m sure we&#8217;ll be seeing more and more bells and whistles added to the NAC Clients as time goes by. </p><p><strong><span class="sizeGreater20">802.1X Supplicant.</span> </strong>An 802.1X supplicant is a different creature all together. First of all, it&#8217;s worth noting a supplicant can exist as a piece of software on an endpoint, or as part of an infrastructure device, including switches, APs and even printers. On an infrastructure device, the built-in supplicant lets us do things like authenticate switches to one another for maintaining integrity of network devices and prevent rogues from joining the network. </p><p>If the supplicant is on a PC or laptop, it may be built in to the operating system, or provided as a 3rd party software. The supplicant is what communicates through the switches to the RADIUS server for authentication and &#8216;speaks EAP&#8217;. EAP, the Extensible Authentication Protocol, is what makes 1X. Generally a supplicant&#8217;s only function in life is to speak EAP and get the device authenticated to the network. </p><p>What you may see from some vendors, such as Juniper, is an <strong>integrated NAC Client with a built-in Supplicant</strong>. Juniper&#8217;s Odyssey Client bundles both functions in to 1 agent. </p><p><strong>Okay, so back to the money&#8230;</strong> Understanding what does what, and what comes from where is helpful when we start talking dollars. In many cases you&#8217;ll end up paying separately for the NAC Client licenses and the Supplicant licenses. You won&#8217;t have to pay for both if&#8230; </p><ol><li><div>If the NAC Client and Supplicant are bundled</div></li><li><div>If you&#8217;re using the Supplicant integrated with the OS or&nbsp;</div></li><li><div>If you&#8217;re using an open source Supplicant</div></li><li><div>If you&#8217;re not 802.1X with your NAC, and of course</div></li><li><div>If you&#8217;re not using NAC on top of 802.1X</div></li></ol><p>Some vendors may offer a pricing advantage depending on what you&#8217;re planning to do. We started with two main Supplicants a few years ago- <strong>Meetinghouse&#8217;s Aegis</strong>&nbsp;and <strong>Funk&#8217;s Odyssey Access Client</strong>. What happened to those guys? <strong>Cisco</strong> bought Meetinghouse and now offers the Aegis client as an option with their solution and <strong>Juniper</strong> bought Funk and integrated the Odyssey Access Client directly into their endpoint integrity agent. Most likely they want to try and recoup some of the money from those acquisitions, so what that means for you is that <strong>you will likely pay money</strong> for products containing those technologies. </p><p>On the other hand, some of the home-grown technology from the NAC side may lessen the budget burden. Cisco&#8217;s endpoint integrity agent is actually included with their NAC solution, so they don&#8217;t charge any per-seat fee (unless you add 802.1X). Juniper&#8217;s is integrated, so you&#8217;re getting both functions regardless. You can probably spot companies that OEM another solution or another client if they charge for the NAC Client license&#8230; that&#8217;s not definite, but a good rule of thumb. </p><p><strong>From a deployment perspective</strong> an bundled agent (NAC + 1X)&nbsp;is nice, since it means you only need to download 1 piece of &#8216;thing&#8217; onto the endpoint. <strong>From a budget persepctive</strong> it can be good or bad- it really depends on how many licenses you need and how willing your vendor is to work with you on price. </p><p># # #</p>
]]></content:encoded>
      <pubDate>Thu, 05 Jun 2008 13:01:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/client">client</category>
      <category domain="http://securityratty.com/tag/nac client license">nac client license</category>
      <category domain="http://securityratty.com/tag/nac">nac</category>
      <category domain="http://securityratty.com/tag/nac client licenses">nac client licenses</category>
      <category domain="http://securityratty.com/tag/nac solution">nac solution</category>
      <category domain="http://securityratty.com/tag/nac client">nac client</category>
      <category domain="http://securityratty.com/tag/supplicant">supplicant</category>
      <category domain="http://securityratty.com/tag/licenses">licenses</category>
      <category domain="http://securityratty.com/tag/supplicant licenses">supplicant licenses</category>
      <source url="http://www.securityuncorked.com/security-uncorked/2008/6/5/know-the-difference-between-a-nac-client-and-a-1x-supplicant.html">Know the Difference Between a NAC Client and a 1X Supplicant</source>
    </item>
    <item>
      <title><![CDATA[Starbucks, AT&T Brick Loyalty Card Service Launch]]></title>
      <link>http://securityratty.com/article/7b29ed98f6b523f87ff75c3ab5bf5ff6</link>
      <guid>http://securityratty.com/article/7b29ed98f6b523f87ff75c3ab5bf5ff6</guid>
      <description><![CDATA[Starbucks, AT&amp;T biff day one of the card loyalty program: After several hours of occasional attempts to register my Starbucks Card (actually, two) with the company for free Wi-Fi and other rewards,...]]></description>
      <content:encoded><![CDATA[<p><a href="http://flickr.com/photos/matt-davis/2045538813/"><img src="http://wifinetnews.com//images/2008/coffee_stain.jpg" alt="coffee_stain.jpg" border="0" width="150" height="100" align="right" hspace="5" /><a href="https://www.starbucks.com/cardrewards/"></a><strong>Starbucks, AT&T biff day one of the card loyalty program:</strong></a> After several hours of occasional attempts to register my Starbucks Card (actually, two) with the company for free Wi-Fi and other rewards, seeing "Service Unavailable," long delays, errors, and a general failure to accept my card--now there's a message. "Due to overwhelming interest in Card Rewards we are currently experiencing difficulty accessing Starbucks Cards accounts. We are working to fix the problem and ask that you please try again later."</p>

<p>The Card Rewards program allows anyone with a Starbucks Card to register it with Starbucks for freebies, including Wi-Fi. There's an interesting choice (when it worked) where you can select whether to have freebies like free exotic milk options or brewed coffee refills by themselves or with Wi-Fi on top. If you choose Wi-Fi, you're redirected to SBC servers (for nostalgia's sake), at which point everything seems to fall apart.</p>

<p>Trying two separate cards, I was unable to set up an account and get the cards to take. The errors weren't clearly spelled out. Clearly, the system was neither designed to handle demand, nor designed to fail gracefully, blocking users until capacity was available.</p>

<p>For loyal Starbucks patrons, this doesn't come across very well at all.</p>

<p><span class="posted">[<a href="http://flickr.com/photos/matt-davis/2045538813/">Photo by Matt Davis</a>. Used under <a href="http://creativecommons.org/licenses/by-sa/2.0/deed.en">Creative Commons license</a>.]</span></p>]]></content:encoded>
      <pubDate>Tue, 03 Jun 2008 09:34:56 +0000</pubDate>
      <category domain="http://securityratty.com/tag/starbucks">starbucks</category>
      <category domain="http://securityratty.com/tag/card">card</category>
      <category domain="http://securityratty.com/tag/card rewards program">card rewards program</category>
      <category domain="http://securityratty.com/tag/card rewards">card rewards</category>
      <category domain="http://securityratty.com/tag/starbucks cards accounts">starbucks cards accounts</category>
      <category domain="http://securityratty.com/tag/cards">cards</category>
      <category domain="http://securityratty.com/tag/starbucks card">starbucks card</category>
      <category domain="http://securityratty.com/tag/rewards">rewards</category>
      <category domain="http://securityratty.com/tag/choose wi-fi">choose wi-fi</category>
      <source url="http://wifinetnews.com/archives/008340.html">Starbucks, AT&amp;T Brick Loyalty Card Service Launch</source>
    </item>
  </channel>
</rss>
