<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Logblog</title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/" />
    <link rel="self" type="application/atom+xml" href="http://blog.loglogic.com/atom.xml" />
   <id>tag:blog.loglogic.com,2010://1</id>
    <link rel="service.post" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1" title="Logblog" />
    <updated>2010-09-02T22:03:35Z</updated>
    <subtitle>Log Management &amp; Intelligence For Compliance, Risk Mitigation &amp; Business Continuity</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2</generator>
 
<entry>
    <title><![CDATA[The LogLogic Story &ndash; Chapter 9]]></title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/09/the_loglogic_story_chapter_9.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=837" title="The LogLogic Story &amp;ndash; Chapter 9" />
    <id>tag:blog.loglogic.com,2010://1.837</id>
    
    <published>2010-09-02T22:03:34Z</published>
    <updated>2010-09-02T22:03:35Z</updated>
    
    <summary>Use The ‘use’ section of our technology is actually lots of products that all feed off the central warehouse. We...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p><strong>Use</strong></p>  <p><a href="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter9_C5B3/Slide10.jpg"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="Slide10" border="0" alt="Slide10" src="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter9_C5B3/Slide10_thumb.jpg" width="479" height="360" /></a> </p>  <p>The ‘use’ section of our technology is actually lots of products that all feed off the central warehouse. We have a S.E.M. solution that we refer to as a SOC-in-a-box, which is probably the most accurate correlation engine available. We have compliance technology that takes your assets and people and matches them against directives, and then enforces your processes. We have a forensic workflow solution that is indisputably the most efficient in the business. We have a special data-aware console called Database Security Manager that gives you SOC-type security over your databases. And of course, everything we do is extensible with open APIs. </p>  <p>The point I’m trying to make here is that we give you the ability to do the alerting, searching and reporting that you need, whether it’s for compliance, security or IT operations - all of it enriched from our central warehouse in ways that others can’t match. </p>]]>
        
    </content>
</entry>
<entry>
    <title><![CDATA[The LogLogic Story &ndash; Chapter 8]]></title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/09/the_loglogic_story_chapter_8.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=836" title="The LogLogic Story &amp;ndash; Chapter 8" />
    <id>tag:blog.loglogic.com,2010://1.836</id>
    
    <published>2010-09-01T21:19:22Z</published>
    <updated>2010-09-01T21:19:46Z</updated>
    
    <summary>See Our ‘see’ is simply the biggest, fastest, most scalable and complete IT data warehouse available today. We have one...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p><strong>See</strong></p>  <p><a href="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter8_BB57/Slide9.jpg"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="Slide9" border="0" alt="Slide9" src="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter8_BB57/Slide9_thumb.jpg" width="444" height="334" /></a> Our ‘see’ is simply the biggest, fastest, most scalable and complete IT data warehouse available today. We have one customer that currently gives us 53 BILLION logs per day. Twitter (not a customer), <a href="http://blog.loglogic.com/2010/05/size_really_does_matter.php">we estimate</a>, produces 127,000 log messages per second. Our biggest box peaks at 250,000. This level of scalability means that if you’re considering building a large datacenter, we’re the only people you should talk to. </p>  <p>But we’re more than just scalable. Our warehouse specializes in structuring unstructured data. We take the data from our Universal Collection Framework and automatically identify it – no more tedious manual configuration the way you do with other vendors. We then feed that IT data into our taxonomy where we add the insight. We take information from asset databases, from active directories (LDAP) and use it, along with our deep knowledge of events, to turn error code 14 on device w3q into “Andy (West Sales) failed to gain external access to main CRM system.” </p>  <p>This insight comes from our unique patent pending taxonomy. But we don’t know everything. You may have a device we’ve never heard off, an application you built yourself, or something that’s so old it’s unique to your environment. Using our Log Labels technology you can, using a simple drag and drop GUI, teach our taxonomy about your uniqueness. And of course, we do this in an enterprise-class fashion. You define data just once, it gets added to a central library of terms, and is automatically pushed to all your appliances. The next version of this will enable you to share your work with the greater community, meaning as an industry, we can finally tackle the long tail of IT data sources. </p>  <p>To be a good corporate citizen, we of course have to play nicely with others. And so we have an open storage system that scales using our own disks, or plays nicely with your corporate SAN’s and NAS’s. It also uses a unique open forwarding technology so we can share our enriched view of the world with any vendor you wish. </p>  <p>And again, we have open APIs, so we’re extensible should we not entirely meet your needs. </p>]]>
        
    </content>
</entry>
<entry>
    <title>VMware vCloud Director Support</title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/vmware_vcloud_director_support.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=834" title="VMware vCloud Director Support" />
    <id>tag:blog.loglogic.com,2010://1.834</id>
    
    <published>2010-08-31T17:26:54Z</published>
    <updated>2010-09-01T17:47:10Z</updated>
    
    <summary>To quote BusinessWire, we’ve just announced another world first. At VM World today we announced our support for VMware vCloud...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="Cloud Computing" />
            <category term="Innovation" />
            <category term="LogLogic News" />
            <category term="SaaS" />
            <category term="Security" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p align="left">To quote <a href="http://www.businesswire.com/news/home/20100831005599/en">BusinessWire</a>, we’ve just announced another world first. At VM World today we announced our support for VMware vCloud Director in <a href="http://www.loglogic.com/5">LogLogic 5</a>. Want to see it in action? Press play below… </p>  <p align="center"><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/K5SmUsj-gPQ&amp;hl=en&amp;fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/K5SmUsj-gPQ&amp;hl=en&amp;fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"></embed></object></p>]]>
        
    </content>
</entry>
<entry>
    <title><![CDATA[The LogLogic Story &ndash; Chapter 7]]></title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/the_loglogic_story_chapter_7.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=833" title="The LogLogic Story &amp;ndash; Chapter 7" />
    <id>tag:blog.loglogic.com,2010://1.833</id>
    
    <published>2010-08-31T17:11:29Z</published>
    <updated>2010-08-31T17:11:50Z</updated>
    
    <summary>Get Let’s look at ‘get, see, use’ in a little more detail. Our “get” is actually technology called the Universal...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p><strong>Get</strong></p>  <p align="center"><a href="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter7_813F/Slide8.jpg"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="Slide8" border="0" alt="Slide8" src="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter7_813F/Slide8_thumb.jpg" width="435" height="327" /></a></p>  <p> Let’s look at ‘get, see, use’ in a little more detail. </p>  <p>Our “get” is actually technology called the Universal Collection Framework. </p>  <p>This framework provides universal IT data collection capable of collecting, without agents, from just about anywhere. Where we do need agents for those hard to reach places, like HP Integrity NonStop (tandem) machines, or exotic devices, we have them. We also provide specialized technology for capturing database activity without the need for you to turn on costly auditing. All of this technology is vertically scalable to suit data centers of any size. It is also the world’s only WAN-aware store-and-forward technology capable of adapting to time-zones, being scheduled, compensating for unstable pipes, and protecting your data from unauthorized viewers. </p>  <p>The technology that makes all of this work is a brand new protocol we’ve invented called the Universal Lossless Data Protocol – which we intend to open-source next year. </p>  <p>Of course, we also publish open APIs so that you can add to this framework if you wish. </p>]]>
        
    </content>
</entry>
<entry>
    <title><![CDATA[The LogLogic Story &ndash; Chapter 6]]></title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/the_loglogic_story_chapter_6.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=832" title="The LogLogic Story &amp;ndash; Chapter 6" />
    <id>tag:blog.loglogic.com,2010://1.832</id>
    
    <published>2010-08-30T19:02:42Z</published>
    <updated>2010-08-30T19:03:02Z</updated>
    
    <summary>The Flexibility Wheel This ‘get, see, use’ is what we refer to as ‘360 Insight.’ Put simply, it means that...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p><strong>The Flexibility Wheel</strong></p>  <p><a href="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter6_9B4A/Slide7.jpg"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="Slide7" border="0" alt="Slide7" src="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter6_9B4A/Slide7_thumb.jpg" width="444" height="334" /></a> </p>  <p>This ‘get, see, use’ is what we refer to as ‘360 Insight.’ </p>  <p>Put simply, it means that we don’t care where your data is, or what format it’s in; we can get it and give you 360 degrees of sight into all your IT data. </p>  <p>We don’t care why you’re capturing all that data. Whether it’s compliance, security, or IT-ops, we give you 360 degrees of sight into all your business drivers. </p>  <p>We don’t care who you are. Whether you’re looking for insight because you’re HR, an auditor/assessor, a partner, or that guy in IT - we give you insight. </p>  <p>‘We don’t care’ is harsh. ‘We’re neutral’ lacks the passion behind our focus. What I’m trying to say is that we’re doing all the hard work to understand all of your data, for whatever driver motivates you, while respecting your role within your organization. </p>  <p>We do the work, so that you (or a team of consultants) don’t have to.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Understanding and Selecting SIEM/Log Management</title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/understanding_and_selecting_siemlog_management.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=831" title="Understanding and Selecting SIEM/Log Management" />
    <id>tag:blog.loglogic.com,2010://1.831</id>
    
    <published>2010-08-27T23:58:11Z</published>
    <updated>2010-08-27T23:58:31Z</updated>
    
    <summary>There’s an analyst firm you may not have heard of called Securosis. Every member of the firm is a rock-star...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p>There’s an analyst firm you may not have heard of called <a href="http://securosis.com/">Securosis</a>. Every member of the firm is a rock-star from one of the major players that got fed up constantly having to guard their words and toe a corporate line. These guys speak it like they see it, and it often isn’t pretty. I butted heads with them my first day at LogLogic and lost. I like them for that.</p>  <p>Anyway, they’ve just written a “<a href="http://securosis.com/research/publication/white-paper-understanding-and-selecting-siem-log-management/">what the heck is SIEM</a>” paper. Whilst I disagree with their definition of what SIM and SEM are (my definition is <a href="http://blog.loglogic.com/2010/08/the_loglogic_story_chapter_3.php">here</a>), the paper is well worth your time. It’s long – 40 pages, but there’s something new for everyone in there.</p>  <p>I highly recommend you make the time (even if it is sponsored by a competitor).</p>]]>
        
    </content>
</entry>
<entry>
    <title><![CDATA[The LogLogic Story &ndash; Chapter 5]]></title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/the_loglogic_story_chapter_5.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=830" title="The LogLogic Story &amp;ndash; Chapter 5" />
    <id>tag:blog.loglogic.com,2010://1.830</id>
    
    <published>2010-08-27T18:59:25Z</published>
    <updated>2010-08-27T18:59:45Z</updated>
    
    <summary>The difference is clear Our approach is different. Firstly, there’s no spaghetti! Ours is a simple world where all data,...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p><strong>The difference is clear</strong></p>  <p><a href="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter5_9A8A/Slide6.jpg"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="Slide6" border="0" alt="Slide6" src="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter5_9A8A/Slide6_thumb.jpg" width="420" height="316" /></a> </p>  <p>Our approach is different. Firstly, there’s no spaghetti! Ours is a simple world where all data, regardless of source or type, is centralized, augmented, enriched, parsed and understood, then smartly passed onto the appropriate visualization tools. We aim to create a virtual information pool that enables you to see 360 degrees of your operation; to provide you insight into the workings of your infrastructure. </p>  <p>Over on the left we have what we’re calling ‘Get.’ This is our Universal Collection Framework technology – our unique ability to capture audit trail information from almost any device, in almost any format and then securely and wisely move it to a central store, regardless of LAN or WAN complications. </p>  <p>In the center we have ‘See.’ This is our uniquely, massively scalable IT Data Warehouse, currently represented by our ST range of appliances. If you think of Google for a second you’ll understand why we call this ‘see.’ You know there are a million places on the web to book a flight. But rather than reach into the net and try each site directly, if you ask Google, it will do the search for you. It will display results directly. It will order them in terms of popularity and augment your view of those travel companies, giving you greater insight than you would have gotten if you’d visited all the sites directly yourself. Google enables you to see the raw information in a new way. That’s what we do. We enable you to see your IT data in new and insightful ways. </p>  <p>Over on the right we have the ‘Use’ column. Here we list all the visualization tools you may need. Some we make, others we expect you to source elsewhere. Regardless, they are all able to reach into the warehouse, without all the spaghetti, and be fed enriched, consistent information. </p>  <p>‘Get, See, Use.’ A simple solution to a very complex problem. We provide visibility, control, and improve security without adding all the complexity that others rely upon. There’s also an openness implied in this diagram. We offer an expansible framework, so if our ‘get’ doesn’t meet your exact needs, you can add something else. If our ‘see’ isn’t quite what you need, you can extend it. And if our ‘use’ is not a perfect match, you can use someone else’s. </p>  <p>When you go with our solutions you’ll also find that we pride ourselves in building technology that is simple to use and easy to deploy. </p>]]>
        
    </content>
</entry>
<entry>
    <title>Products of the week</title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/products_of_the_week.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=829" title="Products of the week" />
    <id>tag:blog.loglogic.com,2010://1.829</id>
    
    <published>2010-08-26T20:28:30Z</published>
    <updated>2010-08-26T20:29:29Z</updated>
    
    <summary>Hmmm, products of the week? Us? Again? Wow, people love the 5 thank you...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
            <category term="LogLogic News" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p>Hmmm, <a href="http://www.loglogic.com/5">products</a> of the <a href="http://www.networkworld.com/slideshows/2010/082310-products-of-the-week.html">week</a>? Us? Again? Wow, people love the 5</p>  <p>thank you</p>  <p><a href="http://www.networkworld.com/slideshows/2010/082310-products-of-the-week.html"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="image" border="0" alt="image" src="http://blog.loglogic.com/WindowsLiveWriter/Productsoftheweek_AF6D/image_3.png" width="359" height="323" /></a></p>]]>
        
    </content>
</entry>
<entry>
    <title><![CDATA[The LogLogic Story &ndash; Chapter 4]]></title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/the_loglogic_story_chapter_4.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=828" title="The LogLogic Story &amp;ndash; Chapter 4" />
    <id>tag:blog.loglogic.com,2010://1.828</id>
    
    <published>2010-08-26T16:11:49Z</published>
    <updated>2010-08-26T16:12:10Z</updated>
    
    <summary>Adding Complexity And that brings us to what I’ll call 1st generation solutions to your problem. On the left of...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p><strong>Adding Complexity</strong></p>  <p><a href="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter4_7345/Slide5.jpg"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="Slide5" border="0" alt="Slide5" src="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter4_7345/Slide5_thumb.jpg" width="444" height="334" /></a> </p>  <p>And that brings us to what I’ll call 1st generation solutions to your problem. </p>  <p>On the left of the slide you’ll see what I call “data assets.” These are your routers, firewalls, switches, servers, operating systems, databases, commercial and homegrown applications and pretty much anything with a plug. It’s a fact of life that almost all of the technology we use creates an audit trail. Some of those trails are called logs, others flow, sometimes they’re just file dumps. The point is, everything we do within the connected world leaves a trail. </p>  <p>Over on the right of the slide are the consumers of those trails. These are the analytics engines - the panes-of-glass from the previous slide. Hopefully, from the tangled spaghetti of colored lines you can see the problem here. We have one customer that has deployed 4 S.E.M. products from several vendors in their SOC. They also have other solutions, such as network monitoring tools. What this means to them is that they have servers with 4 agents on them – all doing the same thing! They get alerts that some S.E.M.’s corroborate, and others totally miss. They have no consistency, they can’t confirm that all the right information is getting to all the right places. And to make matters worse, they’re fearful of upgrading or switching out some of these solutions because the tendrils reach too deeply into the organization and no one knows quite how it’s all wired together. </p>  <p>What started off with the best intentions of adding clarity to a complex network of devices has simply made things worse. An alarm you can’t verify and trust is worse than useless – it becomes the car alarm that goes off in the middle of the night that everybody ignores. </p>]]>
        
    </content>
</entry>
<entry>
    <title><![CDATA[The LogLogic Story &ndash; Chapter 3]]></title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/the_loglogic_story_chapter_3.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=827" title="The LogLogic Story &amp;ndash; Chapter 3" />
    <id>tag:blog.loglogic.com,2010://1.827</id>
    
    <published>2010-08-24T21:57:35Z</published>
    <updated>2010-08-24T21:57:56Z</updated>
    
    <summary>The Standard Answer The good news for you is that, as an industry, we’ve recognized your needs and even given...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p><strong>The Standard Answer</strong></p>  <p><a href="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter3_C44C/Slide4.jpg"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="Slide4" border="0" alt="Slide4" src="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter3_C44C/Slide4_thumb.jpg" width="391" height="294" /></a> </p>  <p>The good news for you is that, as an industry, we’ve recognized your needs and even given them a name – S.I.E.M. or Security Information and Event Management. </p>  <p>S.I.E.M. is made up of two separate technologies - the first and most important is S.I.M., Security Information Management. This is the foundational work of <i>collecting</i> all tracking data - be it Logs, Flow, Assets, Users or Files - <i>consolidating</i> it, and then <i>turning</i> it into useful data. It is the S.I.M. technology that allows for the forensic searching and reporting we just discussed. It is this that you use for good IT management or compliance. We can even use it for simple alerting, such as someone failing to authenticate against a database. </p>  <p>The S.E.M. on the other hand is often referred to as the pane-of-glass or the analytics engine that consumes the collected data and presents it in a way that is meaningful to your needs; whether that’s event management for a SOC, or trending for capacity planning, or SLA management. Some of these visualization tools even provide dashboards that reflect your compliance posture. </p>  <p>The important part of S.I.E.M. is that for it to truly work efficiently and effectively, the pane-of-glass needs to be presented with ALL of the available data and not just a subset. </p>]]>
        
    </content>
</entry>
<entry>
    <title>Open Standards: Not everyone gets it</title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/open_standards_not_everyone_gets_it.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=826" title="Open Standards: Not everyone gets it" />
    <id>tag:blog.loglogic.com,2010://1.826</id>
    
    <published>2010-08-24T00:10:39Z</published>
    <updated>2010-08-24T15:22:52Z</updated>
    
    <summary>By Bill Roth, CMO In a recent article, our competitor LogRhythm commented on our technology plans which indicated either they...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="Innovation" />
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p><strong>By Bill Roth, CMO</strong></p>  <p>In a recent <a href="http://bit.ly/aBXt7n">article</a>, our competitor LogRhythm commented on our technology plans which indicated either they don’t understand what we’re doing, or that they think what we’re trying to do will threaten the status quo - and their business.</p>  <p>LogRhythm’s VP of Marketing said the following:</p>  <blockquote>   <p><i>“The idea of a standardized protocol for transporting and storing log data sounds good in theory, but it’s unrealistic given the hundreds of different types of log sources and vendors.</i> <i>A standard like this does more to benefit the vendor than it does the end customer, from both a technological and marketing standpoint,&quot; he added. &quot;Standardization would make it easier for the log management or SIEM vendor, but the positive impact on the end customer is hard to see given the widespread collection and transportation capabilities that exist today.&quot;</i></p> </blockquote>  <p>We think the exact opposite.</p>  <p>The Security Information and Event Management <a href="http://www.loglogic.com/siem">SIEM</a> industry needs more standardization not less. As markets mature, they all tend towards open standards. Open standards ensure that customers are free from being locked in to any one vendor, or any one proprietary technology. Additionally, standards provide a way for the consumers to provide input to the technology that they actually use. Standards also make sure there is a level playing field so no one vendor can dominate an industry. The open competition that standards encourage is good. They ensure that the consumers get the technology that they want at a reasonable price.</p>  <p>Consider the work done on CORBA standardization in the early ‘90s, and the standardization that continues to happen with the Java Platform. The Java Platform is an object lesson. Companies like IBM and Oracle were initially opposed to the standardization of Java on the server, in the form of J2EE, because they had large investments in their proprietary application server product lines. But as customers started clamoring for the kind of openness that standardization brings, both IBM and Oracle became licensees of the technology, as did nearly 50 other companies who signed on as licensees of the technology.</p>  <p>As Mark Twain said, “History doesn’t repeat itself, but it does rhyme.” Our path for the ULDP will not be an exact match to the J2EE experience. But we will take an open, community-based approach to developing our standard.</p>  <p>If only the rest of the industry would do the same.</p>  <p>LogRhythm and other competitors obviously benefit from having proprietary technology that essentially locks in their customers to a specific vendor. Take for example ArcSight’s putative “standard” Common Event Format, or <a href="http://www.arcsight.com/solutions/solutions-cef?utm_source=loglogic&amp;utm_medium=loglogic&amp;utm_campaign=loglogic">CEF</a>. While this looks like an open standard, in reality it is clearly copyrighted and there is no mention of a neutral standards body.</p>  <p>Clearly LogRhythm does not understand what we’re doing here, or does not want to understand. Standards necessarily create a level playing field among the vendors, and force those companies to compete on the features that matter to consumers: ease of use, scalability, and price.</p>  <p>The history of the last 30-years in the computer industry clearly illustrates the benefits of open standards. We believe that the creation of the ULDP will be a positive step forward for the SIEM industry and is something we’re excited to champion. And to share.</p>]]>
        
    </content>
</entry>
<entry>
    <title><![CDATA[The LogLogic Story &ndash; Chapter 2]]></title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/the_loglogic_story_chapter_2.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=825" title="The LogLogic Story &amp;ndash; Chapter 2" />
    <id>tag:blog.loglogic.com,2010://1.825</id>
    
    <published>2010-08-23T18:50:02Z</published>
    <updated>2010-08-23T18:50:22Z</updated>
    
    <summary>The need. Driving this desire for greater visibility, control and security is usually one of three things (there are of...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p><strong>The need.</strong> <p><a href="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter2_985A/Slide3.jpg"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="Slide3" border="0" alt="Slide3" src="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter2_985A/Slide3_thumb.jpg" width="391" height="294" /></a> Driving this desire for greater visibility, control and security is usually one of three things (there are of course other drivers, but these are the big three): compliance, security and the need to operate an efficient IT infrastructure. </p>  <p>Regardless of whether you’ve just failed an audit, or you’ve got one looming on the near horizon…or whether your firewall has just been kicked in, or you’re being paranoid because a “like” company has just been breached…or a critical system recently failed and it took you too long to recover - we always get asked for the same 3 things: alerting, searching and reporting. </p>  <p>People always ask us for the big red flashing light that screams something bad just happened. Our PCI data just made it out of the safe network. Warning! Our database just released data through a firewall port that it’s not used before. Warning! A router just went off-line and we’ve lost VPN access. Warning! Something bad has happened. Warning! </p>  <p>Of course, once the siren is silenced you need to get on with the very serious business of Crime Scene Investigation. You need to know: “How did the data get to the unsafe part of the network? Who did it? What else did they do?” You need to know: “Why did the database just send data outside the company? What else uses that port? When was the firewall last reconfigured? By whom?” You need to know: “Why did the router just stop working? Who was the last person to administer it? What was their reasoning?” </p>  <p>Once you’ve gathered your evidence, you need to document your findings – you need reporting. You need to be able to stand up in court and defend your compliance posture, to stand in front of HR or your CEO and defend your security best-practices, to stand in front of your LOB director and defend your operations. </p>  <p>That’s what we do. We give you the big flashing red light, we give you all the forensic searching tools you’ll ever need and we back it all with solid evidentiary reporting. </p>  <p>There are companies out there that specialize in each of these areas. They’ll tell you that once you have an alarm system, you don’t need the CSI stuff. Others will tell you that crime happens so you may as well let it get on with its thing and then have the best CSI team ready to pounce. Others still simply document everything that happens so that lawyers can later pour over the basic facts. </p>  <p>LogLogic believes you need three to be truly protected, to truly have total visibility and control. </p></p>]]>
        
    </content>
</entry>
<entry>
    <title><![CDATA[The LogLogic Story &ndash; Chapter 1]]></title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/the_loglogic_story_chapter_1.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=824" title="The LogLogic Story &amp;ndash; Chapter 1" />
    <id>tag:blog.loglogic.com,2010://1.824</id>
    
    <published>2010-08-20T23:27:27Z</published>
    <updated>2010-08-20T23:27:49Z</updated>
    
    <summary>I’m about to post the full LogLogic story, a short book in 12 chapters. Hopefully it will tell you who...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p>I’m about to post the full LogLogic story, a short book in 12 chapters. Hopefully it will tell you who we are, what we’re trying to do, and why we’re so very proud of LogLogic 5.</p>  <p><strong>The Problem</strong></p>  <p><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="Slide2" border="0" alt="Slide2" src="http://blog.loglogic.com/WindowsLiveWriter/TheLogLogicStoryChapter1_D961/Slide2_1.jpg" width="365" height="275" /> </p>  <p>The problems we’re trying to address are simple to define but harder to resolve, namely the lack of control, visibility and security in today’s IT shops. </p>  <p>These issues manifest themselves in many ways that we’ll discuss, but they all arise from a basic fact of life – IT is complex. You have lots of apps, databases, servers, routers, firewalls, and just ‘stuff’ to manage. Pretty much anything with a plug these days falls under the realm of the IT department. And of course, it’s all inter-connected. It’s wired together in a way that is difficult to unravel. This complexity means that it’s hard for you to react quickly to security breaches or new compliance demands. It’s hard for you to adapt your system to changes within your organizations, such as mergers or departmental re-structuring. And with complexity come the ever present issues of management – or the lack of it. If I were to try and generically sum up the problems people describe to me, it’s that IT has a lack of visibility and control over the systems that are running the very core of your enterprises. And then of course, there’s security. There’s always the security problem. </p>]]>
        
    </content>
</entry>
<entry>
    <title>LogLogic 5.0: And it keeps on getting better.</title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/loglogic_50_and_it_keeps_on_getting_better.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=823" title="LogLogic 5.0: And it keeps on getting better." />
    <id>tag:blog.loglogic.com,2010://1.823</id>
    
    <published>2010-08-18T23:17:22Z</published>
    <updated>2010-08-18T23:27:38Z</updated>
    
    <summary>By Dimitri McKay LogLogic 5 has been years in the making and I’ve been privileged to play with, kick at...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="Dimitri" />
            <category term="Innovation" />
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p>By Dimitri McKay</p>  <p><a href="http://www.loglogic.com/5">LogLogic 5</a> has been years in the making and I’ve been privileged to play with, kick at and test numerous iterations of it since its inception.</p>  <p>The task of building 5 began with a complete back-end overhaul, as we built out the industry’s most scalable IT data platform. This may sound easy, but being able to get massive amounts of data, and clearly see (or translate from machine bleeps to human linguistics) that data, and then use this haystack of facts, is a lot more difficult than you might think. Bringing in upwards of 150,000 MPS, indexing, parsing, enriching, and then using this new insight to search, report and alert in real-time is a massive undertaking. Especially when you scale this across an infinite number of appliances. Map Reduce technology is clever, but speaking to, working with and rendering reports, alerts and searches across a vast array of hardware still takes effort. Remember, we have customers that regularly generate more than 50 billion IT events each day, and they rely on us to interpret that in real time and make it meaningful to them.</p>  <p>That said, I’m going to ignore the back-end and present my top 3 list of front-end features new in 5. I think you will agree they demonstrate a <a href="http://www.loglogic.com/news/news-releases/2010/august/loglogic-introduces-loglogic-5-solution-comprehensive-it-data-managem">huge leap forward</a> in logging and IT data management technology.</p> <DL> <DT><B>1) The Sex</b></DT>    <dd>First up, the GUI - time for more sex appeal. The LogLogic GUI was of particular interest to me, as frankly it hadn’t changed since version 1.0. Sure we’d done some minor updates (added to the sidebar, reorganized some stuff), and to those with experience, it all made sense - there was method to our madness and reviewers regularly gave us 5 stars for “really cutting to the heart of things.” But for those stepping in for the first time, well, we needed to show you a little more TLC. We’ve known this for some time, but for the front-end that we had in mind, we first required that back-end work I talked about. Sure we could have just put lipstick on our stuff, but that’s a tactic we’ll leave to others.</dd>    <dd>The <a href="http://www.loglogic.com/5/faq">LogLogic 5</a> GUI has been completely redesigned with you in mind: consolidation, use cases, intuition - we threw the kitchen sink at it. To achieve our goal we brought in a group of UI designers who’ve built many of the interfaces you and I use every day in common products. These guys are experts. They spent months interviewing customers, identifying top use cases, understanding not only what our product did, but how people use it. And with that, they designed a UI that was not only a user interface, but a workflow engine. And they did so without adding dozens of annoying pop up windows (something else we’ll leave to others). What we now have is indisputably the best forensics workflow solution available. Anywhere.</dd>  <dt><B>2) The Insight</b></dt>    <dd>Second on my list of awesomeness is the new Log Labels feature. Like the interface story above requiring a better back-end, the story of Log Labels is in two parts. </dd>    <dd>Several years ago we invented the index search for log data. And it was hugely successful. So much so that at least one other vendor in the log management space went and built an entire business out of it. Ours was fast. It was mean. And just like everybody else’s it was dumb. It didn’t understand the data it was indexing. It just indexed as much as possible for ultra fast search. And as a slick search tool, it certainly got the job done. So now for part two, where for the second time, we re-invent IT data searching.</dd>    <dd>For awhile now, customers have been asking for a way to create custom parsers, but we stepped back and asked “is it parsers that you really want, or are you trying to add business intelligence to your existing logs?” And as it turns out, that was THE question. Enter Log Labels. Here is a feature that gives our customers the capability they’ve been asking for, without requiring a BSc in Development (something else we’ll leave to the competition). What we’ve created is a way for businesses to interpret their own IT data in a way that makes sense from their unique view point. We know other vendors describe possible solutions to this problem as “very complicated” or even worse, “solvable with professional services” (code for “very expensive with no guaranteed outcome”). So we went the other way. As my father always said, “K.I.S.S” - keep it simple, stupid. And we did just that. We KISSed our Log Labels feature. It’s the next step in evolution from indexing. It adds intelligence to unstructured data. It’s GUI-based. It’s simple to use. It does not require 6 months of professional services. And it’s built into 5 for free. Everyone say Yay! </dd>  <dt><b>3) The Time Saver</b></dt>    <dd>Lastly, I’m psyched about Policy Based Grouping. I know it seems like just a little thing, but when you actually start to peel it back, it makes perfect sense for our target market (think really really big players). Let me give you a few examples.</dd>    <dd>PCI Compliance: customers who have to adhere to PCI often segregate their networks and apply the PCI controls only to that specific subnet, which makes perfect sense. But what if you’re logging your entire network, but only want to see specific reports, alerts or searches from a specific subnet? Well, LogLogic can create a dynamic group that will add devices to that specific group as they come online. This automation cuts down administration for our customers tenfold. </dd>    <dd>Another example? You want to see all firewalls worldwide, but those firewalls are from a handful of different vendors. However, the naming convention all matches a specific standard. You can now create a dynamic group to add all devices with that naming convention worldwide. One shot deal. Job done.</dd> </DL> <p>So to all of our customers, you’ll get <a href="http://www.loglogic.com/5/faq">LogLogic 5</a> with your current support agreement. No extra charge. No additional cost. No reason to wipe your machine for a clean install. Easy-peasy. </p>  <p>For those who want to see how to consolidate your IT data, get visibility into, and act on events from all of your network devices, operating systems, custom applications, and more...<a href="http://www.loglogic.com/5#signup">sign up</a> to receive detailed information. We’ll show you how it gets done. The right way.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Why 360 Insight?</title>
    <link rel="alternate" type="text/html" href="http://blog.loglogic.com/2010/08/why_360_insight.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.loglogic.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=822" title="Why 360 Insight?" />
    <id>tag:blog.loglogic.com,2010://1.822</id>
    
    <published>2010-08-17T23:49:18Z</published>
    <updated>2010-08-17T23:49:39Z</updated>
    
    <summary>By Guy Churchward With the imminent release of LogLogic 5, our clients can now have true 360 degree Insight of...</summary>
    <author>
        <name>Andy Morris</name>
        <uri>http://loglogic.com</uri>
    </author>
            <category term="Guy" />
            <category term="LogEd" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.loglogic.com/">
        <![CDATA[<p>By Guy Churchward</p>  <p>With the imminent release of LogLogic 5, our clients can now have true 360 degree Insight of IT data. We’ve always hung our hat on the ability to deliver visibility into the inner workings of an IT environment for security purposes; however, what we’re repeatedly asked is ‘how can you get alerted on something you don’t collect. Obviously this is fraught with complexity, but it plays very well into the formation of a massively scalable IT data warehouse and an essential architectural consideration to deliver peace of mind in the opaque and volatile world of virtualized cloud services. </p>  <p>The baseline deployments for data collection lead to sticking agents on all the sources you think will be relevant, and manually stitching them directly to a GUI - whether a change monitoring product, compliance suite, SEM or forensics tool. </p>  <p>Most companies have a SOC, a few SME’s and a handful of other monitoring application that require their own form of collection. What then transpires is a bloat of agents on the source with lots of end-points to update, and unexpected bills - sometime’s vendors even charge you for customization work! Then there is the ‘WAY TOO MUCH’ network chatter, with a handful of solution providers having their sticky tendrils laced across your network making what should be a simple GUI change feel more like an architectural lobotomy. </p>  <p>Metaphorically, this is like viewing the ocean through a small window - you know what you can see but it’s a subset of what is there, and you have no ability to expand your field of vision as the tool is designed for what it does and ONLY that.</p>  <p><a href="http://blog.loglogic.com/WindowsLiveWriter/Why360Insight_DE79/image_2.png"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="image" border="0" alt="image" src="http://blog.loglogic.com/WindowsLiveWriter/Why360Insight_DE79/image_thumb.png" width="240" height="220" /></a> </p>  <p>LogLogic 5 accentuates the ability to abstract IT data- or dare I say, create a virtual data information pool - that can be tapped into from any GUI regardless of the use or user requirements. So, regardless of your specific chosen window of information and initial design principle, you now have the ability and flexibility to adjust on the fly and retrofit data sets that might not necessarily have been in your initial scope. For instance, perhaps you’re collecting data for compliance purposes; perhaps you underestimated the breadth of data needed, your initial posture is limited, and your new QSA is a little more demanding than your last. Now it’s just a simple task of encapsulating a larger normalized data set rather than scrambling to protect your company from being written up for non compliance. </p>  <p>Perhaps you run a SOC, and have a some extensive correlation algorithms ticking along but find a ‘like’ company just suffered a breach in a source area you’re not monitoring; so encompass, track back and remediate as you’ve been collected that data all along.</p>  <p>This ability to collect, normalize and store IT data opens up a wealth of use cases that aren’t immediately obvious but substantially enhances both the ROI and TCO of your initial investment. Knowledge is power and you have facilitated a goldmine of information and a key company asset.</p>  <p><a href="http://blog.loglogic.com/WindowsLiveWriter/Why360Insight_DE79/image_4.png"><img style="border-bottom: 0px; border-left: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px" title="image" border="0" alt="image" src="http://blog.loglogic.com/WindowsLiveWriter/Why360Insight_DE79/image_thumb_1.png" width="454" height="337" /></a> </p>  <p>By no means have we completed the journey but the technological advancement with LogLogic 5 such as UCF, ULDP, &amp; Log Labels, we’ve set our high watermark even higher. Our moniker is Get-See-Use, if you don’t get it and don’t have the ability to see it, there’s little point in having a flashy dashboard displaying a square foot of ocean floor! </p>]]>
        
    </content>
</entry>

</feed> 

