<?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: dig]]></title>
    <link>http://securityratty.com/tag/dig</link>
    <description></description>
    <pubDate>Mon, 21 Jul 2008 18:55:10 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Links for 2008-11-19 [del.icio.us]]]></title>
      <link>http://securityratty.com/article/359d830ca1e8df85568ee491fac7b4b0</link>
      <guid>http://securityratty.com/article/359d830ca1e8df85568ee491fac7b4b0</guid>
      <description><![CDATA[QualysGuard PCI Pass/Fail Status Criteria - Qualys
Press Releases - November 11, 2008 - Q1 Labs free, downloadable, log management and compliance product that provides organizations with visibility...]]></description>
      <content:encoded><![CDATA[<ul>
<li><a href="http://www.qualys.com/products/pci/qgpci/pass_fail_criteria/">QualysGuard PCI Pass/Fail Status Criteria - Qualys</a></li>
<li><a href="http://www.q1labs.com/pr.php?id=711">Press Releases - November 11, 2008 - Q1 Labs</a><br/>
free, downloadable, log management and compliance product that provides organizations with visibility across their networks, data centers, and infrastructures</li>
<li><a href="http://www.cheapest-service.com/blog/2008/11/11/healthy-paranoia-top-50-internet-security-blogs/">&nbsp; Healthy Paranoia: Top 50 Internet Security Blogs&nbsp;by&nbsp;The Daily Netizen</a></li>
<li><a href="http://www.govcert.nl/symposium/audiovideo.html">GOVCERT.NL Symposium 2008</a></li>
<li><a href="http://sec.online.wsj.com/article/SB122461917614955373.html">Looking for Trouble - WSJ.com</a></li>
<li><a href="http://blog.clearnetsec.com/articles/2008/11/11/it%E2%80%99s-hard-to-build-a-smart-siem">ClearNet Security : It&rsquo;s hard to build a smart SIEM</a><br/>
If you find yourself evaluating SIEM products, dig in and investigate how each works - you don’t want yesterday’s product.</li>
<li><a href="http://www.thecomplianceauthority.rsvp1.com/articles/111908_taylor.shtm">PCI Perspectives by Dave Taylor</a></li>
<li><a href="http://physicsworld.com/blog/2008/09/killed_by_complexity_1.html">Lehman Bros 'killed by complexity' (physicsworld.com Blog) - physicsworld.com</a></li>
</ul><img src="http://feeds.feedburner.com/~r/AntonChuvakinPersonalBlog/~4/459218630" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 19 Nov 2008 21:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/internet security blogs">internet security blogs</category>
      <category domain="http://securityratty.com/tag/clearnet security">clearnet security</category>
      <category domain="http://securityratty.com/tag/dave taylor">dave taylor</category>
      <category domain="http://securityratty.com/tag/compliance product">compliance product</category>
      <category domain="http://securityratty.com/tag/healthy paranoia">healthy paranoia</category>
      <category domain="http://securityratty.com/tag/labs free">labs free</category>
      <category domain="http://securityratty.com/tag/press releases">press releases</category>
      <category domain="http://securityratty.com/tag/physicsworld">physicsworld</category>
      <category domain="http://securityratty.com/tag/siem products">siem products</category>
      <source url="http://feeds.feedburner.com/~r/AntonChuvakinPersonalBlog/~3/459218630/anton18">Links for 2008-11-19 [del.icio.us]</source>
    </item>
    <item>
      <title><![CDATA[The Economics of Finding and Fixing Vulnerabilities in Distributed Systems ]]></title>
      <link>http://securityratty.com/article/8a34266a61546df04c75d0de7416a33d</link>
      <guid>http://securityratty.com/article/8a34266a61546df04c75d0de7416a33d</guid>
      <description><![CDATA[The Economics of Finding and Fixing Vulnerabilities in Distributed Systems
Quality of Protection Keynote
Alexandria, VA
October 27. 2008

Gunnar Peterson
Managing Principal, Arctec Group
Blog:...]]></description>
      <content:encoded><![CDATA[<div>The Economics of Finding and Fixing Vulnerabilities in Distributed Systems&#0160;</div><div><a href="http://qop-workshop.org/Program.htm">Quality of Protection Keynote</a></div><div>Alexandria, VA</div><div>October 27. 2008</div><br /><div>Gunnar Peterson</div><div>Managing Principal, Arctec Group</div><div>Blog: http://1raindrop.typepad.com</div><br /><div>When Andy Ozment asked me over the summer to do this talk at QoP, I knew back in August that the topic I wanted to address was security and economics. So to that end I would like to start by thanking all of our friends on Wall Street and here in Washington DC for providing such a rich tapestry of recent events that I can speak to.</div><br /><div>Like many people in this industry, my focus on security was fundamentally altered by Dan Geer&#39;s speech &quot;Risk Management is Where the Money Is&quot;[1], there are not many people who can call a ten year shot in the technology business, but Dan Geer did. The talk revolutionized the security industry. Since that speech, the security market, the vendors, consultants, and everyone else has realized that security is really about risk management.</div><br /><div>Of course, saying that you are managing risk and actually managing risk are two different things. Warren Buffett started off his 2007 shareholder letter [2] talking about financial institutions&#39; ability to deal with the subprime mess in the housing market saying, &quot;You don&#39;t know who is swimming naked until the tide goes out.&quot; In our world, we don&#39;t know whose systems are running naked, with no controls, until they are attacked. Of course, by then it is too late.</div><br /><div>So the security industry understands enough about risk management that the language of risk has permeated almost every product, presentation, and security project for the last ten years. However, a friend of mine who works at a bank recently attended a workshop on security metrics, and came away with the following observation - &quot;All these people are talking about risk, but they don&#39;t have any assets.&quot; You can&#39;t do risk management if you don&#39;t know your assets.</div><br /><div>Risk management requires that you know your assets, that on some level you understand the vulnerabilities surrounding your assets, the threats against those, and efficacy of the countermeasures you would like to use to separate the threat from the asset. But it starts with assets. Unfortunately, in the digital world these turn out to be devilishly hard to identify and value.</div><br /><div>Recent events have taught us again, that in the financial world, Warren Buffett has few peers as a risk manager. I would like to take the first two parts of this talk looking at his career as a way to understand risk management and what we can infer for our digital assets.</div><br /><div>Warren Buffett&#39;s evolution as an investor can be broken up into two parts. He began his career very much influenced by Ben Graham, who sought to buy &quot;cheap stocks&quot;, comparing the price of the stock to value of the company&#39;s assets, and placing many, diversified bets on companies whose share price was below the total assets. Note that the businesses may have been of unremarkable quality, but when the price was right Graham would buy in, wait for it to rise and then sell. This was the dawn of value investing.</div><br /><div>Buffett&#39;s later career departed from Graham&#39;s strict, statistical measures, where he sought to buy into companies that were selling at a fair price, but were also high quality businesses. We will examine high quality in Part 2 of this talk, but first we go to Part 1 which is asset value.</div><br /><div>Why does a talk on finding and fixing vulnerabilities start with valuing assets? The reason is that vulnerabilities are everywhere, we are literally marinating in them. Interesting vulnerabilities are attached to high value assets. In a world that quite literally presents us with too much information, we need screens to sift out what is worth paying attention to. &#0160;You can run your vulnerability assessment tool of choice on your system, and come back with hundreds or thousands of vulnerabilities, but which ones should you pay attention to and act on? The first part of answering this question is asset value.</div><br /><div>When Warren Buffett was 19 years old studying at the University of Nebraska, he read Ben Graham&#39;s book &quot;The Intelligent Investor&quot;, Buffett said he thought it was the best book on investing he has ever read and still feels that way today. In the Intelligent Investor Graham lays out the framework of value investing. Specifically, Graham talks about three concepts - Mr. Market, a stock is a piece of a business, and Margin of Safety.</div><br /><div>Mr. Market is a fictional, teaching device invented by Graham. You imagine that you have a somewhat manic depressive business partner called Mr. Market. Every day, Mr. Market comes into the office and offers you quotes on companies, some days he is in a good mood and the prices are high, other days he is gloomy and prices are low. The market is a quote machine, for quoting prices, not a value assessment machine. Your job is to wait for the right price, and you are free to take as many passes and be as patient as you would like, Mr. Market will just show up the next day and throw out a new price.&#0160;</div><br /><div>Graham used Mr. Market to teach us the separation between a price of a stock, and the value of a company. The second big concept from Intelligent Investor is that buying a stock is buying a small piece of the underlying business. You are not buying a roulette chip, or a number that fluctuates in the newspaper every day, rather you are buying a piece of the company&#39;s existing and future cash flow. What the stock market says General Electric is worth yesterday, today or tomorrow is separate from GE&#39;s actual ability to generate cash flow.</div><br /><div>The last big concept in &quot;The Intelligent Investor&quot; and the one seemingly most applicable to information security is the Margin of Safety. Graham&#39;s margin of safety involved calculating the intrinsic value of a business and then buying stock where the market cap of a company is less than its intrinsic value. So if a company has $100 million in assets and a market capitalization of $75 million, then an investor would get a 25% margin of safety. Ideally, Graham wanted to buy stocks that were selling for one half of their book value, i.e. with a 50% margin of safety. Graham said that buying stocks without a margin of safety, above their book value, speculation, not investing.</div><br /><div>So price is readily available, but how do we calculate intrinsic value so that we can ascertain the margin of safety? Graham used quantitative statistical measures, relying heavily on the company&#39;s book value, like its hard assets. What would it take for a competitor to reproduce the company&#39;s assets - its factories, distribution system, and so on. The difference between the book value of the assets and market cap is the margin of safety.</div><br /><div>What can we learn in information security from this quantitative approach? Where price and value are readily ascertainable we should build countermeasures and eliminate on vulnerabilities that give our assets a wide margin of safety. Since budgets are not unlimited we should prefer vulnerabilities that are cheap to find, cheap to fix.</div><br /><div>First to the asset question, information security budgets like all IT budgets are crufty, they are not a reflection of today&#39;s top issues and priorities so much as an accumulating snowball of decisions, legacy contracts, and solution attempts to yesteryear&#39;s problems. Today the normal Information Security budget is just a legacy artifact from bygone years when the network was the purported greatest vulnerability. If you were around in 1995, you remember the great gnashing of gears as the enterprises opened up their networks, connected their back ends to the Web and began to transact business in the giant virtual space.</div><br /><div>The security people huffed and puffed that it was dangerous but there was simply too much money to be made, so businesses went ahead. The security people would not go down without a fight and insisted on countermeasures. They got two - the network firewall and SSL. The firewall was used to separate the average Fortune 500s network of hundreds of thousands of machines, employees, consultants, and partners from the web at large. SSL was used to protect the network channel between the web server and the client browser. so the network firewall separated the network segments, and SSL in effect encrypted the last mile of many million complex transactions and computations.</div><br /><div>In 1995, this seemed like a good security architecture. When we built out these security architectures, the eCommerce market was derided as a toy. Amazon famously lost money for years - losing a little on every transaction but making it up in volume. When the market is nascent, a quaint security architecture offers cost effective protection. But what about 2008? Those cute little eCommerce buggers have grown they even make profits now - market caps measured in the tens of billions, accumulating large cash hordes, no debt, and the largest ones are in better financial shape than the financial services players that kicked sand in their face in the dotcom era.&#0160;</div><br /><div>And its not just eCommerce, the &quot;real&quot; economy Fortune 500 types are all connected as well. Directly and indirectly the Web is seeping into all businesses. Major changes from when the security architecture of the web was built out. But has the security architecture changed to reflect these new business realities? Not a bit of it!</div><br /><div>We can use the book value of the IT budget investments and the book value of the Information Security investments to see what kind of Margins of Safety Information Security groups are engineering.</div><br /><div>Let&#39;s look at some market data, Gary McGraw reviewed the numbers [2] in software security for 2007, breaking down software security sectors like tools and services. Here is a summary of his findings on software security tools:</div><br /><div>&quot;One of the most important developments in the software security market can be seen in the tools space which, combined, almost doubled to $150-180 million. Top of list are two major acquisitions that closed in 2007: Watchfire&#39;s purchase by IBM (somewhere in the range of $120-150 million on 2006 revenue of $26 million) and SPI Dynamics&#39;s purchase by HP (for around $100 million on 2006 revenue of $21.2 million).</div><br /><div>...</div><br /><div>The black box space was flat in 2007, with IBM/Watchfire checking in at $24.1 million and HP/SPI Dynamics earning $22.3 million. Smaller companies in the space, including Cenzic, Codenomicon, WhiteHat and the like had combined revenues around $12.5 million (a growth of 25%, though Cenzic grew 16% and WhiteHat 52%). Most of the growth &quot;hiccup&quot; in the black box market can be attributed to the serious challenges posed by any acquisition. So far 2008 looks to be back on track from a growth perspective in the black box testing space. The global reach that IBM and HP offer are already making a big difference.</div><br /><br /><div>On a more positive note, static analysis tools for code review grew at a healthy clip in 2007 into a $91.9 million dollar market. Fortify was up 83% to $29.2 million. Klocwork grew over 60% to $26 million. Coverity grew over 50% to $27.2 million. Ounce Labs tripled their revenue to $9.5 million.&quot;</div><br /><div>These are very nice growth numbers, what company doesn&#39;t want 83% growth? However, the let&#39;s look at the total picture and compare the software security countermeasures against other security mechanisms. Gary McGraw&#39;s estimate shows the software security space coming in at $150 Million total, yet we see a company like Checkpoint that won the network security war in 1995 with earnings of around $900 Million! One single network security vendor is 6 times bigger than the entire software security space, in what alternate universe does this make sense?</div><br /><div>This is where we begin to see that decisions in the People&#39;s Republic of Information Security have no real risk management thinking, they truly are swimming naked and hoping the tide doesn&#39;t go out.</div><br /><div>Let&#39;s look at network assets. Obviously Cisco is the biggest, they earned $39.5 Billion last year. Pretty stellar. So spending $900 Million (Checkpoint) to defined $39.5 Billion seems like a pretty good deal.</div><br /><div>Except, let&#39;s compare software security spending - last year Microsoft earned $60 Billion, SAP $16 billion, and Oracle $22 Billion. So that is about $98 Billion in just three vendors and you are going to &quot;defend&quot; that with allocating $150 Million worth of software security tools?</div><br /><div>On the network side we are buying $900 million of security countermeasures (Checkpoint firewalls) to protect $39.5 billion worth of Cisco gear, about 2.3% of the network investment goes to security.</div><br /><div>On the software side, we are buying $150 million of security countermeasures (like static analysis and black box scanners) to protect $98 billion of software (you know the stuff that runs the whole business), roughly coming to about 0.2% of the software budget goes to security.</div><br /><div>This is very disturbing. From a prioritization standpoint The People&#39;s Republic of Information Security is misaligned by an order of magnitude at least. Next time you read about a data breach, or see an auditor&#39;s report with thousands of findings you won&#39;t have to wonder how it happened. It happened because Information Security doesn&#39;t have its eye on the ball, it invests in network security not because those controls have greater efficacy (the whole point of networks is they are dumb), no, they invest in network firewalls because they bought a bunch in 1995, some more in 1998, and heck they just kept buying them, the Checkpoint rep kept showing up and taking CISOs out to play golf, contracts got renewed, and poof - there goes the security budget.</div><br /><div>Consider that software security tools could grow 50% a year for five years and still be half of where Checkpoint is today.</div><br /><div>The optimistic way of looking at all this data is that there is major room for growth for software security, if you take network security as a target for a mature industry and assume that 2.3% is a reasonable margin of safety, then the software security space should evolve to around 2% of the software space meaning that it should evolve into a $2 billion space around fifteen times larger than it is today. Unprotected assets will either be protected or will cease to be assets, VCs get your check books ready.</div><br /><div>My friend Brian Chess has a nice way of looking at this he says 2007 was the turning point - &quot;the first year there was a bigger market for products that help you get code right than there was for products that help you demonstrate a problem exists.&quot;</div><br /><div>Now I am not suggesting that Information Security budgets have to be aligned with IT budget one for one, but I do think that looking at the overall IT budget is the starting point. If Information Security has a more cost effective security mechanism they should deploy it, but the starting point should be aligned to the business. Businesses spend most of their money on software, and there are very good reasons - competitive advantage, increased revenues and lower costs. Information Security spends most of its money on network security, and there is no good reason why, except that it was a seemingly good idea in 1995. You really don&#39;t have to go beyond the book value of IT investment as a whole versus Information Security to see a stunning disparity. Information Security&#39;s job is to deliver a Margin of Safety to the business, but they are not.&#0160;</div><br /><div>To deliver a real Margin of Safety to the business, I propose the following based on a defense in depth mindset. Break the IT budget into the following categories:</div><br /><div>- Network: all the resources invested in Cisco, network admins, etc.</div><div>- Host: all the resources invested in Unix, Windows, sys admins, etc.</div><div>- Applications: all the resources invested in developers, CRM, ERP, etc.</div><div>- Data: all the resources invested in databases, DBAs, etc.</div><br /><div>Tally up each layer. If you are like most business you will probably find that you spend most on Applications, then Data, then Host, then Network.</div><br /><div>Then do the same exercise for the Information Security budget:</div><br /><div>- Network: all the resources invested in network firewalls, firewall admins, etc.</div><div>- Host: all the resources invested in Vulnerability management, patching, etc.</div><div>- Applications: all the resources invested in static analysis, black box scanning etc.</div><div>- Data: all the resources invested in database encryption, database monitoring, etc.</div><br /><div>Again, tally each up layer. If you are like most business you will find that you spend most on Network, then Host, then Applications, then Data. Congratulations, Information Security, you are diametrically opposed to the business!</div><br /><div>Its not just about alignment for alignment&#39;s sake, its about applying controls as a way to have a Margin of Safety properly placed so that when not if there is a failure on a higher value asset you are relatively better positioned to deal with it.&#0160;</div><br /><div>The pure statistical approach can only take us so far. Buffett said he would be a lot poorer if all he did was listen to Ben Graham. Book value is great to see the diametric opposition mentioned above, but it doesn&#39;t really tell us much about the efficacy of the security mechanisms.</div><br /><div>What we do get out of this statistical approach is a screen. The asset value screen filters out subjective opinion and narrows the field for where we need to dig in to do the high value, time consuming analytical work.</div><br /><div>The second part of Warren Buffett&#39;s career and the second part of this talk leave behind pure statistical measures. In Warren Buffett&#39;s case he was joined by a guy named Charlie Munger who talked him out of the pure Ben Graham approach. Charlie Munger has a saying - &quot;a great business at a fair price beats a fair business at a great price.&quot; Where Graham was focused on price and margin of safety, Munger wants a fair price but also a high quality business. This lead to Warren Buffett&#39;s company Berkshire Hathaway investing in companies like Coca Cola, Wells Fargo, and American Express, where the prices were far from dirt cheap (as Graham would have wanted), but the long term returns were outstanding.</div><br /><div>In our world of Information Security, we start by aligning our priorities with the business using the thumbnail defense in depth approach, but then we would like to invest in high quality, effective controls.</div><br /><div>To get at the notion of control quality and effectiveness, I am going to start part 2 of this talk with a brief history of software. The first web software was just static HTML, but web software really got interesting when developers started creating dynamic websites using CGI an PERL.</div><br /><div>Once websites were hooked up to company databases and were not just serving static content, the security people realized they needed a security architecture, and they sprung into action. What they came up was was model that divided the world into &quot;good stuff&quot; which was comprised of all their networks, systems, and data; and then there was everything else the &quot;bad stuff&quot; on the Internet. So job one of the early days Internet security architecture was to separate all your good stuff (i.e. your network) for the bad stuff (the Internet). To do this the security people used a sophisticated tool called Visio to draw a flaming brick wall on the network diagram, and this flaming brick wall was supposed to keep the good stuff and the bad stuff separate.</div><br /><div>The security people also realized that the data and session tokens that they served up from their Web server would have to traverse the &quot;bad&quot; neighborhood called the Internet, so they added one more security mechanism to secure the last mile of the transaction - SSL between the browser and the Web server.</div><br /><div>And this was the state of the art security architecture used circa 1995 to protect the earliest dynamic web applications.</div><br /><div>What happened next was that the dotcom boom started to happen and businesses realized they could make some real money on the Web, the web apps started to get more sophisticated, more personalization, richer session experiences and so on. This led the Java people to create JSP and the Microsoft people to create ASP, and of course the PERL people to create even greasier PERL scripts, all of this in the effort to pooling resources and sessions on the Web server. The security people defended this new application programming model with network firewall and SSL.</div><br /><div>Around 1998, developers began building out more distributed N tier or 3 tier applications that separated the business logic layer, the presentation layer and the data access layer. Among other things, your web application could seamlessly integrate data from multiple back ends systems. Let&#39;s say you have pricing data in Oracle, order data in SAP, and customer data in a Mainframe. You write separate data access objects, apply business logic in the middle tier and then you tie it all together in a friendly user interface. At this point the web applications are beginning to integrate across departments and geographic boundaries, huge critical chunks of the business are now connected to the web. How did the security people defend this part of the business? They applied the same 1995 security architecture - network firewall and SSL.</div><br /><div>Around 1999-2000 timeframe businesses relied on web applications for major parts of the revenue, and the apps were built in different technologies like Java and Microsoft technologies, but the customer didn&#39;t care (still doesn&#39;t), the customer wanted (and still wants) data access and functionality. So to integrate the disparate technologies, SOAP and XML were deployed so that Microsoft could talk to Java and so Websphere could talk to Weblogic and so on. And, oh yes, SOAP and XML were used to connect B2B networks so partners in a supply chain and business process can exchange data and interoperate. &#0160;SOAP and XML present a fundamentally new programming model based on a message document style integration, where XML is used to mesh together data and functionality across platforms. SOAP and XML have no security model by default for authentication, authorization, and confidentiality. How did the security people deal with this? They kept the security architecture the same as they had in 1995 - network firewalls and SSL.</div><br /><div>The software world did not stop innovating in 2000 of course, in the last few years we have seen Web services and XML form the basis of baroque and powerful SOAs and simple REST applications. We have seen Web 2.0 come on the scene, and entirely new networked applications built on top of that.</div><br /><div>What we have not seen, is a single meaningful change in security architecture in 13 years. Developers have evolved, businesses have increasingly bet their entire business models on the web and they have increased security budgets. But what has the security architecture as its deployed in the field got to show for all of this? More firewalls and more SSL connections.</div><br /><div>Since Information Security has proven incapable of evolving, it is time to learn from a discipline that has mastered innovation - software development, and yes, I will step back in case the lightning bolts hits.</div><br /><div>What does software development focus on these days? Well, let&#39;s look at Service Oriented Architecture (SOA), all hype aside I look at SOA as a set of technologies that delivers three things:</div><br /><div>Virtualization: we want Beijing, Bangalore and Boston to communicate.</div><br /><div>Interoperability: we want our .Net stuff to talk to our java stuff.</div><br /><div>Reusability: how many order/claim/pricing/customer systems does one company need?</div><br /><div>To build out their SOA, developers separated the application interface from its implementation. So you can host the interface in a variety of locations, but its separate from the application logic and data.</div><br /><div>This is also a useful trick for putting services like SOAP through the firewall. SOAP was designed as a firewall friendly protocol. When SOAP first came out, Bruce Schneier said calling SOAP a firewall friendly protocol is like having a skull friendly bullet. Which is a great line and explains why his books fly off the shelves, it does not explain, why security people think an architecture designed in 1995 is the one we should be using today. Maybe the problem is not that the developers figured out how to go through the firewall to get the data their customers want, maybe the problem is that the firewall is the sum total of the security architecture, and it never adapted.</div><br /><div>A big part of this problem is that we have left Newton&#39;s world behind and entered Einstein&#39;s universe. Mainframes are Newton’s world, we have THE computer, THE price, THE record and so on.</div><br /><div>As Pat Helland explained [4,5], Mainframes are Newron&#39;s world, but Distributed computing is Einstein’s world. More specifically in the Einstein world of distributed computing - &quot;Computers don’t make decisions, computers try &#0160;to make decisions.&quot; Our computers don&#39;t really make a decision, they say you can buy this book from Amazon at this price, we have it in stock and will deliver on such and such a date. But the warehouse runs out, the pallet gets dropped in the warehouse, your boo is crushed, and the package is stolen off your front step. The computer confirmed your transaction, but the real world intervened.</div><br /><div>So we don&#39;t have iron clad decisions, instead its all about Memories (last time I checked your book was in stock), Guesses (we should be able to ship on this date) and Apologies (sorry the forklift ran over your book)</div><br /><div>Translating this into security, security mechanisms don’t make policy-based decisions, security mechanisms try to make policy-based decisions</div><br /><div>Some examples of memories, guesses and apologies in security</div><br /><div>Memories</div><div>Security Policies - for example Triple A policy</div><div>Triple A policies can memorize a map of subjects, objects, and roles. They can even replicate these memories and play them back at runtime to try to make policy enforcement decisions.</div><br /><div>Guesses</div><div>Security Policy Enforcement Decision</div><div>Unfortunately, while the policy enforcement decisions can be based on memorized logic, the decision itself is still a guess, even in the case of Triple A. Any guesses why? Because, the authentication process itself is a guess. It happens to be a guess that you then bind to a principal so it looks very official once you bind your guess to a Kerberos ticket or SAML assertion, but it still a guess.</div><br /><div>Apologies</div><div>Giant Global Bank is sorry your account was compromised!</div><div>And this leads to lots and lots of apologies by companies with poor access control models.</div><br /><div>Some additional examples of information security memories, guesses and apologies.</div><br /><div>Example Memories - Triple A Security Policies, Audit logs, User account information , Authorization Logic - concrete mapping Subject, Resource, Condition, Action</div><br /><div>Example Guesses - Security Policy Enforcement Decision Points, Authentication Logic, Monitoring, detection, fraud response</div><br /><div>Example Apologies - Identity Management tools - provisioning, deprovisioning, Reimburse customer for fraud losses, Compensating Transaction - Giant Global Bank is still sorry your account was compromised!</div><br /><div>The point of this is that security memories, guesses and apologies utilize different processes, different people, and different capabilities to be effective.</div><br /><div>What trends can we identify to lead us toward better qualitative analysis based on the best practices of virtualization, interoperability and reusability.</div><br /><div>Virtualization</div><div>Finding Vulnerabilities in a Virtualized World is a problem because applications are more configured than coded. Runtime behavior and structure not apparent due to weak typing and inversion of control.</div><br /><div>Result - finding bugs becomes harder. Action - use screens to target finding time and resources</div><br /><div>Fixing Vulnerabilities in a Virtualized World is a problem because how do I locate the controls when interfaces run in Beijing, Bangalore and Boston?</div><br /><div>Result - synchronization and/or replication of security policy is problematic. Action - decentralized policy enforcement points and policy decision points. &#0160;</div><br /><div>Interoperability</div><div>Finding interoperable vulnerabilities</div><div>XSS - Javascript is an equal opportunity offender - interoperability for developers and attackers alike.</div><br /><div>Fixing interoperable vulnerabilities</div><div>App servers, ESBs, and services are the attacker’s red carpet to your enterprise, right into your book of business. Interoperable access control can be leveraged across the enterprise.</div><br /><div>Use XML signature for authentication and integrity&#0160;</div><br /><div>&lt;SOAP:Envelope&gt;</div><div><span class="Apple-tab-span" style="white-space:pre">	</span>&lt;SOAP:Header&gt;</div><div><span class="Apple-tab-span" style="white-space:pre">		</span>&lt;WSSE:Security&gt;</div><div><span class="Apple-tab-span" style="white-space:pre">			</span>&lt;ds:Signature&gt;</div><div><span class="Apple-tab-span" style="white-space:pre">				</span>&lt;ds:Reference URI=‘#body’&gt;</div><div><span class="Apple-tab-span" style="white-space:pre">		</span>&lt;/WSSE:Security&gt;</div><div><span class="Apple-tab-span" style="white-space:pre">	</span>&lt;/SOAP:Header&gt;</div><div><span class="Apple-tab-span" style="white-space:pre">	</span>&lt;SOAP:Body wsu:Id=‘body’&gt;</div><div><span class="Apple-tab-span" style="white-space:pre">		</span>…</div><div><span class="Apple-tab-span" style="white-space:pre">	</span>&lt;/SOAP:Body&gt;</div><div>&lt;SOAP:Envelope&gt;</div><br /><div>Use XML encryption to protect sensitive data, don&#39;t pass sensitive data in the clear</div><br /><div>&lt;?xml version=&#39;1.0&#39; encoding=&#39;UTF-8&#39;?&gt;</div><div>&lt;soapenv:Envelope xmlns:soapenv=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;&gt;</div><br /><div>&lt;soapenv:Body&gt;&lt;ns1:echo xmlns:ns1=&quot;http://sample01.samples.rampart.apache.org&quot;&gt;</div><br /><div><span class="Apple-tab-span" style="white-space:pre">	</span>&lt;param0&gt;My Credit Card Number&lt;/param0&gt;</div><div>&lt;/ns1:echo&gt;</div><div>&lt;/soapenv:Body&gt;</div><div>&lt;/soapenv:Envelope&gt;</div><br /><div>Encrypt the data</div><br /><div>&#0160;&lt;wsse:Security xmlns:wsse=&quot;http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd&quot; soapenv:mustUnderstand=&quot;1&quot;&gt;…</div><div>&#0160;&#0160; &#0160; &#0160; &#0160; &#0160; &#0160;&lt;xenc:EncryptedKey Id=&quot;EncKeyId-3020592&quot;&gt;</div><div>&#0160;&#0160; &#0160; &#0160; &#0160; &#0160; &#0160; &#0160; &lt;xenc:EncryptionMethod Algorithm=&quot;http://www.w3.org/2001/04/xmlenc#rsa-1_5&quot; /&gt;</div><div><span class="Apple-tab-span" style="white-space:pre">		</span> &lt;xenc:CipherValue&gt;</div><div>XNQ0a4legiie5mWFxO6CQkk2hhldYNnKroObue/LXS/VYtvaTgMbCujhGExDi+vlkU//Qc2/T6mx0WVTmBMT3z8rogha8jD+nS9Zr2Bc3CwoTh2lh8wL3D0DEu91iwJT9JByLGXvt7v9lyuxK0ooDOYEClsH974CPmTs3tBC+GQ=</div><div><span class="Apple-tab-span" style="white-space:pre">		</span>&lt;/xenc:CipherValue&gt; &#0160; &#0160; &#0160; &#0160; &#0160; &#0160; &#0160;&#0160;</div><div>&lt;/xenc:CipherData&gt;</div><br /><div>To ensure that these controls are applied use automated tools like static analysis to scan for security mechanism use and coverage.</div><br /><div>In terms of reusability findings and fixes consider two bug findings</div><br /><div>Session management bug: session state is passed around to every component, service and user. Makes for many high priority findings in audit report, also the fix is required on virtually every program</div><br /><div>Data validation bug: Data access object (DAO) has a SQL injection hole. One major high priority finding in report. DAO used by many business logic classes, one fix location serves many classes&#0160;</div><br /><div>To bring these factors together, I generally use a scorecard index [6], so you can measure such things as transport security, message security, threat protection and so on. The hard work in developing the index is developing a useful scale. A scale for XML tokens could use the following</div><br /><div>0: no token</div><div>1: hashed token</div><div>2: hashed and signed token</div><div>3: hashed and signed token from standard authoritative source</div><br /><div>An example scale for XML validation could use:</div><br /><div>0: no validation</div><div>1: schema validation</div><div>2: schema validation against hardened schema</div><div>3: schema validation against standard, hardened schema</div><br /><div>These indexed scales are used to show maturity across the factors in the scorecard. The first part of the talk described value, the value assessment is used to focus time and effort on high value assets. The value assessment can be determined quantitatively. There is hard analytical work to qualitatively determine the scorecard, index, and scales, the quantitative value assessment is used to screen out high value targets for these endeavors. The scoring index is used to track progress and improve quality over time. In the best case scenario, automated tools are used to perform the checks described in the index, and once security is automated just like software developers we may see security innovation make progress in years not decades.</div><br /><div>Thank you for your time.</div><br /><div>1 &quot;Risk Management is where the Money Is&quot; by Dan Geer,&#0160;<a href="http://catless.ncl.ac.uk/Risks/20.06.html">http://catless.ncl.ac.uk/Risks/20.06.html</a></div><br /><div>2 Berkshire Hathaway 2007 Shareholder Letter by Warren Buffett, <a href="http://www.berkshirehathaway.com/letters/2007ltr.pdf">http://www.berkshirehathaway.com/letters/2007ltr.pdf</a></div><br /><div>3 &quot;Software [In]security: Software Security Demand Rising, by Gary McGraw</div><div><a href="http://www.informit.com/articles/article.aspx?p=1237978">http://www.informit.com/articles/article.aspx?p=1237978</a></div><br /><div>4 &quot;SOA and Newton&#39;s Universe&quot; by Pat Helland, <a href="http://blogs.msdn.com/pathelland/archive/2007/05/20/soa-and-newton-s-universe.aspx">http://blogs.msdn.com/pathelland/archive/2007/05/20/soa-and-newton-s-universe.aspx</a></div><br /><div>5 &quot;Memories, Guesses and Apologies&quot; by Pat Helland, <a href="http://blogs.msdn.com/pathelland/archive/2007/05/15/memories-guesses-and-apologies.aspx">http://blogs.msdn.com/pathelland/archive/2007/05/15/memories-guesses-and-apologies.aspx</a></div><br /><div>6 &quot;Web Servicres Security Checklist&quot; by Gunnar Peterson, <a href="http://arctecgroup.net/pdf/WebServicesSecurityChecklist.pdf">http://arctecgroup.net/pdf/WebServicesSecurityChecklist.pdf</a></div>]]></content:encoded>
      <pubDate>Tue, 18 Nov 2008 19:47:55 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/information security spends">information security spends</category>
      <category domain="http://securityratty.com/tag/safety information security">safety information security</category>
      <category domain="http://securityratty.com/tag/versus information security">versus information security</category>
      <category domain="http://securityratty.com/tag/information security budgets">information security budgets</category>
      <category domain="http://securityratty.com/tag/information security budget">information security budget</category>
      <category domain="http://securityratty.com/tag/software security">software security</category>
      <category domain="http://securityratty.com/tag/software security space">software security space</category>
      <source url="http://1raindrop.typepad.com/1_raindrop/2008/11/the-economics-of-finding-and-fixing-vulnerabilities-in-distributed-systems-.html">The Economics of Finding and Fixing Vulnerabilities in Distributed Systems </source>
    </item>
    <item>
      <title><![CDATA[Game on!]]></title>
      <link>http://securityratty.com/article/811075c6e59d5ec00b606569ae49ba5d</link>
      <guid>http://securityratty.com/article/811075c6e59d5ec00b606569ae49ba5d</guid>
      <description><![CDATA[In my last blog, we looked at increasing complexity on the part of both the good guys who are building legitimate businesses and on the part of the bad guys who are building a dark network of sorts...]]></description>
      <content:encoded><![CDATA[<p>In my last blog, we looked at  increasing complexity on the part of both the &ldquo;good&rdquo; guys who are building  legitimate businesses and on the part of the &ldquo;bad guys&rdquo; who are building a  &ldquo;dark network&rdquo; of sorts that is remarkably like the first.&nbsp; Today, I&rsquo;d like to dig into that and look at  a system for explaining this; and I thought I&rsquo;d use the phrase we used playing  street hockey in my youth in <a href="http://en.wikipedia.org/wiki/Canada">Canada</a> when the cars cleared the road, and  the game got serious again: <B>game on!</b>...</p>]]></content:encoded>
      <pubDate>Tue, 04 Nov 2008 21:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/game">game</category>
      <category domain="http://securityratty.com/tag/bad guys">bad guys</category>
      <category domain="http://securityratty.com/tag/guys">guys</category>
      <category domain="http://securityratty.com/tag/dark network">dark network</category>
      <category domain="http://securityratty.com/tag/street hockey">street hockey</category>
      <category domain="http://securityratty.com/tag/system">system</category>
      <category domain="http://securityratty.com/tag/youth">youth</category>
      <category domain="http://securityratty.com/tag/complexity">complexity</category>
      <category domain="http://securityratty.com/tag/cars">cars</category>
      <source url="http://www.rsa.com/blog/blog_entry.aspx?id=1380">Game on!</source>
    </item>
    <item>
      <title><![CDATA[A Cryptographer and a Data Communications Guy Talk About Risk Management]]></title>
      <link>http://securityratty.com/article/5c18b17d022b8a56101fd4b3d13c5f03</link>
      <guid>http://securityratty.com/article/5c18b17d022b8a56101fd4b3d13c5f03</guid>
      <description><![CDATA[Sounds like the beginning of a joke, right? So these two guys walk into a bar
The Bruce Schneier and Marcus Ranum have an article up on TechTarget/Information Security Magazine called, creatively...]]></description>
      <content:encoded><![CDATA[<blockquote><p>Sounds like the beginning of a joke, right?  <em>So these two guys walk into a bar&#8230;</em></p></blockquote>
<p>&#8220;The&#8221; Bruce Schneier and Marcus Ranum have an article up on TechTarget/Information Security Magazine called, creatively enough, &#8220;<span class="homeSplashTitle"><span class="text0"><strong><a href="http://searchsecurity.techtarget.com/magazineFeature/0,296894,sid14_gci1332745_idx1,00.html">Bruce Schenier, Marcus Ranum debate risk management</a>&#8220;. </strong></span></span></p>
<p>Unfortunately, to get to the article, you&#8217;ll have to either already be a subscriber to IT Security, a subscriber to TechTarget, or go through the 20 minute process of signing up by giving TechTarget all sorts of &#8220;market information&#8221; about how you&#8217;re really Brandon Walsh, CSO of &#8220;The Peach Pit&#8221; Industries in Beverly Hills, CA 90210 (phone 714-867-5309).</p>
<p>For those of you who are already a TechTarget person, the link is above.  For those who aren&#8217;t, or those who just don&#8217;t have the time, I&#8217;ll summarize.  The &#8220;debate&#8221; is kind of awkward because both authors seem come to the same conclusion:</p>
<p style="text-align: center;"><em><strong>Risk Management, it&#8217;s something our profession should do, something humans do naturally, it&#8217;s necessary in business, but gosh - we don&#8217;t have enough data.</strong></em></p>
<p>I&#8217;m not a cryptographer.  I don&#8217;t *nearly* have the insight on privacy and politics that Bruce has.  I&#8217;m not deep in IP communications.  I haven&#8217;t got a proven track record of innovation in IP Security products like Marcus has.  But here&#8217;s the thing, I hope you&#8217;ll never hear me pretend that I have the skill set to speak authoritatively on those subjects.  Heck, I wouldn&#8217;t claim to be a &#8220;risk&#8221; expert because I have a some insight into my shortcomings and what is needed to tackle such a complex problem.  But such a tepid article on something that (at least I think) is so important kind of, well, confuses me.</p>
<p>Why is it such a boring article?  I&#8217;m not sure.  Maybe because they&#8217;re just two guys who would rather debate the merits of specific controls or control activities (after all, their penetration testing debate was a huge success), but there&#8217;s no new information in the &#8220;debate&#8221;.  It&#8217;s the same old &#8220;insurance companies know risk because they have scads of data and we don&#8217;t have that&#8221; complaint. You know what?  I&#8217;m tired of hearing that line, so let&#8217;s talk about it.</p>
<p><strong>HOW DO YOU KNOW WE DON&#8217;T HAVE THE AMOUNT OF DATA WE NEED TO DO RISK MANAGEMENT WELL?</strong></p>
<p>Not particularly picking on Marcus, but in the article he uses the common complaint, &#8220;We lack the data to do risk management well.&#8221;  This mantra is repeated to the point where I&#8217;m blase&#8217; about it.  But for some reason, this sentence really jumped out at me this time for two reasons.  It made me ask:</p>
<p>1.)  How do you <em>know</em> we don&#8217;t have the proper amount of data?</p>
<p>2.)  Can we even define &#8220;well&#8221; (i.e. what &#8220;good&#8221; risk management is) yet?</p>
<p>I really don&#8217;t know that the industry, especially concerning IT risk, is mature enough to really conclude that we don&#8217;t know (in the case of the former), nor that we can define (latter), conclusively.</p>
<p><strong>PLAYING THE CONTRARIAN</strong></p>
<p>Just because I&#8217;m feeling kind of zany this morning, let me suggest something.  Maybe there actually is lots of evidence out there for us to use.  Maybe:</p>
<p>1.)  It&#8217;s just that we don&#8217;t have particularly good models that provide context.</p>
<p>2.)  When that evidence isn&#8217;t an obvious phenomena that lends itself to easy measurement, we throw our hands up in disgust and fall back on &#8220;lack of data&#8221;, &#8220;can&#8217;t quantify risk&#8221;, &#8220;best practices work just fine&#8221; or any other number of arguments, no,<em> excuses</em> we use to justify our inability to be precise about the past (more or less the present or future - apologies to Niels Bohr).</p>
<p><strong>IT&#8217;S IN THE WAY THAT YOU USE IT</strong></p>
<p>Now I actually am happy to acknowledge that we don&#8217;t have enough data to be precise.  You, me, even smart guys like Marcus and Bruce - we&#8217;ll never be able to &#8220;engineer&#8221; risk management.  But you know what?  Neither can Insurance companies.  Sure, there are plenty of places where they have enough data to apply a traditional frequentist approach to risk valuations.   But there are plenty of times Insurers actually insure and they don&#8217;t have centuries or decades of data.  There are plenty of times when they rely on the &#8220;estimates&#8221; of subject matter experts.  There are many times they have enough information to be <em><strong>accurate</strong></em> rather than precise, and that&#8217;s good enough for them.</p>
<p>For that matter, it&#8217;s worth noting that there are plenty of scientific disciplines that have to deal in imprecise prior information, or evidence that&#8217;s fraught with uncertainty (what Ranum calls &#8220;squishy&#8221;, and what I&#8217;ve heard real honest to goodness physicists call &#8220;noisy&#8221;).  Unfortunately, we&#8217;re going to be like them.  Until we can read minds and predict the future, there will always be uncertainty in our measurements and posterior conclusions.  The trick is in how you deal with it and express it.  And while I really don&#8217;t know how much time Marcus or Bruce have really spent in the deep end on the subject of risk and its management - I have seen people doing brilliant things around risk (though they just aren&#8217;t mainstream).  Whether the tools are Bayesian methods, Monte Carlo engines, reductionist models of complex problems, there are risk analysts trying to deal with the problem.  These analysts are applying scientific method(s) and developing reasonable approaches to a very complex problem.  <em><strong>There are people trying, and our body of knowledge is growing</strong></em>, growing well beyond &#8220;gee, I haven&#8217;t got an obvious solution so I&#8217;ll blame it on lack of data&#8221;.  Heck, I&#8217;ve seen readers of this blog suggest Douglas Hubbard&#8217;s book in other security forums!<span style="color: #ff0000;">*</span></p>
<p><strong>I&#8217;VE GOT YOUR DATA RIGHT HERE&#8230;</strong></p>
<p>But we don&#8217;t have enough data?  I have to ask, how much more do we need?  I mean crikey, JPMC just visited our ISSA chapter claiming, like, a bajillion events an hour.  There&#8217;s not one, but several companies out there that will want to tell you about how they have deep &#8220;insight&#8221; into the attacker community.  The boundaries of IT Risk losses are pretty well established by events that happen to public companies.  We have pretty mature testing/assessment tools and methodologies now that help us test our ability to resist the force an attacker can apply to us.  So what part of the Threat Landscape, Asset (Controls) Landscape, or Loss Magnitude landscape is too incomplete (and what are you doing to find the information you need)?</p>
<p><strong>SO WHY DO WE FAIL?</strong></p>
<p>Which brings me to a final, somewhat depressing conclusion.  Maybe there&#8217;s data, and maybe we&#8217;re starting to see the means to use it.  But in the end I do have to agree with Marcus that the vast majority of the infosec world *is* doing a really, really bad job with regards to &#8220;risk&#8221; and &#8220;risk management&#8221;.  The majority of people I know consider GRC to be a cruel, expensive joke.  Risk Assessment Methodologies tend to be built on the faulty premise that if we create a repeatable process, our measurements and conclusions will magically become accurate and wise.  Risk models tend to be factors loosely measured by ordinal scales and then somehow &#8220;multiplied&#8221; together to create a relatively meaningless qualitative value.  The State of the Union here is not good.  But after reading such a superficial treatment of an important and complex subject, I am left wondering if Bruce and Marcus were the right people to write about risk management in a mainstream publication.  As Inspector Callahan says, &#8220;<strong><a href="http://www.youtube.com/watch?v=cZNlraF0xec">A man&#8217;s got to know his limitations</a></strong>.&#8221;</p>
<p>===============================</p>
<p><span style="color: #ff0000;">*</span> <em>Speaking of which, if you want to do one cost effective thing to address your uncertainty - go find Douglas Hubbard&#8217;s book. It&#8217;s even got a nice recommendation from Peter Tippett.  The book is called &#8220;How To Measure Anything&#8221; - the title sounds rather hyperbolic, but there are good techniques in it we can use to identify useful information and refine our ability to frame that qualitative information into quantitative values. The key is how Hubbard has you deal with your uncertainty.  For those of you who are more scientific minded and want to dig deep into the subject, I have on good authority that E.T. Jaynes &#8220;Probability Theory, The Logic of Science&#8221; is a rather under appreciated work.</em></p>
]]></content:encoded>
      <pubDate>Thu, 16 Oct 2008 11:32:16 +0000</pubDate>
      <category domain="http://securityratty.com/tag/risk management">risk management</category>
      <category domain="http://securityratty.com/tag/management">management</category>
      <category domain="http://securityratty.com/tag/risk">risk</category>
      <category domain="http://securityratty.com/tag/engineer risk management">engineer risk management</category>
      <category domain="http://securityratty.com/tag/methodologies">methodologies</category>
      <category domain="http://securityratty.com/tag/risk assessment methodologies">risk assessment methodologies</category>
      <category domain="http://securityratty.com/tag/risk models">risk models</category>
      <category domain="http://securityratty.com/tag/risk analysts">risk analysts</category>
      <category domain="http://securityratty.com/tag/models">models</category>
      <source url="http://riskmanagementinsight.com/riskanalysis/?p=487">A Cryptographer and a Data Communications Guy Talk About Risk Management</source>
    </item>
    <item>
      <title><![CDATA[Speculation on Palin E-mail Hack]]></title>
      <link>http://securityratty.com/article/fd7684786fde741aba76349aad10a6a8</link>
      <guid>http://securityratty.com/article/fd7684786fde741aba76349aad10a6a8</guid>
      <description><![CDATA[Assuming the mailbox hack is not an elaborate ruse, how did they do it
Almost as bad as the Sprint PCS password reset fiasco that made the news in April, here is the Yahoo Mail password reset screen
...]]></description>
      <content:encoded><![CDATA[<p>Assuming <a href="http://www.veracode.com/blog/2008/09/sarah-palins-yahoo-mailbox-compromised/">the mailbox hack</a> is not an elaborate ruse, how did they do it?</p>
<p>Almost as bad as the <a href="http://consumerist.com/376845/flawed-security-lets-sprint-accounts-get-easily-hijacked">Sprint PCS password reset fiasco</a> that made the news in April, here is the Yahoo Mail password reset screen:</p>
<p><a href="http://www.veracode.com/blog/wp-content/uploads/2008/09/yahooreset.gif"><center><img src="http://www.veracode.com/blog/wp-content/uploads/2008/09/yahooreset-300x178.gif" alt="" title="yahooreset" width="300" height="178" class="aligncenter size-medium wp-image-283 photoborder" /></center></a></p>
<p>As you can see, you need to know the user&#8217;s birthday, country of residence, and postal code.  Not difficult information to dig up in Palin&#8217;s case, <a href="http://wikileaks.org/leak/sarah-palin-hack-2008/email-account-info.txt">as shown here</a>.  After you enter this information correctly, you are asked to type in the alternate e-mail address that&#8217;s associated with the account.  But they give you hints &#8212; so if your alternate e-mail was sarah@alaska.gov, they would show you s****@a*****.gov.</p>
<p>Assuming you guess the alternate e-mail correctly, Yahoo mails a password reset link to that address.  So it&#8217;s likely that the attacker may have also had to gain access to her alternate e-mail account.  Either that, or they exploited a vulnerability in the Yahoo password reset mechanism itself, which seems less likely but not implausible.</p>
<p>So Yahoo itself probably didn&#8217;t get hacked, per se, even though there will probably be a lot of FUD in the media about that.</p>
]]></content:encoded>
      <pubDate>Wed, 17 Sep 2008 14:12:08 +0000</pubDate>
      <category domain="http://securityratty.com/tag/e-mail">e-mail</category>
      <category domain="http://securityratty.com/tag/e-mail correctly">e-mail correctly</category>
      <category domain="http://securityratty.com/tag/e-mail account">e-mail account</category>
      <category domain="http://securityratty.com/tag/account">account</category>
      <category domain="http://securityratty.com/tag/e-mail address">e-mail address</category>
      <category domain="http://securityratty.com/tag/password reset link">password reset link</category>
      <category domain="http://securityratty.com/tag/address">address</category>
      <category domain="http://securityratty.com/tag/yahoo">yahoo</category>
      <category domain="http://securityratty.com/tag/yahoo mails">yahoo mails</category>
      <source url="http://www.veracode.com/blog/2008/09/speculation-on-palin-e-mail-hack/">Speculation on Palin E-mail Hack</source>
    </item>
    <item>
      <title><![CDATA[The Real Migration Problem]]></title>
      <link>http://securityratty.com/article/066428c6b802b3676a2c3982d275cbbd</link>
      <guid>http://securityratty.com/article/066428c6b802b3676a2c3982d275cbbd</guid>
      <description><![CDATA[Preview of Tom Friedman's thinking for his new book - Hot, Flat and Crowded. Killer quote (emphasis added

FP: And what about drilling? Republican presidential candidate Sen. John McCain, his running...]]></description>
      <content:encoded><![CDATA[<p><a href="http://www.foreignpolicy.com/story/cms.php?story_id=4463">Preview</a> of Tom Friedman&#39;s thinking for his new book - Hot, Flat and Crowded. Killer quote (emphasis added):</p><br /><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><p><span style="font-family: Verdana; font-size: 12px; line-height: 16px; "><span class="fp_red" style="color: #8c182d; font-weight: bold; "><strong>FP:&#160;</strong></span>And what about drilling? Republican presidential candidate Sen. John McCain, his running mate Gov. Sarah Palin, and President George W. Bush are implying that lifting environmental restrictions on drilling is the way to promote energy independence.</span></p></blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><p><span style="font-family: Verdana; font-size: 12px; line-height: 16px;"><br /></span><span style="font-family: Verdana; font-size: 12px; line-height: 16px; "><strong>TF:&#160;</strong>Well, I think it’s patent nonsense. No one believes that somehow offshore, there’s enough oil in any near term and even the long term to provide us oil independence. It’s the wrong approach because in a world that’s hot, flat, and crowded, fossil fuels—and particularly crude oil—are going to be expensive and exhausting. Therefore the focus should be on the next great global industry: clean energy technology. <span style="font-weight: bold;">When I hear McCain pounding the table for “drill, drill, drill,” it reminds me of someone pounding the table for IBM Selectric typewriters on the eve of the IT revolution.</span></span></p></blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><p><span style="font-family: Verdana; font-size: 12px; line-height: 16px;"><br /></span><span style="font-family: Verdana; font-size: 12px; line-height: 16px; ">I’m not against offshore drilling, by the way, because I believe the technology and the safety has improved far beyond where it was back in the 70s, 80s, and 90s, even. What I’m against is making it the centerpiece of our energy policy. If all McCain said was, “Let’s drill, but let’s also throw everything into innovating the next generation of clean-energy technologies,” I’d say, “You’ve got it exactly right, pal.”</span></p></blockquote><p><span style="font-family: Verdana; font-size: 12px; line-height: 16px;"><br /></span></p><div><span style="font-family: Verdana; font-size: 12px; line-height: 16px;">Its funny because as someone who has done a half dozen legacy migration projects (with mental and emotional scars to prove it), I was thinking the same thing. The entrenched mindset. &quot;If we just dig our trench deeper (in this case literally) then we will be ok.&quot;...at least until the person in question retires...</span></div><div><span style="font-family: Verdana; font-size: 12px; line-height: 16px;"><br /></span></div><div><span style="font-family: Verdana; font-size: 12px; line-height: 16px;">One of the legacy migration project I worked on, I was the third consultant that tried to get this company off of mainframe and onto distributed systems (which are no panacea but this company really did need to make the move). The core developers of the mainframe were actively hostile to change, as opposed to simply passive aggressive, which we expect. For example, if you asked about how a piece of functionality worked, say a report writer, the developer would not answer, stand up, walk out of the room, come back with a 800 page &quot;data model&quot;, slam it on the table and walk out of the room. Good times.</span></div><div><span style="font-family: Verdana; font-size: 12px; line-height: 16px;"><br /></span></div><div><span style="font-family: Verdana; font-size: 12px; line-height: 16px;">A chief objection beyond fear of the unknown was the perceived lack of elegance in the distributed systems as opposed to the control from say JCL. Anyway, what progress I made was due to analogizing that we were leaving Greece which has a rich culture, history, philosophy and moving to Rome which maybe was not as elegant as Greece but still people like circuses, roads and acqueducts. So when, several times a day, a perceived go/ no go issue arose, I would gently remind &#160;the developers that &quot;we are now in Rome and things work differently here.&quot;</span></div><div><span style="font-family: Verdana; font-size: 12px; line-height: 16px;"><br /></span></div><div><span style="font-family: Verdana; font-size: 12px; line-height: 16px;">Intransigently digging the trench deeper is not the way, instead we need to better understanding the energy &#160;problem in a larger context, and finding deployable technologies to help address it. If you think drill, drill, drill is the answer, then I think the answer for you is the same as someone who knows COBOL and flat refuses to learn modern languages even when that is required - a nice retirement house on a golf course somewhere.</span></div>]]></content:encoded>
      <pubDate>Tue, 09 Sep 2008 05:38:33 +0000</pubDate>
      <category domain="http://securityratty.com/tag/energy">energy</category>
      <category domain="http://securityratty.com/tag/clean-energy technologies">clean-energy technologies</category>
      <category domain="http://securityratty.com/tag/clean energy technology">clean energy technology</category>
      <category domain="http://securityratty.com/tag/drill">drill</category>
      <category domain="http://securityratty.com/tag/energy policy">energy policy</category>
      <category domain="http://securityratty.com/tag/technology">technology</category>
      <category domain="http://securityratty.com/tag/promote energy independence">promote energy independence</category>
      <category domain="http://securityratty.com/tag/trench deeper">trench deeper</category>
      <category domain="http://securityratty.com/tag/mccain">mccain</category>
      <source url="http://1raindrop.typepad.com/1_raindrop/2008/09/the-real-migration-problem.html">The Real Migration Problem</source>
    </item>
    <item>
      <title><![CDATA[Links List 8.15.08]]></title>
      <link>http://securityratty.com/article/803e2f6db1563e98882d0a71faf66398</link>
      <guid>http://securityratty.com/article/803e2f6db1563e98882d0a71faf66398</guid>
      <description><![CDATA[Cloud Computing will also cure the common cold! Not really. But amidst all the hype and overly-used marketing speak its hard to tell the difference. Researchers from the University of Michigan...]]></description>
      <content:encoded><![CDATA[<p>Cloud Computing will also cure the common cold! Not really. But amidst all the hype and overly-used marketing speak it&#8217;s hard to tell the difference. Researchers from the University of Michigan announced CloudAV, a network service using the <a href="http://www.infoworld.com/article/08/08/08/Researchers_look_to_cloud_computing_to_fight_malware_1.html?source=NLC-TB&amp;cgd=2008-08-08">&#8220;cloud-computing&#8221; concept to fight malware</a>. Please stop the insanity! I&#8217;m just waiting for someone to put &#8220;my&#8221; and &#8220;cloud computing&#8221; together&#8230;</p>
<p>Here&#8217;s an interesting post on High Earth Orbit about the usage and promotion of <a href="http://highearthorbit.com/open-source-in-defense/">open source software for defense</a> contracts. As a developer of open source tools, Andrew Turner of course brings up some &#8220;pros&#8221; for the government to push open source, but it&#8217;s the &#8220;cons&#8221; that are really interesting. A big &#8220;con&#8221; &#8211; the US government having something called &#8220;<a href="http://tech.slashdot.org/article.pl?sid=08/08/04/2253246">sovereign immunity</a>&#8221; which apparently means something like it can&#8217;t be sued unless it consents to be sued. Hunh &#8211; the Republic of ScienceLogic-Land? Closing the loop here, a federal appeals court just boosted open-source software licenses by saying that any infringements can now get more <a href="http://weblog.infoworld.com/openresource/archives/2008/08/court_rules_tha.html?source=rss">severe remedies under copyright law</a> (instead of contract law); here&#8217;s the case, <a href="http://blawgletter.typepad.com/bbarnett/2008/08/can-you-copyrig.html">Jacobsen v Katzer</a>. But apparently not if it&#8217;s the <a href="http://arstechnica.com/news.ars/post/20080804-air-force-cracks-software-carpet-bombs-dmca.html">US government</a>?? Who knows more?</p>
<p>Does Linus Torvalds hate everyone except for developers? You have to check out this article on an email exchange he had with Network World this week, talking about how fed up he is with the &#8220;<a href="http://www.infoworld.com/article/08/08/14/Torvalds_Fed_up_with_the_security_circus_1.html">security circus</a>&#8221;. Over the course of the exchange and some other comments from last month, he manages to blast security folk, OpenBSD (on security) in particular, vendors and PR people (of course). In the midst of the barrage of colorful language, it&#8217;s difficult to really get his point &#8211; which if you can dig it out, ends up being surprisingly sensible.</p>
<p>Sharon Taylor, Chief Architect of ITIL V3, recently wrote that with the release of the latest version of ITIL<a href="http://itmanagersinbox.com/345/itil-v3-and-business-service-management/">, BSM is now an &#8216;ITIL best practice</a>.&#8217; You say potato&#8230; &#8220;The distinction between IT and the business has blurred, and the language of IT has been replaced with the language of the business.&#8221;</p>
]]></content:encoded>
      <pubDate>Fri, 15 Aug 2008 16:04:33 +0000</pubDate>
      <category domain="http://securityratty.com/tag/source software">source software</category>
      <category domain="http://securityratty.com/tag/open-source software licenses">open-source software licenses</category>
      <category domain="http://securityratty.com/tag/source">source</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/blast security folk">blast security folk</category>
      <category domain="http://securityratty.com/tag/colorful language">colorful language</category>
      <category domain="http://securityratty.com/tag/language">language</category>
      <category domain="http://securityratty.com/tag/itil">itil</category>
      <category domain="http://securityratty.com/tag/email exchange">email exchange</category>
      <source url="http://blog.sciencelogic.com/links-list-81508/08/2008">Links List 8.15.08</source>
    </item>
    <item>
      <title><![CDATA[HP StorageWorks sets the bar for iSCSI SAN server security]]></title>
      <link>http://securityratty.com/article/05d800433c4d2b0a0aba4dad9036b161</link>
      <guid>http://securityratty.com/article/05d800433c4d2b0a0aba4dad9036b161</guid>
      <description><![CDATA[Our testing of iSCSI SAN servers show they all handle basic functions as advertised. But we had to dig deeper into other enterprise features offered such as security, high availability, and...]]></description>
      <content:encoded><![CDATA[Our testing of iSCSI SAN servers show they all handle basic functions as advertised. But we had to dig deeper into other enterprise features offered — such as security, high availability, and expandability -- to find bigger differentiations between the products.]]></content:encoded>
      <pubDate>Sun, 27 Jul 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/iscsi san servers">iscsi san servers</category>
      <category domain="http://securityratty.com/tag/handle basic functions">handle basic functions</category>
      <category domain="http://securityratty.com/tag/enterprise features">enterprise features</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/dig deeper">dig deeper</category>
      <category domain="http://securityratty.com/tag/bigger">bigger</category>
      <category domain="http://securityratty.com/tag/availability">availability</category>
      <category domain="http://securityratty.com/tag/products">products</category>
      <category domain="http://securityratty.com/tag/expandability">expandability</category>
      <source url="http://www.networkworld.com/reviews/2008/072808-test-iscsi-sans-features.html?fsrc=rss-security">HP StorageWorks sets the bar for iSCSI SAN server security</source>
    </item>
    <item>
      <title><![CDATA[When is 4 out of 5 stars is not 4 out of 5 stars or do I have a car for you!]]></title>
      <link>http://securityratty.com/article/e9877b84765f2874457cb3dd3cdfa96b</link>
      <guid>http://securityratty.com/article/e9877b84765f2874457cb3dd3cdfa96b</guid>
      <description><![CDATA[After my used car salesman of NAC series I was going to give Ray and the gang a break. But the depths they sink to just never cease to amaze me! Today I received a Google alert on NAC with a link to a...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>After my “<a href="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/06/the-used-car-sa.html">used car salesman of NAC</a>” series I was going to give Ray and the gang a break.&nbsp; But the depths they sink to just never cease to amaze me! Today I received a Google alert on NAC with a <a href="http://www.sourcewire.com/releases/rel_display.php?relid=40444&amp;hilite=">link to a press release</a> announcing the NAC used car sales guys continuing to deliver best in class security management solutions, yada, yada, yada.&nbsp; The basis for this claim was that “SC Magazine awarded ForeScout’s CounterACT a four-out-of-five star rating, lauding the product’s ability to “function like a firewall, an IPS and a NAC device all rolled into one”.&nbsp; They wrapped some customer quote (that had nothing to do with the SC magazine story) and voila!, can they put you in this car today? </p>

<p>So why do I call this out? No, no sour grapes here.&nbsp; Actually StillSecure Safe Access received the same 4 out of 5 stars and when we dig into the rating here are some interesting facts:</p>

<p><a href="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/forescout.jpg"><img title="forescout" height="301" alt="forescout" src="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/forescout_thumb.jpg" width="197" border="0" style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" /></a>&nbsp; <a href="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/stillsecure%20sc%20mag_1.jpg"><img title="stillsecure sc mag" height="329" alt="stillsecure sc mag" src="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/stillsecure%20sc%20mag_thumb_1.jpg" width="195" border="0" style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" /></a><a href="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/slimy_salesguy_1.jpg"><img title="slimy_salesguy" height="240" alt="slimy_salesguy" src="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/slimy_salesguy_thumb_1.jpg" width="170" border="0" style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; MARGIN: 0px 0px 0px 40px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" /></a> </p>

<p>In actuality, our friends the used car salesmen only received a 2 star rating in ease of use, a 2 star rating in documentation and a 3 star rating in support.&nbsp; In contrast <a href="http://www.scmagazineus.com/StillSecure-Safe-Access/Review/2460/">StillSecure Safe Access</a> received 5 stars across the board, except for a 4 star grade in documentation.&nbsp; How both products finish up with a 4 star rating overall based upon this is frankly baffling to me. I think it has more to do with the reviewer not wanting to spank any of the products too badly.&nbsp; I have already asked for a clarification and will let you know what I find out.&nbsp; But being a slick marketing machine, I thought it the height of chutzpah that they would put out a release around this, considering the best buy and editors choice were two different products.&nbsp; But I guess that is why they did not have a quote or a link to the <a href="http://www.scmagazineus.com/ForeScout-Technologies-CounterACT/Review/2457/">actual review</a>.&nbsp; The review starts out with this memorable quote, “The ForeScout CounterACT was the device which took the most time to install and configure.”&nbsp; Later on the reviewers had this to say, “The second part of the configuration was far more difficult. The initial screens for the GUI made us feel lost and we immediately began looking for the documentation CD.”&nbsp; Now does that sound like a review to be touting?&nbsp; Only those master car salesman would seek to put out a press release trumpeting the results of this review.&nbsp; They are counting by wrapping enough other quotes (and frankly who knows about those) around it, no one will bother to dig into the facts here. Hey, thats what you guys pay me for, telling it like it is!</p></div>

<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=Vt7jr0"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=Vt7jr0" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=BcRnNJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=BcRnNJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=JYqH5J"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=JYqH5J" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=82rLAJ"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=82rLAJ" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=dMvV1J"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=dMvV1J" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=BWbDPj"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=BWbDPj" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=2I5Scj"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=2I5Scj" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/342141149" height="1" width="1"/>]]></content:encoded>
      <pubDate>Mon, 21 Jul 2008 19:47:46 +0000</pubDate>
      <category domain="http://securityratty.com/tag/car">car</category>
      <category domain="http://securityratty.com/tag/master car salesman">master car salesman</category>
      <category domain="http://securityratty.com/tag/car salesman">car salesman</category>
      <category domain="http://securityratty.com/tag/car sales guys">car sales guys</category>
      <category domain="http://securityratty.com/tag/nac device">nac device</category>
      <category domain="http://securityratty.com/tag/star">star</category>
      <category domain="http://securityratty.com/tag/star grade">star grade</category>
      <category domain="http://securityratty.com/tag/nac">nac</category>
      <category domain="http://securityratty.com/tag/products">products</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/342141149/when-is-4-out-o.html">When is 4 out of 5 stars is not 4 out of 5 stars or do I have a car for you!</source>
    </item>
    <item>
      <title><![CDATA[When is 4 out of 5 stars not 4 out of 5 stars or do I have a car for you!]]></title>
      <link>http://securityratty.com/article/c7f2260d59e070e01911cb7ea5ecaf69</link>
      <guid>http://securityratty.com/article/c7f2260d59e070e01911cb7ea5ecaf69</guid>
      <description><![CDATA[After my ??? used car salesman of NAC ??? series I was going to give Ray and the gang a break. But the depths they sink to just never cease to amaze me! Today I received a Google alert on NAC with a...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p>After my ???<a href="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/06/the-used-car-sa.html">used car salesman of NAC</a>??? series I was going to give Ray and the gang a break.&nbsp; But the depths they sink to just never cease to amaze me! Today I received a Google alert on NAC with a <a href="http://www.sourcewire.com/releases/rel_display.php?relid=40444&amp;hilite=">link to a press release</a> announcing the NAC used car sales guys continuing to deliver best in class security management solutions, yada, yada, yada.&nbsp; The basis for this claim was that ???SC Magazine awarded ForeScout???s CounterACT a four-out-of-five star rating, lauding the product???s ability to ???function like a firewall, an IPS and a NAC device all rolled into one???.&nbsp; They wrapped some customer quote (that had nothing to do with the SC magazine story) and voila!, can they put you in this car today? </p>

<p>So why do I call this out? No, no sour grapes here.&nbsp; Actually StillSecure Safe Access received the same 4 out of 5 stars and when we dig into the rating here are some interesting facts:</p>

<p><a href="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/forescout.jpg"><img title="forescout" height="301" alt="forescout" src="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/forescout_thumb.jpg" width="197" border="0" style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" /></a>&nbsp; <a href="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/stillsecure%20sc%20mag_1.jpg"><img title="stillsecure sc mag" height="329" alt="stillsecure sc mag" src="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/stillsecure%20sc%20mag_thumb_1.jpg" width="195" border="0" style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" /></a><a href="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/slimy_salesguy_1.jpg"><img title="slimy_salesguy" height="240" alt="slimy_salesguy" src="http://www.stillsecureafteralltheseyears.com/ashimmy/WindowsLiveWriter/slimy_salesguy_thumb_1.jpg" width="170" border="0" style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; MARGIN: 0px 0px 0px 40px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" /></a> </p>

<p>In actuality, our friends the used car salesmen only received a 2 star rating in ease of use, a 2 star rating in documentation and a 3 star rating in support.&nbsp; In contrast <a href="http://www.scmagazineus.com/StillSecure-Safe-Access/Review/2460/">StillSecure Safe Access</a> received 5 stars across the board, except for a 4 star grade in documentation.&nbsp; How both products finish up with a 4 star rating overall based upon this is frankly baffling to me. I think it has more to do with the reviewer not wanting to spank any of the products too badly.&nbsp; I have already asked for a clarification and will let you know what I find out.&nbsp; But being a slick marketing machine, I thought it the height of chutzpah that they would put out a release around this, considering the best buy and editors choice were two different products.&nbsp; But I guess that is why they did not have a quote or a link to the <a href="http://www.scmagazineus.com/ForeScout-Technologies-CounterACT/Review/2457/">actual review</a>.&nbsp; The review starts out with this memorable quote, ???The ForeScout CounterACT was the device which took the most time to install and configure.???&nbsp; Later on the reviewers had this to say, ???The second part of the configuration was far more difficult. The initial screens for the GUI made us feel lost and we immediately began looking for the documentation CD.???&nbsp; Now does that sound like a review to be touting?&nbsp; Only those master car salesman would seek to put out a press release trumpeting the results of this review.&nbsp; They are counting by wrapping enough other quotes (and frankly who knows about those) around it, no one will bother to dig into the facts here. Hey, thats what you guys pay me for, telling it like it is!</p></div>
]]></content:encoded>
      <pubDate>Mon, 21 Jul 2008 18:55:10 +0000</pubDate>
      <category domain="http://securityratty.com/tag/car">car</category>
      <category domain="http://securityratty.com/tag/master car salesman">master car salesman</category>
      <category domain="http://securityratty.com/tag/car salesman">car salesman</category>
      <category domain="http://securityratty.com/tag/car sales guys">car sales guys</category>
      <category domain="http://securityratty.com/tag/star">star</category>
      <category domain="http://securityratty.com/tag/star grade">star grade</category>
      <category domain="http://securityratty.com/tag/nac device">nac device</category>
      <category domain="http://securityratty.com/tag/review">review</category>
      <category domain="http://securityratty.com/tag/nac">nac</category>
      <source url="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/07/when-is-4-out-o.html">When is 4 out of 5 stars not 4 out of 5 stars or do I have a car for you!</source>
    </item>
  </channel>
</rss>
