<?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: sloppy]]></title>
    <link>http://securityratty.com/tag/sloppy</link>
    <description></description>
    <pubDate>Wed, 28 Nov 2007 12:39:00 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[SSO Summit Day One Morning Session]]></title>
      <link>http://securityratty.com/article/500327e2eca382c04451c330dcc1e875</link>
      <guid>http://securityratty.com/article/500327e2eca382c04451c330dcc1e875</guid>
      <description><![CDATA[I am at the SSO Summit , high in the Colorado mountains (9200 feet elevation to be exact), the I-70 West sign is one of my favorite road signs. Ping Identity has done a great job putting this...]]></description>
      <content:encoded><![CDATA[<div>I am at the <a href="http://www.ssosummit.com/">SSO Summit</a>, high in the Colorado mountains (9200 feet elevation to be exact), the I-70 West sign is one of my favorite road signs. <a href="http://www.pingidentity.com/">Ping Identity</a> has done a great job putting this together. It is the perfect size around 125 people. Most of the best conferences I have been to have been around 60-150 people. There are a *lot* of enterprises involved here. </div><br><div>John Haggard who has an extensive background in SSO and lately is at Passfaces kicked off the sessions with a SSO history talk. Going through a lot of mainframe centric SSO protocols from the 80s and 90s, I am no expert in these areas and it was fascinating to see the way things vacillated between strength and weakness of SSO protocols.</div><br><div>A couple of points from the presentation:</div><br><div><blockquote><p>The history of SSO is a story of extreme complexities, compromises, vulnerabilities and unintended consequences.</p></blockquote></div><div><blockquote><br></blockquote></div><div><blockquote><p>SSO is a story of one simple objective - to spin off units of computation work to execute on behalf of an authenticated user without requiring the original user's password.</p></blockquote></div><div><blockquote><br></blockquote></div><div><blockquote><p>Phishing has always been completely avoidable</p></blockquote></div><br><div>He went through the various incarnations of mainframe SSO from logon id through things like ACF2, VTAM Session managers, terminal emulators, multiplatform access to web access through facades. The implication he drew from this last step are well worth repeating: "Time to rethink everything." Problem is - of course, people don't rethink, they put MQ Series in front of the mainframe and hook a web app in front of that and go. </div><br><div>Finally, he connected some interesting dots to SAML and SOA security issues. </div><br><div><blockquote><p>SSO without strong auth is and always will be simply nuts</p></blockquote></div><div><blockquote><br></blockquote></div><div><blockquote><p>SAML gets its right</p></blockquote></div><div>His points around common weaknesses in integration in SOA and Web 2.0 technologies for companies that are *not* using SAML were excellent. Of course, I will go into some more details on this tomorrow.</div><br><div>Ping's CTO Patrick Harding took the stage and gave an overview of the next generation of SSO options from Kerberos to present and as is his wont demonstrated various real world strengths and weaknesses, quoted a Gartner analyst (shock!) saying OpenID is the hare and Cardspace is the tortoise. Nice.</div><br><div>Andrew Cameron from GM is speaking now on GM's experiences implementing SSO, and there are a lot of real world lessons learned in his presentation.  Plus my favorite identity architecture, user has Kerberos, services speak SAML. very nice, very scalable. All in all, its my starting point for how to identity in an enterprise. He also spoke about a pet peeve of mine - how to globalize authorization. This is not a problem that vendors have historically attacked with relish. They are very happy to help you solve authentication, but they are perfectly happy to keep their authorization internal either for vendor lock in reasons and/or for sloppy authorization design. This will take a LIberty-esque consortium of enterprises to resolve. </div><br><div>So many conferences are dominated by vendors and consultants who conspire to what I call the "sacred church of things YOU should be doing." Instead this conference is bringing together a great mix of real world in the trenches practitioners who have problems to solve today, with rubber meets the road deployable solutions and an eye towards longer term strategy for SSO and identity.</div>]]></content:encoded>
      <pubDate>Thu, 24 Jul 2008 09:35:02 +0000</pubDate>
      <category domain="http://securityratty.com/tag/sso">sso</category>
      <category domain="http://securityratty.com/tag/sso history talk">sso history talk</category>
      <category domain="http://securityratty.com/tag/sso summit">sso summit</category>
      <category domain="http://securityratty.com/tag/mainframe sso">mainframe sso</category>
      <category domain="http://securityratty.com/tag/sso options">sso options</category>
      <category domain="http://securityratty.com/tag/sso protocols">sso protocols</category>
      <category domain="http://securityratty.com/tag/real world">real world</category>
      <category domain="http://securityratty.com/tag/real world lessons">real world lessons</category>
      <category domain="http://securityratty.com/tag/authorization internal">authorization internal</category>
      <source url="http://1raindrop.typepad.com/1_raindrop/2008/07/sso-summit-day-one-morning-session.html">SSO Summit Day One Morning Session</source>
    </item>
    <item>
      <title><![CDATA[Share, but share insecurely?]]></title>
      <link>http://securityratty.com/article/136cba038e18c6f08a668a0a6ec44029</link>
      <guid>http://securityratty.com/article/136cba038e18c6f08a668a0a6ec44029</guid>
      <description><![CDATA[In all the hoopla about IT admins getting into your stuff , (from the recent Cyber-Ark survey) most folks might have missed this interesting nugget

Majority are sloppy at handling and exchanging...]]></description>
      <content:encoded><![CDATA[In all the hoopla about <a href="http://www.globalsecuritymag.com/Cyber-Ark-s-Survey-reveals-scandal,20080619,3638">IT admins getting into your stuff</a>, (from the recent <a href="http://www.cyber-ark.com/">Cyber-Ark</a> survey) most folks might have missed this interesting nugget...<br /><br /><span style="font-style: italic;">"Majority are sloppy at handling and exchanging sensitive data Seven out of 10 companies rely on out-dated and insecure methods to exchange sensitive data when it comes to passing it between themselves and their business partners with 35% choosing to email sensitive data, 35% sending it via a courier, 22% using FTP and 4% still relying on the postal system. This shouldn’t be any big surprise when you learn that 12% of these senior IT personnel who were interviewed also choose to send cash in the post!</span>"<br /><br />Over 70% of companies share sensitive information within and without in an insecure way! Here we are, locking down data at rest within the company. However, as it leaves the safe haven - it is sent out in the clear!<br /><br />This is where I think a more information-centric approach can help - protect the data rather than the devices and wherever the data goes, the protection follows. A bit like Mary's little lamb, if you get my drift...<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BitArmor1?a=jKiXQI"><img src="http://feeds.feedburner.com/~f/BitArmor1?i=jKiXQI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BitArmor1?a=wirpci"><img src="http://feeds.feedburner.com/~f/BitArmor1?i=wirpci" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BitArmor1?a=YJWEII"><img src="http://feeds.feedburner.com/~f/BitArmor1?i=YJWEII" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/BitArmor1/~4/319671932" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 25 Jun 2008 08:08:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/email sensitive data">email sensitive data</category>
      <category domain="http://securityratty.com/tag/exchange sensitive data">exchange sensitive data</category>
      <category domain="http://securityratty.com/tag/sensitive data">sensitive data</category>
      <category domain="http://securityratty.com/tag/insecure">insecure</category>
      <category domain="http://securityratty.com/tag/recent cyber-ark survey">recent cyber-ark survey</category>
      <category domain="http://securityratty.com/tag/insecure methods">insecure methods</category>
      <category domain="http://securityratty.com/tag/business partners">business partners</category>
      <category domain="http://securityratty.com/tag/companies rely">companies rely</category>
      <source url="http://feeds.feedburner.com/~r/BitArmor1/~3/319671932/share-but-share-insecurely.html">Share, but share insecurely?</source>
    </item>
    <item>
      <title><![CDATA[Data thieves get focused (but buyers get sloppy)]]></title>
      <link>http://securityratty.com/article/9bdde936ee7f425e7fe1928c812f2361</link>
      <guid>http://securityratty.com/article/9bdde936ee7f425e7fe1928c812f2361</guid>
      <description><![CDATA[When it comes to online data theft, credit card numbers and bank account data are so...]]></description>
      <content:encoded><![CDATA[When it comes to online data theft, credit card numbers and bank account data are so 2007.]]></content:encoded>
      <pubDate>Tue, 17 Jun 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/bank account data">bank account data</category>
      <category domain="http://securityratty.com/tag/online data theft">online data theft</category>
      <category domain="http://securityratty.com/tag/credit card">credit card</category>
      <source url="http://www.networkworld.com/news/2008/061808-data-thieves-get-focused-but.html?fsrc=rss-security">Data thieves get focused (but buyers get sloppy)</source>
    </item>
    <item>
      <title><![CDATA[Information Centric Security is dead!]]></title>
      <link>http://securityratty.com/article/dde288653b5dc334f4108a1e5ffeb8de</link>
      <guid>http://securityratty.com/article/dde288653b5dc334f4108a1e5ffeb8de</guid>
      <description><![CDATA[Ok,ok, I just want to jump on the bandwagon. It seems you are not regarded as an innovative and forward thinking Information Security Blogger unless you declare something dead so I will do that with...]]></description>
      <content:encoded><![CDATA[Ok,ok, I just want to jump on the bandwagon. It seems you are not regarded as an innovative and forward thinking Information Security Blogger unless you declare something dead so I will do that with Info-Centric Security.<br /><br />So, what do I elect to replace this with? Process-centric Security.<br /><br />I think that as we get closer to Information Security Nivana (and isn't that what we really want?) we will start to get closer to the point where we look at Business and how it uses Information to do what it does. We define processes, work out what Information is needed, add in resources and voila we have all the information (process, standard, information classification, user details, etc) that we need to properly define and hence secure a process.<br /><br />If this brings back bad memories of Flowcharts and the like then maybe, just maybe, flow charts are what we really need to secure our businesses. Maybe when we decided to throw out all of those tools we had way back when, we did it without thining of the repurcussions. The goal to get a "Fast Company" and "be more adaptable" and "beat our competitors" just made us more sloppy and insecure. It may be a good time now to reassess.<br /><br />And, by the way, Information Centric Security is not really dead... its just part of this larger idea, just like IDS is part of IPS.<img src="http://feeds.feedburner.com/~r/SecurityThoughts/~4/295608709" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 22 May 2008 02:11:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/information security blogger">information security blogger</category>
      <category domain="http://securityratty.com/tag/information centric security">information centric security</category>
      <category domain="http://securityratty.com/tag/information security nivana">information security nivana</category>
      <category domain="http://securityratty.com/tag/information classification">information classification</category>
      <category domain="http://securityratty.com/tag/process-centric security">process-centric security</category>
      <category domain="http://securityratty.com/tag/process">process</category>
      <category domain="http://securityratty.com/tag/dead">dead</category>
      <category domain="http://securityratty.com/tag/define processes">define processes</category>
      <source url="http://feeds.feedburner.com/~r/SecurityThoughts/~3/295608709/information-centric-security-is-dead.html">Information Centric Security is dead!</source>
    </item>
    <item>
      <title><![CDATA[In Passing on DLP]]></title>
      <link>http://securityratty.com/article/3a5afe6f222c255f620d6d4fac61c5bf</link>
      <guid>http://securityratty.com/article/3a5afe6f222c255f620d6d4fac61c5bf</guid>
      <description><![CDATA[Now, I am not some world-famous DLP analyst , but it doesn't mean that I cannot have an opinion on this &quot;searing -warm&quot; :-) security concept: &quot;data leak 'prevention'&quot; or DLP (notice the double quotes...]]></description>
      <content:encoded><![CDATA[<p>Now, I am not some <a href="http://securosis.com/2008/04/17/best-practices-for-dlp-content-discovery-part-3/">world-famous DLP analyst</a>, but it doesn't mean that I cannot have an opinion on this "searing<em>-warm"</em>&nbsp; :-) security concept: "data leak 'prevention'" or DLP (notice the double quotes around prevention...)</p> <p>I admit that in the past I <a href="http://chuvakin.blogspot.com/2007/04/think-accidental-leak-prevention.html">poked jokes at DLP</a> for being "ADLP", with "A" standing for "accidental." Indeed, most of the technology approaches I've seen were "good enough" for preventing accidental leaks (e.g. Excel sheet with SSNs being emailed to an external party by mistake)&nbsp; and for preventing truly idiotic "insider" attacks of the same nature. Whether they sniffed or used desktop agents, the tools were good enough to do the above, but not much more (or, they allowed you to do more, but via a truly <em>ginormous</em> effort by your security team). And then a retarded kindergarten kid can bypass them in his sleep without working up a sweat ...</p> <p>In other words, DLP was for keeping honest (but sloppy) people honest and keeping idiots idiotic (but a bit safer). Which is, don't get me wrong, pretty darn useful: after all, overall, employee mistakes still cause more damage than hackers (!)</p> <p>However, whenever I heard about DLP, I always felt some deeper longing for more - maybe for a technology that CAN actually stop some, clearly defined classes of malicious data theft, perpetrated by non-idiots.</p> <p>What such technology might be? Well, IMHO,&nbsp; it should have three things:</p> <ol> <li><strong>Easy on the end user (=information owner)</strong> - thus no manual information tagging needed (don't you know, <a href="http://securosis.com/2008/04/23/data-classification-is-dead/">its dead</a>!)  <li><strong>Easy on the tool operator (=security team)</strong> - thus no super-granular policy-writing&nbsp; needed (and please - spare me the regexes!)  <li><strong>Effective enough to stop malicious insider</strong> of reasonable skill&nbsp; over specific information channels- thus, some new technology for accurate detection of possibly modified documents across channels (e.g. common network)</li></ol> <p>Tough to match? Yup, it sure it. But that's not all: I'd like it to defend against theft of&nbsp; structured, unstructured and <em>structured-&gt;unstructured</em> (e.g. database contents pasted to email!) information over just about any network channel (not device theft and not USB/portal device download - these are a different story).&nbsp; What's more, I think that to enable #3 above the DLP "box" needs to actually understand <em>what the document is about</em> and to do it in a human-like fashion (Yes, including <em>rephrased</em> (!) content. Yes, I am picky :-)).</p> <p>The above clearly does NOT mean that the technology is&nbsp; not bypassable - there is always an encrypted zip file and gpg, custom encrypted network protocols, or even a screenshot emailed, etc (not even going to device theft, USB xfers or camera phone + screenshot + MMS). It just means that it takes DLP a few big notches up from "anti-retard defense"&nbsp; to blocking a malicious and dedicated non-IT employee from stealing the crown jewels.</p> <p>And, if one is trying to be honest about DLP, he need to define what is out of scope (after all, only narrowly defined problems are actually solvable in this space, not "our MagicBox&nbsp; 6.1 will block ALL data theft," which is absurd - if you believe that, you need your head examined).</p> <p>I was pretty shocked to learn that something like this actually exists today: the next wave of DLP start-ups is about to emerge. For example, <a href="http://www.nextiernetworks.com/">NexTierNetworks</a> can detect information traces even in modified and heavily edited documents (I would like to try rephrasing as well; I suspect it will work!). When I saw a demo I was pretty impressed that you can get a financial document, change a few things here and there, paste it to email - and the system will still stop it by saying "uh-uh, this is sensitive info, no can do" :-) Mind you, this is not what current DLP vendors call "fingerprinting," since it actually uses what the document is about i.e. works on a - <em>hate the word!</em> - semantic or meaning level. So, DLP + a bit of NLP (<em>the other</em> NLP) = magic :-)</p> <p>As a disclosure, I have to say that I just joined their Advisory Board, but, as you can guess, I joined because I am impressed (not "impressed because I joined!" :-))</p> <div class="wlWriterSmartContent" id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:5d49e280-6ee2-4817-b9ad-d21c7605fc15" style="padding-right: 0px; display: inline; padding-left: 0px; padding-bottom: 0px; margin: 0px; padding-top: 0px">Technorati tags: <a href="http://technorati.com/tags/security" rel="tag">security</a>, <a href="http://technorati.com/tags/DLP" rel="tag">DLP</a>, <a href="http://technorati.com/tags/new%20technology" rel="tag">new technology</a></div>  <div class="blogger-post-footer">About me: http://www.chuvakin.org</div><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?a=PwSKoH"><img src="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?i=PwSKoH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?a=hYZB0H"><img src="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?i=hYZB0H" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?a=RutBpH"><img src="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?i=RutBpH" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AntonChuvakinPersonalBlog/~4/292031373" height="1" width="1"/>]]></content:encoded>
      <pubDate>Fri, 16 May 2008 15:08:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/dlp">dlp</category>
      <category domain="http://securityratty.com/tag/data theft">data theft</category>
      <category domain="http://securityratty.com/tag/malicious data theft">malicious data theft</category>
      <category domain="http://securityratty.com/tag/dlp start-ups">dlp start-ups</category>
      <category domain="http://securityratty.com/tag/theft">theft</category>
      <category domain="http://securityratty.com/tag/world-famous dlp analyst">world-famous dlp analyst</category>
      <category domain="http://securityratty.com/tag/manual information">manual information</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/takes dlp">takes dlp</category>
      <source url="http://feeds.feedburner.com/~r/AntonChuvakinPersonalBlog/~3/292031373/in-passing-on-dlp.html">In Passing on DLP</source>
    </item>
    <item>
      <title><![CDATA[Risk Preferences in Chimpanzees and Bonobos]]></title>
      <link>http://securityratty.com/article/59e230c217d7a124054cfb3063e70b9d</link>
      <guid>http://securityratty.com/article/59e230c217d7a124054cfb3063e70b9d</guid>
      <description><![CDATA[I've already written about prospect theory, which explains how people approach risk. People tend to be risk averse when it comes to gains, and risk seeking when it comes to losses: Evolutionarily,...]]></description>
      <content:encoded><![CDATA[<p>I've <a href="http://www.schneier.com/essay-155.html">already written</a> about prospect theory, which explains how people approach risk.  People tend to be risk averse when it comes to gains, and risk seeking when it comes to losses:</p>

<blockquote>Evolutionarily, presumably it is a better survival strategy to -- all other things being equal, of course -- accept small gains rather than risking them for larger ones, and risk larger losses rather than accepting smaller losses. Lions chase young or wounded wildebeest because the investment needed to kill them is lower. Mature and healthy prey would probably be more nutritious, but there's a risk of missing lunch entirely if it gets away. And a small meal will tide the lion over until another day. Getting through today is more important than the possibility of having food tomorrow.

<p>Similarly, it is evolutionarily better to risk a larger loss than to accept a smaller loss. Because animals tend to live on the razor's edge between starvation and reproduction, any loss of food -- whether small or large -- can be equally bad. That is, both can result in death. If that's true, the best option is to risk everything for the chance at no loss at all.</blockquote></p>

<p>This behavior has been demonstrated in animals as well: "species of insects, birds and mammals range from risk neutral to risk averse when making decisions about amounts of food, but are risk seeking towards delays in receiving food."</p>

<p>A <a href="http://journals.royalsociety.org/content/hj235725w4pp2872/?p=dca3144c481b44358c2fed990c973bc4&pi=5">recent study</a> examines the relative risk preferences in two closely related species: chimanzees and bonobos.</p>

<blockquote>Abstract

<p>Human and non-human animals tend to avoid risky prospects. If such patterns of economic choice are adaptive, risk preferences should reflect the typical decision-making environments faced by organisms. However, this approach has not been widely used to examine the risk sensitivity in closely related species with different ecologies. Here, we experimentally examined risk-sensitive behaviour in chimpanzees (Pan troglodytes) and bonobos (Pan paniscus), closely related species whose distinct ecologies are thought to be the major selective force shaping their unique behavioural repertoires. Because chimpanzees exploit riskier food sources in the wild, we predicted that they would exhibit greater tolerance for risk in choices about food. Results confirmed this prediction: chimpanzees significantly preferred the risky option, whereas bonobos preferred the fixed option. These results provide a relatively rare example of risk-prone behaviour in the context of gains and show how ecological pressures can sculpt economic decision making.</blockquote></p>

<p>The basic argument is that in the natural environment of the chimpanzee, if you don't take risks you don't get any of the high-value rewards (e.g., monkey meat).  Bonobos "rely more heavily than chimpanzees on terrestrial herbaceous vegetation, a more temporally and spatially consistent food source."  So chimpanzees are less likely to avoid taking risks -- as most species are.</p>

<p>Fascinating stuff, but there are at least two problems with this study.  The first one, the researchers explain in their paper.  The animals studied -- five of each species -- were from the Wolfgang Koehler Primate Research Center at the Leipzig Zoo, and the experimenters were unable to rule out differences in the "experiences, cultures and conditions of the two specific groups tested here."</p>

<p>The second problem is more general: we know very little about the life of bonobos in the wild.  There's a lot of popular stereotypes about bonobos, but they're <a href="http://www.newyorker.com/reporting/2007/07/30/070730fa_fact_parker">sloppy at best</a>.</p>

<p>Even so, I like seeing this kind of research.</p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=0TkOYsG"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=0TkOYsG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=b7ammhG"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=b7ammhG" border="0"></img></a>
</div>]]></content:encoded>
      <pubDate>Thu, 17 Apr 2008 02:20:51 +0000</pubDate>
      <category domain="http://securityratty.com/tag/risk preferences">risk preferences</category>
      <category domain="http://securityratty.com/tag/risk">risk</category>
      <category domain="http://securityratty.com/tag/relative risk preferences">relative risk preferences</category>
      <category domain="http://securityratty.com/tag/risk-prone behaviour">risk-prone behaviour</category>
      <category domain="http://securityratty.com/tag/approach">approach</category>
      <category domain="http://securityratty.com/tag/people approach risk">people approach risk</category>
      <category domain="http://securityratty.com/tag/people">people</category>
      <category domain="http://securityratty.com/tag/losses">losses</category>
      <category domain="http://securityratty.com/tag/risk larger losses">risk larger losses</category>
      <source url="http://www.schneier.com/blog/archives/2008/04/risk_preference.html">Risk Preferences in Chimpanzees and Bonobos</source>
    </item>
    <item>
      <title><![CDATA[Sensitive Milwaukee County information posted to Web]]></title>
      <link>http://securityratty.com/article/9a37ae356f5cfbd90131b6d98ca62b4a</link>
      <guid>http://securityratty.com/article/9a37ae356f5cfbd90131b6d98ca62b4a</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
2/11/08

Organization
Milwaukee County (Wisconsin, USA

Contractor/Consultant/Branch
Citizens for Responsible Government Network

Victims
Persons...]]></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/milwaukee.jpg" align="right" height="51" width="181"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>2/11/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.milwaukeecounty.org/" target="_blank"> Milwaukee County (Wisconsin, USA)</a><br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.crgnetwork.com/" target="_blank"> Citizens for Responsible Government Network</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Persons <span style="font-style: italic;">involved</span> with the county<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>"patient and legal records"<br><br><span style="font-weight: bold;">Breach Description:</span><br>Milwaukee County officials released a copy of their "county spending database" to the activist group Citizens for Responsible Government Network that contained sensitive personal information belonging to various persons who had contact with the county.&nbsp; Citizens for Responsible Government Network agreed to remove the confidential information at the request of county officials, but the information had been posted for as many as six (6) days.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.jsonline.com/story/index.aspx?id=716850" target="_blank"> Milwaukee Journal Sentinel story</a> <br><a href="http://www.upi.com/NewsTrack/Top_News/2008/02/11/court_records_released_on_public_web_site/2277/" target="_blank"> United Press International story</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Milwaukee Journal Sentinel<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>Citizens for Responsible Government Network agreed to dump descriptions from some 6,900 bills that county officials feared included names of people who had court-ordered psychiatric exams, other patient service information and guardianship case details.<br><br>The information had been displayed on the group's Web site for six days, after CRG obtained a database on all county spending for the last two years.<br><br>CRG pulled a few hundred descriptions on court spending from its Web site over the weekend, after county Clerk of Court John Barrett complained about the release.<br><br>The group on Monday trashed thousands more county records CRG had displayed that came from the Sheriff's Department, the House of Correction, the district attorney's office, the Department of Health and Human Services, the Personnel Review Board and the Division of Economic and Community Development.<br><br>The county will supply the group with an edited version of the same county spending database, after department heads get a chance to better scrutinize the records, said Cynthia Archer, acting director of the county's Department of Administrative Services.<br><br>On Monday, Archer said she "questioned the wisdom" of Barrett's office forwarding confidential information included in its vendor database in response to a public record request by the group.<br><span style="font-style: italic;">[Evan] What wisdom?</span><br><br>County Executive Scott Walker said he had not heard of any complaints from anyone whose confidential information was placed on the Internet for nearly a week.<br><br>Barrett said he was happy the records that identified court-ordered psychiatric exams and guardianship details were removed from the site but still worried about whether they had been found by any browsers. That type of information is generally confidential.<br><span style="font-style: italic;">[Evan] I am not sure if this information was indexable by the various search engines, but it should definitely be explored and attended to, if necessary.</span><br><br>"Now I have to concern myself with whether we can put the toothpaste back into the tube," Barrett said.<br><span style="font-style: italic;">[Evan] This is an excellent analogy.&nbsp; Once information (toothpaste) is disclosed, it is very difficult if not impossible to re-secure it (put it back in the tube).</span><br><br><span style="font-weight: bold;">Commentary:</span><br>The database is backup (without the confidential information it appears) here; <a href="http://www.upi.com/NewsTrack/Top_News/2008/02/11/court_records_released_on_public_web_site/2277/" target="_blank"> <a href="http://milwaukeecounty.headquarters.com/search_mke.aspx</a><br><br>It">milwaukeecounty.headquarters.com/search_mke.aspx</a><br><br>It</a> was a really poor decision to send information without looking at it or considering sensitivity issues.&nbsp; I bet they wish they had a "do over".<br><br><span style="font-weight: bold;">ACLU ALERT:</span><br>Chris Ahmuty, executive director of the American Civil Liberties Union of Wisconsin, said the county's sloppy handling of confidential information could expose it to a lawsuit for invasion of privacy.<br><span style="font-style: italic;">[Evan] We need more lawsuits like we need a hole in the head.</span><br><br>"It seems like careless disrespect for the rights of individuals receiving service from the county," Ahmuty said. <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/02/13/milwaukee.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Wed, 13 Feb 2008 14:06:24 +0000</pubDate>
      <category domain="http://securityratty.com/tag/milwaukee county">milwaukee county</category>
      <category domain="http://securityratty.com/tag/milwaukee county officials">milwaukee county officials</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/county">county</category>
      <category domain="http://securityratty.com/tag/county officials">county officials</category>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/confidential information">confidential information</category>
      <category domain="http://securityratty.com/tag/county clerk">county clerk</category>
      <category domain="http://securityratty.com/tag/county records crg">county records crg</category>
      <source url="http://breachblog.com/2008/02/13/milwaukee.aspx">Sensitive Milwaukee County information posted to Web</source>
    </item>
    <item>
      <title><![CDATA[New survey: Consumers plan to sharply limit use of cards (AKA, have we awakened a sleeping giant?)]]></title>
      <link>http://securityratty.com/article/1404b6993746213bac46b1eb113903d8</link>
      <guid>http://securityratty.com/article/1404b6993746213bac46b1eb113903d8</guid>
      <description><![CDATA[We have heard it all over customers do not seem to be concerned about retailers mismanaging their data. They still spend money in those stores. It does not impact retailer revenue or stock price. So,...]]></description>
      <content:encoded><![CDATA[We have heard it all over – customers do not seem to be concerned about retailers mismanaging their data. They still spend money in those stores. It does not impact retailer revenue or stock price. So, let us not worry about it too much.<br />Wrong. I believe it is just a matter of time before consumers understand the issue and become intolerant of sloppy data protection. And maybe that time has come. The <a href="http://www.cbsnews.com/stories/2007/11/21/60minutes/main3530302.shtml">recent story on “60 Minutes”</a> is shining a light on the issue and is an indicator of rising consumer awareness.<br />Coincidently, we at <a href="http://www.bitarmor.com/">BitArmor</a>, in partnership with several local TV news departments, conducted a survey over the Black Friday weekend (400 respondents) on this very issue. The results are significant, if not surprising:<br />· Three out of four consumers are concerned about companies not adequately protecting their data;<br />· Two-thirds of consumers plan to use their credit card for less than 25% of their holiday purchases;<br />· Only around 2% say they will continue shopping at a retailer they have heard does not do a good job of protecting data;<br />· More than 40% have had their identity stolen or know of someone who has;<br />· 75% of respondents say they would warn friends and family if they knew a store where they shopped wasn’t adequately protecting their data, 33% would sign up for credit monitoring and around 70% say they would be more careful while using their cards.<br />This should serve as a huge wakeup call to any company that works with sensitive payment card data; their customers are seeing what’s going on, and they don’t like it. Shoppers are increasingly concerned about what’s happening to their data. It’s reflected in fewer people using their credit cards, and it’s reflected in them saying they’ll shop at other stores if they don’t feel their personal information is being adequately protected. It seems we have awakened a sleeping giant…consumers who are spreading the word among friends and families about whom they consider to be are “poor” retailers (from the data protection point of view).<br />I’ve talked with some analysts who reject the notion that things will ever change. They say that consumers talk a good game, but don’t change their actual buying habits. Perhaps…but when “60 Minutes” starts referring to TJX by name, and calling its security efforts “outdated” and “obsolete,” I have to believe that a lot of shoppers will think twice before using their credit cards there right away. <a href="http://www.cnet.com/defensive-computing/8301-13554_1-9822842-33.html">(And apparently Michael Horowitz at CNET agrees with me.)</a><br />All this points to the importance of securing customer data and making sure the right policies are in place. Is that enough? Maybe, but to increase customer confidence in a retailer, they will have to work just as hard in protecting their brand and increasing perception of trust.<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BitArmor1?a=mVCb0OB"><img src="http://feeds.feedburner.com/~f/BitArmor1?i=mVCb0OB" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BitArmor1?a=9Bv7Ndb"><img src="http://feeds.feedburner.com/~f/BitArmor1?i=9Bv7Ndb" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BitArmor1?a=6apOfgB"><img src="http://feeds.feedburner.com/~f/BitArmor1?i=6apOfgB" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/BitArmor1/~4/191896743" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 28 Nov 2007 12:39:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/customer data">customer data</category>
      <category domain="http://securityratty.com/tag/cards">cards</category>
      <category domain="http://securityratty.com/tag/sloppy data protection">sloppy data protection</category>
      <category domain="http://securityratty.com/tag/consumers">consumers</category>
      <category domain="http://securityratty.com/tag/data protection">data protection</category>
      <category domain="http://securityratty.com/tag/consumers plan">consumers plan</category>
      <category domain="http://securityratty.com/tag/credit cards">credit cards</category>
      <category domain="http://securityratty.com/tag/credit">credit</category>
      <source url="http://feeds.feedburner.com/~r/BitArmor1/~3/191896743/awakening.html">New survey: Consumers plan to sharply limit use of cards (AKA, have we awakened a sleeping giant?)</source>
    </item>
  </channel>
</rss>
